Gnus development mailing list
 help / color / mirror / Atom feed
From: Jonas Steverud <tvrud@bredband.net>
Subject: Re: Spam splitting and multiple nnimap methods
Date: Tue, 18 May 2004 15:50:47 +0200	[thread overview]
Message-ID: <m2brkl6dzc.fsf@Neocortex.local> (raw)
In-Reply-To: <20040518085316.A4024@gwyn.tux.org> (Timothy Brown's message of "Tue, 18 May 2004 08:53:16 -0400")

Timothy Brown <tim@tux.org> writes:

> On Tue, May 18, 2004 at 11:53:01AM +0200, Jonas Steverud wrote:
>
>> No problem, I have two POP sources. Spam.el does not care about how
>> many sources you have.
>
> This I keep reading, but i'm a little confused.
>
> Using nnimap, I guess, my real challenge is understanding three things:
>
> Where can I make a server declaration?  If I have something like:
>
>>       spam-split-group "Spam"
>
> Does that split to the spam group locally (nnfolder), does it split to
> the IMAP group on that particular server, or does it split to an IMAP
> group on a different server?

On that particular server. spam-split-group shall never contain a
colon and any part before it since that will be automatically
added. If Gnus fetches emails form nnimap+my.isp.com, the spam will
end up in nnimap+my.isp.com:Spam. When it fetches by POP for nnfolder
it will end up in nnfolder+pop.my.isp.com:Spam. you will always be
able to see form which backend the spam comes from.

> And when is split-group looked at?  Many times my messages will say
> they are being "IMAP split host:INBOX:xx to INBOX" but Gnus never
> sees them as part of that mailbox.  They aren't being lost, exactly,
> but they do exist.  Also, how does splitting on nnimap, and
> spam-split, interact?  So far i've had terrible luck with imap
> splitting, even with splitting on the bodies as the manual says.
>
> This is one area where Gnus' flexibility is giving me a huge headache - the
> manual just isn't clear enough.

Sorry, I haven't used IMAP so I don't know.

>> I've added (: spam-split) to my split rules.
>
> My own split rules are pretty simple - essentially split from "INBOX"
> (which nnimap box is it splitting from?  From all of them?), run
> : spam-split, (see question above), and then return messages not split
> to "INBOX" (again, is this on the server i'm currently checking)?

It seems like you need to understand how splitting is done - esp. for
IMAP. I cannot help you since I have never used IMAP. You could try to
send a specific IMAP-question to the list to see if anyone responds.

>> Now comes the second part; tell spam.el which groups contains spam and
>> which don't. That is done with group parameters.
>
> This part i'm sort of kind of -- well, totally lost on.
>
> My assumption is:
>
> 	- INBOX will always contain spam.
> 	- I don't care about any other groups at the moment.
> 	- If there is spam in INBOX, move it elsewhere;

All emails that are marked as spam when you exit the group is moved to
the spam-process-destination, declared by that group's parameters.

> 	- when I leave INBOX, process what I have marked (with S x) as
> 	  spam for bogofilter to train with.

Done automatically.

> The questions:
>
> 	- Do I need to do anything with ham?

Unless they are in a spam only group (like my nnfolder:Spam) you might
want to move it, otherwise it sounds like it is a good idea to let it
be. You need to train bogofilter on some ham otherwise it will
consider everything as spam (since it won't have a list of legitimate words).

> 	- If so, what?
> 	- How do I achieve the right functionality with the rules above?

Try copy-and-past my setup and work from there. Add one feature at the time.

1. Decide on how spam should be treated when it arrives (i.e. Gnus
   fetches it) - should it end up in your normal boxes or should it
   end up in a specific spam box? I have the latter in my case but you
   can have the former if you want to - just don't add (: spam-split).

2. On your email groups, press G p and replace the nil (or add to the
   list if you already have set some parameters) and add the suggested
   parameters I have. Remove the comments around the ham-marks and
   contents-is-ham lines, that way all you ham will be processed as
   ham and bogofilter will be trained on it as ham. When you done so
   for a couple of hundred of emails, insert the comments again - or
   remove the lines.

It might be so that you should do a G c instead of G p if you are
unfamiliar with Lisp/editing group parameters by hand. G c invokes the
customization engine for group parameters.

3. Add the lisp code in my last mail to your .gnus.

4. Add the autodetecion feature according to the info file (you seems
   to want it, while I do not so it is not included in my example).

-- 
(        http://hem.bredband.net/steverud/        !     Wei Wu Wei     )
(        Meaning of U2 Lyrics, Roleplaying        !  To Do Without Do  )




  reply	other threads:[~2004-05-18 13:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 21:50 Timothy Brown
2004-05-18  9:53 ` Jonas Steverud
2004-05-18 12:53   ` Timothy Brown
2004-05-18 13:50     ` Jonas Steverud [this message]
2004-05-18 14:02     ` IMAP Splitting with multiple mailboxes (was Re: Spam splitting and multiple nnimap methods) Timothy Brown
2004-05-18 14:13       ` IMAP Splitting with multiple mailboxes Kai Grossjohann
2004-05-18 14:15         ` Timothy Brown
2004-05-18 15:53           ` Kai Grossjohann
2004-05-18 15:58             ` Timothy Brown
2004-05-18 16:14               ` Kai Grossjohann
2004-05-18 14:13     ` Spam splitting and multiple nnimap methods Jonas Steverud
2004-05-18 19:11     ` Ted Zlatanov
2004-05-18 22:19       ` Timothy Brown
2004-05-19 11:36         ` Jonas Steverud
2004-05-19 14:50           ` Ted Zlatanov
2004-05-19 14:48         ` Ted Zlatanov
2004-05-20 10:27       ` Yair Friedman
2004-05-20 18:49         ` Ted Zlatanov
2004-05-22 23:45           ` Lars Magne Ingebrigtsen

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=m2brkl6dzc.fsf@Neocortex.local \
    --to=tvrud@bredband.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).