From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: nnimap-split-download-body feature request
Date: Thu, 20 Nov 2003 08:37:15 -0500 [thread overview]
Message-ID: <4nllqbjh4k.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <iluk75vbtvq.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 20 Nov 2003 04:28:57 +0100")
On Thu, 20 Nov 2003, jas@extundo.com wrote:
> 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...
Nah, just fetch the headers. I think that's all you can reasonably
expect as a Gnus user. Maybe fake the body with "BODY TOO LARGE" or
something like that, or add a header, but I personally think that
retrieving just the headers in such a case is a perfectly good
solution.
This reminds me: is it possible to alter a message while splitting?
The reason I ask is that I'd like to insert a header that will tell
me, later, what the eventual destination of that message should be.
This is useful when the destination is "nnml:mail" (as returned by the
registry sometimes) but we're in the nnimap server.
If I can't insert headers, I can do it with the registry.
Ted
next prev parent reply other threads:[~2003-11-20 13:37 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
2003-11-20 13:37 ` Ted Zlatanov [this message]
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=4nllqbjh4k.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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).