[Mailman-Users] Mailman and virtual domains...
Is it possible to have (a single instance of) Mailman installed and accessed by different domain names such that each domain sees a different set of mailing lists? I.e. example.com has the following lists comlist1 comlist2 example.net has the following lists netlist1 netlist2 example.org has the following lists orglist1 orglist2 I would like the Mailman interface on each domain (http://maillists.example.(com|net|org)/mailman/listinfo) to only show the lists appropriate for the domain. Is this possible? Grant. . . . -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
* Brad Knowles b...@shub-internet.org wrote: on 7/8/09 6:12 PM, Stefan Förster said: Thanks for your advice, Brad. The problem is that, due to policy reasons, outgoing mail has to pass a content filter, running locally on the Mailman box. With VERP... Chuq von Rospach wrote some stuff in the FAQ detailing his experience with how VERP impacted performance on the systems he was managing. Of course, this doesn't necessarily apply directly to your case, but it is instructive to read. To be honest - I never understood where he got his numbers from. Or to be more precisely, how he got that lucky (note that I obfuscated the listname): # list_members mylist | cut -d@ -f2 | sort | uniq -c | sort -rn | head -3 1414 gmx.de 1009 web.de 404 freenet.de # list_members mylist | wc -l 2966 For that list, there would be 5 connections from Mailman to the local MTA for 2827 recipients, followed by = 139 connections for the remainder of the whole list, i.e. no more than 144 delivery attempts. With VERP, there would be 2966 connections from Mailman to the local MTA. With the content filter set up the way it is, without VERP, the MTA would create no more than 144*2 queue files and the content filter would in turn create 144 subdirectories with about 3 files each, for a total of 720 files and 144 directories created/unlink'd. VERP'd, I'd have to create/unlink 14830 files and 2966 directories. And yes, I know that the MTA might create more than one file per message delivery - I was assuming the best case. Perhaps I just got unlucky with the recipient distribution for that particular list - if it is of any importance to the lsit archives, I'd gladly investigate other lists I'm running. Or perhaps you could provide some live data from python.org lists? BTW - will MM3 be able to utilize the VERP features offered by many modern MTAs? I guess I will simply move the list server to another computer (and a different network). OTOH, moving the mailing list function to a different server and separating that from the content scanning system is also a good idea, including lots of other reasons. My main reason to move the whole installation is mainly that in another network, I don't have to scan every outgoing message. After all, it's not Mailman's fault that the box is heavily loaded. Good luck, and I hope that this works out for you. Thank you, Brad. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
Grant Taylor wrote:
Is it possible to have (a single instance of) Mailman installed and
accessed by different domain names such that each domain sees a
different set of mailing lists? I.e.
example.com has the following lists
comlist1
comlist2
example.net has the following lists
netlist1
netlist2
example.org has the following lists
orglist1
orglist2
I would like the Mailman interface on each domain
(http://maillists.example.(com|net|org)/mailman/listinfo) to only show
the lists appropriate for the domain.
Mailman does this. If VIRTUAL_HOST_OVERVIEW is on (the default), Mailman
only shows the lists for the url host (domain) on the admin and listinfo
overview pages.
There are two possible issues. List names must be globally unique, and if
you know a list name, you can go to it from any host. E.g. using the
above, http://example.org/mailman/listinfo will show only orglist1 and
orglist2 (assuming they are public), but
http://example.org/mailman/listinfo/netlist1 will work to get netlist1's
listinfo page.
You need to have (e.g.) an
add_virtualhost('example.net', 'example.net')
directive in mm_cfg.py for each domain, except possibly the
DEFAULT_(URL|EMAIL)_HOST domain if it is properly set by configure in
Defaults.py, so that lists can be properly created.
See the FAQ at http://wiki.list.org/x/mIA9.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
Stefan Förster wrote: BTW - will MM3 be able to utilize the VERP features offered by many modern MTAs? There are patches for Postfix which can probably be adapted for other MTAs. See the thread Patch for use of Postfix VERP support starting at http://mail.python.org/pipermail/mailman-users/2009-January/064588.html. This seems to be a good idea for future Mailman. I don't know if Barry has thought about it for MM3, but I will look at it for 2.2. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
[Adding mailman-developers] On Jul 9, 2009, at 10:22 AM, Mark Sapiro wrote: Stefan Förster wrote: BTW - will MM3 be able to utilize the VERP features offered by many modern MTAs? There are patches for Postfix which can probably be adapted for other MTAs. See the thread Patch for use of Postfix VERP support starting at http://mail.python.org/pipermail/mailman-users/2009-January/064588.html . This seems to be a good idea for future Mailman. I don't know if Barry has thought about it for MM3, but I will look at it for 2.2. I have, and it doesn't look difficult to do, although I really want to rework the current delivery architecture so that it's more modular. This would also allow different lists to have different delivery mechanisms (e.g. bulk vs. individual) and should be more efficient and more extensible. VERPing is really only one half of the personalization or individual delivery story. Ideally it's the half that would by default always be enabled since it improves the reliability of your memberships. It's this part that would benefit greatly from adding MTA-specific support. I think Exim supports VERPing without an SMTP extension, and I get the impression it can be made to work in Sendmail too. The other half is really a mail merge operation, where the headers and footers (currently, but maybe someday the email body) contains placeholders that get filled in with personal information for the specific user. I'm not aware of a standard way to do this in any MTA, so I think if you want to do this kind of message body personalization, you still have to do that in Mailman. I'd like to support this better and would consider MTA-specific approaches. Mailman also supports something called full personalization which hacks other headers too. I put this in the category of mail merging since I'm not aware of any MTAs providing support for that either. -Barry PGP.sig Description: This is a digitally signed message part -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
On 7/9/2009 9:06 AM, Mark Sapiro wrote:
Mailman does this. If VIRTUAL_HOST_OVERVIEW is on (the default), Mailman
only shows the lists for the url host (domain) on the admin and listinfo
overview pages.
That's the impression that I got.
How do I associate what list is with what URL?
There are two possible issues. List names must be globally unique, and if
you know a list name, you can go to it from any host. E.g. using the
above, http://example.org/mailman/listinfo will show only orglist1 and
orglist2 (assuming they are public), but
http://example.org/mailman/listinfo/netlist1 will work to get netlist1's
listinfo page.
*nod*
I can live with that. (Or I can block it in Apache.)
You need to have (e.g.) an
add_virtualhost('example.net', 'example.net')
*nod*
directive in mm_cfg.py for each domain, except possibly the
DEFAULT_(URL|EMAIL)_HOST domain if it is properly set by configure in
Defaults.py, so that lists can be properly created.
See the FAQ at http://wiki.list.org/x/mIA9.
I'll take a look at the FAQ and see if I have any other questions.
Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
On 7/9/2009 1:17 PM, Taylor, Grant wrote: How do I associate what list is with what URL? Ok. It looks like I can use withlist to associate a URL with a list. Or at least this is the only thing that I've found thus far that ties a given list to a given URL. Is this correct? Is it possible to specify the URL at list creation time? (I'm creating lists with newlist.) Grant. . . . -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
On 7/9/2009 1:41 PM, Taylor, Grant wrote: Is it possible to specify the URL at list creation time? (I'm creating lists with newlist.) It looks like I can use pass command line options to newlist to create the list under the correct virtual domain. My problem was stemming from the fact that I was running newlist with out any parameters and filling in the questions interactively. Perhaps the interactive questions need to be extended? Grant. . . . -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
Grant Taylor wrote: On 7/9/2009 1:41 PM, Taylor, Grant wrote: Is it possible to specify the URL at list creation time? (I'm creating lists with newlist.) It looks like I can use pass command line options to newlist to create the list under the correct virtual domain. My problem was stemming from the fact that I was running newlist with out any parameters and filling in the questions interactively. Perhaps the interactive questions need to be extended? It looks like you've found answers to most of your questions, but to summarize, assuming you have the requisite add_virtualhost() directives, when creating a list from the web, it gets created in the domain of the url used to access the create page. When creating a list via newlist, there are a couple of ways to specify other than DEFAULT_(URL|EMAIL)_host for the list domain. See below. The domain of an existing list or lists can be changed by running fix_url under withlist. The -u/--urlhost and -e/--emailhost options are relatively recent additions to newlist. The existing interactive dialog wasn't changed when these were added for backwards compatibility reasons. In the past, and still, you can specify the domain for a list by specifying the listname as listn...@web_host. This is the same as specifying the list name as LISTNAME together with the --urlhost=WEB_HOST option. Note that this can be confusing because listn...@web_host is not necessarily the list posting address which is listn...@email_host. This is explained in the help for newlist. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
On 7/9/2009 4:55 PM, Mark Sapiro wrote:
It looks like you've found answers to most of your questions, but to
summarize, assuming you have the requisite add_virtualhost()
directives, when creating a list from the web, it gets created in the
domain of the url used to access the create page.
Yes I do have two add_virtualhost() directives. Per the Defaults.py
file comments I also am setting DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST
as the compile time config of the package from the distribution does not
match my needs.
DEFAULT_EMAIL_HOST = 'maillists.example.net'
DEFAULT_URL_HOST = 'maillists.example.net'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('groups.example.com', 'groups.example.com')
The domain of an existing list or lists can be changed by running
fix_url under withlist.
*nod*
The -u/--urlhost and -e/--emailhost options are relatively recent
additions to newlist. The existing interactive dialog wasn't changed
when these were added for backwards compatibility reasons.
Ah. That makes sense.
In the past, and still, you can specify the domain for a list by
specifying the listname as listn...@web_host. This is the same as
specifying the list name as LISTNAME together with the
--urlhost=WEB_HOST option. Note that this can be confusing because
listn...@web_host is not necessarily the list posting address which
is listn...@email_host. This is explained in the help for newlist.
I got the (mis)understanding that the listn...@web_host was deprecated
and might be removed at some point. Is this not the case?
I guess I should ask, what is the preferred method to do it going
forward? (If I'm going to learn it, I'd like to learn the proper and
preferred way.)
Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
Grant Taylor wrote: On 7/9/2009 4:55 PM, Mark Sapiro wrote: In the past, and still, you can specify the domain for a list by specifying the listname as listn...@web_host. This is the same as specifying the list name as LISTNAME together with the --urlhost=WEB_HOST option. Note that this can be confusing because listn...@web_host is not necessarily the list posting address which is listn...@email_host. This is explained in the help for newlist. I got the (mis)understanding that the listn...@web_host was deprecated and might be removed at some point. Is this not the case? You are correct. That is the case. I only mentioned it because it is at present the only way to specify a web host other than DEFAULT_URL_HOST in a pure dialog interaction with newlist. I guess I should ask, what is the preferred method to do it going forward? (If I'm going to learn it, I'd like to learn the proper and preferred way.) The preferred method is the -u/--urlhost option. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman and virtual domains...
On 7/9/2009 5:49 PM, Mark Sapiro wrote: You are correct. That is the case. I only mentioned it because it is at present the only way to specify a web host other than DEFAULT_URL_HOST in a pure dialog interaction with newlist. *nod* Thank you for the confirmation. The preferred method is the -u/--urlhost option. I'll start using that. Grant. . . . -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
