At 19:57 +0200 on 27/05/2002, Matthias Andree wrote:

(Changing maildrop is probably harder than changing postfix config. :-)

My maildrop transport in master.cf is a copy of the example for maildrop's README.postfix with user and host lowercase canonicalization (flags u & h):

| maildrop unix - n n - - pipe | flags=uhR user=vmail argv=/usr/local/bin/maildrop -d ${recipient}

However, changing that to rewrite the intended destination as:

| ... -d ${user}@${nexthop}

at least rewrites the recipient properly for maildrop. Of course, if the recipient is Bcc:ed as one of multiple local recipients, there's no indication of which tag was used, if any.

Sadly, trying to fix that by adding an -A option:

| flags=uhR ... -d ${user}@${nexthop} -A "X-Originally-To: ${recipient}" or | flags=uhR ... -d ${user}@${nexthop} -A "X-Tag: ${extension}"

just causes maildrop to throw a blank line in at the start of the message file instead of putting the desired aux header in the message.

I'm not certain how to go about getting the tag info into the headers using this technique.

Richard