I’m developing a service (saas) that will include sending email (notification, reminders and so on) im working on a ubuntu 20.04 droplet with a generic domain (myservice.com)
on the same droplet there are the frontend service (domain may vary depending on the user), every frontend can be configured by the owner, it includes the owner email that will be used to communicate with their customer.
The frontend (for example fe.user1.com or fe.user2.com) will send emails using the api located at api.myservice.com, passing too the api the from, the to the content and so on.
it worked for a while but (since there are many frontends sending many email from different address) the ip address of the droplet has been listed on spamhaus and the service can no longer send email (which is a big problem, considering that emails are a core part of my service)
spamhaus ask to setup a HELO/EHLO DNS forward (but i have no idea on how to do it)
how can i setup a reliable way to allow email not to be blocked? considering that i have no control on the email address the user configure to send email?
how can i configure the HELO/EHLO DNS as requested by spamhaus?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
This is a part of services that use similar technologies. When you have no control over e-mails being sent, there might be spam or messages that are considered as spam due to that.
You need to create a way to track what and how many e-mails are being sent.
As for SpamHaus, you need to configure an FQDN on your server you can add DKIM, DMARC, and SPF records.