On Friday 01 September 2006 13:41, decoder took the opportunity to say:
> So adding the line
>
> trusted_networks 134.96.254.200
>
> to local.cf will fix this problem and this mail would be recognized
> correctly (as in pass SPF) ?
If 134.96.254.200 is the MX for your domain, then it should even b
On Friday 01 September 2006 16:14, Ramprasad took the opportunity to say:
> > This is no real forwarding, but all mail for us gets received by that
> > server first, and this server passes it to us. This is a common
> > structure for a bigger mail setup. The trusted_networks option solved
> > my pr
decoder wrote:
The trusted_networks option solved my problems, but it should
definetly be included in the wiki somewhere.
How about this page:
http://wiki.apache.org/spamassassin/TrustPath
The common symptoms of a broken Trust path include:
* ALL_TRUSTED matching spam email from the outside
At 05:54 01-09-2006, decoder wrote:
This is no real forwarding, but all mail for us gets received by that
server first, and this server passes it to us. This is a common
structure for a bigger mail setup. The trusted_networks option solved
my problems, but it should definetly be included in the w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ramprasad wrote:
Return-Path: <[EMAIL PROTECTED]> Received: from
mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) by
wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP
id k7T8rU6P012050; Tue, 29 Aug 2006 10:53:30 +02
Ramprasad writes:
> > >> Return-Path: <[EMAIL PROTECTED]>
> > >> Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200])
> > >> by wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP id
> > >> k7T8rU6P012050;
> > >> Tue, 29 Aug 2006 10:53:30 +0200
> > >> Received: fr
> >>
> >> Return-Path: <[EMAIL PROTECTED]>
> >> Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200])
> >> by wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP id
> >> k7T8rU6P012050;
> >> Tue, 29 Aug 2006 10:53:30 +0200
> >> Received: from mail-eur1.microsoft.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gino Cerullo wrote:
> On 1-Sep-06, at 7:18 AM, decoder wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello,
>>
>> today I saw a strange SPF bug occuring. The original mail header was:
>>
>> Return-Path: <[EMAIL PROTECTED]>
>> Recei
On 1-Sep-06, at 7:18 AM, decoder wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
today I saw a strange SPF bug occuring. The original mail header was:
Return-Path: <[EMAIL PROTECTED]>
Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200])
by wjpserver.cs.uni-sb.
give it a try, anyway ;)
you can see what SpamAssassin thinks of the relays in the message,
using "spamassassin -D -L -t < message" and reading the debug
lines output.
more info: http://wiki.apache.org/spamassassin/TrustPath
http://wiki.apache.org/spamassassin/TrustedRelays
--j.
de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So adding the line
trusted_networks 134.96.254.200
to local.cf will fix this problem and this mail would be recognized
correctly (as in pass SPF) ?
Thanks
Chris
Justin Mason wrote:
> it's trusted_networks -- SpamAssassin doesn't know that it can
it's trusted_networks -- SpamAssassin doesn't know that it can
trust mail.cs.uni-sb.de.
--j.
decoder writes:
> today I saw a strange SPF bug occuring. The original mail header was:
>
> Return-Path: <[EMAIL PROTECTED]>
> Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200])
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
today I saw a strange SPF bug occuring. The original mail header was:
Return-Path: <[EMAIL PROTECTED]>
Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200])
by wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP id
13 matches
Mail list logo
