Announcement

Collapse
No announcement yet.

External OOF Being Rejected By AT&T Smarthost

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • External OOF Being Rejected By AT&T Smarthost

    Gang,

    All emails send fine from my SBS 2008 Exchange 2007 server aside from external Out of Office emails. I have been trying to figure this out for a couple days now. I ran the message tracking for FAILED items and found all of the OOF messages today.

    The failed reason is SMTP 553 "From address not verified". This is an AT&T smarthost and AT&T always requires all sending addresses to be added to their control panel before they'll allow the address to send. In the FAILED log, it shows the sender as the proper user's email address, so I am not sure why it's not going through. I did, however, notice that there's no "return-path" address specified on these messages.

    I called AT&T and they are worthless in figuring this out. The second level technician didn't even understand what I meant about the "return-path" in the message header. From poking around the Internet, I have seen people suggest writing a transport agent in Exchange 2007 to re-write the "return-path" in the headers of all OOF emails. Does anyone know how to accomplish such a feat, or if there's any other way to handle this? Thanks in advance.

    D
    Last edited by RaeKWoNCHeF; 9th July 2009, 21:53.

  • #2
    Re: External OOF Being Rejected By AT&T Smarthost

    This has come up a few times.
    Exchange 2007 is RFC compliant, and is sending the OOTO messages with the address as <>.
    AT&Ts server is not RFC compliant as it is rejecting the legitimate email.

    Therefore you have two choices only.
    1. Don't send external OOTO messages.
    2. Don't use AT&Ts smart host.

    You cannot change the behaviour of Exchange.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: External OOF Being Rejected By AT&amp;T Smarthost

      Sembee,

      Thanks for the response. Then the transport rule is out of the question, yes? I seem to be receiving conflicting advice from multiple sources. Thanks for your time!

      D

      Comment


      • #4
        Re: External OOF Being Rejected By AT&amp;T Smarthost

        A transport agent may work. It isn't something I have created before. It requires the header being rewritten.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment

        Working...
        X