2008/2/11, Håkon Alstadheim <[EMAIL PROTECTED]>: > > Dan wrote: > > I think you are right, I will do it this way. I don't remember why I > > didn't do it this way (believe I was in "howto" mode and just > > following some how-to too literally ;-)) > > > Most of the howtos you stumble upon when searching for postfix and dspam > are geared towards pure filtering installations without local delivery. > I recently posted here on how to filter on incoming mails before alias > expansion. If you run mailing-lists you want to filter, you need to run > dspam as a filter, before local delivery. If you only filter for local > recipients, mailbox_command or mailbox_transport are way simpler.
Yes. Though after starting to get this going, I realised that this also does not 100% match my needs. Admittedly my setup is a bit complicated, as after the initial postfix are multiple email systems. The "local" one is a cyrus IMAP server, but some users get their mails also delivered to other (LAN-local) mail servers we run for different projects (e.g. an Exchange server). Ideally dspam would work for them as well. But then there may even be addresses that are split to go out to other servers outside of our LAN (which should not be filtered). Argh. The latter aside, the content filter may not be good as it uses the resolved forwarding address. This is wanted for aliases, but not wanted for forwards (esp. multiple ones), as the user would not necessarily know the internal addresses. Argh. I think this is something that is rather difficult (if at all) to achieve. Maybe the best would be to use the mailbox_transport method, so anybody who wants email to be filtered & forwarded to other mail systems must do the forwarding in cyrus (should be no big problem with web sieve). Or is there some way to achieve the complicated? Dan
