Configure the SMTP dependency for Delivery Note email

Use the core CRM’s approved outbound-email configuration because the module has no separate mail settings.

What this guide covers

Use the core CRM’s approved outbound-email configuration because the module has no separate mail settings. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Exact step-by-step process

1. Configure the CRM’s sender address and company identity.
2. When using SMTP, enter the approved host, port, username, encrypted password and encryption mode.
3. Send the CRM’s normal test email.
4. Create a controlled Delivery Note with a test Recipient Email.
5. Verify dispatch and signed-confirmation messages.

Fields, choices and supported possibilities

• email_protocol
• smtp_host
• smtp_port
• smtp_email
• smtp_password
• smtp_encryption
• companyname

Code-backed validations and workflow rules

• The module decrypts the stored SMTP password through the CRM encryption library when possible.
• If decryption returns no value, it falls back to the stored value.
• When SMTP is not selected, the module initialises the email library for HTML fallback delivery.
• The module does not change server mail or TLS configuration.

Expected result and verification

• Delivery Note messages use the same authorised outbound-email infrastructure as the CRM.

Checks, security and troubleshooting

• Never place plaintext SMTP credentials in documentation, screenshots or module source.

Related Delivery Note guides