Email woes...

hi,

recently there had been complaints about outgoing mail to be received only hrs later and i realized that most are stuck in queue, not sure for what but they will eventually be sent off, only hrs later...i enabled logging and turned on master_debug for tcp_local channel and can see some transactions encountering smtp routine failure and network read failures...

tcp_local definition:

tcp_local smtp mx daemon mailserver1.abc.com remotehost inner switchchannel identnonelimited subdirs 20 maxjobs 7 pool SMTP_POOL

maytlsserver maysaslserver saslswitchchannel tcp_auth logging master_debug

A failed job on master_debug log:

16:34:18.23: Index into reply string = 9

16:34:18.23: Enhanced status code string: "2.1.5"

16:34:18.23: Got status : "250 2.1.5 <denise.provencher@us.fujitsu.com>... Recipient ok"

16:34:18.23: Index into reply string = 9

16:34:18.23: Enhanced status code string: "2.1.5"

16:34:18.23: Got status : "354 Enter mail, end with "." on a line by itself"

16:34:18.23: Enhanced status code string: "Enter"

16:34:18.23: Write message header/body in one go

16:34:18.25: ... Message header/body, 418 lines ...

16:34:18.25: Sending: "."

16:45:18.26: smtp_pmt_read: [0x0000000b] network read failed

16:45:18.29: smtp_pmt_close: [0x0000000b] status 0

16:45:18.29: SMTP routine failure on file: /local/iplanet/ims/server5/msg-mercury/imta/queue/tcp_local/019/ZZ0J6Z009LJUFB0 H.00

16:45:18.29: Recorded error -- Error reading SMTP packet; response to dot-stuffed message expected

16:45:18.29: Shutting down message dequeue and any open connections

16:45:18.29: End of processing list, connections closed.

Can someone please tell me why this happened? it does not happen for every single email but it does happen quite often, and hence the queue gets clogged...Any help is appreciated. Thanks in advance...

Sj

[1972 byte] By [cypher9] at [2007-11-26 10:44:14]
# 1

Recorded error -- Error reading SMTP packet; response to dot-stuffed message expected

means:

Se sent a message. We ended the send with a dot ".", on a line by itself. We expected to get an acknowledgement back, so we could gracefully end the transmission.

We got nothing back.

that means that

the other server is broken

the ack got lost in a network problem

the other server didn't really get all the message

so we will retry.

jay_plesset at 2007-7-7 2:56:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

Jay,

THanks for the reply, it helped alot (at least in trying to narrow down the problem)...In your reply it seems that it could be one of the 3 issues you've listed. For the 3rd possibility (other end didn't get all messages) - will this mean my end didn't finish sending everything it needs to or can I assume from the error when it says "dot" expected, that means it has already sent out everything it should and done its job, hence waiting for an answer or acknowledgement? THanks again for your help...

Sj

cypher9 at 2007-7-7 2:56:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3
slight correction.It says, "response to dot expected".Messaging sent the whole thing. Sent the dot. Got nothing back. Waited. Timed out.
jay_plesset at 2007-7-7 2:56:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 4

Hi,

As Jay explained, messaging server expects to see a "250 2.5.0 Ok." or similar to the sending of the body of the email (after the final ".") to confirm that the receiving mail-server has accepted the email and we can delete it from our queue.

In this case that response has not occurred. So we have kept the email and will retry the email later.

This issue needs to be followed up with the *receiving* messaging server - as Jay noted there can be a number of causes including:

- I/O issues, messaging server for example must write a message to disk before it returns the 250 OK message.

- Filtering problems, some messaging server software scans an email for virus/spam content before returning the 250 OK message (so they can reject-before-accept), this can result in substantial delay which causes a timeout

- Network issues, messaging server has pushed the data through but network issues have delayed the return of the 250 OK.

Regards,

Shane.

shane_hjorth at 2007-7-7 2:56:14 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...