Is qmail dropping connection?

We're running qmail and occasionally a message is received
with a mangled Message-ID header which causes the connection
to drop when an attempt is made to retrieve the message.

Example:

If I do a telnet session on port 110 do a TOP command, I get this:

top 3 99
+OK headers follow.
Return-Path: xqazvwmx@yahoo.com
Delivered-To: xxxxxx
Received: (qmail 4795 invoked from network); 26 Jan 2004 18:25:26 -0000
Received: from defense-3-81-57-218-75.fbx.proxad.net (81.57.218.75)
by xx.xx.xx.xx with SMTP; 26 Jan 2004 18:25:26 -0000
Received: from 218.96.235.206 by 24.17.8.111; Mon, 26 Jan 2004 23:33:08 +0500
Message-ID: <D[20
..

Notice how the Message-ID header is truncated and there is no data after what is shown.

However, when I do a RETR command as an e-mail client would do, I get this:

retr 3
+OK 362 octets follow.
....connection lost...

Is this or has this ever been an issue with qmail? I've looked high and low and
can find nothing regarding this kind of behavior.

Thanks.

S> Is this or has this ever been an issue with qmail?

No.

S> I've looked high and low and can find nothing regarding
S> this kind of behavior.

Then that's your answer, isn't it? (-:

Show us the script that performs your POP3 service. Tell us what mailbox
format you are using. Read the message directly out of the mailbox and
confirm that it is actually there in the first place.

Hello,
I too have been experiencing the same problem.
Client calls indicating that they cannot check
eMail. To solve, we have to locate the message and remove it.
We have had this problem randomly for about 5 months.

OS: FreeBSD
Plesk 6.0.2

This is the actual (domain and IP's Changed) mail
message in clients inbox. (mdir format)
Notice the Message-ID is truncated.

-----snip-----
Return-Path: <rccnxmsrwttsm@xxxxx.com>
Delivered-To: 201-peamail@myClientsDomain.com
Received: (qmail 80111 invoked from network); 28 Jan 2004 04:03:44 -0000
Received: from unknown (HELO 11.22.33.44) (200.103.43.17)
by xx.domain.com with SMTP; 28 Jan 2004 04:03:44 -0000
Received: from 11.22.33.44 by 11.22.33.44; Wed, 28 Jan 2004 09:02:35 +0500
Message-ID: <T[20
-----end-----

Jonathan de Boyne Pollard <J.deBoynePollard@Tesco.NET> wrote in message news:<4018EB00.AEC7D052@Tesco.NET>...
> S> Is this or has this ever been an issue with qmail?
>
> No.
>
> S> I've looked high and low and can find nothing regarding
> S> this kind of behavior.
>
> Then that's your answer, isn't it? (-:
>
> Show us the script that performs your POP3 service. Tell us what mailbox
> format you are using. Read the message directly out of the mailbox and
> confirm that it is actually there in the first place.

j> This is the actual (domain and IP's Changed) mail
j> message in clients inbox. (mdir format)

Are those the _complete_ contents of the file ? If so, then the place to look
now is what wrote those contents and whether it wrote what was actually
received.

Show us what delivered that message in the first place. Show us the delivery
instruction in the relevant ".qmail" file, or the default delivery
instruction, whichever is appropriate. Also show us the SMTP Relay server and
"qmail-send" logs that apply to the receipt and processing of that particular
message.

"jprince" <johnp@ktro.com> wrote in message
news:287e3614.0401311309.31863996@posting.google.c om...

> I too have been experiencing the same problem.

> Message-ID: <T[20
> -----end-----

This jibes with my experience. Qmail has a pretty obvious bug here.
I have four different examples of messages that exhibit this behavior
and the common thing with them is this odd set of characters in the
mangled Message-ID header.

The message arrives with headers only (no body text) and ends with
the zero in the Message-ID header.

The following is a dump taken directly from the messages as stored on
the server's disk. I have skipped the preceding headers, and what
is shown is the final part of each message. There is a 0X0A (LF) byte
following each zero, and that's the end of the message.

Message-ID: <D[20
Message-ID: <A[20
Message-ID: <A[20
Message-ID: <Z[20

These messages will cause Qmail to drop the connection.

S> These messages will cause Qmail to drop the connection.

No, they won't. Apart from escaping '.' lines in the message body (which is
irrelevant here since we are deling with messages that don't actually have a
body), "qmail-pop3d" is agnostic as to message content. As I said, show us
the script that performs your POP3 service.

"Jonathan de Boyne Pollard" <J.deBoynePollard@Tesco.NET> wrote in message
news:401D0A3C.96BF9BD4@Tesco.NET...
> S> These messages will cause Qmail to drop the connection.
>
> No, they won't. As I said, show us the script that performs your POP3 service.

Of course it will, and there is ample proof of it right here. Why are you so
reluctant to see it? Maybe you missed the original post. This behavior can
be demonstrated without the use of any e-mail client. All you have to do is
perform a manual session as shown below:

If I do a telnet session on port 110 and do a TOP command, I get this:

top 3 99
+OK headers follow.
Return-Path: xqazvwmx@yahoo.com
Delivered-To: xxxxxx
Received: (qmail 4795 invoked from network); 26 Jan 2004 18:25:26 -0000
Received: from defense-3-81-57-218-75.fbx.proxad.net (81.57.218.75)
by xx.xx.xx.xx with SMTP; 26 Jan 2004 18:25:26 -0000
Received: from 218.96.235.206 by 24.17.8.111; Mon, 26 Jan 2004 23:33:08 +0500
Message-ID: <D[20
..

Now, if I do a RETR command, I get this:

retr 3
+OK 362 octets follow.

....connection lost...

S> These messages will cause Qmail to drop the connection.

JdeBP> No, they won't. [...] As I said, show us the script
JdeBP> that performs your POP3 service.

S> Of course it will, and there is ample proof of it right here.

You haven't proven anything. You haven't even shown us what software you are
using for your POP3 server or how you are employing it. Tell us what patches
you applied. Show us the script that performs your POP3 service.

That's three times now that I've said that. How many times do you have to be
told this before you do it ?

S> Maybe you missed the original post.

Pay attention. I _replied_ to the original post.

"Someone" <someone@somewhere.org> wrote in message
news:101qjidasfbbmbc@news.supernews.com...

Additional information:

If I go in and manually add data after the malformed header like this
(I add the X-Anything header):

Return-Path: xqazvwmx@yahoo.com
Delivered-To: xxxxxx
Received: (qmail 4795 invoked from network); 26 Jan 2004 18:25:26 -0000
Received: from defense-3-81-57-218-75.fbx.proxad.net (81.57.218.75)
by xx.xx.xx.xx with SMTP; 26 Jan 2004 18:25:26 -0000
Received: from 218.96.235.206 by 24.17.8.111; Mon, 26 Jan 2004 23:33:08 +0500
Message-ID: <D[20
X-Anything: abc

Then Qmail will work fine. But if the end of the message is the malformed
header ending in [20 then Qmail crashes every time in response to a RETR
command.

I am having the same issue. Here is what one tech guy said to me....

The person asking the question says certain things that are incorrect
For instance, he ( Someone ) says that the e-mail makes QMail crash
QMail did not crash. It correctly delivered the message to his box, an
kept on rolling, just like yours does. He then submits a telnet sessio
which ends in 'connection dropped'. First, this is the POP server, no
the qmail SMTP server, and further, I've included my own session whic
shows that your POP server does not drop the connection. This proble
is really an issue between the spammer who is sending you thes
messages and Microsoft, whose mail client does not handle it very well
Unfortunately, there's nothing anyone can do but delete the message an
keep going.

Is this the only solution? Is there a way for qmail to automaticll
delete theses messages when they arive

dakn
-----------------------------------------------------------------------
Posted via http://www.webservertalk.co
-----------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message102539.htm