We are an ISP and we have several clients requesting a mailing list. Often, the names collide. No problems with email addresses, we know how to configure Postfix to have info@company.com and info@npo.org point to different mailboxes.
But I cannot do the same with Mailman. Mailing lists are apparently unique, whatever the domain is. So, I must create info-company and info-npo and set a different host_name for each list. Not a big deal except that this name appears in messages sent and info-company@company.com is not really elegant.
I tried changing real_name. As its documentation said, it is discouraged and, indeed, it does not work (the original name still appears in messages).
Using Mailman with virtual domains.
- Create the list using the unique local name
- Setup the virtual name and point it to the unique local name (for email
and for web)
- Web admin to list and under General Options set "Host name this list prefers" to the virtual host name "Base URL for Mailman ..." to the virtual hosting site ***
- Web admin, Privacy Options, set "Alias names (regexps).." list to include both the real and the
virtual name of the list
- Web admin, Regular/Digest member options "Footer added..." manually put in the information you want to show up
*** This step could really hose you. Make sure that your virtual web site works or you will loose the ability to access the list config. If that happens, go into ~mailman/lists/<listname>/.. and copy "config.db.last" over the current "config.db". You will loose all recent changes, but you will once more be able to access the config of the list.
This should let you setup multiple virtual lists with the same primary name: info@backrub.org info@ralphismyfriend.edu
The mail for each list will come into your virtual-users tables and be replaced by the unique local name: info-backrub@hostdomain.com info-ralphismyfriend-edu@hostdomain.com
From there they will go to the created mailman lists. They will be accepted
as valid for the lists (since the lists have that name as well as the virtual defined as being acceptable). They will be sent out from Mailman using the "Host name this list prefers" which is the virtual name. (note, your server has to be setup to relay for the virtual domain!).
Really the only tricky parts are the web redirects.
Any critiques or additions are welcome. Good Luck!
Jon Carnes ----- Original Message ----- From: "Stephane Bortzmeyer" bortzmeyer@netaktiv.com To: mailman-users@python.org Sent: Monday, April 08, 2002 9:30 AM Subject: [Mailman-Users] "True" virtual domains [netaktiv.com #99]
We are an ISP and we have several clients requesting a mailing list. Often, the names collide. No problems with email addresses, we know how to configure Postfix to have info@company.com and info@npo.org point to different mailboxes.
But I cannot do the same with Mailman. Mailing lists are apparently unique, whatever the domain is. So, I must create info-company and info-npo and set a different host_name for each list. Not a big deal except that this name appears in messages sent and info-company@company.com is not really elegant.
I tried changing real_name. As its documentation said, it is discouraged and, indeed, it does not work (the original name still appears in messages).
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
On Mon, Apr 08, 2002 at 04:57:32PM -0400, Jon Carnes jonc@haht.com wrote a message of 76 lines which said:
Using Mailman with virtual domains.
Close but it still does not work. I explain:
- Create the list using the unique local name
newlist REALNAME
- Setup the virtual name and point it to the unique local name (for email
and for web)
I translated newlist's output to Postfix virtual addresses ("REALNAME:" becomes "VIRTUALNAME@VIRTUALDOMAIN "). It works for incoming mail.
- Web admin to list and under General Options set "Host name this list prefers" to the virtual host name "Base URL for Mailman ..." to the virtual hosting site ***
- Web admin, Privacy Options, set "Alias names (regexps).." list to include both the real and the
virtual name of the list
- Web admin, Regular/Digest member options "Footer added..." manually put in the information you want to show up
Done (BTW, I use config_list to do so, it is much easier/faster than the Web interface.
happens, go into ~mailman/lists/<listname>/.. and copy "config.db.last" over the current "config.db". You will loose all recent changes, but you will once more be able to access the config of the list.
Or use config_list.
This should let you setup multiple virtual lists with the same primary name: info@backrub.org info@ralphismyfriend.edu
Yes but it still fails for OUTGOING mails. The real name still appears in many places. I can use Postfix's canonical to rewrite what's in the headers but it is painful.
And some messages like "We have received a request from 62.212.103.139 for subscription of your email address, bortzmeyer@gitoyen.net, to the REALNAME@VIRTUALDOMAIN mailing list." are not subject to customization.
I feel inclined to say that Mailman does not really support virtual domains :-(
Stephane Bortzmeyer (bortzmeyer@netaktiv.com) wrote:
Yes but it still fails for OUTGOING mails. The real name still appears in many places. I can use Postfix's canonical to rewrite what's in the headers but it is painful.
And some messages like "We have received a request from 62.212.103.139 for subscription of your email address, bortzmeyer@gitoyen.net, to the REALNAME@VIRTUALDOMAIN mailing list." are not subject to customization.
I feel inclined to say that Mailman does not really support virtual domains :-(
I'm also trying to get "true" virtual support with Mailman & qmail and also realize that if I create test1@lists.net and test2@lists.net, and want them to appear as test@domain1.com and test@domain2.com, still I in the list info page they appear as test1 & test2 list ie. it's not possible to hide them.
Or I am missing something?
(each domain has its own listm but cannot hide real names.)
So, it is proper to conclude that there is no real true virtual domain support in Mailman?
(it can save me some time in experimenting further :-)
Sincerely, Gour
I have the same box serving out lists for (pseudo example): list1.foo.com and list2.bar.com. They are also tied via the web interface to the apache VH configuration associated with that host. My "real name" for each list never appears in header.
I don't (never have, never will) use QMail but Postfix.
-mj
On Tue, 2 Jul 2002, Gour wrote:
Stephane Bortzmeyer (bortzmeyer@netaktiv.com) wrote:
Yes but it still fails for OUTGOING mails. The real name still appears in many places. I can use Postfix's canonical to rewrite what's in the headers but it is painful.
And some messages like "We have received a request from 62.212.103.139 for subscription of your email address, bortzmeyer@gitoyen.net, to the REALNAME@VIRTUALDOMAIN mailing list." are not subject to customization.
I feel inclined to say that Mailman does not really support virtual domains :-(
I'm also trying to get "true" virtual support with Mailman & qmail and also realize that if I create test1@lists.net and test2@lists.net, and want them to appear as test@domain1.com and test@domain2.com, still I in the list info page they appear as test1 & test2 list ie. it's not possible to hide them.
Or I am missing something?
(each domain has its own listm but cannot hide real names.)
So, it is proper to conclude that there is no real true virtual domain support in Mailman?
(it can save me some time in experimenting further :-)
Sincerely, Gour
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
-
Gour -
Jon Carnes -
Michael Johnson -
Stephane Bortzmeyer