![](https://seccdn.libravatar.org/avatar/184f2936f5d39b27534f4dd7c4d15bfb.jpg?s=120&d=mm&r=g)
Anton Aylward wrote:
Per Jessen said the following on 08/30/2011 12:55 PM:
Regardless, dovecot will maintain an index and if you use dovecots LDA, it update the index at time of delivery.
So we're back to where we started, yes that was what I wanted. No, how can I use it with fetchmail and ... I was saying procmail but...
The "BUT" is the big one. People are recommending 'sieve'. OK, but HOW?
sieve scripts are located in your users home directory - for dovecot, the default script is ".dovecot.sieve". Here is a snippet from one of mine: if address :regex "to" "openbios@openbios" { fileinto "INBOX.openbios"; stop; } There is some fairly good reference/example stuff for sieve "out there".
The stuff I see on the net assimes mail is coming in via SMTP into Postfix whihc has - or maybe not - a like to spamd and then loops abck to the dovecot LDA and somehow .... somehow ... somehow ... to the sieve. But the sieve examples I see aren't as flexible as Procmail.
sieve is invoked by dovecot as part of delivery. For instance, here's a bit of my dovecot.conf: protocol lmtp { mail_plugins = sieve quota } I don't know procmail very well, so regarding how it compares to sieve, well, you tell us when you're done converting :-)
Ah, right, 'sieve'. But wasn't that replacing procmail?
Yup.
My current procmail does whitelisting and delivery (for example of this list), blacklist, handling of known spam - BEFORE passing to SpamAssassin.
I'm not sure you'll be able to run spamassassin as part of a sieve script. I would recommend running that under the control of postfix, maybe with amavisd. A while ago, I wrote an article about a postfix-fetchmail-spamassassin config: http://jessen.ch/articles/spamassassin-and-postfix/
Then if its over the threshold for spam it goes into various buckets. The algorithm isn't perfect, some marginal stuff shouldn't be there, and sometimes a reasonable post gets a large score for whatever reason.
Procmail handles all this gracefully and without the odd syntax that sieve has.
procmail just uses it's own odd syntax :-) Sure, sieve is different, but you'll get used to it.
I'm willing to put up with the slightly-removed-from-sendmail geek-happy syntax of sieve, but I can't see how to do what procmail is doing so easily.
Leaving out running spamassassin, what else do you do with procmail? Your whitelisting probably isn't necessary, so leave that out too.
Having to run everything through spamassassin will be a performance pig!
Not at all. You won't notice it on any halfway modern machine. I have a test system running SA on 400MHz PII - a bit slow, but works fine. -- Per Jessen, Zürich (17.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org