jlavery
asked on
No such user here SMTP error when sending email to a new user in AD with mailbox.
i have a windows 2003/exchange 2003 system. I cretaed a new uer yestereday along with a mailbox in exchanghe. when i try to send this user a message from the outside i get SMTP error:
#5.5.0 smtp;550 <name@emaildomain.com> No such user here>
as i said before the mailbox is there, proven by optioon shown in exchange tasks on the user's properties. I had an internal user send a message and it made it there..
The mailbox does show up in ESM. the properties of the user show the proper name and email domain in email addresses user property.. Basics seems to be covered here unsure where to go from here..
#5.5.0 smtp;550 <name@emaildomain.com> No such user here>
as i said before the mailbox is there, proven by optioon shown in exchange tasks on the user's properties. I had an internal user send a message and it made it there..
The mailbox does show up in ESM. the properties of the user show the proper name and email domain in email addresses user property.. Basics seems to be covered here unsure where to go from here..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hypercat (Deb)
Are you using an antivirus/antispam appliance or outside service?
ASKER
Aware that it is not an exchange message but thought it to be an exchange related issue..
I received when sending from my ecxchange environment to theirs via the internet.
no AV SPAM appliance being utilized but we do have GFI mail essentials running on the exchange server..
I received when sending from my ecxchange environment to theirs via the internet.
no AV SPAM appliance being utilized but we do have GFI mail essentials running on the exchange server..
So this is outbound email? Not inbound?
If it is outbound then it cannot be Exchange at fault, unless the other side is running Exchange. It has to be something else causing the message - something that perhaps needs an updated user database?
Simon.
If it is outbound then it cannot be Exchange at fault, unless the other side is running Exchange. It has to be something else causing the message - something that perhaps needs an updated user database?
Simon.