From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: POP/fancy-split bug?
Date: 11 Jan 2000 19:06:20 +0100 [thread overview]
Message-ID: <vaf66x0bi03.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Norman Walsh's message of "Tue, 11 Jan 2000 12:49:44 -0500"
Norman Walsh <ndw@nwalsh.com> writes:
> 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.
But it ought to be simple to use pop3.el to create a babyl file. You
could take pop3-movemail (which only was intended to be an example,
anyway!) and adapt it to produce a babyl file. Gnus will
automagically grok this and DTRT.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next prev parent reply other threads:[~2000-01-11 18:06 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
2000-01-11 18:06 ` Kai Großjohann [this message]
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=vaf66x0bi03.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).