From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap and not loading attachments
Date: Fri, 22 Feb 2002 23:05:33 +0100 [thread overview]
Message-ID: <iluheo9matu.fsf@extundo.com> (raw)
In-Reply-To: <2nk7t5mbjx.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Fri, 22 Feb 2002 16:49:54 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>> Not currently, sorry. Supporting it would take some redesign, so it
>> probably wont be implemented soon.
>
> How about implement it by replacing large attachments with
> message/external parts. Then we can invent a private method for imap,
> and add a function into mm-extern-function-alist to retrieve imap
> parts. I am not familiar with IMAP protocol, so it is just a wide
> thought.
One problem might be that I don't think it is possible to find out how
large a specific MIME part is. But that shouldn't too problematic,
looking at RFC822.SIZE and replacing all MIME parts with
content-disposition=attachment is probably OK. Another problem is
finding someone to implement it. :-)
next prev parent reply other threads:[~2002-02-22 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3ofihesx4.fsf@kolumbus.fi>
[not found] ` <ilun0y1mcux.fsf@extundo.com>
2002-02-22 21:49 ` ShengHuo ZHU
2002-02-22 22:05 ` Simon Josefsson [this message]
2002-02-22 22:05 ` Simon Josefsson
2002-02-22 21:49 ` ShengHuo ZHU
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=iluheo9matu.fsf@extundo.com \
--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).