[Mailman-Users] mailman httpd location question

[Mark]

Hi,

Under OpenBSD's httpd, my mailman setup gives an HTTP 404 error when
'mysite.com/listinfo' is
typed, however 'mysite.com/listinfo/' works.

In order to *solve* this issue, I added 2 different locations pointing to
the same cgi script, as:

location "/listinfo" {
fastcgi socket "/var/www/run/slowcgi.sock"
root "/usr/local/lib/mailman/cgi-bin/listinfo"
request strip 1
}

location "/listinfo/*" {
fastcgi socket "/var/www/run/slowcgi.sock"
root "/usr/local/lib/mailman/cgi-bin/listinfo"
request strip 1
}

The same goes for /create and other cgi scripts as well.

Wondering how to make both ways (with ending '/' and without) work?

Is there any parameter configuring this in mailman2?

Best wishes,
Mark.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@mail-archive.com

[Mailman-Users] Mailman 3 Issue - Unable to Authenticate with Mailman Core REST API

[Patricia Traore]

Fellow mailman enthusiasts,

I am configuring Mailman 3's web frontend components, Hyperkitty, based on the 
provided documentation: . 
I have successfully set up Django and completed various configuration steps, 
but I am encountering an issue with authenticating with the Mailman Core REST 
API.

Description of the issue:
→ Mailman core REST API Configuration: in the Django settings.py file, I have 
set the MAILMAN_REST_API_URL to the correct URL of the Core's REST API server 
(http://localhost:8001/). Additionally, I have specified the 
MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS with the appropriate 
credentials (default values used in the core are 'restadmin' and 'restpass').
→ Authentication failure: despite the correct configuration of the REST API 
settings, when attempting to interact with the Mailman Core REST API through 
Hyperkitty, authentication fails. Depicting that authentication credentials are 
invalid.
→ MAILMAN_ARCHIVER_KEY configuration: I have also configured the 
MAILMAN_ARCHIVER_KEY in the Django settings.py file, ensuring that it matches 
the value set in the mailman-hyperkitty.cfg file as per the documentation.
→ Documentation: I have carefully followed the documentation related to the 
Mailman REST API and the configuration parameters. However, I couldn't find any 
specific troubleshooting steps or additional settings that might be required to 
ensure successful authentication.

That's why I'm here seeking assistance to identify any potential 
misconfigurations or steps I might have missed in setting up the authentication 
between the Mailman web components and the Mailman Core REST API. Your 
insights, suggestions, or guidance on resolving this authentication issue would 
be highly appreciated.

Let me know if additional information or specific configurations are needed. 
Thanks in advance for your support!


Patricia T.
Flexing codes with .
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] Mailman 3 moderator login page as mailman 2.1 one

[aferreiro]

Hi, we have recently migrated from mailman 2.1 to mailman 3.
In mailman 2.1 moderators received  an email with a web link asking for list´s 
moderator password.
I don´t find and i don´t know if this feature is available on mailman 3.
If this option isn´t available, How can moderators  access a login page to 
moderate their lists ? 
Thanks.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] Mailman 2.1.15 doesn't allow admin changes on private lists

[Stephen J. Turnbull]

Charles Buckley writes:

 > I experimented with this a bit, and found that I could eliminate
 > the footer on my public (browsable) list on the same server. So I
 > tried converting my other private (non-browsable) list to be
 > browsable, at which point I could eliminate the footer, and then
 > switch the list back to being non-browsable.
 > 
 > But once I tried to implement the workaround on the non-browsable
 > list I wanted to change, I got the same defective behaviour when
 > trying to switch the list to be browsable

Did you test on the second private list *without* changing the
"private" flag?  If not, my guess is that the private flag is a red
herring, and that there is some other issue with the recalcitrant list
that causes you to get bounced back to the login page.

Please check the Mailman and webserver logs to see if there is
evidence of errors there.  With luck there will be a Python traceback
from an exception.  If you're using Apache as the webserver,
tracebacks are usually in the error.log, and there may be a 5xx status
in the access.log (I bet not though since you get served the login
page rather than a Server Error page, and that makes me somewhat
pessimistic about finding a traceback in error.log).

 > I saw a report of this behaviour on this mailing list from the year
 > 2000.

If you have an URL for this post, or a timestamp, or even a precise
date, it might be helpful.  I can't find it.

 > It is still going on now in 2023. One would think that some
 > information on how to workaround this bug would have been found
 > between now and back then. 

I rather doubt it's the same bug (but it's worth comparing).  Mailman
2.0 was in beta in 2000, and pretty much anything from mail composed
by badly written Japanese MUAs to mail composed by the even less
conformant Windows 2000 Outlook betas could crash it.  Mailman 2.1 was
released in 2006 with a *lot* of attention to input validation and
exception handling, although more on the email side than the web UI
side.

 > Note that, when I am able to successfully change a setting, I am
 > never sent back to the list admin login page.

That's expected.  My guess is that some content, probably an invisible
control character in a text field in the form (I've seen ^T mentioned
more than once, don't ask me why), is causing the form parser to raise
an exception, which who-knows-why gets caught by the not-logged-in
handler.  (My guesses are close to correct about 20% of the time.
Good enough to look there first, but don't bet your car. ;-)

I think all the browsers you mention have developer modes or plugins.
Mailman pages don't have horribly complicated DOMs, so if you want to
go through either the DOM or the page source for the form and see if
you can spot some weird character in one of the fields (likely, but
not certainly, the footer you're trying to change), you might have
some luck.  Also, "_" (underscore) may be a "weird character" --
Mailman 3's list importer complains about footers that contain it.
(Who knows why, I don't think it's weird, but Mailman 3 does kvetch.)

Regards,
Steve

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] Mailman 2.1.15 doesn't allow admin changes on private lists

[Charles Buckley]

I run three Mailman lists on my web server, one browsable and two 
non-browsable. I wanted to eliminate the footer that gets added to the bottom 
of messages distributed by one of the private (non-browsable) lists.

When I tried to do this, I would browse to the admin non-digest page, delete 
the contents of the Footer field, and hit "Submit my changes". This would send 
me to a login for admin privileges of the list in question. I would log back 
in, only to find myself on the page I had just modified, but the modification I 
made did not take place.

I experimented with this a bit, and found that I could eliminate the footer on 
my public (browsable) list on the same server. So I tried converting my other 
private (non-browsable) list to be browsable, at which point I could eliminate 
the footer, and then switch the list back to being non-browsable.

But once I tried to implement the workaround on the non-browsable list I wanted 
to change, I got the same defective behaviour when trying to switch the list to 
be browsable -- I would get redirected to the admin login page for the list in 
question, log in successfully, only to come back and find myself on the same 
privacy page, with no changes having been made.

I saw a report of this behaviour on this mailing list from the year 2000. It is 
still going on now in 2023. One would think that some information on how to 
workaround this bug would have been found between now and back then.

Note that, when I am able to successfully change a setting, I am never sent 
back to the list admin login page.

I have also posted this as a bug via the Mailman launchpad.  This behaviour 
appears to be browser-independent; I have tried it on Firefox, Chrome, and 
Edge.  

 

Any advice would be appreciated.

 

Charles Buckley

 

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] mailman 2.1.30 config

[Thomas Coradeschi via Mailman-Users]

Yes, I know a little behind in version updates. Any rate, I am trying to at 
least slow down the bots which are hammering our subscribe pages.

The challenge (and it’s all me) is in getting baby steps to work.

I am looking to start with SUBSCRIBE_FORM_SECRET, but honestly just don’t get 
the definition of a “non-empty string”

The default is SUBSCRIBE_FORM_SECRET = None

If I replace None with anything else, I get the following when I try to restart 
mailman

Traceback (most recent call last):
  File "../bin/mailmanctl", line 107, in 
from Mailman import mm_cfg
  File "/var/lib/mailman/Mailman/mm_cfg.py", line 167, in 
SUBSCRIBE_FORM_SECRET = random
NameError: name 'random' is not defined

—
Tom Coradeschi
tjc...@icloud.com


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

[Mailman-Users] mailman not sending email to all the members of mailing list

[Ninad via Mailman-Users]

Dear All,

Myself Ninad and we are using mailman 2.1.29 from long time. From last 
few days, I have observed a strange behavior in mailman. mailman not 
sending email to all the members of mailing list and the mail is getting 
posted to random members of the list.


Even "nomail" option is also not set for the members. I observed this 
issue with random mailing lists. Below are the some logs form the smtp 
log. I dont know how can I debug this issue. I kindly request all to 
guide me in this regard.


Nov 22 17:20:41 2022 (1322) 
 
smtp to list1 for 11 recips, completed in 1.202 seconds
Nov 22 17:20:41 2022 (1322) 
 
smtp to list1 for 4 recips, completed in 0.028 seconds
Nov 22 18:27:20 2022 (1322) 
 
smtp to list1 for 10 recips, completed in 0.283 seconds
Nov 04 11:09:42 2022 (1343) 
 
smtp to list1 for 11 recips, completed in 5.258 seconds


Nov 23 17:49:54 2022 (1322) 
<88544ba3992180de5188352919b97...@iitb.ac.in> smtp to list22 for 62 
recips, completed in 0.064 seconds
Nov 23 20:14:49 2022 (1322) 
<5565d2bfa86e838052cca3abea808...@iitb.ac.in> smtp to list22 for 63 
recips, completed in 0.397 seconds
Nov 14 08:00:03 2022 (1343) 
 smtp to list22 for 1 
recips, completed in 0.012 seconds
Nov 14 08:00:05 2022 (1343) 
 smtp to list22 for 2 
recips, completed in 0.010 seconds
Nov 14 09:41:49 2022 (1343) 
<86ef86895b0f73e7ad7022618706a...@iitb.ac.in> smtp to list22 for 62 
recips, completed in 0.033 seconds
Nov 14 12:49:04 2022 (1343) 
<850359ef924e3a0baccf7d61e6fc4...@iitb.ac.in> smtp to list22 for 63 
recips, completed in 0.025 seconds
Nov 14 15:28:20 2022 (1343) 
<4245de3a59b019b8f21e7266c30b7...@iitb.ac.in> smtp to list22 for 62 
recips, completed in 0.175 seconds
Nov 14 15:35:20 2022 (1343) 
 smtp to list22 for 63 
recips, completed in 0.027 seconds
Nov 14 16:33:39 2022 (1343) 
<7073bbae72718616732bd391fa1aa...@iitb.ac.in> smtp to list22 for 63 
recips, completed in 0.294 seconds


Regards,

Ninad.

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] mailman user problem

[Dennis Putnam]

I don't know what happened but mailman is no longer working (CentOS 7). 
I don't think it is mailman per se but I don't know where else to turn 
for help. I am feeding mailman using fetchmail from gmail.com which has 
been working fine for eons. For some reason fetchmail no longer works as 
I get this error:


Old UID list from pop.gmail.com: 

After considerable research I THINK I have traced the problem to the 
mailman account since fetchmail runs as mailman via cron. It appears 
that the crontab for mailman is gone and I cannot 'su - mailman' to run 
'crontab' on 'crontab.in'. Although isn't that supposed to happen 
automatically? Nor can I run fetchmail as mailman. I get the error:


This account is currently not available.

The passwd file entry is:

 mailman:x:41:41:GNU Mailing List Manager:/usr/lib/mailman:/sbin/nologin

I think it has always been that way but I'm not sure since 
'/sbin/nologin' means there is no shell and is why I am getting that 
error. I don't, at this point, see how it could have ever worked. In any 
case I need some help figuring out why mailman is getting that error.


FWIW, if I run 'passwd -S mailman', I get this:

mailman NP 2022-03-19 -1 -1 -1 -1 (Empty password.)

TIA



OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman data backup

[kukyayuni--- via Mailman-Users]

Hi

Please tell me about Mailman backup.
We want to back up our mailing list configuration data, archives, etc. without 
stopping the Mailman service.
Can you please tell us how to do this?
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.39 Release

[Mark Sapiro]

I am pleased to announce the release of Mailman 2.1.39.

This is a bug fix release. It fixes 
https://bugs.launchpad.net/mailman/+bug/1954694


This addresses two issues.

The fix for CVE-2021-42097 was case sensitive and should not be.
The fix for CVE-2021-44227 introduced a potential NameError in logging.

This could cause a user's changes to the option's page to not be 
accepted and perhaps cause a `We hit a bug` response if the user visited 
the page with a mixed- or upper-case email address


For those who just want a patch one is attached to the bug report.

As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1
branch from the GNU Mailman project. There has been some discussion as
to what this means. It means there will be no more releases from the GNU
Mailman project containing any new features. There may be future patch
releases to address the following:

i18n updates.
security issues.
bugs affecting operation for which no satisfactory workaround exists.

Mailman 2.1.39 is the ninth such patch release.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see our web site at one of:

http://www.list.org
https://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.39 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.38 security release

[Mark Sapiro]

A CSRF vulnerability has been reported by Riccardo Schirone of RedHat. 
This is assigned CVE-2021-44227. I plan to release Mailman 2.1.38 on 
Tuesday, 30 November to fix this.


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1 security release

[Mark Sapiro]

I am pleased to announce the release of Mailman 2.1.36.

This is a security release. It fixes 
https://bugs.launchpad.net/mailman/+bug/1949401 CVE-2021-43331 and 
https://bugs.launchpad.net/mailman/+bug/1949403 CVE-2021-43332. The 
former of these could allow an XSS attack against the user options page 
and the latter could allow a list moderator to discover the list admin 
password via a brute force attack against the admindb page CSRF token.


For those who just want a patch for the security issues, patches are 
atteched.


As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1
branch from the GNU Mailman project. There has been some discussion as
to what this means. It means there will be no more releases from the GNU
Mailman project containing any new features. There may be future patch
releases to address the following:

   i18n updates.
   security issues.
   bugs affecting operation for which no satisfactory workaround exists.

Mailman 2.1.36 is the sixth such patch release.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see our web site at one of:

http://www.list.org
https://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.36 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
=== modified file 'Mailman/Cgi/options.py'
--- old/Mailman/Cgi/options.py  2021-10-18 23:56:42 +
+++ new/Mailman/Cgi/options.py  2021-11-03 19:02:21 +
@@ -346,6 +346,8 @@
 varhelp = qs[0]
 if varhelp:
 # Sanitize the topic name.
+while '%' in varhelp:
+varhelp = urllib.unquote_plus(varhelp)
 varhelp = re.sub('<.*', '', varhelp)
 topic_details(mlist, doc, user, cpuser, userlang, varhelp)
 return
=== modified file 'Mailman/Cgi/admindb.py'
--- old/Mailman/Cgi/admindb.py  2018-06-17 23:47:34 +
+++ new/Mailman/Cgi/admindb.py  2021-11-03 19:04:49 +
@@ -59,8 +59,7 @@
 else:
 ssort = SSENDER
 
-AUTH_CONTEXTS = (mm_cfg.AuthListAdmin, mm_cfg.AuthSiteAdmin,
- mm_cfg.AuthListModerator)
+AUTH_CONTEXTS = ((mm_cfg.AuthListModerator,))
 
 
 


OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1 security release

[Mark Sapiro]

Two new security issues have been reported in Mailman 2.1. These have 
been given the IDs CVE-2021-43331 and CVE-2021-43332.


I plan to release 2.1.36 with full details this Friday, November 12. At 
that time the vulnerabilities will be made public and patches will also 
be made available.


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman in two servers

[Ivan Tejeiro Izquierdo]

Hi,
Is it possible to run mailman on 2 servers at the same time? What directories 
should be shared between both servers and how to configure the mm_cfg.py?
Thanks.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1 security release

[Mark Sapiro]

A couple of vulnerabilities have recently been reported. Thanks to Andre 
Protas, Richard Cloke and Andy Nuttall of Apple for reporting these and 
helping with the development of a fix.


CVE-2021-42096 could allow a list member to discover the list admin 
password.


CVE-2021-42097 could allow a list member to create a successful CSRF 
attack against another list member enabling takeover of the members account.


These attacks can't be carried out by non-members so may not be of 
concern for sites with only trusted list members.


In any case, I am planning to make a 2.1.35 release and to post a patch 
for those who don't want to upgrade to address these issues. This is 
scheduled for Tuesday, October 19.


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



OpenPGP_signature
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman + postfix automatically adding aliases

[Bruce Johnson via Mailman-Users]

I'm setting up a new CentOS8 mailman server to take over from our ancient 
existing one, and have run into some issues trying to get it working.

I installed mailman from source, following the directions here: 

https://wiki.list.org/DOC/How%20do%20I%20upgrade%20a%20RHEL/CentOS%20Mailman%20package%20from%20source.

I'm at: 
https://www.gnu.org/software/mailman/mailman-install/postfix-integration.html

Run the bin/genaliases script to initialize your aliases file.
% cd /usr/local/mailman
% bin/genaliases

But when I do this I get the following. Am I supposed to create these 
data/aliases files manually? Where are they supposed to go? There is no data/ 
directory in /usr/lib/mailman and /var/lib/mailman has a data directory but 
nothing inside named aliases


[root@dhbmailman2 mailman]# bin/genaliases 
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:

## newserver_test mailing list
newserver_test:  "|/usr/lib/mailman/mail/mailman post 
newserver_test"
newserver_test-admin:"|/usr/lib/mailman/mail/mailman admin 
newserver_test"
newserver_test-bounces:  "|/usr/lib/mailman/mail/mailman bounces 
newserver_test"
newserver_test-confirm:  "|/usr/lib/mailman/mail/mailman confirm 
newserver_test"
newserver_test-join: "|/usr/lib/mailman/mail/mailman join 
newserver_test"
newserver_test-leave:"|/usr/lib/mailman/mail/mailman leave 
newserver_test"
newserver_test-owner:"|/usr/lib/mailman/mail/mailman owner 
newserver_test"
newserver_test-request:  "|/usr/lib/mailman/mail/mailman request 
newserver_test"
newserver_test-subscribe:"|/usr/lib/mailman/mail/mailman subscribe 
newserver_test"
newserver_test-unsubscribe:  "|/usr/lib/mailman/mail/mailman unsubscribe 
newserver_test"

## mailman mailing list
mailman:  "|/usr/lib/mailman/mail/mailman post mailman"
mailman-admin:"|/usr/lib/mailman/mail/mailman admin mailman"
mailman-bounces:  "|/usr/lib/mailman/mail/mailman bounces mailman"
mailman-confirm:  "|/usr/lib/mailman/mail/mailman confirm mailman"
mailman-join: "|/usr/lib/mailman/mail/mailman join mailman"
mailman-leave:"|/usr/lib/mailman/mail/mailman leave mailman"
mailman-owner:"|/usr/lib/mailman/mail/mailman owner mailman"
mailman-request:  "|/usr/lib/mailman/mail/mailman request mailman"
mailman-subscribe:"|/usr/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe:  "|/usr/lib/mailman/mail/mailman unsubscribe mailman"


-- 
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman instance suddenly stopped working

[Kevin Bowen]

Hello,
My ancient mailman installation, 2.1.9 (yes, I know, I'm in the process of
decommissioning it) suddenly stopped working overnight. When I send a test
message to a test list, I see it being received by sendmail in
/var/log/maillog:
Aug 11 09:19:53 mailman sendmail[29533]: 17BGJi9w029255:
to="|/usr/lib/mailman/mail/mailman post kbowentest-l",
ctladdr= (8/0), delay=00:00:08,
xdelay=00:00:00, mailer=prog, pri=124726, dsn=2.0.0, stat=Sent

But then it never shows up in the mailman logs and never gets posted:
[root@mailman mailman]# grep kbowentest-l /var/log/mailman/*
[root@mailman mailman]#

I've restarted mailman and sendmail, and don't see any obvious problems. No
configurations have changed recently aside from deleting some lists. I
haven't worked on this in quite some time, can anyone point me to some
emergency troubleshooting ideas?

Kevin Bowen
kevin.t.bo...@gmail.com 
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] #mailman irc channel moving to libera.chat

[Abhilash Raj]

Hey Everyone,

As some of you might already know that Freenode IRC server now has new owners
and most of the volunteer staff have decided to move away from it to create a 
new
IRC server libera.chat[1] due to the policies of the new owners.

Along with many other open source projects, we have also decided to move away 
from
freenode to use libera.chat instead. We have registered #mailman there and will 
be using
that as primary IRC channel for Mailman things.

Freenode has also decided to drop all registrations, so, #mailman channel there 
is
no longer registered to any member of Mailman Core team as of some time earlier
today (Tue June 15th).


[1]: https://libera.chat/

-- 
  thanks,
  Abhilash Raj (maxking)
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] mailman held pck messages problem errors

[Ivan Tejeiro Izquierdo]

Hi,

I deleted a four pck files in /var/lib/mailman/data (heldmsg-mailman-x.pcki) n 
redhat server where the pck held messages are stored and now, I received this 
messages form mailman


regular_text: Subject: [abrt] mailman: dumpdb:128:main:IOError: [Errno 2] No 
such file
regular_text:  or directory: 'heldmsg-mailman-12.pck'
regular_text: Message-ID: <60c05f08.RQPXfjdnphKh2T7P%user@localhost>
regular_text: User-Agent: Heirloom mailx 12.5 7/5/10
regular_text: MIME-Version: 1.0
regular_text: Content-Type: text/plain; charset=us-ascii
regular_text: Content-Transfer-Encoding: quoted-printable
regular_text: 
regular_text: reason: dumpdb:128:main:IOError: [Errno 2] No such file 
or dire=
regular_text: ctory: 'heldmsg-mailman-12.pck'
regular_text: cmdline:/usr/bin/python /usr/lib/mailman/bin/dumpdb -p 
heldmsg-=
regular_text: mailman-12.pck
regular_text: executable: /usr/lib/mailman/bin/dumpdb
regular_text: package:mailman-2.1.15-30.el7
regular_text: component:  mailman
regular_text: pid:60541
regular_text: hostname:   vlin-rh-mail1
regular_text: count:  2
regular_text: abrt_version:   2.1.11
regular_text: analyzer:   Python
regular_text: architecture:   x86_64
regular_text: duphash:b612c1ceac5448c796fdfe342ddca8dd39680f04
regular_text: event_log: =20
regular_text: kernel: 3.10.0-1160.24.1.el7.x86_64
regular_text: last_occurrence: 1623219975
regular_text: os_release: Red Hat Enterprise Linux Server release 7.9 
(Maipo)
regular_text: pkg_arch:   x86_64
regular_text: pkg_epoch:  3
regular_text: pkg_fingerprint: 199E 2F91 FD43 1D51
regular_text: pkg_name:   mailman
regular_text: pkg_release:30.el7
regular_text: pkg_vendor: Red Hat, Inc.
regular_text: pkg_version:2.1.15
regular_text: runlevel:   N 3
regular_text: time:   Mon 07 Jun 2021 09:15:09 PM CEST
regular_text: type:   Python
regular_text: uid:0
regular_text: username:   root
regular_text: uuid:   b612c1ceac5448c796fdfe342ddca8dd39680f04
regular_text: 
regular_text: backtrace:
regular_text: :dumpdb:128:main:IOError: [Errno 2] No such file or directory: 
'heldmsg=
regular_text: -mailman-12.pck'
regular_text: :
regular_text: :Traceback (most recent call last):
regular_text: :  File "/usr/lib/mailman/bin/dumpdb", line 156, in 
regular_text: :msg =3D main()
regular_text: :  File "/usr/lib/mailman/bin/dumpdb", line 128, in main
regular_text: :fp =3D open(filename)
regular_text: :IOError: [Errno 2] No such file or directory: 
'heldmsg-mailman-12.pck'
regular_text: :
regular_text: :Local variables in innermost frame:
regular_text: :load: 
regular_text: :opt: '-p'
regular_text: :pp: 
regular_text: :args: ['heldmsg-mailman-12.pck']
regular_text: :filetype: 0
regular_text: :doprint: True
regular_text: :filename: 'heldmsg-mailman-12.pck'
regular_text: :typename: 'pickle'
regular_text: :arg: ''
regular_text: :opts: [('-p', '')]
regular_text: environ:
regular_text: :LANG=3Des_ES.UTF-8
regular_text: :TERM=3Dxterm
regular_text: :SHELL=3D/bin/bash
regular_text: :SHLVL=3D1
regular_text: :OLDPWD=3D/home/soporte
regular_text: :HOSTNAME=3Dvlin-rh-mail1
regular_text: :LESSOPEN=3D||/usr/bin/lesspipe.sh %s
regular_text: :HISTSIZE=3D1000
regular_text: :HISTCONTROL=3Dignoredups
regular_text: :PWD=3D/tmp/1
regular_text: :LOGNAME=3Droot
regular_text: :USER=3Droot

I understand that it is looking for that pck file and cannot find it, I deleted 
them because I thought they were not used at all. I have seen that the mailman 
service is fully operational, but I like stop this errors.
How can I solve this problem?.
Thank you. so much.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2 settings to minimise bounces

[jonathan.mailing.lists]

I've had quite a lot of bounces recently. This seems largely to have been
because my hosting company was having difficulty sending to Outlook (and
therefore maybe Microsoft servers generally). But I've been taking more
interest in the bounce messages as well.

 

These have included "Rejected by header based Anti-Spoofing policy" (an
organisation using Mimecast recognising its own email address in the From:
header), "DMARC Verification Failed" for a domain with p=reject (despite
dmarc_moderation_action being Munge From), "This email has been delivered to
the intended recipient, but our email system has identified that DKIM
Signing is missing or has been misconfigured. Please ask your IT department
to configure DKIM Signing to allow us to confirm the authenticity of your
emails." (despite the hosting company having the right DKIM record) and
more.

 

I have added REMOVE_DKIM_HEADERS = Yes to mm_cfg.py and restarted Mailman,
and changed from_is_list from No to Munge From.

 

Nobody seems to mind that all emails are now from the list address -
reply_goes_to_list was already set to This list, and now the sender's own
email address now appears in the Cc: header.

 

Is there anything I could do as well as or instead of that?

 

Thanks

 

Jonathan 

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1 - notifications not being properly sent to list owner

[David Nicol]

 I recently rebuilt my server (Ubuntu 20.04) and rebuilt mailman 2 -
upgrading to the latest version 2.1.34. The mail server is postfix

I run three mailing lists, including "TESTmail". The same issue below
affects all three lists which are set up in the same way.

On the General Page, I have filled in an administrator and a owner. The
list options are set so that emails from non-members are held and the
moderator should be notified.
* The poster of the email receives a notification that the email is being
held
* The moderator does not receive any messages
* But looking at the postfix logs, it appears to me that mailman does try
to send a message to the moderator

Apr  5 22:12:05 ip-xxx-xxx-xxx-xxx postfix/smtp[9473]: 6D0973EB91: to=<
testmail-ow...@lists.xxx.org.uk>,

But, the email message is being sent to the generic owner, rather than the
specific names filled into either the moderator or administrator boxes on
the general tab.

Also, I note that the footer of the mailing list has:
   TESTmail list run by testmail-owner at lists.XXX.org.uk
rather than the specific owner. Which suggests the same issue.

Any clues as to what is not quite correct in the mailman setup?
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman Grey listing Member Disablement Question

[pwilliam]

Hi,

We're running Mailman version 3 that's using a mail relay for sending mail. 
We've been running into issues where many mailing list members are being 
disabled due to their mail servers using grey listing through Mimecast. Sending 
mail to an individual user from the relay server directly results in the 
message being sent, as the mail is retried after one minute and is allowed 
through. I'm noticing that it seems like when Mailman sends mailing list 
messages to these users it seems like the message is not being retried after a 
minute, or that mailman is interpreting the grey listing as a bounce back and 
disabling the member as a result.

I realize this could be a MTA issue, but I was wondering if any one else has 
come across this before and how they've fixed it. Any help is greatly 
appreciated!
Peter
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman Archives problem

[sundar]

Hi,

I am using mailman 2.1.29, pipermail 0.09 , I am facing a problem with the
archives attachment.  The HTML attachments are scrubbed in the url like
"mailman/private/announce/attachments/20191231/1ef651ee/*attachment.htm*" ,
when we open that url it shows as  a html source code.   can anyone help me
with this issue?

It show as following :

html>


















" रोज एक हिन्दी
शब्द सीखें "



























-- 
Regards,
Sundar
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.24 Recurring Pending Requests

[jackson]

Some time ago, spam received from a faked address.

Admin email received 8am each morning listing the pending
posts from non-members.

Go in and:

1. select 'Reject' on each post
2. add the faked sender to the block from subscribing filter
3. submit all data

Mailman reports "There are no pending requests."

Tomorrow the same thing happens reporting the same historic
date of the non-member post.

* Have checked mailserver logs; not being received daily
* Have added fake addresses to upstream anti-spam blacklist

So, narrowing-down, seems Mailman has groundhog day syndrome?
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman-2.1.34 with Captcha

[Odhiambo Washington]

Hello good people,

Which of the many HOWTOs online is the recommended one for integrating
Captcha with mailman-2.1.34?

-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] mailman 2 and postfix problem

[Steven Jones]

Hi,

I am trying to setup a mailman 2 instance on RHEL8.2 and postfix seems to be 
rejecting the input, not sure if it is a Postfix issue or a Mailman issue.  The 
list aaa-seteven is in the aliases file in /etc/mailman


telnet vuwunicomailmd1.ods.vuw.ac.nz 25
Trying 130.195.14.234...
Connected to vuwunicomailmd1.ods.vuw.ac.nz.
Escape character is '^]'.
220 lists.victoria.ac.nz ESMTP Postfix
ehlo vuwunicossj0002.ods.vuw.ac.nz
250-lists.victoria.ac.nz
250-PIPELINING
250-SIZE 3072
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 SMTPUTF8
mail from:ste...@.ac.nz
250 2.1.0 Ok
rcpt to: aaa-ste...@lists.victoria.ac.nz
550 5.1.1 : Recipient address rejected: User 
unknown in local recipient table
quit
221 2.0.0 Bye
Connection closed by foreign host.

any idea please?




regards

Steven



regards

Steven
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] mailman v2.x

[Stephen J. Turnbull]

Jim Popovitch via Mailman-Users writes:

 > A couple of days ago, over on the MAILOP mailinglist, there was a
 > long thread titled 'Mailman confirmation email denial of service'.

*sigh* The price of success.  Of course this can be done with any
automated service that accepts an email address as an identity, eg,
Wordpress blog comment sections.

 > Recently, a kind person submitted a patch [1] to Mailman for
 > hCAPTCHA an alternative to ReCAPTCHA.  In the discussion of that
 > patch, Mark has stated that he is not interested in any more
 > features for Mailman 2.x.

[...]

 > So, I have volunteered to spearhead an effort to add one or two
 > more people to the Mailman Coders group[2] in order to vet and
 > approve new features that continue the long tradition of providing
 > value to Mailman 2.x.  Who's with me on this?

In the following I'm expressing personal opinions and suggestions,
which should not be taken as representing the position of the Mailman
Project.

I'm not willing to join the group.  I've thrown my lot in with Mailman
3, and don't have energy to spare for new development on Mailman 2.
However, if I can contribute support to Mailman 2 users, I'll do that.
I don't object to people making efforts to maintain Mailman 2, nor do
I begrudge sharing Mailman resources (including the mailing lists and
official repos) -- our hosts are quite elastic about the resources we
use, it's no cost to us.  On the contrary, aside from the intrinsic
value to Mailman 2 users, it's an interesting social experiment.
There was a lot of grumbling about maintaining Python 2, but nothing
ever came of it.  I'd like to see if you can make this work, and I'll
be rooting for your success.

I (again, this is me, I am not speaking for the team) would appreciate
it if you could come up with team nickname or motto to express that
you're not the same as the core project (at least for now).  And you
probably don't want to overpromise.  "Classic Mailman Volunteer Fire
Dept" is the best I can think of offhand.[1]

Steve

Footnotes: 
[1]  Remember, "Classic Coke" won in the end. ;-)

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] mailman v2.x

[Jim Popovitch via Mailman-Users]

Hi Folks,

A couple of days ago, over on the MAILOP mailinglist, there was a long
thread titled 'Mailman confirmation email denial of service'.  This
detailed some of the problems we've all seen with Mailman subscription
spam.  The Mailman team has addressed a lot of these problems with 
ReCAPTCHA support and additional configuration options.  Arguably the
best solution has been the ReCAPTCHA integration.  BUT, a lot of people
don't like the Google tie-ins that come with ReCAPTCHA. 

Recently, a kind person submitted a patch [1] to Mailman for hCAPTCHA an
alternative to ReCAPTCHA.  In the discussion of that patch, Mark has
stated that he is not interested in any more features for Mailman 2.x. 
I think that is fine, Mark has given decades of this time to Mailman and
I think it's perfectly natural for him to want to move on.  He deserves
a lot of credit for Mailman's success, both the 2.x and 3.x branches. 

So, I have volunteered to spearhead an effort to add one or two more
people to the Mailman Coders group[2] in order to vet and approve new
features that continue the long tradition of providing value to Mailman
2.x.  Who's with me on this?



1. https://code.launchpad.net/~jks/mailman/hcaptcha/+merge/389691

2. https://launchpad.net/~mailman-coders/+members#active


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman error sending email when Mailman not installed

[markandrewellis]

Hello I have recently taken over management of a website for my advanced 
motorcyclists' group. The site is Wordpress based and we are setting up a 
mailing list using the WP Mailster plugin. However, when sending an email to 
the list I receive the following error:

"This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its 
recipients. This is a permanent error. The following address(es) failed:

  pipe to |/usr/local/cpanel/3rdparty/mailman/mail/mailman post 
committee_mbeam.org.uk
generated by commit...@mbeam.org.uk
local delivery failed"

As stated in the thread title, Mailman is not installed in Cpanel as our 
hosting provider does not allow it to be used. Speaking to the previous 
webmaster it seems that Mailman was used with a previous hosting provider, so 
I'm wondering if some configuration may have been copied across with the 
website to the new host server which could cause this error.

I have searched the directories and found several one directory and several 
files with Mailman in the title or text. The directory is 
/.cpanel.mailmanconfig and contains files for each of the lists that were used 
with Mailman and each file contains text similar to: 

{"owner": ["li...@mbeam.org.uk"], "private_roster": 1, "archive_private": 0, 
"advertised": 0, "subscribe_policy": 2}

There are two directories files in the cpanel cache from 2012 and 2017 that 
refer to mailman-list-usage. 

To test if any of these files were causing the problem, I renamed them with a 
bak prefix, but I still receive the same error.

Siteground support has looked at the site for me and said that there does not 
appear to be any config file that should not be there, but as WP Mailster is 
third party software and they do not support Mailman, they can't help further.

I should add that we have used phplist and that works without any errors.

Any advice will be gratefully received.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.34 released

[Mark Sapiro]

I am pleased to announce the release of Mailman 2.1.34.

This is a minor bug fix release and has updates to the Spanish i18n. See
the attached README.txt for details.

As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1
branch from the GNU Mailman project. There has been some discussion as
to what this means. It means there will be no more releases from the GNU
Mailman project containing any new features. There may be future patch
releases to address the following:

   i18n updates.
   security issues.
   bugs affecting operation for which no satisfactory workaround exists.

Mailman 2.1.34 is the fourth such patch release.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see our web site at one of:

http://www.list.org
https://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.34 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
2.1.34 (26-Jun-2020)

  i18n

- The Spanish translation has been updated by Omar Walid Llorente.

  Bug Fixes and other patches

- The fix for LP: #1859104 can result in ValueError being thrown on
  attempts to subscribe to a list. This is fixed and extended to apply
  REFUSE_SECOND_PENDING to unsubscription as well.  (LP: #1878458)

- DMARC mitigation no longer misses if the domain name returned by DNS
  contains upper case.  (LP: #1881035)

- A new WARN_MEMBER_OF_SUBSCRIBE setting can be set to No to prevent
  mailbombing of a member of a list with private rosters by repeated
  subscribe attempts.  (LP: #1883017)

- Very long filenames for scrubbed attachments are now truncated.
  (LP: #1884456)
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.12 and issues with TLS 1.2 and DMARC

[Jonathan Ashby]

Hello

I wonder if you can help.

My organisation represents and supports GPs across most of London. We have 
elected representatives and we use Mailman mailing lists to provide listservers 
to elected representatives.

We currently use version 2.1.12 (http://lists.lmc.org.uk/mailman/admin) but I 
am aware of changes with TLS and DMARC are starting to effect our messages to 
listserver members. An example is doctors.org email addresses do not accept our 
listserver messages because the DMARC settings in their systems sees the 
‘sender’ is sending mail out purporting to be from the email address of the 
person posting the entry on the listserver, which they regard as spoofing.

We send emails to NHS mail addresses which currently reach their destination 
but I am aware that NHS mail is going to move to Exchange Online next month.

I am looking at ways to future proof our listservers as they are such an 
important part of our communication strategy.

Are you able to assist in providing me with guidance on the steps I should be 
taking?

Many thanks in advance.

Best wishes.

Jonathan

Jonathan Ashby
Head of Communications and ICT
Londonwide LMCs and Londonwide Enterprise Ltd
Direct dial: 020 3818 6228
Mobile: 07768 109601
Fax: 020 7383 7442
Email: jonathan.as...@lmc.org.uk
Web: www.lmc.org.uk
Twitter: @LondonwideLMCs


Visit 
www.lmc.org.uk/coronavirus-covid-19 
for the latest official resources and guidance on covid-19.

Remember that you can use WhatsApp and FaceTime for online consultations as 
well as the usual online tools.

Think of the environment - do you really need to print this email?

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please accept our apologies and notify 
the sender.

The registered and office address for Londonwide Local Medical Committees 
Limited is: Tavistock House South, Tavistock Square, London WC1H 9LG. 
Registered in England No: 6391298.

Londonwide Enterprise Limited is a wholly owned subsidiary of Londonwide Local 
Medical Committees Limited. Londonwide Enterprise Limited is registered at: 
Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England 
No. 6990874. Londonwide Enterprise Limited is registered as a Company Limited 
by Shares. VAT no: 130 1454 66.

Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited 
do not provide legal or financial advice and thereby excludes all liability 
howsoever arising in circumstances where any individual, person or entity has 
suffered any loss or damage arising from the use of information provided by 
Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited 
in circumstances where professional legal or financial advice ought reasonably 
to have been obtained.

Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited 
provide guidance and support to GPs and practice teams in the Londonwide area. 
Additionally Londonwide Local Medical Committees Limited provides 
representation to GPs and practice teams in the Londonwide area. Londonwide 
Local Medical Committees Limited and Londonwide Enterprise Limited strongly 
advises individuals or practices to obtain independent legal or financial 
advice.



__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] mailman stopped working

[csa--- via Mailman-Users]

Running Ubuntu 16.04.6 LTS  
kernel version: 4.4.0-179-generic

I've not updated the server as in the past doing that broke Mailman

over the past few days mailman just decided to stop working. Rebooting has
not helped. Logfiles show

/var/log/mailman# more qrunner
Jun 04 06:25:02 2020 (1884) RetryRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1881) NewsRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1882) OutgoingRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1880) IncomingRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1883) VirginRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1879) CommandRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1877) ArchRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1878) BounceRunner qrunner caught SIGHUP.  Reopening
logs.
Jun 04 06:25:02 2020 (1876) Master watcher caught SIGHUP.  Re-opening log
files.

My mail.err shows lots of these entries:
Jun  5 05:05:01 mahavihara postfix/smtps/smtpd[26213]: warning:
unknown[52.185.149.198]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun  5 05:05:01 mahavihara postfix/smtps/smtpd[26213]: lost connection after
AUTH from unknown[52.185.149.198]
Jun  5 05:05:01 mahavihara postfix/smtps/smtpd[26213]: disconnect from
unknown[52.185.149.198] ehlo=1 auth=0/1 commands=1/2
Jun  5 05:05:43 mahavihara postfix/smtps/smtpd[26698]: connect from
unknown[52.185.149.198]
Jun  5 05:05:48 mahavihara postfix/smtps/smtpd[26698]: warning:
unknown[52.185.149.198]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun  5 05:05:52 mahavihara postfix/smtps/smtpd[26698]: lost connection after
AUTH from unknown[52.185.149.198]

went through this
https://www.gnu.org/software/mailman/mailman-install/troubleshooting.html 

please advise. Thank you!

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2&3 coexistence

[Lars Bjørndal]

Hi

Is it safe/ok to have Mailman 2 and 3 both installed on the sam system,
using Mailman 3 for new lists?

Thanks
Lars
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] MAILMAN Sender name

[justinhumphres--- via Mailman-Users]

My question is how can I in the settings for when I email out the mass email 
that it says from: bbcn...@bellviewbaptistpaducah.com instead of being from my 
work email of: jus...@bellviewbaptistpaducah.com? I know it’s probably very 
simple, but any help would be great thanks!
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.33 released.

[Mark Sapiro]

For the third time in as many days I have released a new Mailman 2.1
version. This one is 2.1.33 and fixes another content injection
vulnerability. See the attached README.txt and the bug report at
https://bugs.launchpad.net/mailman/+bug/1877379 for details.

Again, for those who don't want to install the full update, the above
bug report contains a simple patch to fix the security issue.

As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1
branch from the GNU Mailman project. There has been some discussion as
to what this means. It means there will be no more releases from the GNU
Mailman project containing any new features. There may be future patch
releases to address the following:

i18n updates.
security issues.
bugs affecting operation for which no satisfactory workaround exists.

Mailman 2.1.31 is the first such patch release, Mailman 2.1.32 is the
second and Mailman 2.1.33 is the third.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see our web site at one of:

http://www.list.org
https://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.33 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
2.1.33 (07-May-2020)

  Security

- A content injection vulnerability via the private login page has been
  fixed.  (LP: #1877379)

2.1.32 (05-May-2020)

  i18n

Fixed a typo in the Spanish translation and uptated mailman.pot and
the message catalog for 2.1.31 security fix.

2.1.31 (05-May-2020)

  Security

- A content injection vulnerability via the options login page has been
  discovered and reported by Vishal Singh. This is fixed.  (LP: #1873722)

  i18n

- The Spanish translation has been updated by Omar Walid Llorente.

  Bug Fixes and other patches

- Bounce recognition for a non-compliant Yahoo format is added.

- Archiving workaround for non-ascii in string.lowercase in some Python
  packages is added.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.31 security release

[Mark Sapiro]

I am pleased to announce the release of Mailman 2.1.31

Python 2.6 is the minimum supported, but Python 2.7, preferably 2.7.17 -
the final Python 2 release, is strongly recommended.

This is a security fix release with an update to the Spanish translation
and another couple of minor fixes. See the attached README.txt and the
bug report at  for details.

For those who don't want to install the full update, the above bug
report contains a simple patch to fix the security issue.

As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1
branch from the GNU Mailman project. There has been some discussion as
to what this means. It means there will be no more releases from the GNU
Mailman project containing any new features. There may be future patch
releases to address the following:
 - i18n updates.
 - security issues.
 - bugs affecting operation for which no satisfactory workaround exists.

Mailman 2.1.31 is the first such patch release

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see our web site at one of:

http://www.list.org
https://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.31 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
2.1.31 (05-May-2020)

  Security

- A content injection vulnerability via the options login page has been
  discovered and reported by Vishal Singh. This is fixed.  (LP: #1873722)

  i18n

- The Spanish translation has been updated by Omar Walid Llorente.

  Bug Fixes and other patches

- Bounce recognition for a non-compliant Yahoo format is added.

- Archiving workaround for non-ascii in string.lowercase in some Python
  packages is added.


signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Mailman 2.1.30 released

[Mark Sapiro]

 to send the confirmation
  request message to a new subscriber has been fixed.  (LP: #1851442)

- The SimpleMatch heuristic bounce recognizer has been improved to not
  return most invalid email addresses.  (LP: #1859011)



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman queues

[Mark Sapiro]

On 3/16/20 1:20 PM, k...@keldix.com wrote:
> I have a problem with removing failing subscription requests
> eg from a bogus requester. I thought I could remove the request
> from a queue somewhere but cannot find it.
> the subscription requests keep recurring, over 1000 in my maillog -postfix


The requests waiting user confirmation are in the file
lists/LIST_NAME/pending.pck. Requests waiting moderator action are in
the file lists/LIST_NAME/requests.pck.

There are scripts at <https://www.msapiro.net/scripts/> (mirrored at
<https://fog.ccsf.edu/~msapiro/scripts/>) which can help with this. In
particular, "erase" and "list_requests". Also, the withlist script
"discard_subs.py".

More recent Mailman has defenses against robotic web subscribes, but
none are in 2.1.9.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman queues

[keld]

I have a problem with removing failing subscription requests
eg from a bogus requester. I thought I could remove the request
from a queue somewhere but cannot find it.
the subscription requests keep recurring, over 1000 in my maillog -postfix

I looked in /var/spool/mailman , but no ordinary files in the dirs.
running 2.1.9 in a somewhat complex env, mulitiple domains.

keld
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 2.1.30rc1 released

[Mark Sapiro]

Over a month ago, I posted the following announcement particularly
asking for i18n updates prior to the final release of Mailman 2.1.

To date I have only received updates for the Japanese translation.

If you can help update any of the other translations, please submit
changes as indicated below.


On 1/11/20 7:09 PM, Mark Sapiro wrote:
> I am pleased to announce the release of Mailman 2.1.30rc1.
> 
> Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended.
> 
> This is a routine bug fix release with a few new features. See the
> attached README.txt for details.
> 
> Mailman 2.1.30 will be the last release of the Mailman 2.1 branch from
> the GNU Mailman project. It contains some new strings which are
> untranslated in most of the i18n translations. If you can help update
> any of the translations, please contribute your changes.
> 
> Changes can be submitted via a bzr merge proposal on Launchpad or by
> sending an updated mailman.po file and or templates directly to me. This
> will be the last chance to get i18n updates into a release.
> 
> Mailman is free software for managing email mailing lists and
> e-newsletters. Mailman is used for all the python.org and
> SourceForge.net mailing lists, as well as at hundreds of other sites.
> 
> For more information, please see our web site at one of:
> 
> http://www.list.org
> https://www.gnu.org/software/mailman
> http://mailman.sourceforge.net/
> 
> Mailman 2.1.30rc1 can be downloaded from
> 
> https://launchpad.net/mailman/2.1/
> https://ftp.gnu.org/gnu/mailman/
> https://sourceforge.net/projects/mailman/


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[Mark Sapiro]

On 2/17/20 2:27 AM, Dennis Putnam wrote:

> It turns out that the only version available for RHEL 7 is 2.1.12.
> However, the mailman documentation indicates that also has DMARC
> mitigation.


What documentation? I assume Red Hat's. In any case, what you will have,
as others have said, is 2.1.12 with who knows what later features and
fixes backported by Red Hat to make what they call 2.1.12-xx.yy, and if
you run into trouble, we (this list) my not be able to help.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[dmaziuk via Mailman-Users]

On 2/17/2020 11:24 AM, Lindsay Haisley (linode) wrote:





This is common practice for all major distributions. The only way to keep up 
with upstream versions is to install from same from the git-go. This has its 
own pitfalls, but I do this for Mailman and have never had a problem.


I'm still hoping to some day get a round tuit for trying to fit MM2 in a 
docker container. You know exactly what codebase you have from the 
git-go, and if the new one does not cut it, the good old container is 
still there to fall back to.


The clue is strong with docker people.

D
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[Lindsay Haisley (linode)]

On Feb 17, 2020, at 10:45 AM, Phil Stracchino  wrote:
> 
>> On 2020-02-17 10:56, Bill Cole wrote:
>> RedHat has a policy of nailing down nominal versions of software with 
>> each major RHEL release and then backporting whatever fixes they deem 
>> important into their packages over the life of the major release, adding 
>> their own subordinate versioning. 

> An unfortunate side effect of this is that it makes it very difficult to
> support some software on Red Hat because you don't know for sure what
> codebase you're actually running, except that it's probably neither fish
> nor fowl nor good red meat.

This is common practice for all major distributions. The only way to keep up 
with upstream versions is to install from same from the git-go. This has its 
own pitfalls, but I do this for Mailman and have never had a problem.

Sent from my iPhone


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[Phil Stracchino]

On 2020-02-17 10:56, Bill Cole wrote:
> RedHat has a policy of nailing down nominal versions of software with 
> each major RHEL release and then backporting whatever fixes they deem 
> important into their packages over the life of the major release, adding 
> their own subordinate versioning. I know from working on the 
> SpamAssassin security team that RH is particularly attentive to security 
> issues and other major bugfixes.


An unfortunate side effect of this is that it makes it very difficult to
support some software on Red Hat because you don't know for sure what
codebase you're actually running, except that it's probably neither fish
nor fowl nor good red meat.


-- 
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[Bill Cole]

On 17 Feb 2020, at 5:27, Dennis Putnam wrote:


On 2/16/2020 11:45 PM, Stephen J. Turnbull wrote:

Dennis Putnam writes:

Since migrating to mailman 3 on the latest RHEL is going to take 
some

time, I need an interim solution to DMARC mitigation. I understand
version 2.1.18


Why 2.1.18?  Do you have that already installed?  It's already pretty
old, and many of the fixes still being made are security-related.

It turns out that the only version available for RHEL 7 is 2.1.12.
However, the mailman documentation indicates that also has DMARC
mitigation. Anyway, I am giving it a try. Seems silly that RHEL
repositories are so far behind the curve.


RedHat has a policy of nailing down nominal versions of software with 
each major RHEL release and then backporting whatever fixes they deem 
important into their packages over the life of the major release, adding 
their own subordinate versioning. I know from working on the 
SpamAssassin security team that RH is particularly attentive to security 
issues and other major bugfixes.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not For Hire (currently)
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

[Dennis Putnam]

On 2/16/2020 11:45 PM, Stephen J. Turnbull wrote:
> Dennis Putnam writes:
>
>  > Since migrating to mailman 3 on the latest RHEL is going to take some
>  > time, I need an interim solution to DMARC mitigation. I understand
>  > version 2.1.18
>
> Why 2.1.18?  Do you have that already installed?  It's already pretty
> old, and many of the fixes still being made are security-related.
It turns out that the only version available for RHEL 7 is 2.1.12.
However, the mailman documentation indicates that also has DMARC
mitigation. Anyway, I am giving it a try. Seems silly that RHEL
repositories are so far behind the curve.
>
>  > will do what I need, at least until I can finish the
>  > migration. However, I have been unable to find a repository or rpm
>  > for that version for RHEL 5. Can someone help me out with that?
>
> The Red Hat or Fedora lists would be a much better place to ask.
> We're not likely to know, and we can't provide much support except
> generic comments since we're generally not using packaged versions of
> Mailman, even for testing.  We just don't have the time.
>
> Steve




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman 2.1.18 for RHEL 5

[Stephen J. Turnbull]

Dennis Putnam writes:

 > Since migrating to mailman 3 on the latest RHEL is going to take some
 > time, I need an interim solution to DMARC mitigation. I understand
 > version 2.1.18

Why 2.1.18?  Do you have that already installed?  It's already pretty
old, and many of the fixes still being made are security-related.

 > will do what I need, at least until I can finish the
 > migration. However, I have been unable to find a repository or rpm
 > for that version for RHEL 5. Can someone help me out with that?

The Red Hat or Fedora lists would be a much better place to ask.
We're not likely to know, and we can't provide much support except
generic comments since we're generally not using packaged versions of
Mailman, even for testing.  We just don't have the time.

Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman 2.1.18 for RHEL 5

[Dennis Putnam]

Since migrating to mailman 3 on the latest RHEL is going to take some
time, I need an interim solution to DMARC mitigation. I understand
version 2.1.18 will do what I need, at least until I can finish the
migration. However, I have been unable to find a repository or rpm for
that version for RHEL 5. Can someone help me out with that?



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman on TMDHosting.com

[Mark Sapiro]

On 2/1/20 9:54 AM, Tim H wrote:
>
> Top posting my reply, hope this is OK.  Oddly, my host included a
> Terminal window! I have never seen that before.

And it appears from the # prompt in that window that you have root 
access to the server. This seems to say to me that the host doesn't have 
much of a clue at all about what they are doing.



> Attached are screen
> shots of some ls -l results.
>
> Mark are these normal for a mailman installation?

Your screenshots were removed by the list's content filtering, but I got 
them in off-list mail. The only interesting one is


# ls -l /usr/local/cpanel/3rdparty/mailman

'x 2 mailman mailman  22 Nov 11 01:37 bin
'x 2 mailman mailman 170 Nov 11 01:37 cgi-bin
'x 2 mailman mailman  21 Nov 11 01:37 mail

Note, this would be much better just copied and pasted into your email 
rather than attached as a screenshot.


Yes, these are normal, but there is much more missing. If this were 
actually a working Mailman installation there would also be archives, 
cron, data, icons, lists, locks, logs, Mailman, messages, pythonlib, 
qfiles, scripts, spam and tests directories in addition to the bin, 
cgi-bin and mail directories that are there.


So basically, Mailman is not really installed in any functional way.

--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman on TMDHosting.com

[Tim H via Mailman-Users]

 On Friday, January 31, 2020, 01:45:36 PM EST, Brian Carpenter 
 wrote:
 
 
 On 1/31/20 12:03 AM, Tim H via Mailman-Users wrote:
>  I just moved a cluster of domains to TMDHosting.com
> I had two Mailman mailing lists on the old service.  I made a gziped tarball 
> of the entire account using the usual tool. Staff at TMD brought it over and 
> in minutes all my files were in place.
> But. They do not have Mailman in cPanel. They do not have Mailman available 
> in Softalicious.  This is a shared hosting type of account.  I don't have 
> root access to the server.
> Their suggestion was to create an email address the same as the mailing list 
> address, then use that to set up BCC to a group of contacts in Roundcube.
> So I tried to create mymailingl...@mydomain.com
> I could not create the address. Instead I got an error message saying a 
> mailing list with that address already exists.
> But the address does not show up in the list of email addresses in cPanel, 
> so, I cannot delete it.
> I didn't think about the Mailman mailing lists when I set up to do the 
> transfer.  I took the time to save the member lists and some of the archives, 
> but I should have gone ahead and deleted the lists. I did not suspect that 
> the new service would not have Mailman.  Every web service provider I've been 
> with in years and years has had Mailman.
> So - what now?  Anyone on TMDHosting?  Have you been where I just landed?
> Thanks.
> Tim
> --

Hi Tim,

Screenshots of what you are seeing would be helpful. Are you sure 
Mailman is not accessible via cPanel? They are under Mailing Lists in 
the Email section of cPanel. Mailing lists and email accounts are 
treated as separate services on a cPanel server. Also Mailman is not 
available via Softaculous.

-- 
Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients.
Brian Carpenter
EMWD.com

--

I am sure that Mailman is not accessible via cPanel.  Screen shot attached. 
Thank you for confirming that Mailman is not available via Softalicious. That 
helps. 
I opened a support ticket with TMD. The 2 email addresses that were the SendTo 
addresses for the old Mailman lists were brought over in the transfer. They 
were invisible to me.  A senior tech deleted them, and created normal email 
addresses in their place. They recommend I use Roundcube and Contact Groups 
instead.  That's not a mailing list. If there were a function in Roundcube for 
"on receipt of new message, send to the Group Contact List", I'd be fine. 
Minimal but it would work. 
- Tim 



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman on TMDHosting.com

[Tim H via Mailman-Users]

 

  Top posting my reply, hope this is OK.  Oddly, my host included a Terminal 
window! I have never seen that before. Attached are screen shots of some ls -l 
results. 
Mark are these normal for a mailman installation?
I think my host does not want to support Mailman. Maybe new accounts aren't 
getting it in cPanel but the program is still on my server to support legacy 
accounts that are still using it. 
And yes, I replied to Brian, with screen shots. 
Thanks!
Tim
On Friday, January 31, 2020, 07:29:24 PM EST, Mark Sapiro 
 wrote:  
 
 On 1/31/20 2:51 PM, Tim H wrote:
> On Friday, January 31, 2020, 12:43:39 PM EST, Mark Sapiro 
>  wrote:
> 
> On 1/30/20 9:03 PM, Tim H via Mailman-Users wrote:
>  >  I just moved a cluster of domains to TMDHosting.com
>  > I had two Mailman mailing lists on the old service.  I made a gziped 
> tarball of the entire account using the usual tool. Staff at TMD brought 
> it over and in minutes all my files were in place.
>  > But. They do not have Mailman in cPanel.
> 
> 
> As far as I know, every cPanel installation has Mailman 2.1.
> 
> The issue may be that they just dropped your files into somewhere in
> /usr/local/cpanel/3rdparty/mailman. You can't just do that. cPanel's
> Mailman is different enough that the config.pck files aren't directly
> compatible and the file names and or locations maybe different to.
> 
> See <https://wiki.list.org/x/4030641>.
> 
> I searched my entire file set for "mailman" and came up empty.

/usr/local/cpanel/3rdparty/mailman is in the server's file system, but 
it is not somethin that users on a shared cPanel host have access to.

> I thought all cPanel installations came with Mailman.  Maybe something 
> happened and it isn't the case since some later version.

I doubt it, although I suppose it's possible that the host disabled it. 
But then, the fact that cPanel thinks your list address exist seems to 
say your list is at least partially there.

This is an issue that your hosting provider needs to resolve, but if 
they are like a lot of cPanel hosts, Mailman is only there because it 
comes with cPanel and they aren't interested in supporting it.

Brian is an exception. See his post at 
<https://mail.python.org/pipermail/mailman-users/2020-January/084961.html> 
and follow up with him.

-- 
Mark Sapiro         The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman on TMDHosting.com

[Brian Carpenter]

On 1/31/20 12:03 AM, Tim H via Mailman-Users wrote:

  I just moved a cluster of domains to TMDHosting.com
I had two Mailman mailing lists on the old service.  I made a gziped tarball of 
the entire account using the usual tool. Staff at TMD brought it over and in 
minutes all my files were in place.
But. They do not have Mailman in cPanel. They do not have Mailman available in 
Softalicious.  This is a shared hosting type of account.  I don't have root 
access to the server.
Their suggestion was to create an email address the same as the mailing list 
address, then use that to set up BCC to a group of contacts in Roundcube.
So I tried to create mymailingl...@mydomain.com
I could not create the address. Instead I got an error message saying a mailing 
list with that address already exists.
But the address does not show up in the list of email addresses in cPanel, so, 
I cannot delete it.
I didn't think about the Mailman mailing lists when I set up to do the 
transfer.  I took the time to save the member lists and some of the archives, 
but I should have gone ahead and deleted the lists. I did not suspect that the 
new service would not have Mailman.  Every web service provider I've been with 
in years and years has had Mailman.
So - what now?  Anyone on TMDHosting?  Have you been where I just landed?
Thanks.
Tim
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/brian_carpenter%40emwd.com


Hi Tim,

Screenshots of what you are seeing would be helpful. Are you sure 
Mailman is not accessible via cPanel? They are under Mailing Lists in 
the Email section of cPanel. Mailing lists and email accounts are 
treated as separate services on a cPanel server. Also Mailman is not 
available via Softaculous.


--
Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients.
Brian Carpenter
EMWD.com

--
EMWD's Knowledgebase:
https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums
http://discourse.emwd.com/

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman on TMDHosting.com

[Mark Sapiro]

On 1/30/20 9:03 PM, Tim H via Mailman-Users wrote:

  I just moved a cluster of domains to TMDHosting.com
I had two Mailman mailing lists on the old service.  I made a gziped tarball of 
the entire account using the usual tool. Staff at TMD brought it over and in 
minutes all my files were in place.
But. They do not have Mailman in cPanel.



As far as I know, every cPanel installation has Mailman 2.1.

The issue may be that they just dropped your files into somewhere in 
/usr/local/cpanel/3rdparty/mailman. You can't just do that. cPanel's 
Mailman is different enough that the config.pck files aren't directly 
compatible and the file names and or locations maybe different to.


See <https://wiki.list.org/x/4030641>.

Also, there are others on this list who are much more knowledgeable 
about cPanel Mailman than I am, and they may chime in.




So I tried to create mymailingl...@mydomain.com
I could not create the address. Instead I got an error message saying a mailing 
list with that address already exists.


Which indicates cPanel is aware of it.



But the address does not show up in the list of email addresses in cPanel, so, 
I cannot delete it.



You need advice from someone who knows more about Mailman in cPanel than 
I do.


--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman on TMDHosting.com

[Tim H via Mailman-Users]

 I just moved a cluster of domains to TMDHosting.com
I had two Mailman mailing lists on the old service.  I made a gziped tarball of 
the entire account using the usual tool. Staff at TMD brought it over and in 
minutes all my files were in place. 
But. They do not have Mailman in cPanel. They do not have Mailman available in 
Softalicious.  This is a shared hosting type of account.  I don't have root 
access to the server. 
Their suggestion was to create an email address the same as the mailing list 
address, then use that to set up BCC to a group of contacts in Roundcube.  
So I tried to create mymailingl...@mydomain.com
I could not create the address. Instead I got an error message saying a mailing 
list with that address already exists.  
But the address does not show up in the list of email addresses in cPanel, so, 
I cannot delete it.
I didn't think about the Mailman mailing lists when I set up to do the 
transfer.  I took the time to save the member lists and some of the archives, 
but I should have gone ahead and deleted the lists. I did not suspect that the 
new service would not have Mailman.  Every web service provider I've been with 
in years and years has had Mailman. 
So - what now?  Anyone on TMDHosting?  Have you been where I just landed?
Thanks.
Tim 
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 2.1.30rc1 released

[Mark Sapiro]

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman-Users Digest, Vol 191, Issue 3

[Allan Hansen]

Thanks again, Mark!
My responses below.

> On 1/4/20 5:47 PM, Allan Hansen wrote:
>> 
>> a. The server was set up with the wrong domain name (our fault), so I had to 
>> add the ‘correct’ one. I had seen the command ‘Add Domain’ in
>> the UI and thought that would do it, but Brian kindly sent me a list of 
>> additional instructions, which we then implemented. That made it possible to 
>> create a list in the new domain, subscribe people and post messages. 
>> However, messages are not archived. What extra step is needed to enable 
>> archiving? 
> 
> 
> What are the setytings in Postorius -> Settings -> Archiving?

Archive policy: Private archives
Archive archivers: hyperkitty, prototype
> 
> 
>> b. When go to the server using the new domain (both before and after logging 
>> in), I see not just the lists I created in the new domain, but the lists 
>> created in the old domain. These lists of lists are domain specific and 
>> should not be listed together. That’s just IMHO, but not serious, as I will 
>> soon get rid of anything in the old domain. So feel free to ignore this one 
>> if this is intended, which I could see might be the case.
> 
> 
> Set
> 
> FILTER_VHOST = True
> 
> in settings_local.py
> 

Yes, Brian told me to do the same. This is the what I wrote back:

hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py

Edited the setting to:
# Only display mailing-lists from the same virtual host as the webserver
FILTER_VHOST = True

Then Brian told me to restart qcluster:
hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster

I then logged in, but the same lists are showing. It either takes the system a 
long time to reset or it has ignored the 
setting.
Just tried it again, and the lists are all showing. Do I need to manually 
recompile the file?

> 
>> c. I then moved on to the templates and added a template for the message 
>> text to send to new subscribers. That resulted in the following error 
>> message when I went in as moderator to approve of a new subscription:
>> 
>> Something went wrong
>> Mailman REST API not available. Please start Mailman core.
> 
> 
> Postorius is unable to access core's REST API. Is Mailman running?

Well, I was able to post to the lists, so I assume it is. Listing at processes, 
I see a bunch of postgres, python3, nginx, django-adminp but
nothing explicitly with a ‘mailman’ string.

> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's
> called - defined as `filename` in the `file` handler in the LOGGING
> definition in settings(_local).py.

hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log
return Site.objects.get_current(request)
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py",
 line 60, in get_current
return self._get_site_by_request(request)
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py",
 line 45, in _get_site_by_request
SITE_CACHE[domain] = self.get(domain__iexact=domain)
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", 
line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", 
line 408, in get
self.model._meta.object_name
django.contrib.sites.models.Site.DoesNotExist: Site matching query does not 
exist.

[ABH] At this point I click to accept a subsription request:

ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not 
available
Traceback (most recent call last):
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", 
line 672, in urlopen
chunked=chunked,
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", 
line 421, in _make_request
six.raise_from(e, None)
  File "", line 3, in raise_from
  File 
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", 
line 416, in _make_request
httplib_response = conn.getresponse()
  File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse
response.begin()
  File "/usr/lib/python3.7/http/client.py", line 296, in begin
version, status, reason = self._read_status()
  File "/usr/lib/python3.7/http/client.py", line 265, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response

So yes, the REST API is not there. How can I get it going? 
Before we added the new domain, I was able to accept subscription requests to 
the previous domain’s lists. No more.

Yours,

    Allan

> 

Re: [Mailman-Users] Mailman 3.0 Documentation

[Mark Sapiro]

On 12/29/19 1:27 PM, Allan Hansen wrote:
> All,
> 
> I have spent some time now trying to understand the list admin interface to 
> Mailman 3.0. There is no context-sensitive help and looking around at the 
> Mailman sites, I mostly find instructions on how to install Mailman 3.0, but 
> no documentation on using it (other than for end users - which is much 
> improved over MM2).
> 
> I also looked in the FAQ. Is there such docs and, if so, where can I find 
> them. It’s about terminology and how to mangle the headers, etc.


Unfortunately, there are currently no list admin docs for Postorius
other than the Postorius UI itself.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 3.0 Documentation

[Allan Hansen]

All,

I have spent some time now trying to understand the list admin interface to 
Mailman 3.0. There is no context-sensitive help and looking around at the 
Mailman sites, I mostly find instructions on how to install Mailman 3.0, but no 
documentation on using it (other than for end users - which is much improved 
over MM2).

I also looked in the FAQ. Is there such docs and, if so, where can I find them. 
It’s about terminology and how to mangle the headers, etc.

Oh, and a big thanks to Brian Carpenter of EMWD for his help installing MM3, as 
I ran into a wall in my own attempt. MM3 appears to be a big end-user 
improvement over MM2. Thanks also, developers, for the work on MM3 development. 
I can see that it was a mountain of work to get that done.

Yours,

Allan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Allan Hansen]

Hi all,

Thank you for your responses, Stephen. Much appreciated. I have forwarded them 
to my friend. I don’t know if he is on this list, but I have recommended that 
he be, so we can get over whatever hump is getting in the way.

I used the instructions on the Mailman 3 site on my own attempt. 

The fact that the mangling will continue is a disappointment. I’m inclined to 
tell all my AOL and Yahoo users and others in the same boat to find another 
email service. The problem is that my MacOS users are getting tripped up by the 
mangling, as it is hidden by the mail clients. I have instructed them to remove 
previous recipients regularly from the list of such, if they contain the ‘via 
list’ string. But they don’t read my emails, and we see many embarrassing email 
ssent to the lists that are meant for one-on-one communication.

What is the best, easiest, guaranteed-to-work way to get this Mailman 3 up and 
running (OS, add-ons, options, etc.). When I tried myself, I saw a lot of 
options that I really did not really care to have because I did not know the 
consequences of each. I’m an application programmer, not a systems programmer.

Yours,

Allan Hansen
allan_han...@icloud.com



> On Nov 24, 2019, at 22:15 , Stephen J. Turnbull 
>  wrote:
> 
>> 
>> I’m ready and eager to move on to MM3 on a Linux box.
> 
> The obvious "turn-key" installation is to use the Docker containers,
> which Abhilash keeps fairly up-to-date.  But see comment below about
> universal working solutions.
> 
> Which distro do you have?  Are you using the distro's packages of
> Mailman 3 (not yet a good idea, unfortunately), or installing from
> source?
> 
>> I have looked into it a few times now and I keep running into the
>> same blocks. I don't see much moving either. I was hoping someone
>> (Mailman developing community) would come up with a better working
>> solution.
> 
> It's email.  There are no universal working solutions.
> 
>> [Some third party wrote:] My concern is that the Mailman3 is not
>> ready. There are too many dead ends and undocumented stuff.
> 
> Who is this guy and has he consulted us?  I'd like to do an archive
> search if he's done so to see what the issues are.
> 
>> For Mailman2 I have a working integration with iRedMail, that does
>> not seem to work with 3.
> 
> What's iRedMail?  How does it fit into the community your lists serve?

--------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Robert Heller]

At Mon, 25 Nov 2019 13:47:16 -0500 Jim Popovitch  wrote:

> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users
> wrote:
> > On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote:
> > > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via 
> > > Mailman-Users :
> > > > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > > > > Is there a timeline for that?  Mailman 2.x requires python 2.x, which 
> > > > > is
> > > > > EOL in about 40 days.  
> > > > 
> > > > I keep saying this a lot... the EOL you are referring to is Python's
> > > > declared date that the Python team will no longer maintain Python2.
> > > > HOWEVER, Redhat, Debian, etc., *will* still be maintaining Python2
> > > > throughout the lifecycles of their releases that contain Python2.   So,
> > > > for Debian 10 (Buster) that is well past 2022 (which is the LTS 
> > > > end-data 
> > > > for Debian 9).
> > > 
> > > Python2 is being removed from Debian's next release, Bullseye, though. 
> > > This already has caused turmoil for the Calibre package and I suppose 
> > > that they will have to remove mailman 2 also so that it is not going to 
> > > be in the bullseye release.
> > 
> > Correct, so LTS End-date for Buster (which will be sometime in 2024?)
> > will be the last of Python2 for Debian.
> > 
> > If you are migrating to Bullseye, then it makes sense to plan for an
> > application (e.g. Mailman) migration too.  BUT if you are not using
> > bleeding edge OSes, you don't need to heed the Python fear mongering.
> 
> Since I'm working on PPAs some today, an additional bullet-point to the
> above is that Ubuntu Bionic (which includes Python 2.7) has an EOL of
> April 2028.
> 
> https://wiki.ubuntu.com/Releases
> 
> Sure, it would be great if everyone migrated to MM3 (and MM3 fit inside
> the requirements of everyone using it..) ASAP, but just like with the
> Linux Kernel there is no magic solution to have everyone on Kernel 5.x
> this week... so guess what, kernel 3x still gets security patches from
> distributors.

And RedHat is still supporting Kernel 2x for RHEL 6...

> 
> - -Jim P.
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCAAdFiEE3RmV4WutJ2KyCS2zPcxbabkKGJ8FAl3cIbQACgkQPcxbabkK
> GJ8C6hAApwN2XGzId6EgR8tWponW5g++4fQvYYS7XmDLIQv3aTOEasVCz1aElp1+
> oEw9BYYcjIvsNAROrs/H1meg0zfMcmCzNBXJ1/zFTUdLTF/bZ7fOutOexhXrmd3w
> V/gOrL8OsiR+BOCKxiFCKH6D9sudbAIgw7cWFUxhcK0b7jEnGSrU/NIhf75xRtOE
> tzp01jS3a9ormxMZyniDV4C8QDbWIySBjrbKrM8S3tVTu8mbz7C+gIQKZzWXiJ7s
> jolEjRKExZ7OF1AM9nRCexIkvNzcdO+E83OheCnDjPyt70NxIdQxXmqYpxTr6YNZ
> MX6jQ3VuYTnMiNWHUvg8xECl6qDj7RU9zNdd9Citsj8QoWQs2Lvi500YjY1IiVSO
> ncmFwRPKBXuR4tv5z2bIcXvru7Fe8tSlZlOyLhL1chqRKQqhvazkJmNgnEgKs8ga
> 9Ha433BHYikXpGOX8+mR6//gREygbQFZInHgWOv5QWeAnY01H80HBwK7Y1vmKAUy
> kqMDoVAH7sO30xK0WdRsKaUktkr8bWES3MQJmb2fwKcH8l8hkh69RLKzxvj8zZi0
> 8NyN+812ujUuuYtgNfZQf+MLggElrqe19b7pViBuRwwuVcxG9GteUWk/lQxC+nl1
> yE4LiZN/q2UE2M2FASZUihLPXZb7OWdzi7Imjf2bRruF0n45bcw=
> =Lsiw
> -END PGP SIGNATURE-
> 
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com
> 
>           
>   

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
   
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Jim Popovitch via Mailman-Users]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users
wrote:
> On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote:
> > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users 
> > :
> > > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > > > Is there a timeline for that?  Mailman 2.x requires python 2.x, which is
> > > > EOL in about 40 days.  
> > > 
> > > I keep saying this a lot... the EOL you are referring to is Python's
> > > declared date that the Python team will no longer maintain Python2.
> > > HOWEVER, Redhat, Debian, etc., *will* still be maintaining Python2
> > > throughout the lifecycles of their releases that contain Python2.   So,
> > > for Debian 10 (Buster) that is well past 2022 (which is the LTS end-data 
> > > for Debian 9).
> > 
> > Python2 is being removed from Debian's next release, Bullseye, though. This 
> > already has caused turmoil for the Calibre package and I suppose that they 
> > will have to remove mailman 2 also so that it is not going to be in the 
> > bullseye release.
> 
> Correct, so LTS End-date for Buster (which will be sometime in 2024?)
> will be the last of Python2 for Debian.
> 
> If you are migrating to Bullseye, then it makes sense to plan for an
> application (e.g. Mailman) migration too.  BUT if you are not using
> bleeding edge OSes, you don't need to heed the Python fear mongering.

Since I'm working on PPAs some today, an additional bullet-point to the
above is that Ubuntu Bionic (which includes Python 2.7) has an EOL of
April 2028.

https://wiki.ubuntu.com/Releases

Sure, it would be great if everyone migrated to MM3 (and MM3 fit inside
the requirements of everyone using it..) ASAP, but just like with the
Linux Kernel there is no magic solution to have everyone on Kernel 5.x
this week... so guess what, kernel 3x still gets security patches from
distributors.

- -Jim P.

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE3RmV4WutJ2KyCS2zPcxbabkKGJ8FAl3cIbQACgkQPcxbabkK
GJ8C6hAApwN2XGzId6EgR8tWponW5g++4fQvYYS7XmDLIQv3aTOEasVCz1aElp1+
oEw9BYYcjIvsNAROrs/H1meg0zfMcmCzNBXJ1/zFTUdLTF/bZ7fOutOexhXrmd3w
V/gOrL8OsiR+BOCKxiFCKH6D9sudbAIgw7cWFUxhcK0b7jEnGSrU/NIhf75xRtOE
tzp01jS3a9ormxMZyniDV4C8QDbWIySBjrbKrM8S3tVTu8mbz7C+gIQKZzWXiJ7s
jolEjRKExZ7OF1AM9nRCexIkvNzcdO+E83OheCnDjPyt70NxIdQxXmqYpxTr6YNZ
MX6jQ3VuYTnMiNWHUvg8xECl6qDj7RU9zNdd9Citsj8QoWQs2Lvi500YjY1IiVSO
ncmFwRPKBXuR4tv5z2bIcXvru7Fe8tSlZlOyLhL1chqRKQqhvazkJmNgnEgKs8ga
9Ha433BHYikXpGOX8+mR6//gREygbQFZInHgWOv5QWeAnY01H80HBwK7Y1vmKAUy
kqMDoVAH7sO30xK0WdRsKaUktkr8bWES3MQJmb2fwKcH8l8hkh69RLKzxvj8zZi0
8NyN+812ujUuuYtgNfZQf+MLggElrqe19b7pViBuRwwuVcxG9GteUWk/lQxC+nl1
yE4LiZN/q2UE2M2FASZUihLPXZb7OWdzi7Imjf2bRruF0n45bcw=
=Lsiw
-END PGP SIGNATURE-

------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Mark Sapiro]

On 11/25/19 7:17 AM, Matthew Pounsett wrote:
> On Mon, 25 Nov 2019 at 05:04, Johannes Rohr  wrote:
> 
>> The obvious big showstopper is that there is no supported upgrade path
>> from Mailman 2.* yet, according to
>>
>> http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x
>> and so you certainly don't want to try to upgrade production instances
>> of mailman  without it.
>>
> 
> Is there a timeline for that?


Actually, that doc is out of date. The 'mailman import21' command for
importing a list from a Mailman 2.1 config.pck currently works quite
well. We've used it to migrate several lists on python.org and it works
well (and bugs when found get fixed).

The biggest issue is anomalies in the archive .mbox files that affect
the hyperkitty_import process.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Jim Popovitch via Mailman-Users]

On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote:
> 
> Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users 
> :
> > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > > Is there a timeline for that?  Mailman 2.x requires python 2.x, which is
> > > EOL in about 40 days.  
> > 
> > I keep saying this a lot... the EOL you are referring to is Python's
> > declared date that the Python team will no longer maintain Python2.
> > HOWEVER, Redhat, Debian, etc., *will* still be maintaining Python2
> > throughout the lifecycles of their releases that contain Python2.   So,
> > for Debian 10 (Buster) that is well past 2022 (which is the LTS end-data 
> > for Debian 9).
> 
> Python2 is being removed from Debian's next release, Bullseye, though. This 
> already has caused turmoil for the Calibre package and I suppose that they 
> will have to remove mailman 2 also so that it is not going to be in the 
> bullseye release.

Correct, so LTS End-date for Buster (which will be sometime in 2024?)
will be the last of Python2 for Debian.

If you are migrating to Bullseye, then it makes sense to plan for an
application (e.g. Mailman) migration too.  BUT if you are not using
bleeding edge OSes, you don't need to heed the Python fear mongering.

-Jim P.

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Johannes Rohr]

Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users <
mailman-users@python.org>:

> On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > Is there a timeline for that?  Mailman 2.x requires python 2.x, which is
> > EOL in about 40 days.
>
> I keep saying this a lot... the EOL you are referring to is Python's
> declared date that the Python team will no longer maintain Python2.
> HOWEVER, Redhat, Debian, etc., *will* still be maintaining Python2
> throughout the lifecycles of their releases that contain Python2.   So,
> for Debian 10 (Buster) that is well past 2022 (which is the LTS end-data
> for Debian 9).
>

Python2 is being removed from Debian's next release, Bullseye, though. This
already has caused turmoil for the Calibre package and I suppose that they
will have to remove mailman 2 also so that it is not going to be in the
bullseye release.


>
> Stop being scared by the Python team's misleading messaging.
>
> -Jim P.
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/jorohr%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Jim Popovitch via Mailman-Users]

On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> Is there a timeline for that?  Mailman 2.x requires python 2.x, which is
> EOL in about 40 days.  

I keep saying this a lot... the EOL you are referring to is Python's
declared date that the Python team will no longer maintain Python2.
HOWEVER, Redhat, Debian, etc., *will* still be maintaining Python2
throughout the lifecycles of their releases that contain Python2.   So,
for Debian 10 (Buster) that is well past 2022 (which is the LTS end-data 
for Debian 9).

Stop being scared by the Python team's misleading messaging.

-Jim P.

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Matthew Pounsett]

On Mon, 25 Nov 2019 at 05:04, Johannes Rohr  wrote:

> The obvious big showstopper is that there is no supported upgrade path
> from Mailman 2.* yet, according to
>
> http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x
> and so you certainly don't want to try to upgrade production instances
> of mailman  without it.
>

Is there a timeline for that?  Mailman 2.x requires python 2.x, which is
EOL in about 40 days.   It would have been nice to have a supported upgrade
path six months ago.  Can we count on one... say... in the next month?  I'm
not going to be able to do a production upgrade between now and the start
of the holidays change freeze anyway, but it would be nice if we could plan
on something for January.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Johannes Rohr]

Am 25.11.19 um 07:15 schrieb Stephen J. Turnbull:


[...]

> The obvious "turn-key" installation is to use the Docker containers,
> which Abhilash keeps fairly up-to-date.  But see comment below about
> universal working solutions.


[...]

Great suggestion. Is it easy to integrate it with the system's MTA or
does it come with its own MTA?

The obvious big showstopper is that there is no supported upgrade path
from Mailman 2.* yet, according to 
http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x
and so you certainly don't want to try to upgrade production instances
of mailman  without it.

Cheers,

Johannes

 

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 3 Ready?

[Stephen J. Turnbull]

Reply-To set to mailman-us...@mailman3.org.

Allan Hansen writes:

 > I need to upgrade from Mailman 2.1 - my hardware needs upgrading
 > (badly) and the address mangling is having my subscribers rip their
 > hair out.

That's not going to go away.  We have ARC support in Mailman 3, but
(a) like most envelope manipulation, that should be done in boundary
MTAs, not in Mailman, and (b) ARC implementation is not universal.
*Very likely* some of your subscribers are going to lose mail if you
depend on ARC, rather than munge from.

 > I need to get this done before they start on my already thinning
 > hair!

I sympathize.  I tell the little kids I meet that my hair grows out of
the bottom of my face, not the top (it's very alliterative in
Japanese[1], the kids frequently don't get it but the accompanying adults
usually laugh).

 > I’m ready and eager to move on to MM3 on a Linux box.

The obvious "turn-key" installation is to use the Docker containers,
which Abhilash keeps fairly up-to-date.  But see comment below about
universal working solutions.

Which distro do you have?  Are you using the distro's packages of
Mailman 3 (not yet a good idea, unfortunately), or installing from
source?

 > I have looked into it a few times now and I keep running into the
 > same blocks. I don't see much moving either. I was hoping someone
 > (Mailman developing community) would come up with a better working
 > solution.

It's email.  There are no universal working solutions.

 > [Some third party wrote:] My concern is that the Mailman3 is not
 > ready. There are too many dead ends and undocumented stuff.

Who is this guy and has he consulted us?  I'd like to do an archive
search if he's done so to see what the issues are.

 > For Mailman2 I have a working integration with iRedMail, that does
 > not seem to work with 3.

What's iRedMail?  How does it fit into the community your lists serve?

 > So, is MM3 ready for the big screen?

Works for us, for values of us including python.org.

 > If so, is there some way/how/where/when that my friend can get help
 > helping me with the installation other than the published
 > installation docs, which did not work for us?

mailman-us...@mailman3.org is the Mailman 3 version of this list.  If
your friend is the type to get his hands dirty with code, and has the
time for development activity, mailman-develop...@python.org would
also be useful.

You might be better off getting bids from consultants.  There's a page
listing them on wiki.list.org.

 > I have looked for both free and commercial alternatives to MM,

There are sites that support MM commercially.  I think the prices are
reasonable, of course YMMV on that.  Again, there's a page for those
services on wiki.list.org.


Footnotes: 
[1]  "hage dakara hige o" -- the vowels are pronounced as Spanish or
Italian, the consonants as in English.

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 3 Ready?

[Allan Hansen]

Dear all happy campers,

I need to upgrade from Mailman 2.1 - my hardware needs upgrading (badly) and 
the address mangling is having my subscribers rip their hair out. I need to get 
this done before they start on my already thinning hair!

I’m ready and eager to move on to MM3 on a Linux box. First I tried to install 
it myself. After all, I had installed MM2 and it worked fine until AOL and 
Yahoo messed it up,  My computer (an iMac) presents with a black screen on 
startup and is apt to die at any moment. I ran into trouble some 4/5 through 
the installation - I simply got lost in jingo. I then hired a pro, but he had 
real-life issues that kept him distracted and he also had trouble with the 
installation. I switched to a second pro, a friend, who has tried valiantly for 
a few months (on and off) but has basically given up now. This is his latest 
comment on his efforts after I (gently) nagged him:

*
Hi Allan,

I have looked into it a few times now and I keep running into the same blocks. 
I don't see much moving either. I was hoping someone (Mailman developing 
community) would come up with a better working solution. 

My concern is that the Mailman3 is not ready. There are too many dead ends and 
undocumented stuff. For Mailman2 I have a working integration with iRedMail, 
that does not seem to work with 3.

So far I don't have anyone who knows how to make Mailman3 work integrated with 
iRedMail (or similar). Things I have tried and documented are not a conclusive 
working installation.
**

So, is MM3 ready for the big screen? If so, is there some way/how/where/when 
that my friend can get help helping me with the installation other than the 
published installation docs, which did not work for us? 

I have looked for both free and commercial alternatives to MM, but, frankly, I 
don’t think that there is anything that comes close to what we have. One of my 
lists started out on LISTSERV many decades ago. I moved it to Appls’s list 
server and then I moved it to MM after Apple starting with OS/X. Apparently 
LISTSERV is still around and is being updated, but I’m not keen on going back 
there, and it’s very expensive too boot.

Any help with this is greatly appreciated!

Yours,

Allan Hansen



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 2.1.12 confirm.py works fine with http but does not work with https

[Mark Sapiro]

On 11/5/19 8:02 AM, jimw...@attglobal.net wrote:
> 
> To make my website more secure, my website is configured to only work
> with https and not with http.
> 
> Please let me know how I can use confirm.py with https.
> 
> confirm.py works fine with http, but not with https.


As I said in a prior reply, do at least steps 1-3 at
<https://wiki.list.org/x/17892007>. Presumably, you have already done
step 1 or an equivalent to force https. Now you must do steps 2 and 3 to
ensure that the ACTION URL for forms is https.

You may also want to do step 4, although that doesn't bear directly on
this issue.


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 2.1.12 confirm.py works fine with http but does not work with https

[jimw...@attglobal.net]

Hi,

I have mailman 2.1.12 installed on Centos 6.5 using Apache 2.2.15 and 
python 2.6.6.


The mailman web page "Confirm Subscription Request" generated by 
confirm.py works fine with http, but does not work with https.


Please let me know if there is a modification that I can make for 
confirm.py to work with https.


To make my website more secure, my website is configured to only work 
with https and not with http.


Please let me know how I can use confirm.py with https.

confirm.py works fine with http, but not with https.

Your help with this problem is appreciated.

Thanks,

Jim West


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Python Apache CGI issue

[Mark Sapiro]

On 11/3/19 11:08 AM, jimw...@attglobal.net wrote:
> 
> Confirming the subscription using the email method works fine, but the
> web page confirmation is having problems.
> 
> For a user named "dot" joining the Skipper group, the URL is:
> 
> http:///mailman/confirm/skipper/b36adbfa6d4b9af927197b75006444262696b9a6
>  
...
> After the user clicks to subscribe to the group on the Confirm
> Subscription web page,
> the confirm.py script checks to see if the cookie was entered in the URL:


So the initial GET of the page at
http:///mailman/confirm/skipper/b36adbfa6d4b9af927197b75006444262696b9a6
works and it is only the subsequent "Subscribe to list ..." button that
fails.

If that is correct, POST data is getting lost. See the FAQ article at
<https://wiki.list.org/x/4030602> for some reasons why this happens
(most likely redirection from http to https, in which case do at least
steps 1-3 at <https://wiki.list.org/x/17892007>).

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman with Interworx server administration

[Brian Carpenter]

On 11/4/19 5:24 PM, Christian F Buser via Mailman-Users wrote:

Hi all

Our hosting provider writes that he wants to change from cPanel to 
Interworx.


At present, we have our virtual server on cPanel version 78.0.41, 
which includes Mailman version 2.1.27.


I found a comparison of the two environments on this page 
<https://www.hostdime.com/kb/hd/interworx/interworx-for-cpanel-administrators-and-resellers> 
stating



Important Differences:
...
cPanel supports PostgreSQL, Mailman mailing lists, NodeJS, 
server-side Java, Ruby on Rails and the DNSSEC protocol, but 
InterWorx does not support those things at this time.

However our provider thinks that Mailman could also be installed there.

Does anybody have (positive or negative) experience with Interworx?

Thank you, Christian


Hi Christian,

Interworx is bought out by LiquidWeb. LiquidWeb is a large hosting 
provider that is abandoning cPanel due to cPanel's price increase in 
September. I doubt your current provider will be able to get Mailman 
installed since cPanel did all the heavy lifting in getting Mailman 2 to 
run on a server. Most webhosts have very little experience with Mailman 
2. Please see our blog article at:


https://www.emwd.com/cpanel-refugee-hosting/

If you want to stay with cPanel/Mailman then I like to invite you to 
consider us. However if you want to stay with your current provider, 
then please visit our Mailman hosting service at 
https://www.mailmanhost.com. We run the latest version of Mailman out 
side of our cPanel servers.


One thing cPanel has that is really nice for list admins is their track 
delivery tool for troubleshooting bounces to list members.


--
Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients.
Brian Carpenter
EMWD.com

--
EMWD's Knowledgebase:
https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums
http://discourse.emwd.com/

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman with Interworx server administration

[Christian F Buser via Mailman-Users]

Hi all

Our hosting provider writes that he wants to change from cPanel to 
Interworx.


At present, we have our virtual server on cPanel version 78.0.41, which 
includes Mailman version 2.1.27.


I found a comparison of the two environments on this page 
<https://www.hostdime.com/kb/hd/interworx/interworx-for-cpanel-administrators-and-resellers> 
stating



Important Differences:
...
cPanel supports PostgreSQL, Mailman mailing lists, NodeJS, server-side 
Java, Ruby on Rails and the DNSSEC protocol, but InterWorx does not 
support those things at this time.

However our provider thinks that Mailman could also be installed there.

Does anybody have (positive or negative) experience with Interworx?

Thank you, Christian

--
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
Hilfe f??r Strassenkinder in Ghana: http://www.chance-for-children.org
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman Python Apache CGI issue

[jimw...@attglobal.net]

I am new to Mailman, and have just installed Mailman 2.1.12-26 on a 
Centos 6.5 server.


My httpd version is 2.2.15   My python version is python-2.6.6-51.

Everything appears to be working fine, except when a new subscriber 
confirms there subscription request.


The email from Mailman gives the user the option of confirming their 
subscription by going to the confirm web page.


Confirming the subscription using the email method works fine, but the 
web page confirmation is having problems.


For a user named "dot" joining the Skipper group, the URL is:

http:///mailman/confirm/skipper/b36adbfa6d4b9af927197b75006444262696b9a6 
 
<http://kjm.PositionDatabase.com/mailman/confirm/skipper/b36adbfa6d4b9af927197b75006444262696b9a6>

The string "b36adbfa6d4b9af927197b75006444262696b9a6"  
<http://kjm.PositionDatabase.com/mailman/confirm/skipper/b36adbfa6d4b9af927197b75006444262696b9a6>  
is the confirmation "cookie".

After the user clicks to subscribe to the group on the Confirm Subscription web 
page,
the confirm.py script checks to see if the cookie was entered in the URL:

# Get the form data to see if this is a second-step confirmation
cgidata = cgi.FieldStorage(keep_blank_values=1)
cookie = cgidata.getvalue('cookie')
if cookie == '':
ask_for_cookie(mlist, doc, _('Confirmation string was empty.'))
return

In my installation, the cdigdata.getvalue is not returning the cookie entered 
in the URL, so
the "Enter Confirmation Cookie" web page is called ... even though the cookie 
was included in the URL.

If the user enters the "cookie" again in the "Confirmation String" window, the user 
clicking "submit" does nothing.

It appears that I have a configuration problem in my Apache or Python interface.

I am not seeing any errors in /var/log/mailman/error log.

My /etc/httpd/conf.d/mailman.conf file is not generating any errors in 
/etc/httpd/error_log, and
The redirect for "/mailman" appears to be working, since my mailman url is 
working.

From the confirm.py script, it appears the "cookie" should have been obtained 
from the URL, and there
should have been no need to call the "Enter Confirmation Cookie" to have the 
user enter the cookie again...
and as luck would have it, the Enter Confirmation Cookie web page is also not 
working.

This is definitely a new user configuration problem, and I would appreciate any 
suggestions for how to fix this problem.

Thanks,
Jim West
Email: jimw...@attglobal.net

------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman not functional

[Bill Cole]

On 17 Oct 2019, at 16:41, Steven Jones wrote:


ssh takes a long time to login but there is no load to cause this.


The first thing to suspect when logins take a long time with no tangible 
loading issues (i/o, memory, and CPU all good) is DNS. If your resolver 
is trying to query a non-responsive DNS server or servers but eventually 
hits one that works, login and anything involving email transport will 
be plagued by delays.


So: check /etc/resolv.conf and make sure all listed servers are 
responding to queries.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman not functional

[Mark Sapiro]

On 10/17/19 3:59 PM, Steven Jones wrote:
> thanks
> 
> I am sort of suspecting postfix as /var/log/maillog is not being written to.
> 
> meanwhile,
> 
> /var/log/mailman/smtp has something odd. The time to send email varies 
> between 0.017 and 180 seconds plus,  and its getting worse,
> 
> ==
> Oct 18 11:26:13 2019 (9398) 
>  smtp to 
> postgradcoordinators for 1 recips, completed in 0.017 seconds
> Oct 18 11:26:26 2019 (9398) 
>  smtp to 
> postgradcoordinators for 14 recips, completed in 12.419 seconds
> Oct 18 11:26:27 2019 (9398) 
>  smtp to 
> vuw-schooladmin for 14 recips, completed in 0.029 seconds
> Oct 18 11:26:27 2019 (9398) n/a smtp to its-alerts for 10 recips, completed 
> in 0.073 seconds
> Oct 18 11:26:27 2019 (9398) 
>  smtp to 
> postgradcoordinators for 1 recips, completed in 0.019 seconds
> Oct 18 11:26:27 2019 (9398) 
>  smtp to 
> postgradcoordinators for 14 recips, completed in 0.019 seconds
> Oct 18 11:26:39 2019 (9398) n/a smtp to its-alerts for 10 recips, completed 
> in 10.111 seconds
> Oct 18 11:26:41 2019 (9398)  
> 
>  smtp to fad-design-postgrads for 102 recips, completed in 0.248 seconds
> Oct 18 11:26:41 2019 (9398) n/a smtp to its-alerts for 10 recips, completed 
> in 0.024 seconds
> Oct 18 11:26:41 2019 (9398)  
> 
>  smtp to fad-design for 56 recips, completed in 0.030 seconds
> Oct 18 11:29:45 2019 (9398) 
> 
>  smtp to nz-libs for 1844 recips, completed in 184.400 seconds
> Oct 18 11:31:31 2019 (9398) 
>  smtp to 
> teachingandlearning for 1 recips, completed in 103.629 seconds
> Oct 18 11:34:22 2019 (9398) n/a smtp to its-alerts for 10 recips, completed 
> in 169.826 seconds
> Oct 18 11:36:26 2019 (9398) n/a smtp to its-alerts for 10 recips, completed 
> in 123.446 seconds
> Oct 18 11:39:33 2019 (9398)  
> 
>  smtp to fad-design for 56 recips, completed in 187.700 seconds
> 8><


Mailman's out queue is backlogged. See
<https://wiki.list.org/x/17892002>. Something is changed affecting
Postfix. Possibly you had a local DNS cache that is now not working and
Postfix DNS lookups are taking a long time. Also consider a separate
Postfix port for Mailman delivery with minimal checking. On
mail.python.org we use something like this in master.cf

127.0.0.1:8027
  inet  n   -   -   --  smtpd
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_data_restrictions=

...
> =
> [root@vuwunicomailmn1 mailman]# tail qrunner
> Oct 18 09:32:13 2019 (9400) RetryRunner qrunner started.
> Oct 18 09:32:13 2019 (9395) CommandRunner qrunner started.
> Oct 18 09:32:13 2019 (9396) IncomingRunner qrunner started.
> Oct 18 09:32:13 2019 (9399) VirginRunner qrunner started.
> Oct 18 09:32:13 2019 (9397) NewsRunner qrunner started.
> Oct 18 09:32:13 2019 (9394) BounceRunner qrunner started.
> Oct 18 09:32:13 2019 (9398) OutgoingRunner qrunner started.
> Oct 18 09:32:13 2019 (8205) OutgoingRunner qrunner exiting.
> Oct 18 09:32:13 2019 (8172) Master qrunner detected subprocess exit
> (pid: 8205, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)
> [root@vuwunicomailmn1 mailman]#
> =
> 
> and its now 11:50am
> 
> Ok to assume the above in the qrunner log is normal?
>


The last three lines are not normal OutgoingRunner has died, but it
seems these are the result of a Mailman restart and the old
OutgoingRunner persisted for a while because it had to finish delivery
of the current message. Note the out of sequence PID and the fact that
ps shows 9398 is running.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman not functional

[Steven Jones]

thanks

I am sort of suspecting postfix as /var/log/maillog is not being written to.

meanwhile,

/var/log/mailman/smtp has something odd. The time to send email varies between 
0.017 and 180 seconds plus,  and its getting worse,

==
Oct 18 11:26:13 2019 (9398) 
 smtp to 
postgradcoordinators for 1 recips, completed in 0.017 seconds
Oct 18 11:26:26 2019 (9398) 
 smtp to 
postgradcoordinators for 14 recips, completed in 12.419 seconds
Oct 18 11:26:27 2019 (9398) 
 smtp to 
vuw-schooladmin for 14 recips, completed in 0.029 seconds
Oct 18 11:26:27 2019 (9398) n/a smtp to its-alerts for 10 recips, completed in 
0.073 seconds
Oct 18 11:26:27 2019 (9398) 
 smtp to 
postgradcoordinators for 1 recips, completed in 0.019 seconds
Oct 18 11:26:27 2019 (9398) 
 smtp to 
postgradcoordinators for 14 recips, completed in 0.019 seconds
Oct 18 11:26:39 2019 (9398) n/a smtp to its-alerts for 10 recips, completed in 
10.111 seconds
Oct 18 11:26:41 2019 (9398)  

 smtp to fad-design-postgrads for 102 recips, completed in 0.248 seconds
Oct 18 11:26:41 2019 (9398) n/a smtp to its-alerts for 10 recips, completed in 
0.024 seconds
Oct 18 11:26:41 2019 (9398)  

 smtp to fad-design for 56 recips, completed in 0.030 seconds
Oct 18 11:29:45 2019 (9398) 

 smtp to nz-libs for 1844 recips, completed in 184.400 seconds
Oct 18 11:31:31 2019 (9398) 
 smtp to 
teachingandlearning for 1 recips, completed in 103.629 seconds
Oct 18 11:34:22 2019 (9398) n/a smtp to its-alerts for 10 recips, completed in 
169.826 seconds
Oct 18 11:36:26 2019 (9398) n/a smtp to its-alerts for 10 recips, completed in 
123.446 seconds
Oct 18 11:39:33 2019 (9398)  

 smtp to fad-design for 56 recips, completed in 187.700 seconds
8><

==

We are getting mail but very slowly so mailman is working, and item 2.2

[root@vuwunicomailmn1 ~]# ps auxww| grep mailmanctl |grep -v grep
mailman   9390  0.0  0.1 214172  9432 ?Ss   09:32   0:00 
/usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start

and,

[root@vuwunicomailmn1 ~]# service mailman status
mailman (pid 9390) is running...
[root@vuwunicomailmn1 ~]# service postfix status
master (pid  7688) is running...
[root@vuwunicomailmn1 ~]#

seems to confirm this.

[root@vuwunicomailmn1 ~]# rpm -q mailman
mailman-2.1.12-26.el6_9.3.x86_64


[root@vuwunicomailmn1 ~]# ps auxww | egrep 'p[y]thon'
root  8152  0.0  0.5 598144 46040 ?Sl   09:24   0:05 
/usr/bin/python2.7 /usr/bin/salt-minion -c /etc/salt -d
mailman   9390  0.0  0.1 214172  9432 ?Ss   09:32   0:00 
/usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start
mailman   9393  2.7  2.8 435468 231896 ?   S09:32   3:36 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman   9394  0.0  0.2 219840 16204 ?S09:32   0:01 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
mailman   9395  0.0  0.1 216084 12204 ?S09:32   0:00 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
mailman   9396  0.0  0.2 226128 22572 ?S09:32   0:04 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
mailman   9397  0.0  0.1 216164 12300 ?S09:32   0:00 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
mailman   9398  0.1  0.2 221688 18224 ?S09:32   0:12 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
mailman   9399  0.0  0.2 221168 17556 ?S09:32   0:03 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
mailman   9400  0.0  0.1 216068 12200 ?S09:32   0:00 
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
root 20071  0.0  0.2 210860 19864 ?S11:21   0:00 
/usr/bin/python /usr/libexec/rhsmd
[root@vuwunicomailmn1 ~]#

qrunner,

=
[root@vuwunicomailmn1 mailman]# tail qrunner
Oct 18 09:32:13 2019 (9400) RetryRunner qrunner started.
Oct 18 09:32:13 2019 (9395) CommandRunner qrunner started.
Oct 18 09:32:13 2019 (9396) IncomingRunner qrunner started.
Oct 18 09:32:13 2019 (9399) VirginRunner qrunner started.
Oct 18 09:32:13 2019 (9397) NewsRunner qrunner started.
Oct 18 09:32:13 2019 (9394) BounceRunner qrunner started.
Oct 18 09:32:13 2019 (9398) OutgoingRunner qrunner started.
Oct 18 09:32:13 2019 (8205) OutgoingRunner qrunner exiting.
Oct 18 09:32:13 2019 (8172) Master qrunner detected subprocess exit
(pid: 8205, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)
[root@vuwunicomailmn1 mailman]#
=

and its now 11:50am

Ok to assume the above in the qrunner log is normal?





regards

Steven



From: Mailman-Users  
on behalf of Mark Sapiro 
Sent: Friday, 18 October 2019 10:29 AM
To: mailman-users@python.org 
Subject: Re: [Mailman-Users] mailman not functional

On 10/17/19 1:41 PM, Steven Jones wrote:
> Hi,
>
> Yesterday we had a major network outage that lasted 2 hours+  This morning I 
> find that the mailman s

Re: [Mailman-Users] mailman not functional

[Mark Sapiro]

On 10/17/19 1:41 PM, Steven Jones wrote:
> Hi,
> 
> Yesterday we had a major network outage that lasted 2 hours+  This morning I 
> find that the mailman server has "stopped working"   I have restarted mailman 
> and now the server but mailman is not processing any emails.  The load in top 
> is 0.00 ~0.01 sort of thing, no no disk i/o, no action at all, disks are not 
> full. ssh takes a long time to login but there is no load to cause this. I 
> can see python is running in top but at like 0.3%.


You say you restarted Mailman and the server, but is Mailman actually
running?

Is Postfix delivering to Mailman (look at Postfix's logs)? Is stuff
piling up in Mailman's queues; if so, which one(s).

See the FAQ at <https://wiki.list.org/x/4030723> focusing on items 2.2,
6.2, 7, 8 and 9.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman not functional

[Steven Jones]

Hi,

Yesterday we had a major network outage that lasted 2 hours+  This morning I 
find that the mailman server has "stopped working"   I have restarted mailman 
and now the server but mailman is not processing any emails.  The load in top 
is 0.00 ~0.01 sort of thing, no no disk i/o, no action at all, disks are not 
full. ssh takes a long time to login but there is no load to cause this. I can 
see python is running in top but at like 0.3%.

I run mail   me@work and postfix sends fast  so postfix seems OK, its like 
Mailman is in a coma, its has chocked to death but its heart is still 
beatingjust seems odd.

What can I do here?




regards

Steven
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman on google comput engine

[황병희]

Sorry for late, i need to time think about that.
Thanks you for *everyone* for me to feedback, indeed...

Sincerely,

-- 
^고맙습니다 _地平天成_ 감사합니다_^))//

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Mark Sapiro]

On 8/26/19 9:59 AM, Bill Richards wrote:
> Mark
> 
> I read the wiki and have inserted the "RedirectPermanent" statement in the
> httpd.conf file and restarted apache.  Then I ran
> "/usr/lib/mailman/bin/withlist -l -r fix_url aewa" and the following
> results came back:
> 
> Importing fix_url...
> Running fix_url.fix_url()...
> Loading list aewa (locked)
> Saving list
> Finalizing
> 
> After that I tried to approve/discard some pending requests and received a
> odd response when the next html page was not found:  "
> http://aewa.c.agile-being-124522.internal/mailman/admindb/aewa;
> Which to me looks like some sort of header I've seen in emails.  Apparently
> the  "/usr/lib/mailman/bin/withlist -l -r fix_url aewa"  command  has
> scrambled most of the web page archives.  I was able to find and fix it in
> the config.pck file but some of the other admin pages still have url's with
> the "aewa.c.agile-being" etc. in them.  Plus the archives are no longer
> accessible.


I can access the pipermail archive for your list with no problem

What is in Mailman's Mailman/Defaults.py and Mailman/mm_cfg.py for the
settings

DEFAULT_URL_PATTERN
DEFAULT_EMAIL_HOST
DEFAULT_URL_HOST
and all add_virtualhost() lines?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
----------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Bill Richards]

Mark

I read the wiki and have inserted the "RedirectPermanent" statement in the
httpd.conf file and restarted apache.  Then I ran
"/usr/lib/mailman/bin/withlist -l -r fix_url aewa" and the following
results came back:

Importing fix_url...
Running fix_url.fix_url()...
Loading list aewa (locked)
Saving list
Finalizing

After that I tried to approve/discard some pending requests and received a
odd response when the next html page was not found:  "
http://aewa.c.agile-being-124522.internal/mailman/admindb/aewa;
Which to me looks like some sort of header I've seen in emails.  Apparently
the  "/usr/lib/mailman/bin/withlist -l -r fix_url aewa"  command  has
scrambled most of the web page archives.  I was able to find and fix it in
the config.pck file but some of the other admin pages still have url's with
the "aewa.c.agile-being" etc. in them.  Plus the archives are no longer
accessible.

Right now I am stumped.

Bill

On Sun, Aug 25, 2019 at 5:45 PM Mark Sapiro  wrote:

> On 8/25/19 10:40 AM, Bill Richards wrote:
> > Mark
> >
> > Ran dumpdb against all the pck files and saw no instances of "new-" yet
> > when using
> >
> > find /home -xdev -type f -print0 | xargs -0 grep -H "new-"
> >
> > it finds matches in config.pck, config.pck.last & config.pck.safety
>
>
> I'm not sure why you are looking in /home since based on an off list
> message, your actual Mailman files are in /var/lib/mailman/lists/.
>
> In any case, if grep finds an instance of "new-" in some config.pck, the
> output of mailman's bin/dumpdb of that file should also contain "new-".
>
> But none of this seems relevant to your issues.
>
> For the smtp-failure log "Sender address
> rejected: Domain not found" errors, what are the messages in the MTA
> logs correlated with this.
>
> For the problems with approving and/or
> discarding messages and unable to add/delete users to the list issues,
> have you looked at <https://wiki.list.org/x/4030602> and did it help? Is
> this still an issue?
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/wildbill.richards%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Bill Richards]

Sorry, It wasn't  actually home I just cut and pasted the wrong line from
.bash_history.  I searched multiple directories but found the matches under
/var/lib/mailman

I'll check the maillogs in the morning.

re: the link, yes I recently converted the web site to https so I'll review
that link in the AM and see if that is it.

Thanks for the help

Bill

On Sun, Aug 25, 2019 at 5:45 PM Mark Sapiro  wrote:

> On 8/25/19 10:40 AM, Bill Richards wrote:
> > Mark
> >
> > Ran dumpdb against all the pck files and saw no instances of "new-" yet
> > when using
> >
> > find /home -xdev -type f -print0 | xargs -0 grep -H "new-"
> >
> > it finds matches in config.pck, config.pck.last & config.pck.safety
>
>
> I'm not sure why you are looking in /home since based on an off list
> message, your actual Mailman files are in /var/lib/mailman/lists/.
>
> In any case, if grep finds an instance of "new-" in some config.pck, the
> output of mailman's bin/dumpdb of that file should also contain "new-".
>
> But none of this seems relevant to your issues.
>
> For the smtp-failure log "Sender address
> rejected: Domain not found" errors, what are the messages in the MTA
> logs correlated with this.
>
> For the problems with approving and/or
> discarding messages and unable to add/delete users to the list issues,
> have you looked at <https://wiki.list.org/x/4030602> and did it help? Is
> this still an issue?
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/wildbill.richards%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Mark Sapiro]

On 8/25/19 10:40 AM, Bill Richards wrote:
> Mark
> 
> Ran dumpdb against all the pck files and saw no instances of "new-" yet
> when using
> 
> find /home -xdev -type f -print0 | xargs -0 grep -H "new-"
> 
> it finds matches in config.pck, config.pck.last & config.pck.safety


I'm not sure why you are looking in /home since based on an off list
message, your actual Mailman files are in /var/lib/mailman/lists/.

In any case, if grep finds an instance of "new-" in some config.pck, the
output of mailman's bin/dumpdb of that file should also contain "new-".

But none of this seems relevant to your issues.

For the smtp-failure log "Sender address
rejected: Domain not found" errors, what are the messages in the MTA
logs correlated with this.

For the problems with approving and/or
discarding messages and unable to add/delete users to the list issues,
have you looked at <https://wiki.list.org/x/4030602> and did it help? Is
this still an issue?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Bill Richards]

Mark

Ran dumpdb against all the pck files and saw no instances of "new-" yet
when using

find /home -xdev -type f -print0 | xargs -0 grep -H "new-"

it finds matches in config.pck, config.pck.last & config.pck.safety

On Sat, Aug 24, 2019 at 8:28 PM Mark Sapiro  wrote:

> On 8/24/19 5:33 PM, Bill Richards wrote:
> > The domain is correct from the web page General Options -> host_name
> > attribute of the list
> >
> > The dumpdb against config.pck shows a lot of list members email
> addresses,
> > "accept_non_members", "ban_list", etc.  It is very long (2413 lines).
> What
> > specifically am I looking for to get the attributes?
>
>
> All occurrences where "new-" is appended to the domain you use.
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --------------
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/wildbill.richards%40gmail.com
>
----------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Mark Sapiro]

On 8/24/19 5:33 PM, Bill Richards wrote:
> The domain is correct from the web page General Options -> host_name
> attribute of the list
> 
> The dumpdb against config.pck shows a lot of list members email addresses,
> "accept_non_members", "ban_list", etc.  It is very long (2413 lines).  What
> specifically am I looking for to get the attributes?


All occurrences where "new-" is appended to the domain you use.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Mark Dale]

Hi,

It sounds like you now have it sorted with Namazu, but for what it's
worth there is an excellent guide to install Namazu "out of the box" on
Mailman 2.1.* at:

http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

And no issues with Private archives or incorrect URLs.

/Mark


On 25/8/19 8:07 am, Robert Heller wrote:
> At Sat, 24 Aug 2019 14:20:42 -0700 Mark Sapiro  wrote:
> 
>>
>> On 8/24/19 1:15 PM, Robert Heller wrote:
>>>
>>> OK, I have installed Namazu, which will do what I want, *BUT* pipermail.pl 
>>> is 
>>> missing from the tarball I downloaded from the Namazu website.  Where can I 
>>> get that file.  At this point, the search works, but the URI's are wrong 
>>> (local file name, not the proper mailman URL).
>>
>>
>> I can't answer directly, but see
>> <https://bugs.launchpad.net/mailman/+bug/558138>.
>>
> 
> I figured out how to hack the Namazu code to incldue a "replacement" function 
> and passed it on to the re-index function.  I think that will work.  (Perl is 
> almost as bad as APL -- the only thing about Perl is that it uses "normal" 
> ASCII, but still is pretty much write-only code, like APL.)
> 
> 
------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Bill Richards]

The domain is correct from the web page General Options -> host_name
attribute of the list

The dumpdb against config.pck shows a lot of list members email addresses,
"accept_non_members", "ban_list", etc.  It is very long (2413 lines).  What
specifically am I looking for to get the attributes?

Bill

On Sat, Aug 24, 2019 at 5:32 PM Mark Sapiro  wrote:

> On 8/24/19 3:14 PM, Bill Richards wrote:
> >
> > After digging around I've found that I maybe experiencing some kind if
> > config corruption in pck files under /var/lib/mailman/lists/mailman  When
> > looking through the smtp-failure log I noticed errors "Sender address
> > rejected: Domain not found" and it appears something has or is appending
> > the text "new-" to the beginning of the domain we use.  Further
> > investigation shows that "new-" is appended to the domain in the
> > config.pck, config.pck.last & config.pck.safety files.
>
>
> What attributes have these things? Do Mailman's `bin/dumpdb` on the
> config.pck files.
>
> On the other hand, this may be the General Options -> host_name
> attribute of the list. If so, just fix it.
>
> Once we know what attributes are affected, we can say more.
>
> > Previous message:
> > =
> >
> > A few weeks ago are started experiencing problems with approving and/or
> > discarding messages.  I am also unable to add/delete users to the list
> but
> > messages from approved list members work fine.  I suspect either some
> file
> > has become corrupted or a permissions issue.
>
>
> Is this still an issue?  As I've said previously, see
> <https://wiki.list.org/x/4030602>.
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/wildbill.richards%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman errors

[Mark Sapiro]

On 8/24/19 3:14 PM, Bill Richards wrote:
> 
> After digging around I've found that I maybe experiencing some kind if
> config corruption in pck files under /var/lib/mailman/lists/mailman  When
> looking through the smtp-failure log I noticed errors "Sender address
> rejected: Domain not found" and it appears something has or is appending
> the text "new-" to the beginning of the domain we use.  Further
> investigation shows that "new-" is appended to the domain in the
> config.pck, config.pck.last & config.pck.safety files.


What attributes have these things? Do Mailman's `bin/dumpdb` on the
config.pck files.

On the other hand, this may be the General Options -> host_name
attribute of the list. If so, just fix it.

Once we know what attributes are affected, we can say more.

> Previous message:
> =
> 
> A few weeks ago are started experiencing problems with approving and/or
> discarding messages.  I am also unable to add/delete users to the list but
> messages from approved list members work fine.  I suspect either some file
> has become corrupted or a permissions issue.


Is this still an issue?  As I've said previously, see
<https://wiki.list.org/x/4030602>.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman errors

[Bill Richards]

Earlier this month I email this list with issues I've had approving/discard
messages via the web interface (see below).

After digging around I've found that I maybe experiencing some kind if
config corruption in pck files under /var/lib/mailman/lists/mailman  When
looking through the smtp-failure log I noticed errors "Sender address
rejected: Domain not found" and it appears something has or is appending
the text "new-" to the beginning of the domain we use.  Further
investigation shows that "new-" is appended to the domain in the
config.pck, config.pck.last & config.pck.safety files.  I have no idea how
this got into the files but it appears to me the source of problem.  I have
reviewed the configuration of mailman via the administrative web interface
and it all appears correct (no arbitrary "new-" text) .  This is not a new
installation of mailman and has been in use for many years.  This issue
seemed to have started occurring in July of this year.  Any help would be
greatly appreciated.

Bill Richards

mailman version 2.1.12

Previous message:
=

A few weeks ago are started experiencing problems with approving and/or
discarding messages.  I am also unable to add/delete users to the list but
messages from approved list members work fine.  I suspect either some file
has become corrupted or a permissions issue.

I also see entries such as the following in the errors logs:

Aug 04 06:47:41 2019 (20501) No such list "aewa<[55":
Aug 04 11:05:13 2019 (28708) No such list "aewahttps://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Robert Heller]

At Sat, 24 Aug 2019 14:20:42 -0700 Mark Sapiro  wrote:

> 
> On 8/24/19 1:15 PM, Robert Heller wrote:
> > 
> > OK, I have installed Namazu, which will do what I want, *BUT* pipermail.pl 
> > is 
> > missing from the tarball I downloaded from the Namazu website.  Where can I 
> > get that file.  At this point, the search works, but the URI's are wrong 
> > (local file name, not the proper mailman URL).
> 
> 
> I can't answer directly, but see
> <https://bugs.launchpad.net/mailman/+bug/558138>.
> 

I figured out how to hack the Namazu code to incldue a "replacement" function 
and passed it on to the re-index function.  I think that will work.  (Perl is 
almost as bad as APL -- the only thing about Perl is that it uses "normal" 
ASCII, but still is pretty much write-only code, like APL.)


-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

  
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Mark Sapiro]

On 8/24/19 1:15 PM, Robert Heller wrote:
> 
> It is not clear if any of the options on that page will work for *private* 
> archives.  Most seem to be using an *external* third party search engine.  
> I'm 
> guessing I need to write a script (*I* don't know phthon and don't really 
> like 
> PHP) to do the searching and indexing on my server.


Ther HtDig branch at <https://code.launchpad.net/~msapiro/mailman/htdig>
definitely works with private archives. I use it.

If you don't want to install that branch which is based on 2.1.29+,
there is a 2.1.16 version of Richard Barrett's htdig and indexing
patches on which this is based at
<https://www.msapiro.net/mm/index_htdig.patch.2.1.16>. Also see
<https://www.msapiro.net/mm/_README>

You can get htdig at
<http://htdig.sourceforge.net/files/htdig-3.2.0b6.tar.gz>.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Mark Sapiro]

On 8/24/19 1:15 PM, Robert Heller wrote:
> 
> OK, I have installed Namazu, which will do what I want, *BUT* pipermail.pl is 
> missing from the tarball I downloaded from the Namazu website.  Where can I 
> get that file.  At this point, the search works, but the URI's are wrong 
> (local file name, not the proper mailman URL).


I can't answer directly, but see
<https://bugs.launchpad.net/mailman/+bug/558138>.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Robert Heller]

At Sat, 24 Aug 2019 08:46:50 -0700 Mark Sapiro  wrote:

> 
> On 8/24/19 5:59 AM, Robert Heller wrote:
> > Is it possible to have a search (eg by keyword) feature available for 
> > private 
> > archives with Mailman version 2.1.16?  There is no obvious setting for it.
> 
> 
> See <https://wiki.list.org/x/4030514>.

OK, I have installed Namazu, which will do what I want, *BUT* pipermail.pl is 
missing from the tarball I downloaded from the Namazu website.  Where can I 
get that file.  At this point, the search works, but the URI's are wrong 
(local file name, not the proper mailman URL).

> 

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
 
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Robert Heller]

At Sat, 24 Aug 2019 08:46:50 -0700 Mark Sapiro  wrote:

> 
> On 8/24/19 5:59 AM, Robert Heller wrote:
> > Is it possible to have a search (eg by keyword) feature available for 
> > private 
> > archives with Mailman version 2.1.16?  There is no obvious setting for it.
> 
> 
> See <https://wiki.list.org/x/4030514>.

It is not clear if any of the options on that page will work for *private* 
archives.  Most seem to be using an *external* third party search engine.  I'm 
guessing I need to write a script (*I* don't know phthon and don't really like 
PHP) to do the searching and indexing on my server.

> 

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
  
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Mark Sapiro]

On 8/24/19 5:59 AM, Robert Heller wrote:
> Is it possible to have a search (eg by keyword) feature available for private 
> archives with Mailman version 2.1.16?  There is no obvious setting for it.


See <https://wiki.list.org/x/4030514>.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman version 2.1.16 -- Search of *private* archives?

[Robert Heller]

Is it possible to have a search (eg by keyword) feature available for private 
archives with Mailman version 2.1.16?  There is no obvious setting for it.

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

 
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman eats this message. Why?

[Stephen J. Turnbull]

Sorry for the delay, I left this in my drafts folder "for lunch" and
forgot it.

Brett Delmage writes:

 > And it is working!

Great!  Thank you for reporting status.

 > The stupid thing is that I never changed anything.

That's useful to know, it means I'm not going crazy.  But these things
happen to all of us, and it's frequently something in the environment
of the moment that does it.  Hard to track down, glad you found your
issue.

Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman eats this message. Why?

[Brett Delmage]

Stephen and Christian,

Thank you for your most helpful replies.

I did some additional testing. I remembered (after) that I had a copy of 
the original message as received by Mailman, as I was copying the Mailman 
posting address mail to another mbox for debugging. Also, the user who had 
HTML-only mail was very helpful in working with me to send more test 
messages.


And it is working!

The stupid thing is that I never changed anything.

I did realize that the user had originally copied me on his list message - 
and "nodupes" caused my Mailman copy to not be sent.


With the tester and me being the only list members at the moment it 
therefore appeared that Mailman ate the message because I (and he) were 
the only recipients. (A previously active list is being moved to a new 
domain and is going online on Monday and I was debugging the new config.)


Duh. Blame my oversight on having a terrible summer cold this past week.

In the process though, I did realize that no list admins were subscribed 
to the site mailman list. Whoops.


You both posted useful info to the list which will be in the archives for 
others and me to refer to for similar problems int he future. (I've kept 
my own copy of the MM list messages since 2000 for easy local 
searchability.)


At the end of all my work I was happy to see my local SpamAssassin give 
our list messages a -1.1 score.


Again, thank you for your help and many contributions to this list.

Brett




--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org