From: lanz@fowi.ethz.ch
Subject: spam.el whitelist and blacklist contents and syntax
Date: Wed, 11 Jun 2003 14:43:07 +0200 [thread overview]
Message-ID: <yova4r2w23ac.fsf@relaskop.wsl.ch> (raw)
Two questions/feature requests concerning spam-whitelist and
spam-blacklist filtering with the Spam Elisp Package provided with
Gnus v5.10.3 (CVS).
- I think new sender addresses should only be added to the whitelist
(or blacklist) file if not already present in the file. At the
moment these files are unnecessarily growing with identical entries
for mail addresses I frequently exchange mail messages with (I get
frequently spam from).
- I think the whitelist and blacklist entries as generated through
gnus-group-ham-exit-processor-whitelist and
gnus-group-ham-exit-processor-blacklist do not use Emacs regular
expression syntax as stated in the documantation? I am not shure
about this, but they produce entries like `Peter Pan
<peter.pan@somewhere.com>' instead of `Peter Pan
<peter\.pan@somewhere\.com>' or `Peter Pan
<peter\\.pan@somewhere\\.com>'? I'm confused, is the documentation
clear enough? gnus-group-ham-exit-processor-blacklist and
gnus-group-ham-exit-processor-whitelist also enters the `Peter Pan'
part into the list, i.e. the mail address label. Therefore, I get
many unreadable charcters stemming from Korean and similar spam in
the blacklist file (I use an unibyte (latin1) emacs). Any problem?
Maybe not, but it might be safer to register only the
email-addresses without labels?
next reply other threads:[~2003-06-11 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 12:43 lanz [this message]
[not found] ` <4ny8zxeu5y.fsf@holmes.bwh.harvard.edu>
[not found] ` <yova8yrt2g4e.fsf@relaskop.wsl.ch>
[not found] ` <4nu1aga67k.fsf@koz.bwh.harvard.edu>
[not found] ` <yovan0g7yi3l.fsf@relaskop.wsl.ch>
[not found] ` <4nn0g7h0jm.fsf@lockgroove.bwh.harvard.edu>
2003-06-25 9:19 ` Adrian Lanz
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=yova4r2w23ac.fsf@relaskop.wsl.ch \
--to=lanz@fowi.ethz.ch \
/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).