Re: Setup problem with SenderID and OWA

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



BK Rogers <BKRogers@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Both the Sending and Receiving Mail servers are Exchange 2003 with SP2.
>The browser is IE 6 SP1. The 70.247.95.109 address is one of my static IPs
>at my home where I was running using the IE explorer from.

I'd be interested to know if anyone else sees this. I know I don't.

>Only one Received from header was in the SMTP DATA Portion. To actually see
>the Received from header, I had to put a packet sniffer on the receiving
>Exchange server and watch the exact data being sent.

Or just use Outlook and the "View | Options" menue . . . or Outlook
Express, or other e-mail clients.

>The Exchange server was
>rejecting the mail with a 550 5.7.1 Sender ID (PRA) Not Permitted as soon as
>the DATA conversation portion was ended with the standard .<CR><LF> . Since
>it was rejected by the SMTP server,I would never see the note in my Inbox.

I wouldn't reject mail if the ony problem was that SPF/SenderID
failed. There are way too many broken SPF TXT records out there to
trust them all that much. Sure, if SPF/SenderID fails, let the IMF (or
whatever you're using for anti-spam control) take that into account
and weight the meesage accordingly, but I trust SPF/SendeID about as
much as I trust DNS RBL's run by people I've never met whose agendas I
don't know. :)

>If you are looking at the headers in Outlook for a note sent via OWA , you
>will need to look at the lowest Received: from the note because it has been
>relay from one SMTP server to another and the path as been updated.

That's true for any message handled by a SMTP server . . . unless they
rip out the Received headers on the way out of the organization.


>(Example from an Inbox after successful transmission...)
>Received: from houston.chickenfriedbacon.com ([70.247.95.98]) by
>solar.solarwinds.net with Microsoft SMTPSVC(6.0.3790.1830);
> Fri, 16 Dec 2005 09:44:54 -0600
>Received: from 206.231.4.58 ([206.231.4.58]) by
>houston.tul.chickenfriedbacon.com ([1.0.0.8]) with Microsoft Exchange Server
>HTTP-DAV ;
^^^^^^^^
^
|
This is the part that disturbs me.

Lemme ask around and see if anyone else is seeing this.

>After making my post last night, I did more reading about the PRA and added
>what I think is the correct workaround to our DNS TXT record. (But if you or
>other have more input it would be welcomed) Since the MAIL From part is
>correct, but the top level PRA may come from anywhere on the Internet logged
>in via OWA, I added a
>
>spf2.0/pra ?all

That should be okay, but it's probably as effective as accepting the
failed PRA and letting the IMF use it as one of its inputs.

--
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: Setup problem with SenderID and OWA
    ... Both the Sending and Receiving Mail servers are Exchange 2003 with SP2. ... Exchange server and watch the exact data being sent. ...
    (microsoft.public.exchange.admin)
  • Re: 2 users not receiving mail
    ... Should cached exchange be enabled for clients? ... My customers server is SBS Standard and has ... Hard Drives and memory, that is the only thing that has ever needed ... had a user that was not receiving mail and another user that was ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups
    ... Most of our users have Exchange accounts, ... Essentially, our server ... > communicates with the receiving server, issues the recipient lists, ...
    (microsoft.public.exchange.connectivity)
  • Re: Setup problem with SenderID and OWA
    ... >mail with OWA. ... of the Exchange server, not the IP address of the machine running the ... >Sample SMTP Header from Exchange server.... ... surely isn't the one inserted by the receiving server. ...
    (microsoft.public.exchange.admin)
  • Re: Does Exchange modify time headers in the mail?
    ... I suspect it is the POP connector that causes the time/date changes. ... really should avoid using it if you want to use exchange as it was intended. ... received and found that the *Date* header for a mail is always the ... So it looks like Exchange server has modified this ...
    (microsoft.public.windows.server.sbs)