Developers of Sympa

[Olivier Salaun <address@concealed>]

Hi,

Daniel Pittman wrote:
> [...]
> That seems to be correct. The 'virtual' table will map from a "virtual"
> address to any address, including a unique local one.
> 
> That would be necessary to allow different "virtual robots" in the Sympa
> process to host mailing lists with the same name.

Currently Sympa does not allow managing 2 MLs with the same name in disctinct
Virtual Robots, BUT managing Sympa Virtual Robots requires defining 
sympa@dom1 
and sympa@dom2 aliases.

> [...]
> This seems to be a correct assessment to me. It's worth noting, though,
> that Postfix supports both "postfix style" and "sendmail style" virtual
> domains.
> 
> Postfix style implies that local alias definitions are /not/ visible to
> the delivery process. This is what the virtual user to unique alias will
> work with.
> 
> You can also use "sendmail style" virtual domains. This involves adding
> the domain name to 'mydestinations', at which point mail delivered to
> anyone at that domain will be treated as a local delivery.
>
> This is the mode that I use for supporting the three domains I have.
> 
> It would be quite possible for Sympa to work with this mode as well. The
> alias entries would need to be in the format:
> 
>    foo: "| /usr/lib/sympa/bin/bouncequeue address@concealed"
> 
> This wouldn't work correctly with lists of the same name in different
> virtual robots but, for me, that's not actually needed.

Supporting Postfix alias management in Sympa implies :
        o providing alternate alias_manager.pl scripts (for 
postfix-postfix_style
          and postfix-sendmail_style)
OR
        o adapt alias_manager.pl at installation time, depending on the 
situation


In the meanwhile, I suggest you just patch your alias_manager.pl to ignore
the list domain on the left part of aliases.

--
Olivier Salaün
Comité Réseau des Universités