#1147 Duplicate Entries in Aliases/Virtual-Mailman File

[chris-taylor]

Hello,

we are using mailman-2.1.7 in cooperation with the
postfix mta. While fiddling around with pipe transport
we recovered the following problem:

Create a mailing list named: students
Create a mailing list named: students-request

Result:
A duplicated entry for students-request in the alias
file and in the virtual-mailman file.

Shouldn't there be a check for avoiding duplicate entries?

The postalias command reports this duplicate entry....

BTW:
The postfix-to-mailman.py script also is not able to
handle the duplicate entries....

Regards

Christian

[Barry Warsaw]

Logged In: YES
user_id=12800

Because each mailing list really consists of a number of
aliases, of which <listname>-request is one, you cannot
create a mailing list witht he same basename and -request.
While this won't change, perhaps Mailman should refuse to
create such -request mailing lists (and -owner, -bounces, etc.)

[chris-taylor]

Logged In: YES
user_id=994602

The refusal of listnames ending with the "administrative
extensions" (like -bounces etc.) sounds good to me.

But maybe other users schould comment if this restriction is
viable for them.....
Because there might be users who want to create lists like:
house-owner
feature-request
etc.
This is no problem as long as there are no lists named house
or feature....

Thank you for this good piece of software

Christian

[chris-taylor]

Logged In: YES
user_id=994602

The refusal of listnames ending with the "administrative
extensions" (like -bounces etc.) sounds good to me.

But maybe other users schould comment if this restriction is
viable for them.....
Because there might be users who want to create lists like:
house-owner
feature-request
etc.
This is no problem as long as there are no lists named house
or feature....

Thank you for this good piece of software

Christian

[chris-taylor]

Logged In: YES
user_id=994602

The refusal of listnames ending with the "administrative
extensions" (like -bounces etc.) sounds good to me.

But maybe other users schould comment if this restriction is
viable for them.....
Because there might be users who want to create lists like:
house-owner
feature-request
etc.
This is no problem as long as there are no lists named house
or feature....

Thank you for this good piece of software

Christian