Jank1887 Posted April 29, 2015 Share Posted April 29, 2015 Tracking URL: https://www.spamcop.net/sc?id=z6106757373z395bb5769d3ea4684a4cc5d1039aabf7z thought it was odd when it suggested the source was 11.0.1.3 and wanted to direct the report to mail.mil. Not that that would be impossible, but looking at the header line Received: from mail6.bemta7.messagelabs.com by mail.asme.org (IceWarp 11.0.1.3 x64) with ESMTP id 201504290744006092 for <x>; Wed, 29 Apr 2015 07:44:00 -0400 I googled and apparently IceWarp is a server software and 11.0.1.3 is the version number. So, not sure if the problem is on the mailserver side (is that received line RFC compliant?) or on the parser side, but 11.0.1.3 is not part of the chain. Cancelled the report, but thought I'd post this in case it comes up again or can be fixed. Link to comment Share on other sites More sharing options...
Lking Posted April 29, 2015 Share Posted April 29, 2015 Yes that does look odd. Hopefully someone from SpamCop will stop by and see the problem so a fix can be addressed. Link to comment Share on other sites More sharing options...
Farelf Posted April 29, 2015 Share Posted April 29, 2015 Agree - and no, that "Received:" line doesn't look compliant - it should include IP address 216.82.255.55 for mail6.bemta7.messagelabs.com. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.