On Tue, Jul 7, 2020 at 4:19 PM Wietse Venema <wie...@porcupine.org> wrote: > > Stats Student: > > On Tue, Jul 7, 2020 at 2:15 PM Wietse Venema <wie...@porcupine.org> wrote: > > > > > > Stats Student: > > > > Thank you, but I still do not understand why I need to provide > > > > additional user aliases. If my system receives a message for > > > > > > To deliver a message to two destinations > > > > > > 1) a script > > > 2) a maildir file > > > > > > That message needs to have (surprise!) two destinations. > > > > > > 1) a destination that delivers to the script > > > 2) a destination that delivers to the maildir file > > > > > > You can add that second destination with virtual_alias_maps, > > > sender_bcc_maps, recipient_bcc_maps, .forward files, and so on. > > > > > > Wietse > > > > > Could you please show an example of what would go into one of those > > maps to indicate a maildir destination? > > Prerequisites: > foo@example delivers to script > bar@example delivers to maildir > > Use virtual_alias_maps with: > foo@example foo@example, bar@example > > Now, mail for foo@example goes to script and maildir. > > How to deliver to script or maildir? Use transport_maps to select > a delivery agent that delivers to script (local or pipe delivery > agent) or maildir (virtual or local delivery agent). > > foo@example
Sorry if I am not explaining the requirement correctly. I need the same message addressed to f...@example.com to be delivered to *two* places - the script AND the mailstore, *not* two different accounts. I do *not* want messages addressed to f...@example.com to also go to b...@example.com which is what the virtual_alias_maps you showed would do. Re: transport maps -- my understanding is that those work on a per domain basis. Don't think I want to have a separate transport for each user.
