Mailman-Users August 2020

mailman-users@python.org

28 participants
20 discussions

Re: [Mailman-Users] Automate Moderator Functions
by Andre de Azevedo Cunha 18 Apr '22

18 Apr '22

Hi, i`m trying to reject messages bigger then MAX_MESSAGE_SIZE. I configured my Hold.py was described bellow: replaced hold_for_approval(mlist, msg, msgdata, _ MessageTooBig(bodylen,_mlist.max_message_size)) with rej = MessageTooBig(bodylen, mlist.max_message_size) _ raise Errors.RejectMessage, rej.reason_notice_ The message was rejected, but the sender dont receive any notify about that. The mailman vette log too. How can i solve this? Thanks, André Dennis Putnam wrote: > >I am getting back to this and I have a question about maintenance. What >is the correct way to modify this so that it will not get destroyed by >updates? There are two ways to proceed. You can modify Mailman/Handlers/Hold.py itself, but before overwriting it, make a "diff -u" between the base Hold.py and your modified version to use as a patch to apply after any upgrade. A better way is to leave Hold.py unchanged and make your own edited version as say Mailman/Handlers/MyHold.py. Then you can replace the base Hold.py Module with your MyHold.py by putting GLOBAL_PIPELINE[GLOBAL_PIPELINE.index('Hold')] = 'MyHold' in mm_cfg.py. Note that if you are going to do this, and you want also to move MimeDel before Hold, you must either put the above line after the lines GLOBAL_PIPELINE.remove('MimeDel') GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'MimeDel') in mm_cfg.py or put it before, but then also change GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'MimeDel') to GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('MyHold'), 'MimeDel') I recommend the former as in # # Put MimeDel ahead of Hold so "too big" is based on content filtered # message. # GLOBAL_PIPELINE.remove('MimeDel') GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'MimeDel') # # Replace Hold with local version # GLOBAL_PIPELINE[GLOBAL_PIPELINE.index('Hold')] = 'MyHold' Since mm_cfg.py survives upgrades, this should survive. >Also does this same procedure apply to other automatic rejections such >as implicit destination? >On 9/24/2012 8:43 PM, Mark Sapiro wrote: >> >> To automatically reject or discard messages that exceed the list's size >> limit, find the section of the Mailman/Handlers/Hold.py that ends with >> the lines >> >> >> if bodylen/1024.0 > mlist.max_message_size: >> hold_for_approval(mlist, msg, msgdata, >> MessageTooBig(bodylen, >> mlist.max_message_size)) >> # no return >> >> (there is one wrapped line in the above) and replace >> >> hold_for_approval(mlist, msg, msgdata, >> MessageTooBig(bodylen, >> mlist.max_message_size)) >> >> with >> >> rej = MessageTooBig(bodylen, mlist.max_message_size)) >> raise Errors.RejectMessage, rej.reason_notice >> >> to reject the message or with >> >> raise Errors.DiscardMessage >> >> to discard the message. Note that this will not honor the list's >> forward_auto_discards setting. to do that you would need to put >> >> from Mailman.Handlers.Moderate import do_discard >> >> with the other imports near the beginning of the >> Mailman.Handlers.hold.py module and then replace the lines with >> >> do_discard(mlist, msg) Yes, similar changes would apply to other holds in Hold.py. -- Mark Sapiro <mark at msapiro.net [1]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- Links: ------ [1] http://mail.python.org/mailman/listinfo/mailman-users

2 11

Newbie User
by David Elliott 17 Mar '22

17 Mar '22

Hi, I am a newbie to Mailman and cpanel and I need some help, please. I have set up a mailing list for my tennis club (about 300 on list) and it seems to work ok BUT each recipient only sees the mailing list name rather than his own email name in the 'to' box. One of the recipients recently did a 'reply to all' and consequently sent his reply to the whole mailing list. I'm sure there must be a way to prevent this but I can't find it! David Elliott

5 6

Subscription Requests
by nikos 01 Jun '21

01 Jun '21

Hello list. I'm receiving a lot of fake Subscription Requests and spend time to discard them. 1. how can I "lock" lists not to receive requests except administrator's mass subscription? 2. how can I mass discard those request from console? Thank you in advance, Nikos.

6 13

Add "sender's name/email" to BODY of mail as header?
by Mal 16 Feb '21

16 Feb '21

I want all mails sent to the list to come from the list's email address... But, in this case, if the user forgets to sign their name at the bottom of their mail body, effectively the mail to the list is anonymous...! Is there a way to add the user name (or email address) to the top of each mail so that the mails have the name of the sender, while the mail itself comes from the list address? I have looked high and low for an answer, but noone seems to have the solution. Thank you! Mal

9 14

mailman v2.x
by Jim Popovitch 20 Sep '20

20 Sep '20

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

21 128

Manual Update on Centos 7
by Dennis Putnam 17 Sep '20

17 Sep '20

Since Centos 7 is way behind on mailman rpm (2.1.15 is the only available rpm) and mailman is currently at 2.1.34 I need to do a manual update. While I know how to install software, I am concerned that just doing a manual install from the tarball will mess up current settings, lists and members. Does anyone have experience doing this that can advise about pitfalls or has a cookbook document to do a safe update? TIA.

4 23

Mailman CGI Error-Group mismatch error
by Wang, Mary Y 09 Sep '20

09 Sep '20

Hi, I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error? "Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Group mismatch error. Mailman expected the CGI wrapper script to be executed as group "nobody", but the system's web server executed the CGI script as group "apache". Try tweaking the web server to run the script as group "nobody", or re-run configure, providing the command line option `--with-cgi-gid=apache'." Thanks Mary

3 3

Problem with unsubscribe from host with tor node
by Konrad Wawryn 30 Aug '20

30 Aug '20

Hi, I would like to unsubscribe that list but it seems that Your MX which hosting mailman-users(a)pythong.org is not Tor friendly. Im getting confirmation from Your host, that my unsubscribe e-mail has been rejected - because it looks like spam. Also I`m not able to do it using website provided in Your E-mail footer. IP of my server is blacklisted by primitive BL pyzor.org - because its part of the tor network. Please remove by address from Your list and be more TOR friendly if possible. Cheers Konrad -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

google/gmail issues
by Jeffrey Westgate 25 Aug '20

25 Aug '20

We run a list of our mailman listserver that our public school sysadmins use to share info. The problem is - a lot of them have become Google schools, and Google has a problem with list servers. Each post winds up going to multiple Google mail domains, and they bounce: stat=Deferred: 451-4.3.0 Multiple destination domains per transaction is unsupported. meaning the emails are queued, sometimes for quite a while, as the system sends each domain, one attempt (and one mess of deferrals) at a time. Is there a setting I can change or add that would allow mailman to kind of bundle each domain, open a thread, and send one-thread-per-domain or one-domain-per-thread to alleviate the issue? We are a bit behind, using Mailman version: 2.1.20 -- Jeff

2 1

Fwd: Mailman error.
by Soporte Syscomed 25 Aug '20

25 Aug '20

Good morning. Today, when I tried to access Mailman, I obtained the following error: --------------------------------------------------- Bug in Mailman version <undetermined> 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 have checked the logs and they have no information. I have checked mailman status and it's active and also have checked the permissions and they're right. It still doesn't work and I have no idea of what to do. Can you help me please? Thank you. -- Iván Molina Pastor. C/Perú, 5-1, Edificio FORUM II, of. 3.9 Polígono . Ind. Oeste 30820 - Alcantarilla (Murcia) Telf: +34 968 351 364 INFORMACIÓN SOBRE PROTECCIÓN DE DATOS Sistemas y Control del Mediterráneo SL como Responsable del Tratamiento, con domicilio C/ Perú, nº 5- Edif. Forum II, 3ª planta oficina 9. P.I.Oeste- 30820 Alcantarilla-Murcia. Telf. 968351364 Mail: info(a)syscomed.es CIF. B73503914. Le informa que trata sus datos para la finalidad de gestionar relación comercial, con la base jurídica de nuestra relación comercial. Sus datos se conservarán todo el tiempo que dure nuestra relación, o se puedan derivar responsabilidades de la prestación de servicios. No se realizan cesiones, excepto por obligación legal. Para ejercer sus derechos de acceso, rectificación, supresión, portabilidad de sus datos, limitación u oposición al tratamiento de sus datos, puede hacerlo dirigiéndose a Sistemas y Control del Mediterráneo SL en la dirección arriba indicada, adjuntando documento que acredite su identidad, o interponer reclamación ante la Autoridad de Control. Más info: www.syscomed.es

2 1