-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi, I'm subscribed to many mailing lists, but I've been getting lots of SPF
517s, such as this:
/var/log/mail/log-2008-03-18-16:03:46:Mar 18 11:22:10 [courieresmtpd]
error,relay=209.132.176.174,from=<[EMAIL PROTECTED]>: 517 SPF
softfail [EMAIL PROT
n" <[EMAIL PROTECTED]>
To: "courier-users"
Sent: Wednesday, March 19, 2008 5:14 AM
Subject: [courier-users] Is my SPF setting incorrect?
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi, I'm subscribed to many mailing lists, but I've been getting lots
nt list software in each case, I did not collect
any descriptions of the list settings required.
- Original Message -
From: "Leigh S. Jones, KR6X" <[EMAIL PROTECTED]>
To: "courier-users"
Sent: Wednesday, March 19, 2008 5:46 AM
Subject: Re: [courier-users] Is my SP
Leigh S. Jones, KR6X ha scritto:
> Thus, the message comes to you ostensibly from the sender, but the
> IP address that the message is received from is that of the list relay.
> Thus it appears to the Courier SPF-checking mechanism that the
> sender has been "aliased" by a spammer.
Since you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alessandro Vesely wrote:
| IMHO there is no reason to discard softfail (~all) while allowing
| neutral (?all). I cannot find google in http://spf-all.com/
So what would your recommendation be, then? How would you modify this settings?
opt BOFHSPFHE
Arturo 'Buanzo' Busleiman wrote:
> Alessandro Vesely wrote:
> | IMHO there is no reason to discard softfail (~all) while allowing
> | neutral (?all). I cannot find google in http://spf-all.com/
>
> So what would your recommendation be, then? How would you modify this
> settings?
>
> opt BOFHSPFH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alessandro Vesely wrote:
| The last line performs the lookup but accepts the message in any case. You
| can then safely discard SPF-failed bounces, e.g. checking empty Return-Path
| with a maildrop recipe.
That sounds like a good idea, problem is, i
