Conversation

Notices

1. Embed this notice
   ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Thursday, 02-Oct-2025 08:02:04 JST ✧✦Catherine✦✧

   in reply to

   • Bitslingers-R-Us
   • bert hubert 🇺🇦🇪🇺🇺🇦

   @AnachronistJohn @bert_hubert hah, looks like my primary rejected Bert's email but the secondary delivered it after all; I never thought of this before so thank you for the insight!

   • Embed this notice
     Bitslingers-R-Us (anachronistjohn@zia.io)'s status on Thursday, 02-Oct-2025 08:02:08 JST Bitslingers-R-Us

     in reply to

     • bert hubert 🇺🇦🇪🇺🇺🇦
     @bert_hubert @whitequark I never thought that there should be a requirement for HELO / EHLO to match reverse DNS, although it's nice and should be done, if possible.
     
     OTOH, one of my checks on my non-primary MX is to block all email coming from IP addresses that have reverse DNS PTRs that either don't resolve or that don't resolve back to the corresponding IP.
     
     I'm much more ready to block on non-primary MX because spammers still try to deliver to them even when there's no issue connecting to the primary MX.
     
     So your HELO / EHLO isn't what you'd prefer, but I take it at least it resolves back to the IP address the connection is from?
   • Embed this notice
     bert hubert 🇺🇦🇪🇺🇺🇦 (bert_hubert@eupolicy.social)'s status on Thursday, 02-Oct-2025 08:02:09 JST bert hubert 🇺🇦🇪🇺🇺🇦

     • Bitslingers-R-Us

     @AnachronistJohn @whitequark I send out 100k legit email messages/month or so, an they arrive at all major email players. I do not control the reverse DNS of my IP address, and other people who make rules force me to have my reverse and my HELO hostname to match.