Delivery Receipt's getting Queued

We're running Exchange 2003 SP2 on three servers in the same site, one of which is a Frontend server, set up to act as a smarthost for the other two, which house the mailboxes.

Everything works great except that, when users request Delivery Receipts from the outside, the receipt ends up in the  "messages queued for deferred delivery" queue on one of the mailbox servers. When I look a the email in the queue, it shows "Envelope Recipients: SMTP:user@mail.mydomain.com;". My users do not have SMTP addresses with that domain name, but when I added one to my account and tested, received a receipt message. I realize that adding SMTP addresses like that through a recipient policy is an easy work around, but I'd rather keep it simple and figure out what I'm doing wrong.

It seems like this problem has something to do with the FQDN and Masquerade domain info set in the Advanced Delivery section of the Default SMTP Virtual Servers on the backend.

Any ideas?
IRADMINAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
The way that you are doing it at the moment is NOT correct. Therefore I suspect something else is wrong with the transport flow.
Smart host is basically a very blunt object way of sending the email between the servers - it is forcing it through. Exchange should route the email correctly on its own. Therefore something is wrong.

Removing the FQDN will cause problems, so you should put it back in. However it should be unique on each server and resolve correctly inside.
On the SMTP virtual server, ensure that it is set to a specific IP address, rather the "All Unassigned". If you then have routing group or SMTP connectors, recreate both.

SMTP connectors should be used to route email out of the Exchange org. Smart host on the SMTP virtual server should not be used under any circumstances - that is just a setting left over from the IIS SMTP and simply causes problems.

Simon.
0
 
SembeeCommented:
Why have you got masquerade domain and the FQDN set on the backend servers? It shouldn't be required.

How exactly do you have the servers configured? You have said the frontend is set as a smart host. Does that mean you have the frontend server configured as the smart host? If that is the case then you haven't done it correctly. What you should have done is set an SMTP connector with the frontend server only as the bridgehead. The backend servers would then send their email to the frotnend for delivery.

Simon.
0
 
IRADMINAuthor Commented:
Yes, I set up my Frontend server as the smarthost for the backend servers because mail wouldn't route without that. I  started off with setting it as a frontend server, Routing Masterand Bridgehead, but I still couldn't send mail. Only after I set the backend servers to use the Frontend as a smarthost did mail start to flow and it's worked fine. I guess I did something wrong?

thanks,
Dan
0
 
IRADMINAuthor Commented:
This is what I get when I don't set the Frontend as a smarthost for my backend servers and try to deliver mail to the outside. Very strange.

Your message did not reach some or all of the intended recipients.
      Subject:      Another test
      Sent:      11/16/2007 10:15 PM
The following recipient(s) could not be reached:
      personal@yahoo.com on 11/16/2007 10:15 PM
            A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.  Contact your administrator.
            <backend1.firm.local #5.3.5>
0
 
IRADMINAuthor Commented:
I removed the FQDN and masquerade domain and the smart host and got the same result as before. I added back the frontend server a smarthost on my backend servers and mail flows again, though for my delivery receipts, it's still trying to send to user@mail.ir-law.com. - Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.