Re: Problems with filters (AGAIN!)
"O. Sinclair" <[email protected]>
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <[email protected]> |
On 24/12/11 12:31, Martin (KDE) wrote: > Am Samstag, 24. Dezember 2011, 08:38:01 schrieb Anne Wilson: >> On 12/23/2011 08:51 PM, Martin (KDE) wrote: >>> - tell KMail to quit picking up my POP mail and stop KMail >>> >>>> - setup Cyrus >>>> >>>> . point it at my ~/Mail (all maildir) >>>> . add my KMail filters >>>> >>>> - start KMail and reconfigure it to use my new Cyrus >> >> Basically, that's almost right. I use Dovecot, but I imagine Cyrus is >> similar. > > The main difference with cyrus and dovecot is that cyrus is always completely > seperated from users. You can configure dovecot to use a mail storage in users > home folder. This is not possible wit cyrus. And dropping mails in cyrus > storage is not allowed. This has to be done with either lmtp protocol or the > cyrus deliver program. > > So there are several flows possible with dovecot: > > - fetchmail/getmail > - deliver (dovecots deliver process includes sieve filtering) > - dovecot imap > > or more complex (if you have no spam checking on your provider side): > - fetchmail/getmail > - procmail (filtering, spam and virus checking) > - dovecot > > or full featured (that's the one I use - I don't need fetchmail/getmail as I > have set up my own mail server) > - postfix (initial checks) > - amavisd (spam and virus check) > - postfix (final delivery via lmtp) > - cyrus lmtp (includes sieve filtering) > - cyrus imap > > All have advantages and disadvantages. I started more than ten years ago with > the second solution (with cyrus instead of dovecot) and slowly moved to the > final solution (took almost five years). > > Martin > >> You use Fetchmail to get your mail in, procmail or similar to >> filter it into your folders, and Dovecot to serve it up to whatever you >> use to read it. Then you point your client to the server address - >> which can be on the same machine as you read, or a different one. One >> added advantage is that you can read your mail when away from home if >> you choose. >> >> There's plenty of documentation online but ask if you need help. On >> UserBase, too, you'll find a section on making Bogofilter work within >> procmail, so your spam filtering is largely taken care of at the same >> time. Good luck. >> >> Btw, I agree that you must take care to use normal IMAP, not >> disconnected IMAP. It saves a lot of problems. >> >> When I was first setting it up, I set it up to fetch from my least used >> address until I was certain that it was working properly. Then again, >> if you don't mind some duplicates while you are testing, fetchmail has a >> --keep option. I have to ask - why? I only use pop3 accounts, I keep/save what I consider important in KMail(2) - I see no need to locally cache mail (as I understand it) and then fetch it? My filters work (spam took some extra tinkering in KMail2), my sorting works for me. So why the whole extra chain? _______________________________________________ KDE PIM users mailing list Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users