From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: problem with bbdb whitelist filtering
Date: Tue, 27 Jan 2004 14:55:12 -0500 [thread overview]
Message-ID: <4n65exjhen.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <87hdyhpu68.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Tue, 27 Jan 2004 11:22:55 +0100")
On Tue, 27 Jan 2004, kai@emptydomain.de wrote:
> Write two functions, mm-spam-split-work and mm-spam-split-home, like
> so:
>
> (defun mm-spam-split-work ()
> (let ((spam-split-group "work-spam"))
> (spam-split)))
>
> (defun mm-spam-split-home ()
> (let ((spam-split-group "home-spam"))
> (spam-split)))
>
> Now you can add a fancy split rule that checks something:
>
> (| ...some rules here...
> (to "workaddress" (| (: mm-spam-split-work)
> ...other.rules.for.work.mail...))
> (to "homeaddress" (| (: mm-spam-split-home)
> ...other rules for home mail...)))
>
> Do you see the logic? It might be less intrusive than Ted's
> suggestion. But it might make your rule logic complicated, I'm not
> sure -- I haven't thought deeply about your rules as you showed
> them.
Cool suggestion, just one note - spam-split can take a string
argument. If given, that sets spam-split-group to avoid exactly what
you have above. So Martin could do, using your example:
(| ...some rules here...
(to "workaddress" (| (: spam-split "work-spam")
...other.rules.for.work.mail...))
(to "homeaddress" (| (: spam-split "home-spam")
...other rules for home mail...)))
I like your way to solve Martin's split issues better than mine, btw
:)
Ted
next prev parent reply other threads:[~2004-01-27 19:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 9:35 Martin Monsorno
2004-01-12 21:06 ` Ted Zlatanov
2004-01-13 8:45 ` Martin Monsorno
2004-01-20 23:58 ` Ted Zlatanov
2004-01-22 9:53 ` Martin Monsorno
2004-01-22 18:13 ` Ted Zlatanov
2004-01-23 15:07 ` Martin Monsorno
2004-01-23 21:20 ` Ted Zlatanov
2004-01-27 10:22 ` Kai Grossjohann
2004-01-27 19:55 ` Ted Zlatanov [this message]
2004-02-02 12:22 ` Martin Monsorno
2004-02-02 13:12 ` Kai Grossjohann
2004-02-02 20:02 ` Ted Zlatanov
2004-02-06 13:31 ` Martin Monsorno
2004-02-09 21:10 ` Ted Zlatanov
2004-02-27 14:37 ` monsorno-nospam
2004-03-04 18:50 ` 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=4n65exjhen.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).