Re: POP/fancy-split bug?

[Stainless Steel Rat <ratinox@peorth.gweep.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Norman Walsh <ndw@nwalsh.com>  on Tue, 11 Jan 2000
| That does seem to be the problem, though it doesn't appear to be
| related to Content-Length. Many of the corrupted messages
| include a content-length that appears to be valid.

Well, FWIW, that Content-Length is valid, as far as I can tell.  What I
think we need to see is where the next message in the Incoming* file abuts
the one that is split incorrectly.  If there is no blank line before the
next message delimter (some POP servers are notorious for stripping
whitespace) then the Content-Length split check will fail and Gnus will
fall back to looking for mbox separators.

If you are going to rewrite pop3.el functions, pop3-munge-message-separator
is the best place to do it.  I probably should have forced the MMDF format
instead of mbox; I really do not know why I did not.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4e98Zgl+vIlSVSNkRAojlAJ0fHwqwMfkAiB2HdZ5gIVA8kr7CdwCfRKXG
GTyknpoTuPhqSr/z/9rDFqA=
=/u4H
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Warning: pregnant women, the elderly, and
Minion of Nathan - Nathan says Hi! \ children under 10 should avoid prolonged
PGP Key: at a key server near you!  \ exposure to Happy Fun Ball.