From: Norbert Koch <nk@viteno.net>
Subject: Re: Problems including spam
Date: Wed, 01 Jan 2003 15:31:06 +0100 [thread overview]
Message-ID: <vzisx9gcwl.fsf@viteno.dyns.net> (raw)
Ted Zlatanov <tzz@lifelogs.com> writes:
Happy new year.
> Can you check on that? I'm working on spam.el right now, so it would
> be helpful if you could look into it if you can't wait.
I've been away for the last 24 hours, no need to hurry :-) It took
the message more than one day to get through (thus the double posting
...).
(require 'gnus-uu) is necessary for the key bindings in spam.el to
work. Maybe it would be a good thing to put this statement into the
file?
> You need the complete group name, it's not a regex.
Thanks, changed... waiting for new spam to arrive.
> I'm working on adding a group parameter "spam-contents" right now that
> would tell spam.el to process messages as spam for a specific group,
> with the related global variable. Wait a few hours :)
Done, I'm using the new version :-)
Thanks,
norbert.
next reply other threads:[~2003-01-01 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 14:31 Norbert Koch [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 14:42 Ted Zlatanov
2003-01-02 0:15 ` Ted Zlatanov
2002-12-31 9:26 Norbert Koch
2002-12-31 17:10 ` Ted Zlatanov
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=vzisx9gcwl.fsf@viteno.dyns.net \
--to=nk@viteno.net \
/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).