From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: spam spltting my sys emails
Date: Tue, 05 Oct 2010 08:12:21 -0500 [thread overview]
Message-ID: <87y6acn5qi.fsf@lifelogs.com> (raw)
In-Reply-To: <eplj6cakgy.fsf@news.eternal-september.org>
On Tue, 05 Oct 2010 14:32:29 +0200 Richard Riley <rileyrg@googlemail.com> wrote:
RR> Using this set up
RR> (setq nnimap-inbox "INBOX")
RR> (setq nnimap-split-methods 'default)
RR> (setq nnmail-split-fancy (quote (: spam-split)))
RR> (setq nnmail-split-methods (quote nnmail-split-fancy))
Ouch. Are you sure you want spam-split to be the only determinant of
where mail goes? I would at least provide a default destination at the
end.
RR> combined with
RR> ,----
RR> | spam-split-group is a variable defined in `spam.el'.
RR> | Its value is "Gnus-Spam"
RR> |
RR> | Documentation:
RR> | Group name where incoming spam should be put by `spam-split'.
RR> `----
RR> I have a select method for nnml which processes var/spool/mail mbox and
RR> usually used to put them in mail.misc group in the nnml-directory
RR> (~/Mail).
RR> Now its determining that all my sys emails from cron etc are spam and
RR> refiling them to spam-split-group, Gnu-Spam. How to stop that?
It depends entirely on your spam.el configuration. Some backend has
decided those e-mails are spam. You need to either check *Messages* or
debug each of your spam backends one by one.
RR> My nnml group looks like this after using command line "mail" to send an
RR> email from root to myself:-
RR> ,----
RR> | Z 1: Gnus-Spam <-- spam splitting created this
RR> | 0: mail.misc
RR> | 1: sys-mail ;<--- I created this group manually moving a message
RR> `----
RR> Where Gnus-Spam has been newly created by the spam-splitting I assume.
Yes, the messages will be spooled to the group and it's created if
necessary.
RR> So how to tell the spam-split assigned to nnmail-split-fancy to ignore
RR> the nnml feed?
You need to customize your nnimap-split-methods to a function which
overrides spam-split-group and nnmail-split-fancy (the variable) and
calls nnmail-split-fancy (the function). I posted an example just the
other day.
Ted
next prev parent reply other threads:[~2010-10-05 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 12:32 Richard Riley
2010-10-05 13:12 ` Ted Zlatanov [this message]
2010-10-05 13:38 ` Richard Riley
2010-10-05 14:57 ` Ted Zlatanov
2010-10-05 13:18 ` Steinar Bang
2010-10-05 13:27 ` Ted Zlatanov
2010-10-05 15:24 ` Steinar Bang
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=87y6acn5qi.fsf@lifelogs.com \
--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).