I have a couple users who have valid emails coming from clients that are
being outright rejected by my server. One of them is using outlook.com
(Microsoft web email) to send the email that is being rejected.

The problem is that there are invalid IPs in the header starting with
"0." and ASSP is picking these up. For instance:

Received: from CY1PR0201CA0020.namprd02.prod.outlook.com
(*0.163.30.158*) by BLUPR02MB1218.namprd02.prod.outlook.com
(*0.163.80.148*) with Microsoft SMTP Server (TLS) id 15.1.136.25; Mon,
20 Apr 2015 19:17:21 +0000
Received: from BN1BFFO11FD039.protection.gbl (2a01:111:f400:7c10::1:124)
by CY1PR0201CA0020.outlook.office365.com (2a01:111:e400:58b9::30) with
Microsoft SMTP Server (TLS) id 15.1.136.25 via Frontend Transport; Mon,
20 Apr 2015 19:17:21 +0000

I have 0.0.0.0/8 as a bogon in my denySMTPConnectionsFromAlways file, as
it is a nonrouteable address. However, ASSP finds these invalid IP's in
the routing:

detected IP's on the mail routing way: 24.125.165.15, 25.165.165.15,
*0.163.30.158, 0.163.80.148

*and as a result, marks the message as spam:

[spam found] ((OIP: 0.163.30.158) blocked by
denySMTPConnectionsFromAlways strict '0.0.0.0/8') [subject here] ->
D:/ASSP/spam/6589.eml;

Is this something new from Microsoft? Is anyone else experiencing this?
I hate to remove 0.0.0.0/8 from my deny list, or to stop ASSP from
scanning the IP addresses in headers, as both are good ways of catching
and killing spam.

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to