From: Brian C. <B.C...@po...> - 2004-10-15 15:13:59
|
On Fri, Oct 15, 2004 at 02:35:53PM +0200, Matthias Andree wrote: > I'd asked Rodolfo if it was POP3 that hung and if so, I said his > upstream server was broken. We'll see what he can figure next. I thought I saw something about downloads hanging because they contained a null (\0) character. That would be different. In the event of any dispute about whether it's fetchmail's fault or the server's, then I'd say the best thing to do is to get a tcpdump -i eth0 -n -s1500 -X tcp port 110 output, and see exactly what is going on. > > qmail-pop3d gives a wrong size because it doesn't count end-of-line as two > > bytes; however using the size would not work anyway even if it did, because > > lines which start with the termination character use byte-stuffing but don't > > count it twice in the size (see RFC1939, section 11) > > That could be compensated for as the message is read, because it is read > line-wise. But if you're going to read the mail line-by-line then you can just as easily check for the CR LF . CR LF termination sequence! I can't imagine that any other major POP3 client does anything other than that, and I don't see why fetchmail should. Regards, Brian. |