Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: imap spam reporting
Date: Wed, 12 May 2004 15:13:45 -0400	[thread overview]
Message-ID: <4nu0yla26u.fsf@lifelogs.com> (raw)
In-Reply-To: <87ekppo3wl.fsf@dod.no> (Steinar Bang's message of "Wed, 12 May 2004 21:12:58 +0200")

On Wed, 12 May 2004, sb@dod.no wrote:

>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
> 
>> On Sat, 08 May 2004, sb@dod.no wrote:
> 
>>> Would it be possible to write a spam reporting function using the
>>> imap library of Gnus, that would move an article to a spam
>>> reporting group on the server?  Ie. without first transferring the
>>> article to Gnus as is done in move operations today?
> 
>> Yes, but I think it's a bad idea.  Maybe it's better to fix Gnus
>> than to spend time writing such hacks.
> 
> I disagree that this is a hack.

Well, it's a workaround that can be avoided :)

> 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.

Writing a spam reporting function to specifically move articles from
IMAP group A to IMAP group B because of unreadable IMAP groups is a
very, very narrow-focus task.  I doubt more than 5 users worldwide
would ever find it useful.  If I'm wrong and there's a crowd of such
users, I'll be more than happy to help them.

> As to fixing Gnus in this respect... I'm not really sure what the
> proper way to handle unreadable nnimap groups is...

I think we should fix nnimap so it does what you want!  I'll be glad
to put my efforts in that direction, since it will benefit many more
users and solve your problem too.

Ted



  reply	other threads:[~2004-05-12 19:13 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 [this message]
2004-05-12 20:04                             ` Zack Weinberg
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=4nu0yla26u.fsf@lifelogs.com \
    --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).