Re: [fetchmail-devel] [art666@poczta.onet.pl: Bug#322683: fetchmail can't get some "special" messages from pop3 o2.pl]

[Brian C. <B.C...@po...>]

On Fri, Aug 12, 2005 at 12:45:27PM -0400, Rob Funk wrote:
> Brian Candler wrote:
> > IMO this is definitely a fetchmail bug.
> >
> > fetchmail should read data until \r\n.\r\n which marks the end of the
> > message. Even though RFC1939 insists that the size from a 'LIST'
> > command needs to be calculated exactly, it is bizarre for a client to
> > perform a LIST command, then issue a RETR, then blindly read that
> > number of bytes, when it could just scan the stream for \r\n.\r\n in
> > the first place.
> > 
> > Why does fetchmail do this silly thing?
> 
> Um, what the bug reporter showed was that does look for \r\n.\r\n and 
> finds it, but the server is sending it too early because it's in the 
> message and the server is not escaping it.
> 
> In other words, fetchmail is doing exactly what you say it should be 
> doing, but the server seems to expect fetchmail to do what you say is 
> silly.  (And I agree with you that it would be silly.)

Oops, sorry :-)

You're quite right. If a server sends a dot on a line of its own without
dot-stuffing, then (a) the server is broken, and (b) there's nothing *any*
POP3 client can do about it.

Cheers,

Brian.