Re: Setup problem with SenderID and OWA



BK Rogers <BKRogers@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>So I've come accross a problem with my setup of my SPF record and users send
>mail with OWA. When a user logs into our Exchange server via OWA and sends a
>new message, the SMTP message header includes the IP address the OWA client
>was sending from....

I just checked a message sent from OWA, and I find only the IP address
of the Exchange server, not the IP address of the machine running the
browser.

I sent one from another organization, and one from within our own
organization, and in neither case does the client appear in the
"Received:" headers.

Both were sent from Exchange 2003 servers, one organization running
SP1 and the other running SP2.

>Sample SMTP Header from Exchange server....
>Received: from 70.247.95.109 ([70.247.95.109]) by solar.tul.solarwinds.net
>([206.231.6.251]) with Microsoft Exchange Server HTTP-DAV ; <CR> <LF> ..

Could this be the browser you're using that's causing this?

IAC, how many "Received:" headers are in the message? The one above
surely isn't the one inserted by the receiving server. How many
"Received:" headers is the SMTP server checking?

>This mail is rejected by the receiving mail server with the error message
>Response: 550 5.7.1 Sender ID (PRA) Not Permitted
>
>The txt record for solarwinds.net is
>v=spf1 mx a:mail.solarwinds.net -all
>and our mx record resolves to 206.231.6.251, so that part is OK.
>
>So what is causing the PRA not permitted?

That's hard to say since you don't say what the sender's e-mail
address is (e.g. the "From" header). The PRA isn't about simple IP
address checking (like SPF), but about whether the e-mail address of
the sender (taken from the RFC2822 headers -- or the MAIL FROM if the
sender can't be found in the message).

>Is it the 70.247.95.109 address
>that was the external IP address where the OWA client was logged in from?

It may be, but that would depend on the checking done by the receiving
server (e.g. how many "Received:" headers they check).

>Can I fix this without setting my SPF records to +all?

Not all implementations of SenderID are error-free. So, trying to fix
this at your end may not be the best approach. I _am_ curious about
the 70.247.95.109 address in the "Received:" header, though.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.



Relevant Pages

  • Re: Delayed Email
    ... >From the information in the header, there was a 25 minute delay between ... mail.external.com sending and myspam.asp.com receiving. ... lookup failures, server failures. ... > mailboxsrvr.mydomain.com with Microsoft SMTPSVC; ...
    (microsoft.public.exchange.admin)
  • Re: Setup problem with SenderID and OWA
    ... >Both the Sending and Receiving Mail servers are Exchange 2003 with SP2. ... >Only one Received from header was in the SMTP DATA Portion. ... >Exchange server and watch the exact data being sent. ...
    (microsoft.public.exchange.admin)
  • Re: Received From IP from behind router
    ... >> to block a server, and I will block them at the firewall, and any server ... >> I really doubt that the header that Sendmail was writing is the problem, ... >> looks to me like the problem is with his DNS. ... > I have tons of rejected mail due to timeouts when the receiving end looks to ...
    (comp.mail.sendmail)
  • Re: Received From IP from behind router
    ... > to block a server, and I will block them at the firewall, and any server ... > I really doubt that the header that Sendmail was writing is the problem, ... > looks to me like the problem is with his DNS. ... I have tons of rejected mail due to timeouts when the receiving end looks to ...
    (comp.mail.sendmail)
  • OWA returns HTTP/1.1 503 Service Unavailable
    ... Outlook Web Access used to work fine, but now users are receiving the ... The OWA Exchange 2003 Server sits on a different subnet from the Exchange ...
    (microsoft.public.exchange.admin)