From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: POP/fancy-split bug?
Date: 11 Jan 2000 16:35:09 +0100 [thread overview]
Message-ID: <vafbt6shb9u.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Norman Walsh's message of "Tue, 11 Jan 2000 08:55:01 -0500"
Norman Walsh <ndw@nwalsh.com> writes:
> But now that I'm using POP, I've noticed that I sometimes get a
> completely empty message in the "approval" folder and the
> unapproved message in the "list" folder, as if it had been
> approved. I haven't been able to nail down what's different
> between messages that succeed and messages that fail, but most
> seem to fail.
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.
The unapproved message starts with a From_ line, hence it is
conceivable that this From_ line is considered start of a message.
But why does this not always happen? Well, I think Gnus also looks at
the Content-Length (maybe also Lines) header. Gnus then moves forward
that many bytes or lines to see if a new message begins there. If so,
the header information is considered to be correct. If, however,
there is no From_ line after the number of bytes/lines given by
Content-Length, Gnus reverts to searching for From_ lines for
beginnings of messages.
Maybe everything works if the Content-Length header is good, and the
message is split in two if the Content-Length header is wrong?
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next prev parent reply other threads:[~2000-01-11 15:35 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 [this message]
2000-01-11 17:49 ` Norman Walsh
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=vafbt6shb9u.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).