Received header & RDNS

sl-jasonr
Posts: 20
Joined: Thu Feb 15, 2018 7:22 pm

Received header & RDNS

Postby sl-jasonr » Fri Apr 27, 2018 6:54 pm

MailEnable Enterprise v10.15

When MailEnable receives a message and appends it's Received: header, it fails to write the PTR value.

For example, MailEnable writes the following:

Code: Select all

Received: from NAM03-BY2-obe.outbound.protection.outlook.com ([104.47.42.44]) by cloudsector.net with MailEnable ESMTPS; Mon, 23 Apr 2018 07:23:16 -0400


It should look like this instead:

Code: Select all

Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0044.outbound.protection.outlook.com [104.47.42.44]) by cloudsector.net with MailEnable ESMTPS; Mon, 23 Apr 2018 07:23:16 -0400


This causes Spamassassin to flag RDNS_NONE, which adds 0.8 to the message spam score.

MailEnable-Ian
Site Admin
Posts: 8883
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Received header & RDNS

Postby MailEnable-Ian » Sun Apr 29, 2018 11:28 pm

Hi,

Please review the following article: https://www.mailenable.com/kb/content/article.asp?ID=ME020640
Regards,

Ian Margarone
MailEnable Support

sl-jasonr
Posts: 20
Joined: Thu Feb 15, 2018 7:22 pm

Re: Received header & RDNS

Postby sl-jasonr » Wed May 02, 2018 8:02 pm

Yeeeeesssss, I could do that, but it ultimately makes Spamassassin less effective. Since MailEnable is already aware of the problem (since at least May 4, 2016), I guess the operative question is, "is fixing this in MailEnable's roadmap?"

227ths
Posts: 6
Joined: Wed May 02, 2018 9:14 pm

Re: Received header & RDNS

Postby 227ths » Wed May 15, 2019 10:40 pm

Wow no reply. Agree. That's not a "resolution" per article but a weak work-around. I found that much via google and other pages. I hope this gets fixed.

Who is online

Users browsing this forum: No registered users and 5 guests