Mailman 3 October 2021 - Mailman-Users

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

Problem with outlook.com
by nikos 15 Jun '22

15 Jun '22

Hello list. For some reason none of hotmail or outlook users don't receive any of our newsletter. Finally all of them auto unsubscribe. The following is an error received form protection.outlook.com: Remote Server returned '550 5.6.0 CAT.InvalidContent.Exception: ExchangeDataException, Decoding of header Subject failed+ADs- raw value: +AFs-Ps+AF0- +AD0-?iso8859-7?b?wer98fnz5yDF8OX05enh6t7yIOXq5N7r+-fPn8iDz9Oft?+AD0-; cannot handle content of message That happened since September 10th this year. Before, all received without problem. Any suggestions? Thank you in advance. Nikos.

5 9

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 18 Mar '22

18 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

Munge without CC or Reply-To
by Diez 22 Feb '22

22 Feb '22

Hello. I'm new at this list. I'm trying to setup a list (I'm not the site admin), and I'd like to use Munge From setting, but I'd like not have Reply-To field or CC field, but I suspect is not possible. I was testing with anonymous_list, but the problem is that only a certain member should send some kind of calls, but with anonymous_list anyone could send it. I'm setting up with 2.1.23 version. Regards and thanks in advanced and sorry for my bad english

6 10

Expected mailq behavior/maintenance commands
by John Lake 01 Nov '21

01 Nov '21

Howdy, Not-so-longtime watcher—first time poster. I’ll start by saying how much that I appreciate this Mailman resource, as a noob it has proved very valuable for me. I inherited the service owner role of Mailman recently and have been impressed at how well it works. Have not had any major pings until a few days ago, our monitoring system alerts if the queue exceeds 400 messages and it spiked to more than 600. It appears that a mass mailer produced a large number of bounces. One of my co-workers moved some of the messages out of the queue and it rapidly went down to below 300—and then vacillated over the next few days between 225-260 messages. It is now below 200 messages. I have not monitored the queue this closely before and it has raised some questions. 😊 I’ve looked through the documentation and community posts on the GNU website and I have not found specific information relating to what the expected mailq behavior/healthy number of messages is. I expect that this would vary by the environment and number of messages sent but am curious as to what would considered to be a normal/healthy threshold of queued messages. Are there purge/maintenance commands that can be leveraged for normal maintenance or in the case above—more of a kill-switch purge? Thanks in advance for any assistance. Happy Friday! John Lake Application Security Analyst University of Oregon

3 8

check_arch script changing owner
by Dean Collins 30 Oct '21

30 Oct '21

Using Mailman version: 2.1.33 packaged for cPanel. Running the script I obtained from https://www.msapiro.net/scripts/check_arch changes directory and file permissions and ownership. For example, in /archives/private/: drwxr-x--- 5 mailman username listname_mydomain.org becomes drwxrwxr-x 5 root root listname_mydomain.org And the list then stops archiving. Is there a way to adjust the script? Or run some command afterwards to set things back to where they were? Thanks for any help! Dean Collins

2 4

Digest on/off via email
by Mark Dale 21 Oct '21

21 Oct '21

Hi, As a list-member I'm unable to turn off digest-mode via email. To: <MY_LISTNAME>-request@lists.<MY_DOMAIN> Subject: set digest off Mailman (v 2.1.34) replies with an email (The results of your email commands) but the digest mode does not get set to "Off". //////////////////////////// //////////////////////////// The results of your email command are provided below. Attached is your original message. - Results: Not authenticated Usage: set help Show this detailed help. ... set digest plain set digest mime set digest off When the `digest' option is turned off, you will receive postings immediately when they are posted. Use `set digest plain' if instead you want to receive postings bundled into a plain text digest (i.e. RFC 1153 digest). Use `set digest mime' if instead you want to receive postings bundled together into a MIME digest. //////////////////////////// //////////////////////////// There isn't any info in the Mailman error log as to why the digest mode did not get turned off, and the only hint I've spotted so far is in the mail log where it says: "delivered to command: /var/lib/mailman/mail/mailman request LISTNAME" //////////////////////////// //////////////////////////// Oct 20 21:28:04 sfo postfix/local[30957]: 0C59141796: to=<***LISTNAME(a)list.***DOMAIN>, relay=local, delay=0.44, delays=0.38/0.01/0/0.05, dsn=2.0.0, status=sent (delivered to command: /var/lib/mailman/mail/mailman request LISTNAME) Oct 20 21:28:16 sfo postfix/smtp[30959]: 86BD141796: to=<mark(a)postmark.io>, relay=mx01.posteo.de[185.67.36.62]:25, delay=10, delays=0.01/0.01/9/1.3, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4HZNy74yvcz11SZ) //////////////////////////// //////////////////////////// I note that sending a request email with the subject as "set show" returns an email with the expected result and the mail log also shows "delivered to command: /var/lib/mailman/mail/mailman request LISTNAME" -- so I'm guessing there isn't a file permissions issue with /var/lib/mailman/mail/mailman. //////////////////////////// //////////////////////////// The results of your email command are provided below. Attached is your original message. - Results: Your current option settings: ack off digest plain delivery on myposts on hide off duplicates off reminders on - Done. //////////////////////////// //////////////////////////// Any clues on where I should be looking to get the Digest on/off working via email (or if I missed a setting in the list's Administration page) would be greatly appreciated. Thanks, Mark

