Mailman 3 October 2014 - Mailman-Users

Membership search changes?
by Jim Popovitch 31 Oct '14

31 Oct '14

Hello, Did something change recently with Membership searches in mm-2.1.18-1? It seems that the search text no longer searches the complete subscriber list, rather only the selected (i.e. A, B, C, D, etc) grouping. I searched the bug reports and didn't see any thing related. Thx, -Jim P.

2 2

Changing ports doesn't seem to work
by Brian Rudy 30 Oct '14

30 Oct '14

Hello all, Due to changing ISP's I was forced to change my web port to something other than 80. On port 80, everything was working well. I moved all of my web interfaces to port 8000. I thought I followed the instructions correctly and did: bin/withlist -l -r fix_url <listname> It seems to work fine using http://host.example.com:8000/mailman/admin/<listname> but any link I click on doesn't add in the port number (:8000) so by default, it's trying port 80. Is there any way around that? If I manually copy the link and paste it in the url of the browser and manually add in the :8000 the link works fine. The problem then is when I try to submit something... It doesn't take. I would appreciate any assistance. Thank you, Brian

2 2

Squirrelmail and wrapped messages
by Ed Ravin 30 Oct '14

30 Oct '14

I've converted a list to Mailman, and as I posted previously, I decided to use "wrapped" messages to keep AOL's hairtrigger spam filters from discarding incoming messages from AOL users. Now I'm getting complaints from Outlook 2007 and Squirrelmail users that the messages from Mailman show up as text attachments that aren't automatically displayed or previewed. It looks like Outlook 2007 users can turn previewing on, but I don't see any such options for Squirrelmail. How have other Mailman admins dealt with this? I wonder if it's possible to to make wrapped messages a user preference, or have them only turned on for certain domains as discussed previously. Is this a patch that would be accepted in the future? -- Ed

4 4

Strange rejection
by Lindsay Haisley 28 Oct '14

28 Oct '14

I'm moving mailing lists from one server to another using a couple of scripts which I've used successfully many times before for other such moves. On the 3rd list I've moved (second domain name) I've run into a very strange problem. On trying to post to the list on the new server my posts get delivered to the list and discarded with no further explanation. The vette logfile just says: Oct 24 23:15:30 2014 (2180) Message discarded, msgid: <1414210524.38839.9.camel(a)pudina.fmp.com> The Mailman version on the old system is 2.1.18, and 2.1.18-1 on the new one. The working environment is almost identical on both systems. The list configurations are completely identical. The two other lists which I've already moved to the new location are working properly, as best I can tell so far. I'm subscribed to the list, which is an open discussion list, added myself as a list moderator, and am on the accept_these_nonmembers list (or not - it makes no difference) in case I should get unsubscribed. The only thing I see which _might_ make a difference is that the new server is running Python 2.7.6 while the old one is running 2.7.3. I backed out the move and posted to this problem list in its old location, and the post went trough to the subscribers and the archive. There are no other related entries in the Mailman log files - just "Message discarded" in the vette file. Is there any way to turn on more thorough debugging, or tracebacks if there are hidden code glitches? What could be causing this? I'm Python-literate and can read tracebacks and poke diagnostic code into Mailman modules if someone can point me in the right direction to get to the bottom of this. I've got half a dozen or so lists to move so I have to get this solved. -- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com |

2 5

Re: [Mailman-Users] Change Mailman URLs on Subscribe Response
by Russell Clemings 26 Oct '14

26 Oct '14

