SMTP Errors

Hi,

I am having some problems with bounced emails with 555 error the smtp logs
show the following

250 0 35 32 0 SMTP - - - - This was a successfully delivered message

250 0 30 27 0 SMTP - - - - This was bounced

I know 250 shows a good connection but does anybody know what the rest of
the codes mean??

Best regards

Peter


--
Best regards

Peter

Peter wrote:

>Hi,
>
>I am having some problems with bounced emails with 555 error the smtp logs
>show the following
>
>250 0 35 32 0 SMTP - - - - This was a successfully delivered message
>
>250 0 30 27 0 SMTP - - - - This was bounced
>
>I know 250 shows a good connection but does anybody know what the rest of
>the codes mean??

Field names are at the top of the log file. But none of those values have
any relevance to the outcome of a particular message - the 250 is the SMTP
status for the line, and indicates that that portion of the SMTP
conversation occurred without error. You need to look at the set of lines
that comprise the entire SMTP conversation to ascertain why a particular
message failed - you can't use the log entries in isolation.

--
Steve Foster
------------
Please reply only to the newsgroups.
For SSL Certificates, Domains, etc, visit.: https://netshop.virtual-isp.net

Peter wrote:
> Hi,
>
> I am having some problems with bounced emails with 555 error the smtp logs
> show the following
>
> 250 0 35 32 0 SMTP - - - - This was a successfully delivered message
>
> 250 0 30 27 0 SMTP - - - - This was bounced
>
> I know 250 shows a good connection but does anybody know what the rest of
> the codes mean??
>

What Steve said... but you need more to go on, those codes aren't
especially useful. Turn up logging to maximum, at least for the duration
of this problem:

This is done in the Exchange Manager, in
Servers-><your server>->Protocols->SMTP->Default SMTP Virtual Server
and then Properties. On the General tab, tick Enable logging, click
Properties, note the file location, then on the Advanced tab, tick
everything and OK it all.

After you do this, you can see the actual SMTP handshaking for any
email, which includes any error messages. If the information you
get from the queues and the Message Tracking isn't enough to solve
a problem, the SMTP details should be. At the very least, you can
see which receiving mail server was involved, and can contact the
organisation and discuss the matter.

Here's a typical outgoing transaction with all log fields enabled
(both IP addresses are private as this is journalled email to another
in-house mail server). The initial connection to port 25 of the
receiving server is not logged. Some handshake commands and responses
may vary, depending on the capabilities of the two servers.

Mail servers normally use either UTC or local time with the timezone
offset appended. Be careful of that if you're comparing logs from two
sources: here, Exchange uses UTC and Exim uses local+offset.

2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - -
220+debian.domain.com+ESMTP+Exim+4.50+Thu,+26+Jul+ 2007+01:02:18++0100 0
0 76 0 110 SMTP - - - -
(receiving server identifies itself, and usually the SMTP server software)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionCommand SMTPSVC1
NEWSERVER - 25 EHLO - domain.com 0 0 4 0 110 SMTP - - - -
(sending server identifies itself: really, the HELO/EHLO string should
match the MX and PTR records rather than just be the domain name, but
this SBS sends via smarthost and it doesn't matter too much.)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - - 250-debian.domain.com+Hello+newserver+[192.168.1.2] 0
0 58 0 110 SMTP - - - -
(receiving server accepts connection, notes IP address of sender)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionCommand SMTPSVC1
NEWSERVER - 25 MAIL - FROM:<>+SIZE=1077 0 0 4 0 110 SMTP - - - -
(sender is empty, but this is Exchange itself, not a user. Also size of
message: not mandatory, but polite, will save time later if the message
is too big)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - - 250+OK 0 0 6 0 110 SMTP - - - -
(OK, we'll accept one that big, from that sender)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionCommand SMTPSVC1
NEWSERVER - 25 RCPT - TO:<> 0 0 4 0 110 SMTP -
- - -
(recipient email address)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - - 250+Accepted 0 0 12 0 110 SMTP - - - -
(OK, we'll accept mail for them: either they have a mailbox here or we
agree to relay for them)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionCommand SMTPSVC1
NEWSERVER - 25 DATA - - 0 0 4 0 110 SMTP - - - -
(ready to send, are you ready to receive?)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - -
354+Enter+message,+ending+with+"."+on+a+line+by+it self 0 0 54 0 110 SMTP
- - - -
(go ahead)

[data is now sent with the trailing empty line and .]


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - - 250+OK+id=1IDqo6-0006Lh-Ns 0 0 26 0 125 SMTP - - - -
(OK, we got it: here's a message ID to quote if there's trouble)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionCommand SMTPSVC1
NEWSERVER - 25 QUIT - - 0 0 4 0 141 SMTP - - - -
(that's all for now)


2007-07-26 00:02:18 192.168.1.252 OutboundConnectionResponse SMTPSVC1
NEWSERVER - 25 - - 221+debian.domain.com+closing+connection 0 0 47 0 141
SMTP - - - -
(OK, bye for now)

The exact messages vary as they are configurable in each mail server.

--
Joe