locked
OOF is sent to "Header from" instead of "Envelope sender" RRS feed

  • Question

  • Hi,

    we are using Exim as SMTP server, and there are a lot of frozen messages beacause of wrongly adressed Out of Office Mails from Exchange. The original mail headers are for example:

    Envelope Sender: pvrs=1234145345=sender@domain.com

    Header From: sender@domain.com

    If the Recipient has OOF configured the automatically generated OOF mail is sent to sender@domain.com instead of pvrs=1234145345=sender@domain.com and the smtp server for domain.com gives me a "550 Recipient not accepted. (BATV: no tag)"

    What could I do?

    Thursday, May 26, 2011 10:27 AM

Answers

  • On Fri, 27 May 2011 05:46:27 +0000, nicx76 wrote:
     
    >thanks for the info. Could you please explain how I can configure our Exchange 2007 not to send OOF and other DSN to those domains that use BATV?
     
    Create a "Remote Domain" for them and set the options on that. Look in
    the "Organization Configuration | Hub Transport" section of the EMC.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by Gen Lin Friday, June 3, 2011 7:11 AM
    Friday, May 27, 2011 9:47 PM

All replies

  • Please explain you exchange topology.
    Regards, Pushkal MishrA
    Thursday, May 26, 2011 5:06 PM
  • On Thu, 26 May 2011 10:27:07 +0000, nicx76 wrote:
     
    >we are using Exim as SMTP server, and there are a lot of frozen messages beacause of wrongly adressed Out of Office Mails from Exchange. The original mail headers are for example:
    >
    >Envelope Sender: pvrs=1234145345=sender@domain.com
    >
    >Header From: sender@domain.com
    >
    >If the Recipient has OOF configured the automatically generated OOF mail is sent to sender@domain.com instead of pvrs=1234145345=sender@domain.com and the smtp server for domain.com gives me a "550 Recipient not accepted. (BATV: no tag)"
    >
    >What could I do?
     
    Contact the domains that send the messages with BATV and ask that they
    not include your domain in that processing.
     
    Once the message is past the MTA the BATV tokens are removed. Messages
    that use a null sender (like a DSN for a "mailbox full" condition, or
    an OOF) will not have the BATV tokens in the recipinet address. When
    the MTA that sent the original message sees the null address it
    expects to see the BATV tokens in the RCPT TO address.
     
    You could also just configure Exchange to not send OOF and other DSN
    to those domains that use BATV.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, May 27, 2011 12:29 AM
  • Hi,

    thanks for the info. Could you please explain how I can configure our Exchange 2007 not to send OOF and other DSN to those domains that use BATV?

     

    Friday, May 27, 2011 5:46 AM
  • On Fri, 27 May 2011 05:46:27 +0000, nicx76 wrote:
     
    >thanks for the info. Could you please explain how I can configure our Exchange 2007 not to send OOF and other DSN to those domains that use BATV?
     
    Create a "Remote Domain" for them and set the options on that. Look in
    the "Organization Configuration | Hub Transport" section of the EMC.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by Gen Lin Friday, June 3, 2011 7:11 AM
    Friday, May 27, 2011 9:47 PM
  • Hi,

    just for my understanding: This is really not a Bug? Why is the Token removed? For me if I understand RFC correctly the Token should not be removed, doesnt matter if the mail is an OOF or something else.

    We have a lot of Maildomains with this problem and its really a pitty if I have to create Remote Domains manually for each of it.

    Thanks & Regards

    Monday, June 6, 2011 9:19 AM
  • Hi,

    news after some more testing: if in the mail header exists a FROM and a RETURN-PATH field with different addresses its always the FROM address used for OOF and other DSN, so as far as I understand RFC this is a bug. The mail address of the RETURN PATH field should be used instead (which includes the batv token).

    Am I right or wrong? ;)

    Monday, June 6, 2011 2:36 PM
  • On Mon, 6 Jun 2011 14:36:25 +0000, nicx76 wrote:
     
    >news after some more testing: if in the mail header exists a FROM and a RETURN-PATH field with different addresses its always the FROM address used for OOF and other DSN, so as far as I understand RFC this is a bug. The mail address of the RETURN PATH field should be used instead (which includes the batv token).
    >
    >Am I right or wrong? ;)
     
    Considering that RFC often contain conflicting or ambiguous
    information, or that have been superceded, it's always a good idea to
    cite the RFC and section number.
     
    If you're refering to RFC2921, I'd concur. But I have no ability to
    change the behavior. You'll have to take this up with Microsoft.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, June 6, 2011 9:51 PM