Here is the situation, we have two companies working for us, company "A" who hosts all our webservers and company "B" who hosts our exchange server only. Now, when our webservers/webapps generate emails and send to our customers they use company "A" exchange server as outbound exchange server, but when an email bounces back will it be returned to exchange server at company "A" or "B". All our email id's including employee & business id's used in application's are hosted at company "B" exchange server? My problem is, when an email is bounced back that email is not getting flagged as undelivered until 3-4 days later and meanwhile, it looks like the email is being retried. I want to decrease the retry time and attempts too, and I am not sure who to ask (admin in company "A" or "B") to set the changes. Any help/advice is highly appreciated. Thanks in advance. Microsoft Blogs

On Tue, 10 Apr 2012 14:11:56 +0000, madasty wrote: > > >Here is the situation, we have two companies working for us, company "A" who hosts all our webservers and company "B" who hosts our exchange server only. Now, when our webservers/webapps generate emails and send to our customers they use company "A" exchange server as outbound exchange server, but when an email bounces back will it be returned to exchange server at company "A" or "B". All our email id's including employee & business id's used in application's are hosted at company "B" exchange server? > >My problem is, when an email is bounced back that email is not getting flagged as undelivered until 3-4 days later and meanwhile, it looks like the email is being retried. I want to decrease the retry time and attempts too, and I am not sure who to ask (admin in company "A" or "B") to set the changes. > >Any help/advice is highly appreciated. If the delay is in sending the mail then you need to work whoever is the sending server. That sounds like "A" to me. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, I understand that the mail flow is WebServer-send message-Exchange-internet, is that right? Then the webserver relay off Exchange Server. When message send to webserver, Exchange will receive the message from internet and then deliver it to webserver. If the message bounce back, it will return to company A. Xiu Zhang TechNet Community Support

The delay / the issue is when the message is bounced back, will it be captured by the "A" exchange server or "B" and the delay is in the "retry" process of that bounced back email. But, I guess you are right if the "A" is sending out the email in first place then its "A" that is implementing all the retry procedures too. Anyway, in the mix of debugging the issue, I pulled out the delivery report for one of the bounced back email and here is what it says, and I think its clearly explaining that "A" is trying to re-deliver the message. Thank you very much for your reply. This is the mail system at host "COMPANY A" #################################################################### # THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. # #################################################################### Your message could not be delivered for more than 4 hour(s). It will be retried until it is 5 day(s) old. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <customer@yahoo.com>: host mta5.am0.yahoodns.net[209.191.88.254] said: 451 mta1042.mail.mud.yahoo.com Resources temporarily unavailable. Please try again later [#4.16.1]. (in reply to end of DATA command) Microsoft Blogs

On Wed, 11 Apr 2012 16:08:13 +0000, madasty wrote: >The delay / the issue is when the message is bounced back, "Bounced" implies that the message was sent. Your description reads as if the message was never sent. >will it be captured by the "A" exchange server or "B" and the delay is in the "retry" process of that bounced back email. If it's just a DSN telling the sender that the message is delayed then it's the server that's trying to deliver the mail to the next hop. But the message isn't sent anywhere so there's nothing to "capture". >But, I guess you are right if the "A" is sending out the email in first place then its "A" that is implementing all the retry procedures too. That's correct. >Anyway, in the mix of debugging the issue, I pulled out the delivery report for one of the bounced back email and here is what it says, and I think its clearly explaining that "A" is trying to re-deliver the message. There's no "re-deliver". It ("server A") is just periodically trying to send the message. It will only send the message once. It will try sending the message numerous times. >Thank you very much for your reply. > >This is the mail system at host "COMPANY A" > >#################################################################### > ># THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. # #################################################################### > >Your message could not be delivered for more than 4 hour(s). > >It will be retried until it is 5 day(s) old. > >For further assistance, please send mail to <postmaster> > >If you do so, please include this problem report. You can delete your own text from the attached returned message. > > The mail system > ><customer@yahoo.com>: host mta5.am0.yahoodns.net[209.191.88.254] said: 451 > > mta1042.mail.mud.yahoo.com Resources temporarily unavailable. Please try > > again later [#4.16.1]. (in reply to end of DATA command) > > > > >Microsoft Blogs --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP