Mailman 3 December 2016 - Mailman-Users

I'm new to this list
by Jim Hopkins 03 Dec '16

03 Dec '16

I’m in Education and recently moved mailman to a linux box. Now when I send a message to the list serve, I don’t receive the email and don’t know that it was sent. Is this correctable? I would appreciate any help on this issue. Thanks. Jim Hopkins

3 2

Temporarily Disable a List
by Anilkumar Padmaraju 02 Dec '16

02 Dec '16

What is the best way to temporarily disable a list in mailman. Later if needed want to enable back. Thank you, Anil.

3 2

How to make forms use https, not http
by Brett Delmage 02 Dec '16

02 Dec '16

I cannot find where to change admin pages to use https on submission instead of http. My config: Mailman version 2.1.20 on Ubuntu 16.04 /etc/mailman/mm_cfg.py was changed to DEFAULT_URL_PATTERN = 'https://%s/mailman/' A config_list dump for the list doesn't show any relevant http that should be changed to https, unless I am missing this. I switched the list to https after being created IIRC (after I got the SSL certs installed and working) The admin pages display correctly in https, but FORM action still submits to a "http" list URL according to the page html source. What am I missing? Thanks! Brett

3 3

munging the To: line?
by Joe Pfeiffer 01 Dec '16

01 Dec '16

I've searched the archives and the FAQs; if I've missed something please point me to it. I've got From: munging turned on, so posts to a list I administer come "from" addresses like John Smith via mylist <mylist(a)example.com> Frequently, list users will post to the list by replying to a previous message, and I'll end up getting a message with a To: header like To: John Smith via mylist <mylist(a)example.com> and it goes out to the list with that To: header. Since this can be confusing, I'd like to munge the To: line as it comes through so it ends up saying To: My List <mylist(a)example.com> Is there a way to do this through standard configuration options (and how?), or do I need to write a handler? -- Joe Pfeiffer 575.525.2764 (H) 1440 Tierra del Sol Dr 575.496.3501 (C) Las Cruces, NM 88007-5548

3 2

subscribers being unsubscribed at wrong time based on bounce settings.
by Christopher Adams 01 Dec '16

01 Dec '16

Hello, I have done some fairly extensive examination of logs and list settings for one of the lists hosted here, and I can't come up with a sensible explanation to tell a customer. The list is set to not send messages when a person unsubscribes. The bounce settings are set so that 2 warning messages are sent after the address is disabled and those messages should be 7 days apart. A message was sent to the list on 11/1. I see in the logs that a substantial number of addresses reached the bounce limit and were disabled. So, based on the bounce settings, many of these should have been unsubscribed 14 days later. They were not. However, on 11/24, there was a mass unsubscribe of addresses that had been disabled. Additionally, many (including some that turned out to have valid addresses) received unsubscribe notices. I tend to think that these are not related, but are two issues that I have not been able to explain. Many thanks, Christopher Adams

2 3

Time needed to deliver list messages
by Christian F Buser 01 Dec '16

01 Dec '16

Hi all Our lists run on a cPanel installation of Mailman (cPanel version 60.0.25, Mailman version 2.1.23). Messages sent to the list take some long time to be delivered to the subscribers - in the best case it is about 10 minutes, but it can take up to over 40 minutes. We asked our provider about it, and he tried to finetune some settings on the server - so far without success. He said he also contacted cPanel support and their response was "this is normal - there is nothing they can do about it", he said. My question to all who run Mailman on cPanel: Is it true? Are you also experiencing delivery delays? Thank you, Christian -- Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org

4 3

Failing https://mail.python.org/mailman/listinfo/mailman-users
by Julian H. Stacey 01 Dec '16

01 Dec '16

Hi postmaster(a)python.org cc: mailman-users(a)python.org I sent this to webmaster(a)mail.python.org per request of your web page -------- https://mail.python.org/mailman/listinfo/mailman-users Bug in Mailman version 2.1.23 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. -------- "Julian H. Stacey" wrote: > Hi webmaster(a)mail.python.org > FYI > https://mail.python.org/mailman/listinfo/mailman-announce > Bug in Mailman version 2.1.23 > > We're sorry, we hit a bug! > > Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. I got this inapproprate automatic junk back: > Sender: "Webmaster" <webmaster-bounces+jhs=berklix.com(a)python.org> > > READ THIS! (If you want help.) No I dont want help. So noise skipped. Your site asked for help. Then your site discarded the help you had requested. PS This also fails: https://mail.python.org/mailman/listinfo/mailman-users Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes

2 2

Mailman-Users December 2016