Wade,
This message was sent by blue.olm.net [69.94.102.4]. You'll need to
specify one of more of their servers in your SPF record.
Since they seem to have multiple servers and don't have an SPF record of
their own, you should probably contact them and ask what you should
specify in your record.
As a start, ip4:69.94.102.4 should be included.
Andrew
artistdomain wrote:
> Hi Alan,
>
> Sorry, you lost me a little bit. This response is going from my Outlook Express, not Spamarrest this time.
>
> I don't anyone know of anyone besides Spamarrest that has inbound SPF filtering for me to test my record.
>
> Is this mail failing? If so it still failing due to that ATT IP#?
>
> My mailserver is only set for authentication not SPF filtering. My mailserver doesn't have inbound SPF filtering. I use Spamarrest for that on my inbound mail.
>
> So, not sending from one "box to another box on same mail server. My tests to myself are going from OLM.Net and coming back to my my Spamarrest box on Spamarrest's network.
>
> Thanks,
>
> wade
>
> Your previous response:
>
> no you are testing for spf mail sent from a mail client
> {your server is misconfigured it should not require spf from mail clients, only authentication}
>
> send a mail to anyone else via your server
> {even me}* {anywhere else == somewhere your server would have to forward to via smtp following mx records not another mailbox on the same server}
> and we can tell you does your mail pass spf when it arrives here
>
> mail between client<>server {esmtpa authentiacated smtp via port 587, or some smtp-auth workaround kludge on port25}
> nothing to do with SPF {if spf checks are done server is mis-configured}
>
> mail between server<>server [e]smtp on port 25 {the only place SPF is designed to be used}
>
>
> -------------------------------------------
> Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
> Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
>
> Archives: https://www.listbox.com/member/archive/1020/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/1020/
> Powered by Listbox: http://www.listbox.com
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com
This message was sent by blue.olm.net [69.94.102.4]. You'll need to
specify one of more of their servers in your SPF record.
Since they seem to have multiple servers and don't have an SPF record of
their own, you should probably contact them and ask what you should
specify in your record.
As a start, ip4:69.94.102.4 should be included.
Andrew
artistdomain wrote:
> Hi Alan,
>
> Sorry, you lost me a little bit. This response is going from my Outlook Express, not Spamarrest this time.
>
> I don't anyone know of anyone besides Spamarrest that has inbound SPF filtering for me to test my record.
>
> Is this mail failing? If so it still failing due to that ATT IP#?
>
> My mailserver is only set for authentication not SPF filtering. My mailserver doesn't have inbound SPF filtering. I use Spamarrest for that on my inbound mail.
>
> So, not sending from one "box to another box on same mail server. My tests to myself are going from OLM.Net and coming back to my my Spamarrest box on Spamarrest's network.
>
> Thanks,
>
> wade
>
> Your previous response:
>
> no you are testing for spf mail sent from a mail client
> {your server is misconfigured it should not require spf from mail clients, only authentication}
>
> send a mail to anyone else via your server
> {even me}* {anywhere else == somewhere your server would have to forward to via smtp following mx records not another mailbox on the same server}
> and we can tell you does your mail pass spf when it arrives here
>
> mail between client<>server {esmtpa authentiacated smtp via port 587, or some smtp-auth workaround kludge on port25}
> nothing to do with SPF {if spf checks are done server is mis-configured}
>
> mail between server<>server [e]smtp on port 25 {the only place SPF is designed to be used}
>
>
> -------------------------------------------
> Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
> Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
>
> Archives: https://www.listbox.com/member/archive/1020/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/1020/
> Powered by Listbox: http://www.listbox.com
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com