NDR message from Exchange, status 5.1.3, action failed?

Question

Any message I attempt to send to any user on the server either from another user on the server or from an outside user is immediately returned undeliverable with the following message:

Reporting-MTA: dns;mydomain.com

Final-Recipient: unknown;[e-mail]
Action: failed
Status: 5.1.3

These users are already setup in "Active Directory Users and Computers" each with an Exchange mailbox. I've verified that I'm using the correct alias from within the "Exchange General" tab and that is the same alias as the SMTP e-mail address already specified in "E-mail Addresses" (except the e-mail address ends with the appropriate "@mydomain.com", specific to my actual domain).

I'm running Exchange on Microsoft Windows 2003 Small Business Server Standard.

Answer 1

Can your internal users send out?
If so, there's something out of whack with your addressing internally. Did you by chance recently migrate up to the SBS2003 server?
If so, send me a PM (click on my avatar) and let me know where the mail accounts used to be (internal or hosted/ISP), what platform they used to be on (Exchange 5.5?) and how you migrated them.

Also please try to generate an email via telnet and that will help determine where the transaction is failing...

From a client machine, open a command prompt and enter:

telnet myserver 25 (your server name goes there obviously, and the 25 indicates the port you want to access)
(you should get a Welcome banner here)
helo me
mail from:[e-mail]
rcpt to:[e-mail]
rcpt to:[e-mail]
data
type whatever you want following the data command then a hard return
.
(there's a dot there--- the dot closes the conversation)

I'm suspecting we will get an acknowledgement onscreen "Message submitted for queuing" but we may expose a different kind of failure using this manual message creation. The syntax is very particular--- careful where you put the : in the Mail From and RCPT to lines. And don't worry if the screen does not capture your keystrokes; there's a toggle in the command shell somewhere but unfortunately I don't remember what it is, so you may have to copy the command out, write a pause after each line, save it as a batchfile and run it that way. Post/PM the results...

Answer 2

no longer a competent signal. do somewhat digging a see how frequently those messages were happening. very few times, or some times a week. no matter if that's better than some cases you could also detect hidden e-mail address or contact being performed on the workplace. This little signal ought to resolve an entire mess that you do not even comprehend is going on in the back of your again.