Yes.. very true.. unless I'm mis understanding how SPF works... that
user should be sending mail from the mail server (where I can watch
him) and NOT from his dial-up account. I am aware that the dial-up
pool doesn't reverse forward and backwards at the moment, but that
shouldn't break my SPF setup, if I'm understanding how it's setup. I
think I have it setup to only allow mail from my mail server.. yes?
So what's the final concensus? Is the Barracuda box broken?
On Thu, 11 Nov 2004 09:06:30 -0600, wayne <wayne(_at_)midwestcs(_dot_)com>
wrote:
In <1100166445(_dot_)28615(_dot_)52(_dot_)camel(_at_)code3> James Couzens
<jcouzens(_at_)6o4(_dot_)ca> writes:
On Wed, 2004-11-10 at 16:53 -0500, Stuart D. Gathman wrote:
IP MAIL FROM HELO
63.174.244.3 pioneer(_at_)chilitech(_dot_)net smtp1-ha.chilitech.net
I get PASS.
I get fail (I'm using the address pulled out of his header):
james(_at_)code3 ~ $ /usr/local/bin/spfqtool_static -d 0 -s
jcouzens(_at_)chilitech(_dot_)net -i 198.69.197.61 -h test
SPF short result: fail
I believe you pulled the wrong header. I had previously checked and
found the same IP address as Stuart. The relevant Received: header is
the transition from smtp1-ha.chilitech.net to eg1.dns77.com:
: Received: from smtp1-ha.chilitech.net (smtp1-ha.chilitech.net
[63.174.244.3])
: by eg1.dns77.com (Spam Firewall) with ESMTP id EB7C5D0CFE94
: for <hofr(_at_)gemabooks(_dot_)com>; Tue, 9 Nov 2004 15:21:27 -0700 (MST)
The one you pulled appears to have been one hop earlier during an
internal chilitech.net relay.
-wayne
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta features
SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com