From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: nnimap mail splitting and bodies
Date: Tue, 16 Nov 2010 20:45:11 -0500 [thread overview]
Message-ID: <87lj4sena0.fsf@andy.bu.edu> (raw)
In-Reply-To: <m3wrocsspt.fsf@quimbies.gnus.org>
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> I just noticed that nnimap downloads the complete article
Lars> bodies when doing mail splitting. Is that really necessary?
I think so---I do statistical splitting based on the email content
(headers and body).
This could be configuration option...
next prev parent reply other threads:[~2010-11-17 1:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 0:23 Lars Magne Ingebrigtsen
2010-11-17 1:45 ` Andrew Cohen [this message]
2010-11-17 8:40 ` Alberto Luaces
2010-11-18 18:55 ` Ted Zlatanov
2010-11-19 14:14 ` Ted Zlatanov
2010-11-21 4:56 ` Lars Magne Ingebrigtsen
2010-11-21 13:19 ` Andrew Cohen
2010-11-22 19:50 ` Ted Zlatanov
2010-11-24 21:13 ` Lars Magne Ingebrigtsen
2010-12-14 22:40 ` Ted Zlatanov
2010-12-14 22:44 ` Lars Magne Ingebrigtsen
2010-12-15 0:13 ` Ted Zlatanov
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=87lj4sena0.fsf@andy.bu.edu \
--to=cohen@andy.bu.edu \
--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).