Closed schlos closed 3 years ago
Everything points to a Sendgrid as one of best options: https://docs.microsoft.com/en-us/azure/sendgrid-dotnet-how-to-send-email ... but then Sendgrid is same as Cuttlefish we have now.
Should be resolved via these tickets:
Expected Behavior
Postfix should send emails nominally to get delivery email statuses from Postfix. Remove Cuttlefish relaying (delivery status is not feed back into IPZ).
Current Behavior
Postfix is relaying emails via Cuttlefish, no real email delivery statuses.
Possible Solution
Recommended method of sending email We recommend you use authenticated SMTP relay services (that typically connect through TCP port 587 or 443 but support other ports, too) to send email from Azure VMs or from Azure App Services. These services are used to maintain IP or domain reputation to minimize the possibility that third-party email providers will reject the message. Such SMTP relay services include but aren't limited to SendGrid. It's also possible you have a secure SMTP relay service that's running on-premises that you can use. (source)
Steps to Reproduce (for bugs)
1. 2. 3. 4.
Context
Reason for this being is because Postfix sends emails via port 25, and Azure is blocking this port (source).
It seems Postfix sending is hard to configure on Azure VM: https://stackoverflow.com/questions/56019983/how-i-can-configure-postfix-to-send-email-from-azure-cloud https://serverfault.com/questions/478076/can-an-email-server-be-set-up-on-an-azure-vm
Your Environment