It would be a little different. The main difference is that the Mailman subscriptions are linked to the Drupal user account, so each subscriber would need to be a Drupal user. I think there's also a way to import existing Mailman subscriptions and create Drupal users for them, but I may be remembering a different module, Mailman Manager: https://www.drupal.org/project/mailman_manager rac > ---------- Forwarded message ---------- > From: Tracey McCartney <tracey(a)fairhousing.com> > To: <mailman-users(a)python.org> > Cc: > Date: Sat, 25 Oct 2014 18:23:51 -0500 > Subject: Re: [Mailman-Users] Change Mailman URLs on Subscribe Response > Ooh, that's an interesting module. I currently have a Drupal site where > people who want to join my list sign into Drupal using a special account > I've set up, then go through a Webform that explains the list rules and > then > get forwarded to the Mailman subscription page. I wonder if this would be > a > more elegant solution. Thanks for posting that. > > > Tracey > > -----Original Message----- > From: Mailman-Users > [mailto:mailman-users-bounces+tracey=fairhousing.com@python.org] On Behalf > Of Russell Clemings > Sent: Saturday, October 25, 2014 4:33 PM > To: mailman-users(a)python.org > Subject: [Mailman-Users] Change Mailman URLs on Subscribe Response > > Since you're using Drupal (http://www.raystedman.org/CHANGELOG.txt), you > might want to look at the User Mailman Register module: > > https://www.drupal.org/project/user_mailman_register > > It allows you to manage Mailman subscriptions from within your Drupal > installation. Your users will never need to see the Mailman pages. > > (By the way your Drupal installation is extremely out of date ... and you > really should hide that CHANGELOG.txt file so that people like me can't > find > out so easily that your Drupal installation is extremely out of date.) > > rac > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users(a)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/tracey%40fairhousing.c > om > > > > >

1 0

Change Mailman URLs on Subscribe Response
by Russell Clemings 26 Oct '14

26 Oct '14

Since you're using Drupal (http://www.raystedman.org/CHANGELOG.txt), you might want to look at the User Mailman Register module: https://www.drupal.org/project/user_mailman_register It allows you to manage Mailman subscriptions from within your Drupal installation. Your users will never need to see the Mailman pages. (By the way your Drupal installation is extremely out of date ... and you really should hide that CHANGELOG.txt file so that people like me can't find out so easily that your Drupal installation is extremely out of date.) rac

2 1

Mailman Htdig integration with Nginx - Path variables
by Andrew Hodgson 25 Oct '14

25 Oct '14

Hi all, Wonder if someone could take a look at this for me? I have moved our Mailman installation to Nginx. Everything is working correctly, however, I am using the Htdig patch to get search functionality. I got the split_path_info set up to work with Mailman, but I am having issues getting a working installation with the mmsearch script. The initial page loads up, but when you refine the search or go to the next page, I get an error with the path splitting which causes the CGI to error. I tried altering the path variable for the mmsearch script specifically, but the issue I am having is getting Nginx to split the path in the right place, since the scripts don't have an extension to work with (like I can use with PHP scripts etc.). It's probably a simple fix, and I can set the location for the mmsearch script so it doesn't mess up the path variable for the other Mailman scripts if required. My config is below, sorry for the formatting in my mailer. Andrew. # HTTP redirects - I had to use separate servers for each domain to stop redirecting to the wrong host server { listen 80; server_name lists.domain1.com; access_log off; error_log off; rewrite ^ https://$server_name$request_uri?$query_string permanent; } server { listen 80; server_name lists.domain2.com; access_log off; error_log off; rewrite ^ https://$server_name$request_uri?$query_string permanent; } server { listen 443 ssl; server_name lists.domain1.com lists.domain2.com; access_log /var/log/nginx/lists-access.log main; error_log /var/log/nginx/lists-error.log warn; root /var/www/lists; ssl_certificate /path/to/cert.pem ssl_certificate_key /path/to/key.key ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS; ssl_prefer_server_ciphers on; add_header Strict-Transport-Security "max-age=31536000; includeSubdomains"; ssl_stapling on; ssl_stapling_verify on; # Redirect to the listinfo page by default location = / { rewrite ^ /listinfo permanent; } # Send the requests to the various scripts to the correct location. URL https://server/listinfo etc. location ~ ^/(admin|confirm|edithtml|listinfo|options|rmlist|subscribe|admindb|create|htdig|private|roster|mmsearch) { fastcgi_split_path_info (^/[^/]*)(.*)$; fastcgi_param SCRIPT_FILENAME /usr/local/mailman/cgi-bin/$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_pass unix:/var/run/fcgiwrap.socket; include /etc/nginx/fastcgi_params; } location /icons { alias /usr/local/mailman/icons; } location /pipermail { alias /usr/local/mailman/archives/public; } location /htdigimages { alias /var/lib/htdig/www; } }

2 2

Change Mailman URLs on Subscribe Response
by Greg Sims 25 Oct '14

