On Thu, Sep 18, 2014 at 10:19:26PM +0000, Doug Sampson wrote:
> I had thought that's what the /usr/local/etc/postfix/virtual file does. Allow
> me to say what I think is the process out loud here.
>
> The main.cf contains:
> virtual_alias_maps = hash:/usr/local/etc/postfix/virtual
>
> It expands any matching entry to any specified address(es) as in the
> following example, no?
> webmas...@example1.com webmas...@example1.com,
> webmaster#example1....@autoreply.example1.com
>
> The original message is then delivered to the first address
> (webmas...@example1.com) and an exact copy is sent to
> webmaster#example1....@example1.com. The inbound Postfix mechanism upon
> receiving these two messages checks its transport table as follows:
> example1.com 192.168.xx1.33
> autoreply.example1.com vacation:
>
> and delivers the first message to 192.168.xx1.33 and the second message to
> the vacation script as defined in master.cf:
> vacation unix - n n - - pipe
> flags=Rq user=vacation argv=/var/spool/vacation/auto-reply.pl -f
> ${sender} -- ${recipient}
>
> The vacation script then executes by sending an autoreply message back to the
> original sender.
>
> Is my understanding correct?
Yes, with the proviso that if different recipients are associated
with different auto-response message bodies, or if auto-reply.pl
for some other reason needs to send separate messages to the original
sender for each original recipient, then the qmgr settings for
"vacation" transport should include:
vacation_destination_recipient_limit = 1
vacation_destination_concurrency_limit = 2
Choose your vacation destination with care and book early! :-)
--
Viktor.
