Hi, I had the same problem, but fixed it. Your problem is with your transport entry and also (possibly) your alias table.
The postfixadmin vacation autoreponder works by first creating an entry in the alias table using a domain name that you have setup in the config.inc.php file for postfix. If you look at the alias table (or file depending on your setup) for any users that have activated VACATION, you should see something like this... [email protected] [email protected], [email protected] When a message comes in for the user above, postfix delivers it to both the entries in the alias table. It will first reference the transport file, to see if an entry exists that it needs to take into account. In your case, you are pushing all your mail for that user to VACATION script, so they will not get a copy in their mailbox. What you need to do is change your transport file entry to: autoreply.mydomain.com vacation now, postfix will deliver any mail for *.autoreply.mydomain,com via vacation script, and a copy will also follow the normal path into the users mailbox. -----Original Message----- From: [email protected] on behalf of roby65 Sent: Tue 1/18/2011 4:37 PM To: [email protected] Subject: Postfix autoresponder and transport problem Hi guys, i finally made it in the intent of adding an autoresponder to my postfix server, and it works, but....it creates problems with dovecot! This is what i've done: master.cf: vacation unix - n n - - pipe flags=DRhu user=vacation argv=/var/spool/vacation/vacation.pl -f ${sender} ${recipient} transport: [email protected] vacation Here is the problem: when i send a message to this account, i get the autoreply (this is ok) but the receiving account doesn't receive the mail i send (i think because the autoresponder plugin gets it and dovecot doesn't get the email). How to fix it? -- View this message in context: http://old.nabble.com/Postfix-autoresponder-and-transport-problem-tp30701687p30701687.html Sent from the Postfix mailing list archive at Nabble.com. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
