Broken Apache Config June 2013
Researching a formum call for help I discovered the procedures, at least with respect to Apache intergration were broken. Links to maillist information pages were broken.
I worked out a solution for Watnuss and applied the changes to this page. I made the change Apache specific because:
- The lighttpd integration does work
- My nginx installation gives 502 errors and I can't verify if the procedures are correct.
- It seemed best to make a single change
RFC for re-organization
The current Mailman page violates KISS. Serving multiple domains email lists from a specially named host? Let's get a simple, single list for a single web domain up first.
Inserting a base config section to get the reader up and configured with the default mailman list and a custom named list all of which is accessed through http:// www.example.org/lists/ URL would seem to be an improvement. The introduce serving lists for other web spaces, etc.
You can present the single domain setup in another section, showed before than the multiple domains'. I understand your point, but I think it does not justifies the deletion of useful information from the wiki.
The difference between both setups are two lines of code; it takes seconds to go from multiple domains to single, and several minutes to hours to do the opposite, if you do not have the recipe.
Apache Httpd Config
I would like to change the way the httpd is configured.
One is told to configure Mailman for httpd like this:
DEFAULT_URL_PATTERN = 'http://%s/lists/'
But you do not need this. You can use the normal way, if you change a little bit in the vhost config:
<IfModule alias_module> Alias /mailman-icons/ "/usr/lib/mailman/icons/" Alias /archives/ "/var/lib/mailman/archives/public/" ScriptAlias /admin /usr/lib/mailman/cgi-bin/admin ScriptAlias /admindb /usr/lib/mailman/cgi-bin/admindb ScriptAlias /confirm /usr/lib/mailman/cgi-bin/confirm ScriptAlias /create /usr/lib/mailman/cgi-bin/create ScriptAlias /edithtml /usr/lib/mailman/cgi-bin/edithtml ScriptAlias /listinfo /usr/lib/mailman/cgi-bin/listinfo ScriptAlias /options /usr/lib/mailman/cgi-bin/options ScriptAlias /private /usr/lib/mailman/cgi-bin/private ScriptAlias /rmlist /usr/lib/mailman/cgi-bin/rmlist ScriptAlias /roster /usr/lib/mailman/cgi-bin/roster ScriptAlias /subscribe /usr/lib/mailman/cgi-bin/subscribe ScriptAlias / /usr/lib/mailman/cgi-bin/listinfo </IfModule>
<IfModule alias_module> Alias /mailman-icons/ "/usr/lib/mailman/icons/" Alias /archives/ "/var/lib/mailman/archives/public/" ScriptAlias /lists/ "/usr/lib/mailman/cgi-bin/" ScriptAlias / "/usr/lib/mailman/cgi-bin/listinfo" </IfModule>
Also i would like to add the vhost config, so one can copy the whole section.
Any thoughts on that?
Mailman 3 Page
Hi, I saw you edited and merged my Mailman 3 page into the Mailman page. Thanks for noticing :-) Mailman 3 is a complete redesign of Mailman. Most of the configuration and commands of Mailman 2 are non-existent in Mailman 3. For that reason I think Mailman 3 should get it's own page, mentioning this in the Mailman 2 page. Currently Mailman 3 is only in the aur (I'm maintaining it). Once Mailman 3.1 is released I guess this will be integrated into the repos. Then the Mailman page should point to Mailman 3. --Simonsmiley (talk) 11:48, 17 September 2015 (UTC)
- Hi, are you going to expand the Mailman 3 info in the wiki before the official package is upgraded? Because otherwise it makes more sense if this page is simply updated (or rewritten as needed), thus keeping all the revisions history in the same place. Or are you aware of plans to maintain the legacy version in the official repos, thus making it worth having two Mailman articles? — Kynikos (talk) 08:27, 18 September 2015 (UTC)
- I don't think it will be a simple upgrade. The complete system will change. I don't know about how it will be handled officially. They could very much opt to maintain both versions. I guess I will contact the maintainer before continuing anything. I do think that the legacy article should be kept, because I think (personal opinion) that Mailman 2 will still be used for quite a while. However, it would be nice to have instructions for Mailman 3 to help people test it. Simonsmiley (talk) 21:12, 20 September 2015 (UTC)
- While reading this, and seeing the approach the package maintainer is taking (keeping the package at Mailman 2), I think it makes more sense to split this page into Mailman 2 and Mailman 3.
- I don't know a lot about Mailman however, so it might be better if someone else does it. The current layout of having documentation about two unrelated pieces of software on one page is unclear. -- Lonaowna (talk) 13:11, 24 May 2016 (UTC)