Hi, Wow, that was quick -- thank you! I am a little bit confused with the format of the transportmap file. What you are suggesting seems very similar to what eventum does. They seem to have the transport maps as a parameter to... $mydestination (!):
mydestination = $transport_maps, $myhostname, eventum.example.com In main.cf they write: transport_maps = regexp:/etc/mail/transportregex local_recipient_maps = unix:passwd.byname $alias_maps $transport_maps That transportregex file is: /note-.*@eventum.example.com/ eventum:notes /issue-.*@eventum.example.com/ eventum:emails /drafts-.*@eventum.example.com/ eventum:drafts Which is a _little_ odd! What does postfix match exactly in such a case? Is only the domain part of each line considered? Thanks, Mike http://forge.mysql.com/wiki/Eventum:Setting_up_email_routing<http://forge.mysql.com/wiki/Eventum:Setting_up_email_routing_with_postfix> _with_postfix<http://forge.mysql.com/wiki/Eventum:Setting_up_email_routing_with_postfix> On Tue, Jun 21, 2011 at 12:32 AM, Sahil Tandon <[email protected]> wrote: > On Tue, 2011-06-21 at 00:07:34 +0200, Mike McDonard wrote: > > > * Email sent to [email protected] AND email sent to > > [email protected] should *all* be redirected to a > specific > > script (that we write), which will need access to the _whole_ destination > > address. > > Perhaps you could direct those emails to a pipe(8) transport. > > http://www.postfix.org/pipe.8.html > http://www.postfix.org/transport.5.html > http://www.postfix.org/postconf.5.html#transport_maps > > -- > Sahil Tandon <[email protected]> >
