Hi again,

I'm running postfix with virtual domains and want to modify the delivery path. Right now, I have one path for each user that's found with a database lookup.

Before mail hits Postfix, it will have an x-spam-header: yes/no/uncertain field. When mail with x-spam-header: yes the lookup for the path would return /var/mail/domain/username/.Inbox/.spam.

What I think I'd like to do is parse the x-spam-header value in postfix, populate a variable, then use the variable to modify the path lookup in the database. header_checks has a FILTER option, but that's just beyond my skillset at the moment.

Or, maybe I'm better off modifying the path with a procmail recipe? Currently, my mailbox_command = procmail -a "$EXTENSTION"

I don't know what's the norm in this situation, so any advice is welcome.

I think the procmail path is the way to go. The MDA should be responsible for those things.

Does postfix even allow a per-user lookup for mailboxes?

Yup.

Thanks for the advice!

You're welcome. Right, so you mean virtual_mailbox_maps. But, then, I'm not sure how procmail would work with virtual users/mailboxes. I have virtual users, but I use the dovecot delivery agent, which can parse headers and deliver into the correct imap folder following sieve filters. You might have a problem with virtual users and procmail.

Right, virtual_mailbox_maps works great for me, procmail has no problem delivering virtual mail to the path in the lookup. But now I want to sort via the headers and procmail looks like it might work, but it would be a new learning curve for me.

I'm more familiar with dovecot, so thank you again for another excellent tip!

Procmail, as far as I understand it, only works for local mailboxes/users and aliases thereof. If you are hosting Virtual Domains (as opposed to plain old virutal users) then I don't think it will help. For these scenarios you can use 'maildrop' instead, but I've never found the right parts to make it work without significant hassle.

Probably the easiest way is to use the SIEVE feature of (later) Dovecot. I don't have any knowledge of it myself, but it looks like it could do what you want.

When I had the need to do this (and I declare my personal hatred for 'amavis-new' at this point) and other clever things with Spam I found it easier to drop Postfix and go with Exim. It has a significant edge on Postfix in control, but at the cost of notable learning curve. To be fair to Postfix it retains 'it's only an MTA' and keeps true(ish) to that, and some of the current developments are exciting. It has better processing on large queues I am told.

Crux, look at 'Sieve' in Dovecot.

HTH and fleshes out what others have said.

1 members found this post helpful.

spampig,

I found that out this morning and have switched from using postfix's virtual transport to the dovecot transport plus a sieve script to get the bad mail into the spam folder.

Thanks to all!