[ mailman-Bugs-1533058 ] Duplicate Entries in Aliases/Virtual-Mailman File

[SourceForge.net]

Bugs item #1533058, was opened at 2006-08-02 13:11
Message generated for change (Comment added) made by chris-taylor
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: chris-taylor (chris-taylor)
Assigned to: Nobody/Anonymous (nobody)
Summary: Duplicate Entries in Aliases/Virtual-Mailman File

Initial Comment:
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

----------------------------------------------------------------------

>Comment By: chris-taylor (chris-taylor)
Date: 2006-08-02 15:40

Message:
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

----------------------------------------------------------------------

Comment By: chris-taylor (chris-taylor)
Date: 2006-08-02 15:38

Message:
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

----------------------------------------------------------------------

Comment By: chris-taylor (chris-taylor)
Date: 2006-08-02 15:36

Message:
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

----------------------------------------------------------------------

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2006-08-02 14:15

Message:
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.)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1533058&group_id=103