From: Alexander Kotelnikov <sacha@myxomop.com>
Subject: Re: Piping an article, imap numbering
Date: Tue, 06 Sep 2005 15:50:51 +0400 [thread overview]
Message-ID: <874q8y8les.fsf@myxomop.com> (raw)
In-Reply-To: <v9br37iq9w.fsf@marauder.physik.uni-ulm.de>
>>>>> On Mon, 05 Sep 2005 15:43:23 +0200
>>>>> "RS" == Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS>
RS> On Mon, Sep 05 2005, Alexander Kotelnikov wrote:
>> So once a certain period I want all this mail to be piped to
>> "sa-learn --spam", marked as read and moved to a spam mailbox (I do
>> not delete them in case of mistake). I wrote a function that helps
>> me but I believe it is not completely elegant:
>>
>> (defun my-gnus-sa-learn-and-move(&optional n) [...]
RS>
RS> I don't quite understand why people prefer to use their own functions
RS> instead of using the Gnus builtin features, see (info
RS> "(gnus)SpamAssassin back end")
O-op... I do not have such info section in Gnus v5.10.7
--
Alexander Kotelnikov
Saint-Petersburg, Russia
prev parent reply other threads:[~2005-09-06 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 12:24 Alexander Kotelnikov
2005-09-05 12:35 ` nntps still hangs | " Alexander Kotelnikov
2005-09-05 13:43 ` Reiner Steib
2005-09-06 11:50 ` Alexander Kotelnikov [this message]
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=874q8y8les.fsf@myxomop.com \
--to=sacha@myxomop.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).