On Mar 10, 2014, at 1:17 AM, Viktor Dukhovni <[email protected]> wrote:
> On Sun, Mar 09, 2014 at 07:53:21PM +0000, Eino Tuominen wrote: > >> >> I guess I'm not yet thinking "the Postfix way", but how would you configure >> the lists if I have multiple e.g. [email protected] -type lists? If I >> understand it correctly, local delivery agent only searches aliases with >> the local part of the address, that is delivering to a local user. So, >> the only options I come up with are: >> >> 1) a postfix instance per recipient domain >> 2) configure aliases info-example-com and info-another-domain and so on, >> that is a dummy "local" address for each "virtual" list and then configure >> corresponding owner-info-example-com aliases, and use expand_owner_alias >> to hide the intermediate local addresses. > > The simplest is probably 2. Instead of 1, you may be able to employ > a local delivery transport per-domain (with master.cf overrides > for myorigin and the like). These could also use per-domain alias > maps. A lot depends on how many domains you need to do this for. > > Another option is to perform the rewrite in a (recipient concurrency > = 1) pipe transport that re-injects messages back into the queue > for further processing. Thanks for the suggestions. I ended up doing a hybrid of these two. I configured another instance (listdelivery) with postmulti(1). I then used ldap transport_maps to redirect the messages to these mail lists to a pipe delivery program. The program, written in Python, resolves the desired envelope sender and resends the message using sendmail(1) to the listdelivery instance. The listdelivery instance then expands the list using virtual(8), and then sends the message back to the main postfix instance via relayhost = [127.0.0.1]:10026. I only need two postfix instances, of which the other one is extremely simple, and the routing configuration is completely in the ldap. If anyone's interested in the details, I'd be happy to share. -- Eino Tuominen
