Secondary SMTP address problems. 2

[Albion]

I am in the process of migrating my Exchange 2003 server to an Exchange 2007 server installed on Windows Server 2008.

A few months back we made a policy change from using <first initial><last name>@domain.com to using <first name>.<last name>@domain.com. To resolve the issue of losing e-mail from customers who hadn't yet changed their address books, I added a secondary SMTP address to my user's exchange 2003 profile containing the old e-mail address. Everything worked great, until I upgraded to Exchange 2007 and moved user mailboxes over. Now the secondary address (the one not set as the reply address) is still visible in Exchange Manager -> Recipient Configuration -> Mailbox -> Properties -> E-Mail Addresses -> SMTP, but when I attempt to send an e-mail from my gmail account to the secondary address I get a bounce "550 550 5.1.1 <user@domain.com> User Unknown" from Exchange. This issue happens with any mailbox that has more then one SMTP address. Any ideas?

thanks

-Craig

 

[58sniper]

Just to verify, the right side of the addresses (@domain.com) stayed the same, right? If not, you'll need to make sure both domain names appear as accepted domains in EMC/EMS.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Zelandakh]

Do you have an edge server or anti spam / hygiene server in between or does it hit Exchange directly?

 

[Albion]

58sniper:
All of the addresses are @domain.com.

Zelandakh
The e-mail first goes through a Sendmail server on our Linux firewall which reads blacklists then forwards email into my Exchange server. It then goes through Scanmail from Trend Micro for Anti-Virus and Spam. Once it's inside the users outlook mailbox it goes through SpamBayes.

I've never had a problem with these secondary e-mail addresses and blacklists, anti-virus, or anti-spam. The fact that none of the secondary e-mail addresses attached to my 25 Exchange users work, yet their primary addresses work fine eliminates anything in between being the problem in my mind. Or does it?

The only thing that has changed is the Exchange Server Version and the Operating System.

Here's how I'm making the Migration. I first installed Server 2008 x64 and Exchange 2007 sp1. I added Exchange 2007 to my Existing Exchange 2003 (on Server 2003) organization during the install. Next I used the move mailbox feature in Exchange manager to move the mailboxes from the old 2003 server to the 2007 server. This is where I currently am in the migration. My intention is to get all of my Exchange 2003 data moved over to the 2007 server, then decommission the Exchange 2003 server. Once that is finished I can begin converting all of the Contact lists over to the new server.

On a side note: As much as I'd love to take a class on Exchange 2007 (as I did with 2003) the current economic condition and spending freezes have limited me to internet forums and Technet. I know everyone has RTFM on the tip of their tongue right now, but I really do appreciate all the help I've received in forums like this one. You guys are an indispensable resource to any Exchange Administrator. If you know of any good guides that might help me solve these problems outside of Microsoft and Technet I'd really appreciate it.

thanks

 

[58sniper]

You'll certainly want to read this series:

Transitioning from Exchange 2000/2003 to Exchange Server 2007

http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html

Do any of your hygiene solutions do recipient filtering? Wondering if it can't read the secondary address.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Zelandakh]

Now that I see the background, I'd start looking at the connectors. You may have a restrictive connector that is causing the problem.

 

[Albion]

Thanks to you guys I've been able to get my entire 2003 server transferred to the new 2007 server. All I have left to do now is decommission the old server. I had some problems with the public folders but since the only thing that's been used in 5 years are the address books, I just recreated it. Thanks for all the help!

 

[Zelandakh]

Thanks for the feedback. Glad you got it sorted. Beware of removing the 2003 server as it will be the last server in the admin group - there's a big article on msexchange.org about the steps needed to do it without everything going wrong.

It sounds like a simple thing but I wouldn't remove the last server without referring to that as a recipe.

 

[Albion]

Great call on the msexchange.org article. Thanks for the tip. One problem though. We I go to move the Public Folder Store Replicas I keep getting "The object is no longer available. ID no: 80040e19." This all seems to be related to the same problems I was having with that information store in the first place. I've again searched technet and google and usenet, etc... I'm just reading the same articles all over again. But none of them seem to fit my problem.

So I am wondering, can I just dismount the store as a replacement to deleting it? If I must delete it, is there a way I can force it's deletion? I don't care about the data within the public folder store so that's not an issue. I am worried though about problems a forced deletion of the old store may have with my new server.

Thanks again.

 

[Zelandakh]

Dismounting will make it unavailable but still in the container and the server will still be there and so on.

Ideally you'd need to fix the 0e19 error and carry on with that article. Yes, technically you could dismount though you aren't removing it, just making it inaccessible.

 

[Albion]

New information. Hmmmm, after doing a lot of digging I am finding that it's BAD NEWS to demote a DC to a member server when it has IIS running. Well, I did just that. My Exchange Server (with IIS) was a DC until I demoted it. I'm kinda assuming that might be my problem. *slaps forehead*

 

[58sniper]

You can never promote or demote a DC running Exchange server. Doing so breaks Exchange. For good, I believe.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Albion]

Well, unfortunately I did demote the DC to a member server. I know I have to decommission it properly, but what if I can't?

 

[58sniper]

Your Exchange is broken. When it's installed on a DC, it will only use that server as a GC/DC.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Zelandakh]

OK, this doesn't always work.

Promote the server again to be a DC.
Install Exchange over the top - you may need to use /disasterrecovery switch.
Uninstall Exchange.
Remove IIS, SMTP and NNTP as applicable.
Demote server.

The other option is your old friend ADSIEdit at which point you might also be better off replacing the DC.

 

[Albion]

Well well well. I ended up opening a support ticket with Microsoft for some other problems. Turns out demoting that DC to a member server caused all kinda of problems, from Certificate Authority to missing permissions on objects. After MS got everything else working I was able to demote and uninstall Exchange 2003 by following that article you all gave to me.

The only problem is that even though I removed the connectors from 2003 Exchange Manager, I am still showing a Send Connector to the old server in 2007 Exchange Management Console. Can I delete that send connector now that Exchange 2003 is uninstalled? I am surprised it didn't go away when I deleted it in the old Exchange Manager.

Thanks again guys, you've been a HUGE help to me.