Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap-split-download-body feature request
Date: Thu, 20 Nov 2003 04:28:57 +0100	[thread overview]
Message-ID: <iluk75vbtvq.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4n3cckdq0h.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 19 Nov 2003 16:09:34 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Fri, 14 Nov 2003, colman@ppllc.com wrote:
>
>> I sometimes receieve work email with very large attachments.  I
>> don't think that large atachments are typical of spam.  It would be
>> great if there could be some way to indicate that message bodies
>> should only be downloaded if they are smaller than some (default)
>> reasonable number.  Otherwise, the processing time for spam.el
>> becomes horrendous.
>
> The key function call in nnimap.el is:
>
> ;; in nnimap-split-articles
>
> (nnimap-request-article article) 
>
> which is invoked if nnimap-split-download-body is on.  I don't know if
> partial requests are possible, this would be a question for Simon
> Josefsson probably.

It is not difficult to find out if a message is "too large", but the
problem is: what should nnimap do if the message is too large?  Throw
an error?  Return no data?  Query the user?  Return dummy data (that
will stick around in the agent and cached forever)?  I fear a backend
interface change would be request to properly support this...




  reply	other threads:[~2003-11-20  3:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 13:18 Jake Colman
2003-11-19 21:09 ` Ted Zlatanov
2003-11-20  3:28   ` Simon Josefsson [this message]
2003-11-20 13:37     ` Ted Zlatanov
2003-11-20 14:01       ` Simon Josefsson
2003-11-20 14:20         ` Ted Zlatanov
2003-11-20 14:34           ` Simon Josefsson

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=iluk75vbtvq.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).