10.x.x.x /8 is private by RFC 1918 and shoud not be used to check the legitimacy of a sender
2011/11/2 Schorny <a9831...@nepwk.com>: > > Hello Guys. > > I have the following problem: > A User sends an Email to my Spamassasin System and gets flagged as Spam. > The Email contains multiple received: headers > > (IPs and Hostnames are changed by me) > > Received: from myhost.com ([127.0.0.1]) > by localhost (spamfilter.local [127.0.0.1]) (...) > with ESMTP id 59NKvpZmxmUc for <u...@myhost.com>; > Tue, 1 Nov 2011 22:30:34 +0100 (CET) > Received: from mailserver.provider.com (mailserver.provider.com [1.2.3.4]) > by myhost.com (Postfix) with ESMTP id E36B31A4B633 > for <u...@myhost.com>; Tue, 1 Nov 2011 22:30:33 +0100 (CET) > Received: from user.local (10-20-30-40.adsl.highway.telekom.at > [10.20.30.40]) > by mailserver.provider.com (Postfix) with ESMTPA id B156729504E6 > for <u...@myhost.com>; Tue, 1 Nov 2011 22:30:31 +0100 (CET) > > The Problem is, that the Users dynamic IP (10.20.30.40) is blacklisted by > various Spamlists. It's a dynamic IP, so can be used by everyone... Now my > Spamassasin thinks, that this EMail was sent from a blacklisted IP, which > isn't really true. The Mailserver who sent the mail was > mailserver.provider.com (which of course is not blacklisted). > > How do I tell Spamassasin to ignore the last received Header? Or are there > other solutions to this problem? It also happens quite often with emails > from cell phones (which always get the strangest dynamic IPs...). > > Thanks! > -- > View this message in context: > http://old.nabble.com/How-to-ignore-multiple-Received%3A-headers-tp32766061p32766061.html > Sent from the SpamAssassin - Users mailing list archive at Nabble.com. > >
