On Thu, 3 Nov 2011 06:59:14 -0700 (PDT)
Schorny wrote:
>
>
> Kelson Vibber-2 wrote:
> >
> > A matter of perspective: You don't need to tell SA to ignore the
> > last header, you need to tell it NOT to ignore the second one.
> > Generally speaking, SA checks blacklists against the first hop
> >
On 03.11.11 06:59, Schorny wrote:
@Darxus:
The following rules are hitting:
RCVD_IN_CBL, RCVD_IN_SBL_XBL, RCVD_IN_SORBS
Which are IIRC all Spamlists we are checking.
the RCVD_IN_CBL and RCVD_IN_SBL_XBL seem to be out of date.
Which version of spamasssassin and rules do you use?
--
Matus UHLAR -
On 11/3/2011 9:59 AM, Schorny wrote:
>
> Kelson Vibber-2 wrote:
>> A matter of perspective: You don't need to tell SA to ignore the last
>> header, you need to tell it NOT to ignore the second one. Generally
>> speaking, SA checks blacklists against the first hop outside your internal
>> network.
Kelson Vibber-2 wrote:
>
> A matter of perspective: You don't need to tell SA to ignore the last
> header, you need to tell it NOT to ignore the second one. Generally
> speaking, SA checks blacklists against the first hop outside your internal
> network. It sounds like your local SA has decide
On Wed, 2 Nov 2011 07:23:46 -0700 (PDT), Schorny wrote:
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...).
trusted_networks 10.0.
> -Original Message-
> >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...).
A matter of perspective: You don't need to tel
> The IP Addresses 1.2.3.4 and 10.20.30.40 are changed by me to protect the
> innocent ;)
> The real IP Addresses are of course not internal.
> 1.2.3.4 and 10.20.30.40 are really 80.*.*.*
yeah, I thought that 1.2.3.4 was the only changed. Private numbers can
appear in mail clients when they are in
On 11/02, Schorny wrote:
> The IP Addresses 1.2.3.4 and 10.20.30.40 are changed by me to protect the
> innocent ;)
> The real IP Addresses are of course not internal.
> 1.2.3.4 and 10.20.30.40 are really 80.*.*.*
What rule is it hitting?
--
"Force, my friends, is violence; the supreme authority
Hi Guys.
The IP Addresses 1.2.3.4 and 10.20.30.40 are changed by me to protect the
innocent ;)
The real IP Addresses are of course not internal.
1.2.3.4 and 10.20.30.40 are really 80.*.*.*
I don't know why 10.20.30.40 (the user's IP) even appears in the Mail Header
because there runs no Mailserv
ahh, i did not see he touched de IPs :p
2011/11/2 RW :
> On Wed, 2 Nov 2011 12:11:27 -0300
> Christian Grunfeld wrote:
>
>> 10.x.x.x /8 is private by RFC 1918 and shoud not be used to check the
>> legitimacy of a sender
>
> I don't think you can infer much from the addresses 1.2.3.4 and
> 10.20.30
On Wed, 2 Nov 2011 12:11:27 -0300
Christian Grunfeld wrote:
> 10.x.x.x /8 is private by RFC 1918 and shoud not be used to check the
> legitimacy of a sender
I don't think you can infer much from the addresses 1.2.3.4 and
10.20.30.40.
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 :
>
> 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
On 02.11.11 07:23, Schorny wrote:
Received: from myhost.com ([127.0.0.1])
by localhost (spamfilter.local [127.0.0.1]) (...)
with ESMTP id 59NKvpZmxmUc for ;
Tue, 1 Nov 2011 22:30:34 +0100 (CET)
Received: from mailserver.provider.com (mailserver.provider.com [1.2.3.4])
On Wed, 2011-11-02 at 07:23 -0700, Schorny wrote:
> 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...
>
You mean its an open relay? If so then IMO its blacklisting is entirely
deserved. Tell your correspon
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]) (...
15 matches
Mail list logo
