TAG the DNG said:
Thanks for the response - if you haven't guessed, the DNG stands for Dumb
New
Guy.
The message is from "System Admionistrator" it says:
Your message did not reach some or all of the intended recipients.
503 Valid RCPT TO <receipient> must precede DATA
Wish I could tell you more but that is the whole message.
TAG the DNG
The SMTP protocol requires that all recipients be specifed by RCPT TO
commands, one command for each recipient. That is followed by a DATA
command that sends the content of your message (which is ALL of your
message, headers and body). The headers are NOT used from the message body
because that is data. That's how spammers falsify from whence their e-mail
originates. You may have many recipients but only one copy (in the DATA
command) of the message gets sent to the mail server. The mail server then
doles out a copy to each recipient.
The e-mail client will compile an aggregate list of recipients from its
From, To, and Bcc fields. It then uses that list to send a RCPT TO command
to the mail server for each recipient. The recipients must be specified
before the DATA tells the mail server what to send those recipients.
Since you say it is a message that you receive rather than an error that
occurs *during* the mail session between your e-mail client and the mail
server, it is a separate and new message that is being sent back to you. It
could be from your own mail server. It could be from the receiving mail
server. You didn't say. If your mail server found the RCPT-TO and DATA
commands were out of order from your e-mail client, you would get an
immediate error during the mail session. So it not likely that your mail
server would miss that during the mail session and then send you a new
e-mail about it later. More likely is that the receiving mail server is
complaining about the wrong order for the commands, and the commands it
received would be from your mail server. So you will need to contact your
e-mail provider (Qwest or Pargin) to tell them their SMTP server is screwing
up by issuing the SMTP commands out of order.
You could turn on the troubleshooting log in Outlook to check the order of
the SMTP commands that Outlook sends to your mail server but I doubt Outlook
is the one screwing up. Have you tried a different e-mail client, like
Outlook Express? Have you tried disabling e-mail scanning in your
anti-virus program?
It is not a problem with Outlook. It is a problem with your mail server.
I've heard this could be caused by a sendmail relaying problem (sendmail is
a mail server). Hopefully the only relaying being performed is across the
mail server's domain to load balance the influx of mails across multiple
regionalized hosts; otherwise, relaying can be abused and such misconfigured
or deliberately open relays get blacklisted as spam sources.