Am 27.05.2011 17:42, schrieb Noel Jones: > local aliases are not expanded until final delivery by local(8).
so i am to stoopid to understand what exactly is "local" >> replace /etc/aliases by database-backend with having something >> like "mailman" in mind > > mailman requires the list domain to be delivered by local(8), or a > transport_maps entry directing the list user to > local: > > The underlying lookup mechanism, flat file vs. database, is irrelevant. that's clear, but i want never see any non-mysql configuration here since all services (mail, httpd, ftp, dns, domainreg) are configured in a centralized and inhouse written web-backend and for theory i am thinking of "how would i act if some service in future needs deliver to a command" on the postfix side as said "theory" now, some months ago mailman was in use on one machine which is now also configured for our mail-backend since mailman is not needed now, but maybe the times will come that anything like this is needed again without lose the currently db-integration am i right that "virtual_alias_maps" with the command on the right side of the table and a dedicated subdomain where public addresses as forwarders (also via virtual_alias_maps) would be a solution?
signature.asc
Description: OpenPGP digital signature
