From: Matthias A. <mat...@gm...> - 2005-08-13 02:29:40
|
Brian Candler <B.C...@po...> writes: > 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. Well, it should be possible to work around this in many cases on systems with 4.4BSD or IEEE Std 1003.1-2001 compatible stacks, and I have some ideas how to do it -- we can peek if there's data behind DOT CR LF and if it looks like some POP3 protocol (in response to further commands we might have sent) response or not. This assumes that the .\r\n doesn't fall on a packet boundary. I'm not doing this now, 6.3.0 is long overdue, with some bug feedback pending, and after 6.3.0 I'd request payment to add such features that make up for somebody else's mistakes. It's not fetchmail's fault after all. -- Matthias Andree |