2 2

Moderators and admins not getting notifications of held posts
by Bruce Johnson 20 Oct '21

20 Oct '21

We have a number of lists that are fully moderated and recently the moderators and admins have stopped getting notifications of held emails. The only change that occurred prior to this was changing the hostname the list prefers for email, which was accomplished by changing the setting in mm_cfg.py and running fix_urls. List emails are going out without any issues. Thinking that changing the mail host would affect the aliases, I ran genaliases, then reloaded postfix. I have confirmed that my postfix config is correct per https://www.gnu.org/software/mailman/mailman-install/postfix-integration.ht… I can see the messages being sent by mailman (I have a test list I'm using to figure this out): Mailman: Oct 19 17:08:50 2021 (2708) <mailman.2701.1634688529.2706.test(a)pharmacy.arizona.edu> smtp to test for 1 recips, completed in 0.005 seconds Oct 19 17:08:50 2021 (2708) <mailman.2703.1634688529.2706.test(a)pharmacy.arizona.edu> smtp to test for 1 recips, completed in 0.006 seconds Then in the mail log (I use Postfix as an mta) Oct 19 17:08:50 dhbmailman1 postfix/qmgr[2614]: CA3AB16111F: from=<test-bounces(a)pharmacy.arizona.edu>, size=6834, nrcpt=1 (queue active) Oct 19 17:08:50 dhbmailman1 postfix/smtpd[6773]: disconnect from localhost.localdomain[::1] Oct 19 17:08:50 dhbmailman1 postfix/smtp[6788]: C89DF160A61: to=<bruce.desertrat(a)gmail.com>, relay=smtp.pharmacy.arizona.edu[150.135.124.58]:25, delay=0.11, delays=0/0/0/0.11, dsn=2.0.0, status=sent (250 Ok: queued as E430F2320061) Oct 19 17:08:50 dhbmailman1 postfix/qmgr[2614]: C89DF160A61: removed Oct 19 17:08:50 dhbmailman1 postfix/smtp[6786]: CA3AB16111F: to=<test-owner(a)pharmacy.arizona.edu>, relay=smtp.pharmacy.arizona.edu[150.135.124.58]:25, delay=0.14, delays=0/0/0/0.14, dsn=2.0.0, status=sent (250 Ok: queued as E82592B00090) Oct 19 17:08:50 dhbmailman1 postfix/qmgr[2614]: CA3AB16111F: removed The email to the moderated sender is recieved: "Your mail to 'Test' with the subject Testing moderator messages Is being held until the list moderator can review it for approval. The reason it is being held: Post to moderated list" But the emails to the moderators and admins just seems to vanish. Our MTA on the lists machine is Postfix, and it is allowed to relay to our actual SMTP host for general delivery. I never see the emails arrive there for the moderators. As I said list mails and notification emails go though just fine. it’s just emails to list-owner that are failing. -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs

2 5

Mailman 2.1 security release
by Mark Sapiro 20 Oct '21

20 Oct '21

A couple of vulnerabilities have recently been reported. Thanks to Andre Protas, Richard Cloke and Andy Nuttall of Apple for reporting these and helping with the development of a fix. CVE-2021-42096 could allow a list member to discover the list admin password. CVE-2021-42097 could allow a list member to create a successful CSRF attack against another list member enabling takeover of the members account. These attacks can't be carried out by non-members so may not be of concern for sites with only trusted list members. In any case, I am planning to make a 2.1.35 release and to post a patch for those who don't want to upgrade to address these issues. This is scheduled for Tuesday, October 19. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 3

Mailman-Users October 2021