Trying to understand SMTPSend logs

I'm trying to check out emails a client is sending out and I'm going through the Send logs.

They have an SBS 2008 server and XP Pro clients.

The messages to me, which I have received end:

221 Goodbye
Local

Messages I think haven't been delivered end:
221 gateway.otherdomain.co.uk Service closing transmission channel,
Local
 
221 hal-ironport-1.halfords.co.uk
Local

221 2.0.0 closing connection e43si126978ert
Local

I would have thought the second one was ok but the sender is convinced it hasn't been received.

Could somebody please help me understand these messages,

Thanks,

Mike

mikeabc27Asked:
Who is Participating?
 
ShrColConnect With a Mentor Commented:
Pretty much. 250 code means that that part of the send is OK. You can see from the log that it 250's all input sent from your server, and then closes with the 221. If a message follows that pattern it sent. Otherwise, you would get a negative response from the receiving mail server at some point. Usually those messages are clear enough to understand the issue.

Its possible that the message once received by the recipients mail server was dropped into a junk mailbox or similar, but there's noway you can tell if that's the case. Your server did its bit correctly.
0
 
ShrColCommented:
http://www.answersthatwork.com/Download_Area/ATW_Library/Networking/Network__3-SMTP_Server_Status_Codes_and_SMTP_Error_Codes.pdf

As per the above, code 221 means that the session is closing. It on its own does not indicate successful mail transmission. Can you paste a little more of the logs for one of these messages?
0
 
mikeabc27Author Commented:
Thanks ShrCol, I've attached one of the ones that failed.
smtpsend.txt
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
mikeabc27Author Commented:
OK I've read the link and the 221 reply doesn't really tell us much, how can I check if it has been delivered?
0
 
ShrColCommented:
All looks good to me, the receiving mail server sends back an acceptance code (250) for both sender and recipient. It then accepts the message and queues it up:

2010-04-29T08:07:37.806Z,Windows SBS Internet Send ourserver,08CCB4F8EEC047E5,18,192.168.0.100:48193,21x.3x.1xx.1xx:25,<,250  Queued mail for delivery,

You then see the 221 code as the session is closed. I would say that message was sent fine, of course the receiving mail system may have had an issue but it left your server fine.
0
 
mikeabc27Author Commented:
Thanks ShrCol, so if I get the 250 codes and nothing to say something along the lines that it is suspected to be spam, I know it has been dellivered?
 
0
 
mikeabc27Author Commented:
Thanks ShrCol, I am always adjusting settings to let reports picked up as spam INWARDS.
I'd be really grateful if you could look at one last log. This is where an email was sent to the blueyonder and not received, but the cc to domain2 was received and forwarded ok to the blueyonder mailbox.
Is there an issue with blueyonder?

smtpsend2.txt
0
 
ShrColCommented:
Thats a slightly odd one. It starts sending the message initially then comes up against an SSL certificate it seems, then just stops - perhaps a time-out. The second message, or CC, is then sent to other recipient correctly.

It seems that Google's mail servers are handling Blueyonder.co.uk email now.
0
 
mikeabc27Author Commented:
excellent help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.