George wrote: > Hi, > Please, Do not top post. Reply to the text directly. > Thanks for your reply > > I am sorry but I am not very technical. > I am the type of guy that can follow howtos > You don't seem to follow J.P.'s example very well. Especially the part about "See the man pages of pipe and transport for more details than what you'll find in this email." In the case of Postfix, the documentation is very complete and some howtos are not very helpful.
> Can you please be more detailed? > > What is "my_custom_transport.example.com" ? A subdomain? > Yes. In addition, this list uses example.com as a basis quite frequently. You didn't provide your own domain, so J.P. used this as an example. > What is "my_custom_transport:"? The command to which the email is > my_custom_transport is a user defined transport in master.cf (as the example shows). > forwarded? Is "| /path/to/some/php/file:" what it needs to be? Is ":" > That format is only valid in an alias map or .forward. Both of which are not used in a virtual mailbox setup. (Virtual mailbox is assumed since you neglected to follow the welcome message.) Brian > required in the end? > > Thanks > > On Fri, Mar 6, 2009 at 7:20 PM, J.P. Trosclair > <jptroscl...@judelawfirm.com> wrote: > >> George wrote: >> >>> I have postfix with postfixadmin and everything stored in a mysql >>> database. >>> >>> How do I forward emails sent to a mail account to an external command? >>> >> Since you are using virtual aliases (postfixadmin w/mysql assumes so) you'll >> need to setup a pipe transport in master.cf and proper settings in >> /etc/postfix/transports. See the man pages of pipe and transport for more >> details than what you'll find in this email. >> >> virtual alias: >> foo...@exampe.com foo...@my_custom_transport.example.com >> >> add to /etc/postfix/transports: >> my_custom_transport.example.com my_custom_transport: >> >> add to /etc/postfix/main.cf: >> transport_maps = hash:/etc/postfix/transports >> >> add to /etc/postfix/master.cf: >> my_custom_transport unix - n n - - pipe >> flags=flags_from_pipe_manual >> user=some_user:some_group >> argv=/path/to/my_custom_script vars_from_pipe_manual >> >> This may be incomplete. It is a rough (very rough?) example of the >> configuration. I strongly recommend having a look at the pipe and transport >> manuals before attempting to implement any of this. >> >>
