Error Reading Smtp Packet Response To Dot Stuffed Message Expected
ProgramVMS Auth Module Support Home » Service & Support » PMDF Support » PMDF FAQ » PMDF FAQ: Troubleshooting Why do I see "Recorded error -- Zero length SMTP status line" error?PMDF is expecting the remote system to contain valid SMTP status code when it does not have it.This error can be found in your mail.log_current file as well as in debug files and TCPdump files.All SMTP status lines are required to begin with three digits, followed by a space or dash, then an optional status message. Having an SMTP status line containing no characters is a protocol violation. The usual suspect is an extraCR or LF just before a status. PMDF treats this as a temporary error and attempts to send the mail again.This is a problem on the server end (usually from firewall software, or some Exchange servers); however, PMDF can handle this broken behavior. All you need to do is specify the smtp_crlf or smtp_lf channel keyword rather than the default keyword smtp_crorlf (smtp is synonymous for the smtp_crorlf keyword), and PMDF no longer treats bare CRs as a terminator. A single CR or a single LF is treated as a "normal" character. Process Software recommends using the keyword smtp_crlf since RFC 821 (section 4.1.1) says that lines should be terminated by a single CRLF sequence.There are some SMTP servers that use LF-only terminators. However, bare CR terminators are quite rare. You needto choose between supporting the agents that use bare CRs and LFs as line terminators or supporting the ones that use them as regular characters. In general, you can not support both.Unfortunately, this is not addressed in current RFCs. RFC821 says that lines should be terminated by a single CRLF sequence, but does not say anything about the interpretation of bare CRs and LFs. Some clients break the rules and use either LF or CR alone instead of CRLF together. So PMDF tries to deal with this by treating these as line terminators (as noted above, this treatment is configurable). The problem is that other agents expect bare CR or LF NOT to be interpreted as a terminator.Newer versions of PMDF have code that ignores such things in status responses, so one way to avoid the problem is to upgrade.Sometimes my email will back up with several hundred jobs that need to be processed, but my system resources are free. What can I do to prevent this?One of the ways of improving throughput is by adding additional queues. By default, all mail gets queued to one queue and is processed from there. On VMS, the queue is MAIL$BATCH, which is a
V6.2-X17; linked 13:01:07, Sep 8 2003I've been getting the following errors from some users, and waswondering if someone could shed some light on whast the meaning is?Delivery attempt history for your mail:Wed, 18 Feb 2004 22:49:20 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expectedWed, 18 Feb 2004 18:48:04 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expectedWed, 18 Feb http://www.process.com/psc/service-support/pmdf-support/pmdf-faq/pmdf-faq-troubleshooting/ 2004 14:48:02 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expectedWed, 18 Feb 2004 10:46:43 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expectedBill Stewart :-)Kaman Corporation1332 Blue Hills AvenueBloomfield, Connecticut, 06002(860) 243-7058 Steve +1 608 278 7700 2004-02-19 17:08:11 UTC PermalinkRaw Message Post by http://vmsnet.mail.pmdf.narkive.com/Qy0RuiIL/response-to-dot-stuffed-message-expected Stewart, BillPMDF version is PMDF V6.2AlphaServer 1200 5/400 4MB running OpenVMS Alpha V7.3-2PMDF_SHARE_LIBRARY version V6.2-X17; linked 13:01:07, Sep =8 2003Post by Stewart, Bill=09I've been getting the following errors from some users, and waswondering if someone could shed some light on whast the meaning is?=20Wed, 18 Feb 2004 22:49:20 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expecte=dPost by Stewart, Bill=20Wed, 18 Feb 2004 18:48:04 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expecte=dPost by Stewart, Bill=20Wed, 18 Feb 2004 14:48:02 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expecte=dPost by Stewart, Bill=20Wed, 18 Feb 2004 10:46:43 -0500 (EST)Error reading SMTP packet; response to dot-stuffed message expecte=dThis means your sending MTA sent a DATA command, got a positiveresponse, then sent the message contents. However, it did not receiv=e a"250 OK" response to the "dot-stuffed message"
remote SMTP server" The emails are delayed for later delivery... that is if they ever get delivered... Anybody got a clue of what could be causing http://osdir.com/ml/mail.ims.general/2007-02/msg00070.html this error other than network issues? Why do you assume it isn't a problem with the network or the remote server? This error occurs when the SMTP client is http://www.freelists.org/post/msexchange/error-reading-SMTP-packet,11 able to transfer the entire message but no response indicating that the server has accepted responsibility is received within the (normally extremely generous) time allowed. It is axiomatic error reading that in such cases there is practically no information about the problems specifics to be had on the client end. Determination of problem specifics must therefore be done by looking at the network and/or the server to see what is going on. Ned Thread at a glance: Previous Message by Date: Re: Brightmail configuration question Hi, first error reading smtp you might want to download brightmail 6.0.4 it is much better... As for the group policy, just set it to Modify -> prepend to subject you might want to write "SPAM" in the text box. This http://docs.sun.com/app/docs/doc/819-2650/6n4u4dtr9?a=view Should help you out. Good luck On 11/28/06, Un Spam
03:35:42 -0800 (PST) Hi Nathan, As you told me I set "no fixup protocol smtp" and after about 1 month it seems that the problem has been fixed and nobody has complained about that. Thanks in advannced. --- Nathan Kodak