From: Zack Weinberg <zack@codesourcery.com>
Subject: Re: imap spam reporting
Date: Wed, 12 May 2004 13:04:33 -0700 [thread overview]
Message-ID: <87y8nxo1im.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <4nu0yla26u.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 12 May 2004 15:13:45 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
>> A command like the one I'm suggesting means that spam can be
>> reported by moving it to a different folder on an IMAP server,
>> without first transferring it to Gnus, and then pushing it back to
>> the IMAP server.
>
> Shouldn't the nnimap backend do this? If it doesn't do it already,
> it seems like an awfully nice feature to move articles without
> retrieving them.
A general facility for moving articles between IMAP groups without
retrieving them would be very nice, yes.
Support for IMAP partial fetch (i.e. not downloading giant binary
attachments when the message is first opened) would also be very nice.
zw
next prev parent reply other threads:[~2004-05-12 20:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 7:42 Moving messages to unreadable nnimap group? (spam reporting) Steinar Bang
2004-04-27 8:02 ` Simon Josefsson
2004-04-29 7:03 ` Steinar Bang
2004-04-29 10:01 ` Simon Josefsson
2004-04-29 10:34 ` Steinar Bang
2004-04-29 10:44 ` Simon Josefsson
2004-04-29 11:40 ` Steinar Bang
2004-04-29 12:06 ` Simon Josefsson
2004-04-29 12:22 ` Steinar Bang
2004-04-29 13:54 ` Simon Josefsson
2004-04-30 8:10 ` Steinar Bang
2004-05-08 20:25 ` imap spam reporting (Was: Moving messages to unreadable nnimap group...) Steinar Bang
2004-05-12 16:44 ` imap spam reporting Ted Zlatanov
2004-05-12 19:12 ` Steinar Bang
2004-05-12 19:13 ` Ted Zlatanov
2004-05-12 20:04 ` Zack Weinberg [this message]
2004-05-13 8:09 ` Steinar Bang
2004-05-13 8:02 ` Steinar Bang
2004-05-13 12:32 ` Ted Zlatanov
2004-05-13 16:38 ` Bjørn Mork
2004-05-14 5:22 ` Steinar Bang
2004-05-14 14:45 ` Bjørn Mork
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=87y8nxo1im.fsf@egil.codesourcery.com \
--to=zack@codesourcery.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).