I generally use Postfix for mail stuff, so I'd lean towards that. Something I threw up awhile back to change the envelope sender of forwarded mail (to avoid tripping out SPF) defined a transport:
/etc/postfix/virtual
Code:
...
rtucker@example.com rtucker+example_com@gmail.com.munger
...
/etc/postfix/transport
Code:
.munger munger:
/etc/postfix/main.cf
Code:
munger_destination_recipient_limit = 1
/etc/postfix/master.cf
Code:
...
munger unix - n n - - pipe
flags=q user=nobody argv=/etc/postfix/redirector ${mailbox}@${nexthop} ${original_recipient}
...
/etc/postfix/redirector
Code:
#!/bin/bash
# Redirects mail to make SPF happy.
# Ryan Tucker <rtucker@gmail.com>, 2010 Oct 24
# Based on http://serverfault.com/q/82234/54177
HOSTNAME=`hostname -f`
DESTINATION=`echo "$1" | sed 's/.munger$//'`
/usr/sbin/sendmail -bm -f "mail@$HOSTNAME" "$DESTINATION"
logger -i -p mail.info -t redirector "Redirecting message to $DESTINATION (orig to $2)"
I thought it was pretty clever: to route mail through it, just append .munger to the recipient e-mail address. You could do something similar without having to do a lot of manual configuration, if you wanted to dedicate something.example.com to the job... en.example.com pipes through procmail to add "#${MAILBOX}" to the subject, so work@en.example.com would add #work, etc.
Or, search for docs on setting up postfix+procmail and someone'll probably have your use case ready to roll.
