Mailman-Users July 2020

mailman-users@python.org

23 participants
22 discussions

Using cronjob to remove and add members to a mailing list
by Jerry Barnabee 10 Aug '22

10 Aug '22

I want to be able to run a cronjob on my server that uses a php script to add new users and/or remove users from a mailing list. Not having any luck finding any simple examples. My thought is that the php script would get email addresses from a database (which I can do) and then feed them to a mailman command line to either add or remove a user. The cronjob is entered via Cpanel. Have several cronjobs that modify databases but have never tried something that would actually execute a unix command. Thanks, Pineyscripter

3 3

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

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

dnspython error
by csa＠web-analysts.net 31 Jul '20

31 Jul '20

I'm updating Mailman from 2.1.19 to 2.1.34 from source. When I run configure ./configure --prefix=/var/lib/mailman --with-username=list --with-groupname=list --with-cgi-gid=www-data --with-mail-gid=list I get an error that dnspython is not installed checking dnspython... configure: error: when I then try and install dnspycthon using pip, I get Requirement already satisfied: dnspython in /usr/lib/python2.7/dist-packages Help (please)! Thank you in advance.

2 5

"Error: Unknown virtual host" trying to create new list from web UI
by Sean McBride 30 Jul '20

30 Jul '20

Hi all, I'm running mailman 2.1.x. I haven't had need to create a new list in years, but now I need to. Trying to do so from the web UI here: <https://mail.rogue-research.com/mailman/create> results in: "Error: Unknown virtual host: mail.rogue-research.com". After searching for this, I now have a partial understanding of the problem. In my Defaults.py I see: DEFAULT_EMAIL_HOST = 'foo.rogue-research.com' DEFAULT_URL_HOST = 'foo.rogue-research.com' DEFAULT_URL_PATTERN = 'http://%s/mailman/' foo is the real hostname of the machine. I guess that's how it ended up there? After reading the comments in that file and FAQ 4.29, I *think* the correct solution is to append the following 5 lines to my mm_cfg.py: DEFAULT_EMAIL_HOST = 'rogue-research.com' DEFAULT_URL_HOST = 'mail.rogue-research.com' DEFAULT_URL_PATTERN = 'https://%s/mailman/' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) Is that correct? Many thanks, Sean

2 5

Very strange issue With Mailman + Exchange(?)
by Bruce Johnson 29 Jul '20

29 Jul '20

I am not sure how to figure this out. Lengthy explanation: Internally in our Exchange server, that address is a distribution group whose only member is the actual <list-name>@lists.pharmacy.arizona.edu, because the Mailman server is not our mail server. (we have a mildly complicated setup: hybrid OnPrem and O365 exchange + Barracuda spam appliance in front of all of it, which is our actual SMTP server. Outgoing email from the list server bypasses Exchange and is sent directly to the Barracuda SMTP server. For two users and ONLY these two users, somewhere between them and mailman and back, the Mailman list is being expanded to put all the members of the list on the CC line. It then gets held for approval with a ’too many addresses’ message. I have watched them send an email to the affected list; the list address is NOT in their local address cache, and they are NOT entering any other addresses in the email other than the list address. The only address that appears on the email in their Sent folder is the list address. Other users in our organization can send to these same lists without this happening. In fact one of the affected users can send to *other* lists on our server with no problems. These are two different lists. I don’t know that this is specifically a Mailman problem (because it’s only happening with specific users) but I cannot see how list members are getting stuffed on the CC line otherwise; because Exchange only knows the list address, not the members; only Mailman does. TLDR: Somehow the all the list addresses are getting stuck onto the list message which then holds it for approval for ’too many addresses’. -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs

2 2

Alternate URL hostname in web UI
by Kevin Bowen 28 Jul '20

28 Jul '20

Hello, I'm trying to set up the mailman (2.1.9) web UI behind a load balancer in order to offload the TLS to it (because this is an ancient machine which doesn't support modern TLS versions, and newer browsers are complaining about it). I need all the links in the web UI to use the new hostname that's in front of the loadbalancer, instead of the actual hostname behind the loadbalancer. Am I understanding correctly that DEFAULT_URL_HOST in mm_cfg.py would be the way to accomplish that? And would that affect only the URLs used in the web UI, it wouldn't change anything about the actual mail handling under the hood? Kevin Bowen kevin.t.bowen(a)gmail.com <kevin(a)ucsd.edu>

3 5

Disable mailman 3 emergency moderation flag after migration from mailman 2
by Johanna Amann 28 Jul '20

28 Jul '20

Hi, I have a kind of interesting problem. We migrated a mailman 2 list that had emergency moderation enabled to mailman 3 (version 3.3.1). This was imported into mailman 3 - so emergency moderation is still enabled. The web interface, however, does not expose the emergency moderation flag. Is there some way to disable it via the command line? Thanks a lot, Johanna

3 4