[Mailman-Users] Mailman without localhost

[Mark Sapiro]

On 11/11/2017 10:34 PM, Kapuzino wrote:

> He was doubtful to apply the patch, described in https://bugs.launchpad.net/mailman/+bug/558281 . 
...
> Is there meanwhile an implementation of this patch in newer version, so an reinstallation of MM gives secure and easy adjustments for that case? 


That "bug" was fixed in Mailman 2.1.23 released over a year ago
(27-Aug-2016). Any 2.1.23 or later Mailman should have this feature.


> Or a foolproof step by step instruction to fix it ? 


Nothing is foolproof ;)

The actual patch is at
<http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1649>.
To apply it in an older Mailman, go to that link and click the "download
diff" link to obtain the actual patch. To apply the patch to an
installed Mailman, change the first 3 lines from

=== modified file 'Mailman/Defaults.py.in'
--- Mailman/Defaults.py.in	2016-04-21 15:01:01 +0000
+++ Mailman/Defaults.py.in	2016-05-06 21:44:28 +0000

to

=== modified file 'Mailman/Defaults.py'
--- Mailman/Defaults.py		2016-04-21 15:01:01 +0000
+++ Mailman/Defaults.py		2016-05-06 21:44:28 +0000

I.e. change Defaults.py.in to Defaults.py and delete the lines beginning
with

=== modified file 'NEWS'
--- NEWS	2016-05-05 01:27:19 +0000
+++ NEWS	2016-05-06 21:44:28 +0000

Then, if you don't know how to apply the resulting patch, you probably
shouldn't be doing it, but with the modified patch in a file, cd to the
directory containing the Mailman/ directory and do

patch -p0 < /the/file/containing/the/patch

You will then have to set things like

SMTP_AUTH, SMTP_USER, SMTP_PASSWD, SMTP_USE_TLS, SMTPHOST and SMTPPORT
in mm_cfg.py.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan