Running two list with same email prefix
Hi all, I'm running a mail server with Debian Lenny, MTA is Postfix and i will use postfix-to-mailma.py script to run list
I would set up Mailman for running mailing list with same email prefix on different domains, obvious with different list names
For example we have ml.domain1.com and ml.domain2.net, i would like to have
LISTADDRESS LISTNAME tech@ml.domain1.com tech-ml.domain1.com tech@ml.domain.2.net tech-ml.domain2.net
In this way i can have the same address on differente domains and Mailman (my version is 2.1.11) can distinguish between lists because the list name is different. The list name will be also used to access web interface, so we have
http://ml.domain1.com/mailman/admin/tech-ml.domain1.com http://ml.domain2.net/mailman/admin/tech-ml.domain2.net
Is possible to accomplish this task? Any idea?
Andrea Cappelli wrote:
I'm running a mail server with Debian Lenny, MTA is Postfix and i will use postfix-to-mailma.py script to run list
I would set up Mailman for running mailing list with same email prefix on different domains, obvious with different list names
For example we have ml.domain1.com and ml.domain2.net, i would like to have
LISTADDRESS LISTNAME tech@ml.domain1.com tech-ml.domain1.com tech@ml.domain.2.net tech-ml.domain2.net
In this way i can have the same address on differente domains and Mailman (my version is 2.1.11) can distinguish between lists because the list name is different. The list name will be also used to access web interface, so we have
http://ml.domain1.com/mailman/admin/tech-ml.domain1.com http://ml.domain2.net/mailman/admin/tech-ml.domain2.net
Is possible to accomplish this task? Any idea?
Yes, it is possible to do this. What you describe is almost exactly what cPanel does in their modified Mailman. There are other patches around, but IMO, none are totally satisfactory. At least one user has recently posted that he is working on his own implementation.
This feature, but not necessarily this implementation, will be in MM 3.
The main thing you need to do is arange for mail delivery (postfix-to-mailman.py in your case) to deliver mail addressed to list@example.com, list-bounces@example.com, etc. and also list-bounces+xxx@example.com and list-confirm+xxx@example.com to the appropriate list-example.com list.
Then the fun begins. If you want the 'correct' address in the List-* headers, etc., that's a patch. Probably just to MailList.getListAddress().
If you are willing to use the list-example.com names for the web interface and elsewhere, that may be enough, but you will undoubtedly discover other things that need to be 'fixed'.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Il giorno mer, 12/08/2009 alle 08.24 -0700, Mark Sapiro ha scritto:
Andrea Cappelli wrote: This feature, but not necessarily this implementation, will be in MM 3.
Ok
The main thing you need to do is arange for mail delivery (postfix-to-mailman.py in your case) to deliver mail addressed to list@example.com, list-bounces@example.com, etc. and also list-bounces+xxx@example.com and list-confirm+xxx@example.com to the appropriate list-example.com list.
So I have to create the list with the original name plus a unique trailing and after create mail alias and let postfix rewrite the destination from the alias to the real name before passing the mail to mailman, correct?
Then the fun begins. If you want the 'correct' address in the List-* headers, etc., that's a patch. Probably just to MailList.getListAddress().
If you are willing to use the list-example.com names for the web interface and elsewhere, that may be enough, but you will undoubtedly discover other things that need to be 'fixed'.
Thany you for the reply, I'll try and if i'll reach the goal i'll post the solution here
Andrea Cappelli wrote:
So I have to create the list with the original name plus a unique trailing and after create mail alias and let postfix rewrite the destination from the alias to the real name before passing the mail to mailman, correct?
You don't want Postfix to rewrite the name. That's more complicated than you need and not what you want anyway because it would expose the 'true' name in the To: header of outgoing posts.
What you do is the following:
For listx in domain example.com, you create the list as listx_example.com or however you want to append domain to name to make it unique. You also add listx@example.com to acceptable_aliases for the listx_example.com list.
For postfix, considering only the list posting address (the others are similar) In the normal case for the listx@example.com list you would have a virtual_alias_maps entry like
listx@example.com listx
and an alias_maps entry like
listx: "|/path/to/wrapper post listx"
Instead of these, you would have a virtual_alias_maps entry like
listx@example.com listx_example.com
and an alias_maps entry like
listx_example.com: "|/path/to/wrapper post listx_example.com"
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 08/12/2009 10:24:50 AM, Mark Sapiro wrote:
Andrea Cappelli wrote:
I'm running a mail server with Debian Lenny, MTA is Postfix and i will use postfix-to-mailma.py script to run list
I would set up Mailman for running mailing list with same email prefix on different domains, obvious with different list names
For example we have ml.domain1.com and ml.domain2.net, i would like to have
LISTADDRESS LISTNAME tech@ml.domain1.com tech-ml.domain1.com tech@ml.domain.2.net tech-ml.domain2.net
In this way i can have the same address on differente domains and Mailman (my version is 2.1.11) can distinguish between lists because the list name is different. The list name will be also used to access web interface, so we have
http://ml.domain1.com/mailman/admin/tech-ml.domain1.com http://ml.domain2.net/mailman/admin/tech-ml.domain2.net
Is possible to accomplish this task? Any idea?
Yes, it is possible to do this. What you describe is almost exactly what cPanel does in their modified Mailman. There are other patches around, but IMO, none are totally satisfactory. At least one user has recently posted that he is working on his own implementation.
I got it working without any patching with a small change to postfix's configuration.
http://www.mail-archive.com/mailman-users@python.org/msg52616.html
This feature, but not necessarily this implementation, will be in MM 3.
The main thing you need to do is arange for mail delivery (postfix-to-mailman.py in your case) to deliver mail addressed to list@example.com, list-bounces@example.com, etc. and also list-bounces+xxx@example.com and list-confirm+xxx@example.com to the appropriate list-example.com list.
Then the fun begins. If you want the 'correct' address in the List-* headers, etc., that's a patch. Probably just to MailList.getListAddress().
I think the postfix rewrite rules in the above post fix this also. I forget. Of course when it comes to the web interface there's lots of things that don't match up with how things look to the email user.
Karl <kop@meme.com> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein
Running two mailing lists with the same email prefix can be a bit tricky but it's certainly possible with some configuration. Here's a general approach you can take:
**Modify the email prefix for one of the lists**: Instead of having both lists with the same<a href="https://martal.ca/b2b-appointment-setting/">Here</a>prefix, you can modify the prefix slightly for one of the lists. For example, if you have two lists named "list1" and "list2", you could have email addresses like
list1@example.comandlist2@example.com.**Use aliases**: You can set up email aliases to redirect emails with different prefixes to the same mailing list. For example, you could set up an alias so that emails sent to
list1@example.comandlist2@example.comboth go to the same mailing list.**Customize Mailman configuration**: You may need to customize your Mailman configuration to handle multiple lists with similar email prefixes. This could involve modifying settings related to email handling, subscriber management, and list moderation.
**Ensure unique list identifiers**: Make sure that each mailing list has a unique identifier within Mailman. This will help prevent any conflicts or confusion within the Mailman system.
**Test thoroughly**: Before deploying this setup in a production environment, be sure to thoroughly test it to ensure that emails are being routed correctly and that subscribers are able to interact with the lists as expected.
If you provide more specific details about your setup and requirements, I can offer more tailored advice.
participants (4)
-
Andrea Cappelli -
Karl O. Pinc -
Mark Sapiro -
Yazib Ali