Thanks Tony, but unfortunately that IMC has since been removed by a
colleague. This leaves the new one and one IMC at a remote site. The
external emails destined for the internal CR are still bouncing between the
MTAs until they NDR.

-----Original Message-----
From: Tony Hlabse [mailto:thlabse@;hotmail.com] 
Sent: Thursday, 17 October 2002 2:15 PM
To: Exchange Discussions
Subject: Re: Custom Recipient NDR


Why happens if you increase the cost of the new IMC. (Wonder why you created
it there in the first place also?)
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Wednesday, October 16, 2002 10:49 PM
Subject: Custom Recipient NDR


> Hi
> We have Exchange 5.5 SP4 at mutlitple sites. A new server went in at 
> our main site with a new IMC that has a lower cost then our older IMC. 
> We believe this has caused the following problem.
>
> Problem: A Custom Recipient is used for forwarding emails to an ISP
address
> ([EMAIL PROTECTED]). The CR has two addresses associated with it 
> ([EMAIL PROTECTED] & [EMAIL PROTECTED]). Since putting in the 
> new server & IMC, this CR no longer works externally when an email is
addressed
> to [EMAIL PROTECTED] The email comes in the IMC and makes it to 
> the MTA. But this MTA then transfers it to another MTA (server where 
> the other IMC is). This tranfer between MTAs continues for a while 
> before NDRing.
This
> CR still works for internal use. ie email gets forwarded to 
> [EMAIL PROTECTED] when an internal email is sent too the CR.
>
> Various NDRs have been received, 2 of which are below
>
> Your message
>
>  To:      [EMAIL PROTECTED]
>  Subject: Test7
>  Sent:    Thu, 17 Oct 2002 09:14:47 +1000
>
> did not reach the following recipient(s):
>
> Bloggs, John on Thu, 17 Oct 2002 10:04:41 +1000
>    Either the message size exceeds the maximum allowed for the 
> recipient
or
> transport, or you have exceeded the storage limit on your mailbox. The 
> MTS-ID of the original message is: c=au;a= 
> ;p=rcl;l=SUNRICE-EMAIL0210162314VAB79C1Z
>    MSEXCH:MSExchangeMTA:HO:SUNRICE-EMAIL
>
> and
>
> Your message
>
>  To:      [EMAIL PROTECTED]
>  Subject: Test
>  Sent:    Thu, 17 Oct 2002 11:31:27 +1000
>
> did not reach the following recipient(s):
>
> Bloggs, John on Thu, 17 Oct 2002 11:42:51 +1000
>    Unable to deliver the message due to a recipient problem The MTS-ID 
> of the original message is: c=au;a= 
> ;p=rcl;l=SUNRICE-EMAIL0210170131VBRNQGBZ
>    MSEXCH:MSExchangeMTA:HO:SUNRICE-EMAIL
>
>
> What I have done so far.
>
> Checked email addresses
> Checked Technet and found nothing obvious.
> Checked routing and recalculated routing.
> Turned up logging on the MTA's and found nothing obvious to me 
> Recreated the CR with no success
>
>
> Looks like a routing problem but I can't work it out. Any suggestions 
> much appreciated.
>
> Thanks
>
> Steve
>
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Archives:               http://www.swynk.com/sitesearch/search.asp
> To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
> Exchange List admin:    [EMAIL PROTECTED]
>

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:leave-exchange@;ls.swynk.com
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to