|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Receiving mail hosts should check the SPF against the IP address of the
machine which connects to their server, rather than the mail headers, as
by relaying the message, the edgemost SMTP server is vouching that the
message is authentic. Thus, rewriting the headers shouldn't acomplish
anything.
I'd guess that the webmail server is the same machine as the MX machine,
and sends messages directly via a local MTA, however your mail host's
published SMTP server is a different box. So in effect, when you send via
wbmail your mail is originating using the MX machine, but when you send
via their SMTP server your mail is originating from some other IP address.
Check on the address of your mail host's SMTP server and make sure that
that server is in your SPF record. Also, send a test message through the
SMTP server to a mailbox that doesn't verify SPFs and make sure that your
mail host doesn't have some internal relaying scheme. If they do, make
sure you find out your mail host's edge outgoing mail servers and add
those to your SPF record.
Hope this helps. Feel free to ask for clarification, as I'm writing this
on very little sleep and may or may not be clear.
Cheers,
Erek Dyskant
On Thu, September 20, 2007 15:10, Matt Mossholder wrote:
>
> On Thu, 20 Sep 2007 15:01:33 -0400, Paul L. Snyder <plsnyder@drexel.edu>
> wrote:
>> I'm having problems with mail delivery, and I suspect that SPF is
>> the culprit. For the domain in question, I send mail in two ways:
>>
>> * Using mutt from my home network
>> * Using a web client at my mail host
>>
>> On my home network, mutt sends the message to a local Postfix
>> installation which relays the mail to the SMTP server at my mail
>> host.
>>
>> Mail sent via the web interface works fine; mail sent from my home
>> network is not received by some addresses. I have an SPF record
>> for the domain specifying my mail host's MX. I would really not
>> rather not publish the addresses of my home network in the SPF
>> record if I can avoid it. Am I diagnosing this problem correctly?
>>
>> Would it be better to configure mutt to use a dumb MSA that
>> directly hands off the mail to the MX rather than using a local
>> MTA? My eventual goal is to be able to send messages via
>> either the SMTP host for my own domains or via Drexel's MX
>> depending on the sending address. (Also, I'd like my messages to
>> be accepted as authentic rather than rejected as spoofed.)
>>
>> Any thoughts appreciated.
>>
>> pls
> --
>
>
> Paul,
> You probably need to rewrite the message headers, so that the
> external systems think all the mail originated at the MX server...
>
> --Matt
>
> ___________________________________________________________________________
> Philadelphia Linux Users Group --
> http://www.phillylinux.org
> Announcements -
> http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion --
> http://lists.phillylinux.org/mailman/listinfo/plug
>
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|