On Fri, Aug 12, 2005 at 10:14:21AM +0200, Nico Golde wrote:
> 1 list dla artii at poczta.o2.pl. (5193 octets).
> fetchmail: POP3> LIST 1
> fetchmail: POP3< +OK 1 5193
> fetchmail: POP3> RETR 1
> fetchmail: POP3< +OK
> fetchmail: SMTP> MAIL
> FROM:<bou...@li...> BODY=8BITMIME
> SIZE=5193
> fetchmail: SMTP< 250 Ok
> fetchmail: SMTP> RCPT TO:<ar...@lo...>
> fetchmail: SMTP< 250 Ok
> fetchmail: SMTP> DATA
> fetchmail: SMTP< 354 End data with <CR><LF>.<CR><LF>
> #********************fetchmail: message ar...@po...:1 was not the
> expected length (4411 actual != 5193 expected)
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?
Regards,
Brian.
|
