I suspect the IMS configuration. What configuration information would you need from the IMS? Let me know and I will provide it. Also this is only happening on two servers that have similar IMS configurations. They both send email to a Unix mail relay instead of directly to the internet or the other exchange servers. Thanks, Jay -----Original Message----- From: Kalpesh Pitale [mailto:kalpesh.pitale@xxxxxxxxxxxxxxxx] Sent: Monday, August 26, 2002 7:42 AM To: [ExchangeList] Subject: [exchangelist] RE: Address encapsulation question http://www.MSExchange.org/ This generally happens due to incorrect Email-Topology or X.400 OR IMS. It will be easy for me to input if you have topology dia and also your IMS or X.400 connectors details. Try to check the connector configurations... [Kalpesh Pitale] -----Original Message----- From: Humphrey, Jay CIV [mailto:c6fsysad@xxxxxxxxxxxx] Sent: Sunday, 25 August 2002 4:38 PM To: [ExchangeList] Subject: [exchangelist] Address encapsulation question http://www.MSExchange.org/ Hi all, We are experiencing a weird problem with how Exchange encapsulates X.400 addresses in SMTP. We have 16 separate sites in various parts of the world all part of the same organization. Directory replication is done over SMTP. We are seeing all of the sites in the GAL and get directory updates when changes are made. However, we are having an issue with two of our servers encapsulating the incorrect SMTP domain onto messages sent over the IMC. On these two servers the IMC is configured to forward messages to a Unix-based email relay rather than use DNS. What happens is instead of putting the SMTP domain address for the recipient exchange is adding the SMTP address for the next hop. So for example a user on ServerA sends a message to a user on ServerD but the message has to pass through ServerB and ServerC (bridgehead) to get there. Instead of encapsulating the message like IMCEAEX-_O=ORGANIZATION_OU=SITEOFSERVERD_cn=RECIPIENTS_cn=USER@xxxxxxxxxxx <mailto:IMCEAEX-_O=ORGANIZATION_OU=SITEOFSERVERD_cn=RECIPIENTS_cn=USER@SERVE RD.COM> the address ends up something like IMCEAEX-_O=ORGANIZATION_OU=SITEOFSERVERD_cn=RECIPIENTS_cn=USER@xxxxxxxxxxx <mailto:IMCEAEX-_O=ORGANIZATION_OU=SITEOFSERVERD_cn=RECIPIENTS_cn=USER@SERVE RB.COM> Notice that it has the correct site name of ServerD but yet it still adds the incorrect SMTP address. Normally this would not be that big of a deal but this is causing some NDRs due to excessive hops because most of these servers are inside of firewalls and the messages have to pass through the firewalls as well as various other virus scanners and what-not. It also causes each server in the link to have to process the message instead of just forwarding it on because the SMTP address that is appended makes it appear that the message is for that server rather than the actual recipient's server. I have been troubleshooting this issue to death and have not made a breakthrough yet. I am hoping someone on the list can shed some light. Thank you, Jay Humphrey ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: kp@xxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: c6fsysad@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')