From: Norman Walsh <ndw@nwalsh.com>
Subject: Re: POP/fancy-split bug?
Date: Tue, 11 Jan 2000 12:49:44 -0500 [thread overview]
Message-ID: <4191-Tue11Jan2000124944-0500-ndw@nwalsh.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "11 Jan 2000 16:35:09 +0100"
/ Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) was heard to say:
| Depending on how you fetch mail, the output of the fetching process
| may be a babyl file (default with movemail.c) or an mbox file (can
| happen with pop3.el but don't know if that always happens). If it is
| an mbox file, a message is considered to start with a From_ line and
| ends with an empty line.
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.
I took a quick peek at epop3mail and it would appear to have the
same problems. At least, I don't see anything that makes me
think it works around the "From " problem.
As you suggested, the external movemail program seems to create
BABYL boxes (and therefore wouldn't suffer from this bug?), but
using it means I don't get any feedback as messages are
downloaded. Since I can't seem to prevent very big messages from
being downloaded, that's unfortunate.
I'm just mortified. Does everyone just live with these problems?
Is POP3 not much used among the gnusers? (Clearly, I have to get
my other system working again :-)
Cheers,
norm
--
Norman Walsh <ndw@nwalsh.com> | It is necessary to try to surpass
http://nwalsh.com/ | oneself always; this occupation
| ought to last as long as
| life.--Christina, Queen of Sweden
next prev parent reply other threads:[~2000-01-11 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-11 13:55 Norman Walsh
2000-01-11 15:35 ` Kai Großjohann
2000-01-11 17:49 ` Norman Walsh [this message]
2000-01-11 18:06 ` Kai Großjohann
2000-01-12 1:55 ` Stainless Steel Rat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4191-Tue11Jan2000124944-0500-ndw@nwalsh.com \
--to=ndw@nwalsh.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).