Outbound Mail not processing through my selected SMTP server - email address changed to mail.baserow.io address

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

Using the app builder, create a form with basic email fields (to, from, subject, body). On the event tab for the form’s submit button, add action to send email. If you don’t have SMTP integration, create one with valid access to an SMTP server that you are authorized to send email on. I use MailJet and have authorized my entire domain, so I can send from any@mydomain.com. Use the integration for the send email action. Connect the From, To, Subject and Body fields. Publish and launch the page. Enter a from address that your smtp server will accept, to: = your emaIl addresss, subject and body don’t matter. Submit the form. Assuming there are no errors and the emaIl sent, check your email account for the email. Look at the headers (sometimes listed as "Show Original).

The from address will be email=domain.com@mail.baserow.io. This is causing my email to not reach many users and to bounce, or to go to spam. Some email providers reject outright since mail.baserow.io has no DNS.

Attach screenshots, videos, or logs that demonstrate the issue.

Test 1 Email Header - rename to txt or eml.patch (4.01 KB)Test 2 Email Header - rename to txt or eml.patch (4.05 KB)Delivery Status Notification (Failure) - rename to txt or eml.patch (13.9 KB)

All of the email functionality I have built into the app is now unreliable and practically unusable. Why was this changed? If we have our own SMTP server that we select, why would it be changing the address and using baserow? Specifically mail.baserow.io - which doesn’t have a valid DNS address, so many mail servers reject it if they do a reverse dns lookup.

Hey @danielgoad, thanks for reporting this.

You’re right — something is wrong with the “from” email being rewritten. This is clearly not intentional and is a side effect of a recent change made to improve the feature. A fix is in progress and should be released very soon.

Sorry for the inconvenience in the meantime.

Hey @danielgoad we released the fix. Could you try again?

It is working! Thanks for a rapid fix!! You guys rock!!

2 Likes