No, I never belived that the SPF check was run against all the received
headers. I'm just looking at how Declude does its SPF check on email that
comes into my server. It always does it on the last hop. But looking at the
headers of the outgoing messages, (as I showed in my message below from
Darin,
I am not sure why, but Gary seems to think SPF checks are run against ALL of
the received headers.
I am guessing that he has an SPF test action at the end of his Global.cfg,
so that it is testing outgoing?
Michael Thomas
Mathbox
978-683-6718
1-877-MATHBOX (Toll Free)
> -Original
Gary,
I thought I tried to get this across. Most servers check SPF at the
connection, not via the received headers. Further excepting very special
circumstances like having proxies or gateways, anyone checking SPF via
received headers should only be checking the first received header, which
means
Yes, it does. Message come in from your mail client and is whitelisted by
SMTP AUTH. Now your server sends it to the destination. Receiving server
sees the message coming from your server, and that your server is a valid
sender for the domain in question according to your SPF policy.
The last h
My question still isn't coming across. In setting up SPF, I don't want any
outgoing messages from my server to be bounced by others because of a bad SPF
string. I can whitelist SMTP auth on my server, but that does't help the SPF
problem because potentially when one of my users sends a message