25 Oct '14

I created the following subscription webpage for list name devotion-chinese: http://www.raystedman.org/daily-devotions/chinese-subscription After clicking "Submit", the user will be transferred to: http://lists.raystedman.org/mailman/subscribe/devotion-chinese I updated subscribe.html so I can control the content of this page. Is it possible for the user to be transferred to a URL that is under the control of our CMS? Perhaps I could use a pattern for all of the URLs associated with this list like: http://www.raystedman.org/daily-devotions/devotion-chinese/* This would allow the format of the subscription page and subscription response page to have the same format (color, headers and the like). I tried to do this with a URL Rewrite in Apache but could not get it to work. I also searched the archives and did not find anything. Thanks for helping me sort this out, Greg

2 1

Re: [Mailman-Users] Customizing information required for subscription
by Charlene Ruell 21 Oct '14

21 Oct '14

Hello all, Thanks so much for the recommendations regarding my query below! The plot thickens as we are operating the lists via cPanel, so I am unsure if the member add-on will work (thoughts?). However, I am also curious if there is any way for our users to subscribe to multiple lists at once? We have (or will have) around 9 or 10 on the same server and a large number of users utilize multiple lists. I'm sure it is a long shot, but we would love to streamline our process. Many thanks in advance! Warm Regards, Charlene ______________________________________ Charlene Ruell Program Assistant Climate Action Network-International (CAN) skype: charlene.ruell cruell(a)climatenetwork.org www.climatenetwork.org <http://www.climatenetwork.org/> www.facebook.com/CANInternational Twitter: @CANIntl Subscribe to the ECO newsletter: http://climatenetwork.org/eco-newsletters From: Charlene Ruell [mailto:cruell@climatenetwork.org] Sent: 08 September 2014 8:14 PM To: 'mailman-users(a)python.org' Subject: Customizing information required for subscription Hello all, I am working with a non-profit organization to establish a new home for our plethora of mailing lists. Mailman has quite a few features that we are hoping will automate our currently labour intensive process. Currently, part of our subscription process involves gathering additional information, such as which one of our member organizations the person requesting access if from. We then match this information to our records and subscribe those who are eligible. I have looked through all of the documentation for Mailman and have not been able to find if there are customizable fields for the subscription process. Does this exist? If not, does anyone have any suggestions on how I might integrate such information with the subscription process? Many thanks in advance! Warm Regards, Charlene Ruell ______________________________________ Charlene Ruell Program Assistant Climate Action Network-International (CAN) skype: charlene.ruell cruell(a)climatenetwork.org www.climatenetwork.org <http://www.climatenetwork.org/> www.facebook.com/CANInternational Twitter: @CANIntl Subscribe to the ECO newsletter: http://climatenetwork.org/eco-newsletters

2 1

AOL screening Reply-To header thru DMARC ?
by Ed Ravin 19 Oct '14

19 Oct '14

I'm setting up a new Mailman server to replace an elderly MajorDomo that isn't DMARC-compatible. I set up the list to use the list's address as the From address and to put the sender's address in Reply-To:. I started playing around with a test list - in no time at all, AOL began bouncing all my mail. After researching AOL's error messages, it appeared that my server had been temporarily blacklisted. That went away but then I noticed this error: Oct 18 01:01:26 vc18 postfix/smtp[25098]: C77D416B4D9: host mailin-01.mx.aol.com[152.163.0.67] said: 421 4.2.1 : (RLY:SN) http://postmaster.info.aol.com/errors/421rlysn.html (in reply to end of DATA command) According to that URL on AOL's site, either my From or Reply-To is using an address in violation of DMARC. I had already checked the From address so it was apparent the Reply-To was at fault. Aalthough the mail was not being rejected, given AOL's hair-trigger sensors I figured it would be better to do it their way. Changing the Reply-To: to the list's address got rid of the 421 error. Has anyone else run into this? I hate doing this, since now we're going to see people sending what they think are private messages to the entire list. I see from the docs that Mailman can do different behavior on the From: address depending on whether it is in a DMARC-protected domain - are there any plans to do the same for the Reply-To? Looks to me like it will be necessary given what AOL is doing. Thanks, -- Ed

4 6