Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Randy Ramsdell (rramsdelllivedatagroup.com)
Date: Thu May 29 2008 - 16:17:46 CDT
> Randy Ramsdell wrote:
>> I was simply trying to organize our setup because entries for lists
>> were added to both aliases AND/OR virtual. Some lists are in aliases
>> and some in virtual and I just didn't see this as organized. Also, I
>> did not need all users to receive e-mail from every domain, in fact,
>> I wanted to discourage this. This would be the only reason I want to
>> have distinct name-spaces.
>> Using Virtual alias domains would not be used if you need pipes,
>> .forward files? It appears that I would be able to create lists and
>> aliases with Virtual alias domains which is really all we need.
> virtual does not exec commands nor parse .forward file (nor
> alias_maps). but if you only exec few commands, you can create a
> transport in master.cf (see MAILDROP README for an example).
Ok thanks. What do you think is the best way to switch from
virtual_maps to virtual_aliase_domains given our following setup?
virtual_maps = hash:/etc/postfix/virtual
virtual_alias_domains = all the domains listed in current maps
virtual_alias_maps = hash:/etc/postfix/virtual
From what I read, it looks like this will work just fine theoretically.