Emails blocked by providers

Hi,

I’ve had a lot of problems trying to register for this website. I’ve never received a single registration email for a lot of different usernames, each one with a different email address and account configuration.

I ultimately succeeded and (together with my hosting company) found out, what the issue was:

exim: 2019-03-26 09:41:13 H=opensuse1.lndyn.com [170.75.162.59] rejected MAIL <noreply@budgetlightforum.com>: REJECT:No-MX sender callout required but failed (ID:550:0:5)

The Budgetlightforum.com mailserver doesn’t have a defined MX record (which defines which servers emails are routed to). This isn’t standard, and it’s often found in association with Spam mails. So many email providers (including mine) flat out reject any mails from such a server.

So all these BLF emails didn’t even make it to a Spam folder (which I checked, multiple times), but they were blocked even before that.

I didn’t find any postings regarding MX records here, so I’m not sure if this is a known issue.

Most of us did it the old fashion way….50 bucks in a plain white envelop. :confounded:

Never had this problem with gmail or hotmail.

Hi SirAndySchneider, I appreciate you letting me know. That’s an interesting explanation for why some providers reject emails from BLF; I had assumed that an MX record wasn’t needed because I don’t receive emails here, i.e. I don’t have an @budgetlightforum.com email inbox. At any rate I just added an MX record. Could you please try again after an hour or so (to make sure your provider gets the updated DNS records) and let me know? Thanks!

Nothing yet… I hope I’ll be able to try a few things tomorrow, and I’ll contact my provider again with the information that you’ve updated your MX record. I’ll post any updates.

Thanks, I appreciate it!

I’m happy to report that I now have no problems receiving emails from BLF. :slight_smile: It works!

Nice!!! Thanks for reporting back, and thanks for helping to identify the source of the problem. That took a lot of effort on your part to communicate with your provider and obtain the exact error message they were generating. :+1: