Well ok... if you want to pick nits :-)
I guess I should have said:
The listserver, and one of the email accounts, originate mail on the
host (the email account, using pine) - so, for SPF purposes, the mail
comes from an IP address listed in the SPF record for the domain in the
envelop sender
I'm sorry, but your query below does not parse. The envelope sender
does not change depending on which host it arrives from when using
Thunderbird et al. The host from which it arrives changes, but that's
not part of the envelope.
And yes, you can disable anything with a network profile. rt
Hi Folks,
I starting to set up SPF records for the domains I manage, and have run
into a little snag. I hope somebody can suggest an approach:
BASIC CONFIGURATION:
Debian Sarge
Postfix (from stable - so it's a relatively old version, 2.1 I believe)
amavisd-new
spamassassin
clamav
Postfix conf
Random email that was forwarded to the customers Exchange server.. no way
to debug... I just happened to notice it later...
The biggest thing is I see the HELO setup on mail servers incorrectly all
the time, I didn't think SPF had anything to do with HELO...
> Brian Taber wrote:
>> Hmmm... A
Brian Taber wrote:
Hmmm... Another potential SPF issue... I have a customer with AMEX,
received an email from them, and the SPF checks conflict with each other:
helo=
Received: from mta301.email.americanexpress.com
(mta301.email.americanexpress.com [206.132.204.250])
From: [EMAIL PROTECTED]
Hmmm... Another potential SPF issue... I have a customer with AMEX,
received an email from them, and the SPF checks conflict with each other:
helo=
Received: from mta301.email.americanexpress.com
(mta301.email.americanexpress.com [206.132.204.250])
From: [EMAIL PROTECTED]
And the scores:
3.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daryl C. W. O'Shea writes:
> Brian Taber wrote:
> > As for the scores, score of 0 for PASS makes perfect sense, but a FAIL
> > should receive at least the same score as a SOFTFAIL, because a FAIL means
> > the email is definately from a forged sender
Brian Taber wrote:
Figured that what are the mass-check's you mentioned? Is there
somewhere I can go to find out more? Is there a way to update
spamassassin with the newest scores?
http://wiki.apache.org/spamassassin/MassCheck
http://wiki.apache.org/spamassassin/RescoreDetails
http://wik
Brian Taber wrote:
As for the scores, score of 0 for PASS makes perfect sense, but a FAIL
should receive at least the same score as a SOFTFAIL, because a FAIL means
the email is definately from a forged sender (on the other hand the FAIL
may be because the person who created the SPF records had n
Since I am using spamassassin via MailScanner, I dug into my config files
more (took a while) I found an option in spam.assassin.prefs.conf called
envelope_sender_header that was not set properly, now all SPF checks
work...
As for the scores, score of 0 for PASS makes perfect sense, but a FAIL
sh
Brian Taber wrote:
The second is about the scores assigned to SPF failures. SPF_HELO_SOFTFAIL
has a score of 3.140 (so if the provider has ~all in their SPF record,
they aren't really sure if their SPF record covers all of their servers,
you get SOFTFAIL), but SPF_HELO_FAIL has a score of 0.001 (
Brian Taber wrote:
I am using spamassassin 3.0.4-1 with MailScanner. I have 2
questions/issues about SPF checks.
It seams that SA is only doing HELO SPF checks (I didn't even know those
existed till now) and not actual checks on the from addresses. Is this a
config issue? I would like to enab
Loren Wilton wrote on Sat, 2 Jul 2005 18:07:19 -0700:
> I think perhaps SPF is supposed to match against the sender in the envelope,
> or possibly the received header, rather than the From header, which is
> trivially forged
Now that you say that I remember that you can configure this in local.
I think perhaps SPF is supposed to match against the sender in the envelope,
or possibly the received header, rather than the From header, which is
trivially forged.
Others will be able to give more information. I know the rule score of .001
is deliberate, but I don't recall immediately why. It
14 matches
Mail list logo
