queue search

Hi

I have an internal user who tries to send an email but it does not reach the receipient. The logs show the following error:

17-Oct-2006 13:01:48.38 tcp_intranet tcp_localE 2089 user1@mycompany.com rfc822;outsider@anothercompany.net outsider@anothercompany.net host1 ([127.0.0.1])

17-Oct-2006 13:30:58.18 tcp_localQ 1205 user1@mycompany.com rfc822;outsider@anothercompany.net outsider@anothercompany.net mx0.anothercompany.net dns;mx0.anothercompany.net (TCP|10.1.4.2

|64443|83.111.83.35|25) (SMTP service ready) smtp;250 Requested mail action okay, completed Error writing SMTP packet

First, why the user does not receive any delivery failure notification?

2nd, I checked the queue and found using ./imsimta qm then top -to that 3 queued messages are being sent to outsider@anothercompany.com

I need to see the history of each message. But hist commands must be followed by the message id. Is there a method to get this id without scanning all queued messages :)

thanks,

[1029 byte] By [Linda_B] at [2007-11-26 10:51:11]
# 1

I was able to hist one of these 3 messages. Nothing much was displayed except:

Sun, 15 Oct 2006 13:44:19 +0100 (GMT)

Error writing SMTP packet

Sun, 15 Oct 2006 16:05:23 +0100 (GMT)

Temporary error from SMTP partner: smtp;421 SMTP service not available, closing transmission channel

Is it a network error? does it justify that my mail server does not notify my user about this error?

Also, I appreciate if u can give me a method to hist these 3 messages (having a pattern the to address) without scanning all queued messages.

thanks,

Linda_B at 2007-7-7 3:03:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

Hi Linda,

>> First, why the user does not receive any delivery failure notification?

The user will not receive a delivery failure notification straight away, but they should receive one some time later - in perhaps a day or so - depending on your notices keyword settings - refer to your imta.cnf file. If the message was rejected by the receiving host outright then they would have received a NDR email immediately, but in this case it's a failure to deliver.

>> 2nd, I checked the queue and found using ./imsimta qm then top -to that 3 queued messages are being sent to outsider@anothercompany.com

>> I need to see the history of each message. But hist commands must be

>> followed by the message id. Is there a method to get this id without

>> scanning all queued messages :)

It should be pretty quick just to do the following:

./imsimta qm

dir -env -to=outsider@anothercompany.com

then you can just run

hist 1

hist 2

hist 3

to get a history of those three messages that matches the pattern of the dir command.

>> Is it a network error? does it justify that my mail server does not notify my user about this error?

It appears from the info you have provided that the receiving server is having some problems processing email (Temporary error from SMTP partner: smtp;421 SMTP service not available). The "Error writing SMTP packet" could be due to a networking issue of some kind as well (i.e. the network/system receiving the email is so slow that the send timed out).

Given that the errors are 'temporary' this would explain why the user is not immediately notified.

Regards,

Shane.

shane_hjorth at 2007-7-7 3:03:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3

Hi Shane and thanks for the reply.

The notices keyword is found in ims-ms and defaults only:

defaults notices 1 2 4 7

ims-ms notices 1 7 14 21 28

I assume here that notices settings in ims-ms will take effect (Why not defaults?)

Also does it mean that the user will receive notification on the 1st day then 7th, then 14...as long as the message is still in the queue?

thanks,

Linda_B at 2007-7-7 3:03:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 4

Defaults settings will work on any channel that does not have a notices keyword in place.

ims-ms is just for delivery to your internal users on this machine. Since ims-ms delivers to local disk, and people sometimes are over quota, it's a good idea to have different values for the notices keyword than on smtp channels.

for outbound messages, users will get notices after

1 day

2 days

4 days

7 days the message will be dropped.

for ims-ms, the sender will get notification at

1, 7, 14, 21 and the message will be returned at 28 days.

jay_plesset at 2007-7-7 3:03:54 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...