[BLU/Officers] [SPAM] [SPAM] Re: [Officers] Question on postfix virtualization

[gaf.linux at gmail.com (Jerry Feldman)]

Mailman is currently set up to maintain its own aliases. The only issues
I have is for the virtg lists. We set them up as virtg-<name>@virtg.com.
But we wanted them to be like board at virtg.com. So I do need to set up
some virtual mapping. BTW: On Pegasus, mailman was installed via YUM,
and the aliases are in /etc/mailman and mailman is in /usr/lib/mailman
and /var/lib/mailman (similar to the way they were on Rosetta). They are
working fine. The issue is translating <name>[-suffix]@virtg.com to
virtg-<name>[-suffix]@virtg.com or @blu.org. Mailman integrates well
into Postfix.

On 06/03/2011 12:18 AM, David Kramer wrote:
> On 06/02/2011 02:52 PM, jerry.feldman at algorithmics.com wrote:
>> The current virtual map was set up a while ago for postfix. 
>>
>> For every list, what I did back then was set up something like this that
>> corresponds to the aliases set up by mailman
>>
>> 61ahc at 61ahc.org                 61ahc at lists.blu.org
>>
>> 61ahc-admin at 61ahc.org           61ahc-admin at lists.blu.org
>>
>> 61ahc-owner at 61ahc.org           61ahc-owner at lists.blu.org
>>
>> 61ahc-request at 61ahc.org         61ahc-request at lists.blu.org
>>
>> 61ahc-post at 61ahc.org            61ahc-post at lists.blu.org
>>
>> 61ahc-bounces at 61ahc.org         61ahc-bounces at lists.blu.org
>>
>>  
>>
>> I think that mailman will set up the appropriate virtual domains once I
>> set it up in mm_cfg.py
> to be pedantic (which may pay off in this situation), mailman will set
> up an aliases file (/var/lib/mailman/data/aliases on my system), not a
> virtual file.  Virtual is only needed when you're crossing domain names.
> _______________________________________________
> Officers mailing list
> Officers at blu.org
> http://pegasus.blu.org/mailman/listinfo/officers


-- 
Jerry Feldman <gaf at bostonusergroups.org>
Treasurer, Boston User Groups, Inc.
http://www.bostonusergroups.com/
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846