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 12:44:05 -0400	[thread overview]
Message-ID: <4nr7tpd296.fsf@lifelogs.com> (raw)
In-Reply-To: <87n04iacoj.fsf_-_@dod.no> (Steinar Bang's message of "Sat, 08 May 2004 22:25:48 +0200")

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.

Ted



  reply	other threads:[~2004-05-12 16:44 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                       ` Ted Zlatanov [this message]
2004-05-12 19:12                         ` imap spam reporting Steinar Bang
2004-05-12 19:13                           ` Ted Zlatanov
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=4nr7tpd296.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).