IspConfig With Sendgrid smtp relay

Some cloud providers do not enable SMTP sending permission, Amazon forces you to use SES, in DigitalOcean to use Sendgrid. In my case you can make it work with sendgrid
Postfix: main.cf add

smtp_sasl_auth_enable = yes
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_sasl_tls_security_options = noanonymous
smtp_tls_security_level = encrypt
header_size_limit = 4096000
relayhost = [smtp.sendgrid.net]:587

Ref: API KEY https://docs.sendgrid.com/for-developers/sending-email/postfix

Once the account has been verified with sendgrid and testing sending the message through the console. We proceed to configure roundube to use TLS on port 587

/etc/roundcube/config.inc.php

$config['smtp_server'] = 'tls://%h'; #edit for tls
$config['smtp_port'] = 587;
$config['smtp_user'] = '%u';
$config['smtp_pass'] = '%p';

#NEW ADD:
$config['smtp_auth_type'] = 'LOGIN';
$config['smtp_conn_options'] = [
'ssl' => [
'verify_peer' => true,
'verify_depth' => 3,
'peer_name' => 'cpanel.isp.link',
'cafile' => '/etc/ssl/certs/ca-certificates.crt'
],
];

With the above, I started sending email through Rouncube. For mobile SMTP there are no modifications, it works the same.
Remember that when registering your domain and account in Sendgrid, you will be required to create CNAMEs in DNS in order to function properly.

For SES (AWS) It's similar. very similar.


Debian 12
IspConfig 3.2.11