Hello, on 10.03.2003 16:19, LuKreme at [EMAIL PROTECTED] wrote:

> 
> I use fetchmail to get my email off my SIMS server, and recently I got
> this message from fetchmail
> 
> fetchmail: reading message [EMAIL PROTECTED]:1 of 68 (224
> octets) fetchmail: message delimiter found while scanning headers
> 
> % telnet southgaylord.com 110
> 
> +OK Stalker POP3 Server 1.8b9d14 at southgaylord.com ready
> <[EMAIL PROTECTED]>
> user kreme
> +OK please send PASS command
> pass <something>
> +OK 69 messages in queue
> retr 1
> +OK Message follows
> Return-Path: [EMAIL PROTECTED]
> Received: from [206.159.154.3] (HELO dunkirkny.com)
> by southgaylord.com (Stalker SMTP Server 1.8b9d14)
> with ESMTP id S.0000568628 for <[EMAIL PROTECTED]>; Fri, 28 Feb 2003
> 17:57:31 -0700
> .
> dele 1
> +OK
> 
> and then everything was fine, and fetchmail retrieved all the messages.
> 
> How did this happen?  How can a invalid message be written to the
> mailbox?  How do I prevent it happening again?

There's nothing invalid about a message which consists of RFC headers only.
On the other hand, POP3 clients are not expected o parse message while
retrieving it and waiting for an empty line separating RFC headers from the
message body. All they should do (per POP3 standard description) is to
collect all the data till a 'single dot on a line per itself'.

The similar bug in POP3 implementation can be observed in Outlook Express 5
for MacOS.

-- 
Best regards,
Dmitry Akindinov

=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your reply.


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to