Add smtp address will not work, Exchange 2007 Version: 08.01.0240.006
http://technet.microsoft.com/en-us/library/bb123794(EXCHG.80).aspxA woman where I work recently got married so we are trying to add a smtp address for her user but mail sent to that address keeps being returned 550 unknown user. We can send internal mail to this address but not external mail. I reviewed the above article to insure that I was not making some silly mistake, but that is the exact procedure I am following. I tried making two different alternate addresses for this user but they both get rejected. I made an alternate address for myself and and have the same problem. The domain on the alternate address is the same as the primary. We use a forefront edge server as a virus/spam gateway. Is it possible that it is not syncronizing with exchange? We have made alternate addresses in the past without problem. Any suggestions?
February 12th, 2010 10:57pm

Hub Transport EMStest-edgesyncronization
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2010 5:13am

When I do Test-EdgeSynchronization I getconnection result failed failure detail the supplied credential is invalidWhen I google this error I find that the certificate used by ADAM is invalid and that I have to remove it and replace it with a new one. This seems to be related to Active Directory which would make sense as my domain controller failed last year which may have caused the problem. My problem is that I don't understand this process very well and I have not yet found instructions that are detailed enough to follow.
February 15th, 2010 4:31pm

Your DC failure is probably not an issue. It's more likely your certificate has expired. run get-exchangecertificate | fl on the hub/edge servers and see if the certs look like they've expired.
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 4:41pm

I ran get-exchangecertificate on the exchange and edge server and no date is displayed, but there is no message that they are expired. How would I tell?
February 15th, 2010 5:05pm

Try setting your edgesync back up.Run new-edgesyncronization from your edge server, copy the resulting .xml file to your HT server, and use that to set up a new edge sync on the HT.
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 5:11pm

OK. I run new-edgesynchronization from my edge server, where/what name does it save the .xml file?I copy it to my HT server, (Hub Transport?) This is my exchange server, correct? Copy it to where?Use that to set up a new edge sync - How?Sorry, but I am not familiar with this process. I never used an edge server before this.
February 15th, 2010 9:14pm

Did it prompt you for a filename when you did the new-edgesync from the Edge server? That will be your .xml file.
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2010 1:11am

On Mon, 15-Feb-10 18:14:18 GMT, sbdt wrote:>OK. I run new-edgesynchronization from my edge server, where/what name does it save the .xml file?It saves the file where you tell it to:new-edgesubscription -filename <fill-in-the-file-path>>I copy it to my HT server, (Hub Transport?)Yes.>This is my exchange server, correct? It's one of your Exchange servers.>Copy it to where?Put it someplace where you'll remember where it is. It doesn't matterwhere, just as long as you know where it is when you need it.>Use that to set up a new edge sync - How?Sorry, but I am not familiar with this process. I never used an edge server before this.Before you create a new edge sync, you should know that your inbounde-mail is going to stop working for a while. It might be a good ideato shut down the inbound port until things are back on-track.On the edge server, run "remove-edgesubscription<name-of-edge-server>" on the edge server.On the Hub Transport, use the EMC and select the "Hub Transport" itemin the "Organization Configuration". Then click "Remove" in the actionpane.Now click the "New Edge Subscription..." in the action pane and browseto where you placed that edge subscription file.If it all works out you'll see a success in thetest-edgesynchronization cmdlet. If you do, runstart-edgesynchronization and when it's done you should be able toreopen port 25 at the firewall.---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
February 16th, 2010 2:08am

Also, Edge servers usually live in a DMZ, which can complicate copying a file to a server on the internal network. You can use Powershell and the send-mailmessage cmdlet (if you have v2), or a script tht uses the .net mailmessage and smtp clients if you have V1. Just use localhost as your relay host, and email the .xml file to yourself as an attachment.
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2010 2:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics