Mailman 3 November 2019 - Mailman-Users

OutgoingRunner processes hanging
by Kevin Bowen 15 Nov '19

15 Nov '19

Hello, Occasionally my mailman instance (2.1.9) gets into a weird state where one or more of its OutgoingRunner processes appears to hang (usually on a large email with a large number of recipients), causing a backlog of all other mail on that process's "shard" (or whatever the terminology is for how mailman divides up mail between runners based on hash). When it gets into this state, doing a mailman restart doesn't manage to successfully kill the "hung" process - it stays around after the restart (along with the mailmanctl instance that started it). Doing a tcpdump on the process usually shows that it's still sending data, but at a trickle (or sometimes not). Any ideas what could cause this, or how to resolve it? Kevin Bowen kevin.t.bowen(a)gmail.com <kevin(a)ucsd.edu>

2 5

LDAP routing
by Zinski, Steve 15 Nov '19

15 Nov '19

I hope that someone here can help me (or point me in the right direction). We are migrating from sendmail (virtuser) mail routing to LDAP routing. Setting up routing for users is pretty straightforward using the inetLocalMailRecipient class and the mail/mailLocalAddress/mailRoutingAddress attributes. But I was wondering what would be the best (correct) way to represent the mailman alias addresses in LDAP (i.e., list-admin, list-bounces, list-confirm, etc.). Would each get its own entry in LDAP or is there a better way? Any help would be appreciated. Steve [University of Richmond] Steven C. Zinski Sr. Network Programmer Network Services, Jepson Hall 221 Richmond Way University of Richmond, Virginia, 23173 804-289-8773 • szinski(a)richmond.edu<mailto:szinski@richmond.edu> • https://is.richmond.edu

3 3

Munge-from "From:" addresses and address auto-complete
by Dan Halbert 15 Nov '19

15 Nov '19

We have a number of Mailman V2 lists with "Munge-from" turned on, due to DMARC issues at receiving mail systems. This rewrites the From: addresses to something like: From: Dan Halbert via SOME-LIST <SOME-LIST(a)example.org> The problem is some email clients (I'm not sure which ones) pick up these "From:" addresses and add them automatically to the user's address book. Then, when the user wants to send a private (not list) message to some person on the mailing list, they start typing the person's name, and the email client may autocomplete with the list address, not the person's address. If the sender doesn't check the address carefully, they may send to the list inadvertently. This has led to several mildly embarrassing private messages being sent to a list. Is there some configuration I can set up that can alter these "From:" addresses to avoid putting the person's name first, but still including it? Or is there some other way to ameliorate this problem? We could choose something other than "Munge-from", but we do not want to lose the identity of the sender, which is worse. We are using a third-party provider and have no direct control over the formatting of the rewritten "From:" header; I would change the Mailman code directly if I could. Thanks, Dan

2 1

Regexp matching failing for accept_these_nonmembers
by Gretchen M Beck 08 Nov '19

08 Nov '19

Hi Folks, I'm on mailman 2.1.18-1, and this week I've received several complaints about messages held for moderation. Specifically, users whose addresses are in the "accept_these_nonmembers" list, or whose addresses match a regexp that is on the list are getting held as "Post by non-member to a members-only list" While I have had one complaint about this happening for a non-umbrella list, most of the examples have the non-member posting to an umbrella list where they are also accept_these_nonmembers, having the message pass through without moderation, then have it held at the next lists down (where it also should be accepted). I thought "well, let's see what parseaddr is returning" and so slapped a syslog at the appropriate point in Moderate.py, but so far what that is showing me matches the regexp in accept_these_nonmembers. What am I missing here? Thanks! --Gretchen Gretchen Beck Carnegie Mellon

2 3

confirm.py not working with https
by jimwest＠attglobal.net 05 Nov '19

05 Nov '19

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. In /etc/httpd/httpd.conf, I am redirecting all http traffic to https using the redirect command in httpd.conf. This may be causing a problem in confirm.py when retrieving the confirmation cookie from the URL using cgidata.getvalue. Entering the confirmation cookie manually in confirm.py also does not work. 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

1 0

Mailman 2.1.12 confirm.py works fine with http but does not work with https
by jimwest＠attglobal.net 05 Nov '19

05 Nov '19

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

2 1

Mailman Python Apache CGI issue
by jimwest＠attglobal.net 05 Nov '19

05 Nov '19

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://<my-web-site>/mailman/confirm/skipper/b36adbfa6d4b9af927197b75006444262696b9a6 <http://kjm.PositionDatabase.com/mailman/confirm/skipper/b36adbfa6d4b9af9271…> The string "b36adbfa6d4b9af927197b75006444262696b9a6" <http://kjm.PositionDatabase.com/mailman/confirm/skipper/b36adbfa6d4b9af9271…> 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: jimwest(a)attglobal.net

2 1

List DMARC compliance reconfiguration
by Andy Cravens 05 Nov '19

05 Nov '19

Using mailman 2.1.26. I’m auditing the lists on my server for DMARC compliance I’ve found several list configs that do not have the DMARC action set to “munge_from.” It appears I need to edit all those list and fix that setting. I’ve also noticed that in mm_cfg.py there is no setting for REMOVE_DMIM_HEADERS. I just wanted to verify the proper order for fixing these issues. Seems like I need to correct the munge_from setting for all the affected lists and them as quickly as possible add REMOVE_DKIM_HEADERS = 1 to mm_cfg.py and restart. It appears that which ever task I complete first some messages will be undeliverable until both changes are complete. Maybe it would be best to stop mailman, complete both changes and then restart? Just looking for the best way to do this.

2 1

Mailman with Interworx server administration
by Christian F Buser 04 Nov '19

04 Nov '19

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-administrator…> 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

2 1

Re: [Mailman-Users] user unsubscribe
by Bernie Cosell 04 Nov '19

04 Nov '19

On 2 Nov 2019 at 21:23, Mark Sapiro wrote: > On 11/2/19 5:03 PM, Bernie Cosell wrote: > > ... Here's the > > message i got.. no reason why: > > > > Subject: NPL-Folk unsubscribe notification > > From: mailman-bounces(a)lists.puzzlers.org > > To: npl-folk-owner(a)lists.puzzlers.org > > Date: Mon, 28 Oct 2019 22:24:21 -0700 > > Sender: "NPL-Folk" <mailman-bounces(a)lists.puzzlers.org> > > > > deartom(a)hotmail.com has been removed from NPL-Folk. > > > This is the generic unsubscribe notification from the list's > .ApprovedDeleteMember method. Starting with Mailman 2.1.27, it also > reported the source of the unsubscribe. The source is reported in the > entry in Mailman's subscribe log if you have access to that. Nope. I have no access to that and I just got another "has been removed" message this morning. Is there any way for a non-privileged mailman admin to figure out why? I didn't get any "bounce score incremented" messages for either unsubscribe. /Bernie\ Bernie Cosell bernie(a)fantasyfarm.com -- Too many people; too few sheep --

4 4

Mailman-Users November 2019