RE: Silly Outlook Addressing Problem
You don't want to hear this, but you should have factored this issue into your decision on how you did your migraton. You can add the old Exchange 5.5 mailbox's distinguished name as an alias to the new mailbox with an address type of X500. HP (of whom I am an employee) sells a tool called LDAP Directory Synchronization Utility that can bring that data over from your old Exchange 5.5 directory (if you still have it). You could also script such a thing. Since over time this problem becomes less and less important you can just choose to live with it and tell your users to readdress replies to old mail. Ed Crowley MCSE+Internet MVP Freelance E-Mail Philosopher Protecting the world from PSTs and Bricked Backups!T -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Hoffman Sent: Monday, November 24, 2003 8:56 AM To: Exchange Discussions Subject: Silly Outlook Addressing Problem OK, I'm sure this is a newbie question, but I don't even know what to call this problem in order to look it up: After our upgrade to Exchange 2000 from 5.5 many of our users are experiencing a problem where they are getting undeliverable emails to other staff members. This is definitely a problem with the X400 addresses, since they have changed and the SMTP addresses have not (and in fact, when looking at their sent item I can see the old X400 address from the 5.5 system is still in there). So, I surmise that the problem has to do with how Outlook holds on to past email addresses. My guess is that the users are responding to old emails that came from users back when the old system was in place and are therefore getting the old X400 addresses. This is sticking in Outlook's cache (again, note that I'm not an Outlook expert) and causing problems when they then attempt to send to that user again. So, two possible related solutions: 1. get rid of the X400 addresses if they are not necessary. We have only one Exchange server and are not likely to get another. Do we really need them? 2. Figure out how to turn off Outlook's caching of email addresses. How does one do that? Is there a way to do it via Active Directory GPO's? Thanks for any help, Matt _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Silly Outlook Addressing Problem
OK, I'm sure this is a newbie question, but I don't even know what to call this problem in order to look it up: After our upgrade to Exchange 2000 from 5.5 many of our users are experiencing a problem where they are getting undeliverable emails to other staff members. This is definitely a problem with the X400 addresses, since they have changed and the SMTP addresses have not (and in fact, when looking at their sent item I can see the old X400 address from the 5.5 system is still in there). So, I surmise that the problem has to do with how Outlook holds on to past email addresses. My guess is that the users are responding to old emails that came from users back when the old system was in place and are therefore getting the old X400 addresses. This is sticking in Outlook's cache (again, note that I'm not an Outlook expert) and causing problems when they then attempt to send to that user again. So, two possible related solutions: 1. get rid of the X400 addresses if they are not necessary. We have only one Exchange server and are not likely to get another. Do we really need them? 2. Figure out how to turn off Outlook's caching of email addresses. How does one do that? Is there a way to do it via Active Directory GPO's? Thanks for any help, Matt _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Silly Outlook Addressing Problem
I don't think you can get rid of X400 addresses. Also what you are seeing in the Sent items are probably not X400, but rather X500 addresses. X500 address was also known as Directory Name back in Exchange 5.5 and that's how Exchange 5.5 constructed the replies - based on the Directory Name. The X500 address legacy still exists in Exchange 2000. Each mail-enabled user has a LegacyExchangeDN field. You can see it with help of ADSIEdit. It is automatically generated, but you can edit it (be prepared to update Outlook profile if you do that). Sincerely, Andrey Fyodorov, MVP Systems Engineer Messaging and Collaboration Spherion -Original Message- From: Matt Hoffman [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 11:56 AM To: Exchange Discussions Subject: Silly Outlook Addressing Problem OK, I'm sure this is a newbie question, but I don't even know what to call this problem in order to look it up: After our upgrade to Exchange 2000 from 5.5 many of our users are experiencing a problem where they are getting undeliverable emails to other staff members. This is definitely a problem with the X400 addresses, since they have changed and the SMTP addresses have not (and in fact, when looking at their sent item I can see the old X400 address from the 5.5 system is still in there). So, I surmise that the problem has to do with how Outlook holds on to past email addresses. My guess is that the users are responding to old emails that came from users back when the old system was in place and are therefore getting the old X400 addresses. This is sticking in Outlook's cache (again, note that I'm not an Outlook expert) and causing problems when they then attempt to send to that user again. So, two possible related solutions: 1. get rid of the X400 addresses if they are not necessary. We have only one Exchange server and are not likely to get another. Do we really need them? 2. Figure out how to turn off Outlook's caching of email addresses. How does one do that? Is there a way to do it via Active Directory GPO's? Thanks for any help, Matt _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Silly Outlook Addressing Problem
We had the same issue migrating from GroupWise to Exchange 5.5 a few years back. Outlook doesn't really cache anything in the sense that you're talking about. It merely neglects to re-look-up the address in a reply. Normally, this makes sense. If you send me a message and I reply, there's no reason to waste the CPU cycles or the bandwidth to verify that the address still exists. What we told people to do is when they get the bounce messages, do a resend, delete all of the addresses from the From, CC, etc. fields and type them again. This forces a new GAL lookup and should find the up to date addresses. This will be a problem that will lessen as time goes on. -Original Message- From: Matt Hoffman [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 11:56 AM To: Exchange Discussions Subject: Silly Outlook Addressing Problem OK, I'm sure this is a newbie question, but I don't even know what to call this problem in order to look it up: After our upgrade to Exchange 2000 from 5.5 many of our users are experiencing a problem where they are getting undeliverable emails to other staff members. This is definitely a problem with the X400 addresses, since they have changed and the SMTP addresses have not (and in fact, when looking at their sent item I can see the old X400 address from the 5.5 system is still in there). So, I surmise that the problem has to do with how Outlook holds on to past email addresses. My guess is that the users are responding to old emails that came from users back when the old system was in place and are therefore getting the old X400 addresses. This is sticking in Outlook's cache (again, note that I'm not an Outlook expert) and causing problems when they then attempt to send to that user again. So, two possible related solutions: 1. get rid of the X400 addresses if they are not necessary. We have only one Exchange server and are not likely to get another. Do we really need them? 2. Figure out how to turn off Outlook's caching of email addresses. How does one do that? Is there a way to do it via Active Directory GPO's? Thanks for any help, Matt _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchanget ext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Re: Silly Outlook Addressing Problem
Hello Matt: If you're looking to remove Outlook's caching of email addresses, recreate the user's Outlook nickname file. It is usually *.nk2 on a user's local machine. See 287623, 293032 or 242074 depending on the Outlook version. Good luck! -Juancho OK, I'm sure this is a newbie question, but I don't even know what to call this problem in order to look it up: After our upgrade to Exchange 2000 from 5.5 many of our users are experiencing a problem where they are getting undeliverable emails to other staff members. This is definitely a problem with the X400 addresses, since they have changed and the SMTP addresses have not (and in fact, when looking at their sent item I can see the old X400 address from the 5.5 system is still in there). So, I surmise that the problem has to do with how Outlook holds on to past email addresses. My guess is that the users are responding to old emails that came from users back when the old system was in place and are therefore getting the old X400 addresses. This is sticking in Outlook's cache (again, note that I'm not an Outlook expert) and causing problems when they then attempt to send to that user again. So, two possible related solutions: 1. get rid of the X400 addresses if they are not necessary. We have only one Exchange server and are not likely to get another. Do we really need them? 2. Figure out how to turn off Outlook's caching of email addresses. How does one do that? Is there a way to do it via Active Directory GPO's? Thanks for any help, Matt _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
