Mailman 3 January 2020 - Mailman-Users

Hide list address?
by Ricardo Kleemann 16 Nov '23

16 Nov '23

Hi, Is there any way to configure Mailman such that, for an announcement-only type list, when a message is sent to the list, the To: shows the member's address, rather than the list address? Some list software allows the ability to hide the list address itself, so that address is not advertised. I couldn't find any configuration specific to that.

7 6

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

Find a smtp server to send out emails
by Leon 20 Mar '20

20 Mar '20

Hi, This problem is not caused by mailman, but I still want to give it a shot here. I'm hosting a mailing list on top of mailman. Emails are supposed to be sent out by AWS ses. However, ses requires that sender address must be verified, which leads to a problem that emails sent by subscribers to mailing list cannot be sent to other subcirbers, since their addresses are not verified. And it is impossible to verified every subscriber. Are there smtp service providers allowing unverified email address to send out emails, or do I have other solutions? Thanks. Leon

7 7

Mailman 2.1.30rc1 released
by Mark Sapiro 19 Feb '20

19 Feb '20

I am pleased to announce the release of Mailman 2.1.30rc1. Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended. This is a routine bug fix release with a few new features. See the attached README.txt for details. Mailman 2.1.30 will be the last release of the Mailman 2.1 branch from the GNU Mailman project. It contains some new strings which are untranslated in most of the i18n translations. If you can help update any of the translations, please contribute your changes. Changes can be submitted via a bzr merge proposal on Launchpad or by sending an updated mailman.po file and or templates directly to me. This will be the last chance to get i18n updates into a release. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.30rc1 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 2

how to disable main mailman-request and mailman list without stopping mailman functionality
by Jelle de Jong 03 Feb '20

03 Feb '20

Hello everybody, I am seeing our mailman(a)lists.company.nl being used to try to spam people and receiving mail delivery failures from mailman-request(a)lists.company.nl attempts. I removed the mailman mailinglist but that ended up disabling mailman and all of the mailinglsit from working. I created the mailman mailinglist again and the spam started again. I looked at the the options but can not find the right ones that might help? PS. I had mailman not advertised by default but some Debian update a while back seem to have made it advertised. I disabled the advertising of the list but the spam keeps coming. Maybe disable advertising by default for the mailman default list? What are the recommended steps? Kind regards, Jelle de Jong

3 5

acceptable_aliases does not seem to work (or more likely I don't understand) V2.1.23
by stinga 01 Feb '20

01 Feb '20

G'day all, I can't seem to get acceptable_aliases to work... (domain names changed to protect the innocent, but all match up) comm(a)lists.lf.me = List email address info(a)lf.me = Google group (google group has one email address which is comm(a)lists.lf.me info(a)lf.me is a member of the mailman list and is set for nomail User another(a)domain.com sends email to info(a)lf.me List receives email and bounces with: List: comm(a)lists.lf.me From: another(a)domain.com Subject: Testing Reason: Post by non-member to a members-only list The above is correct as user another(a)domain.com is not a member of the mailman list In the email header there is To: <info(a)lf.me> I have in acceptable_aliases (tried various things) info(a)lf.me "info(a)lf.me" .*info(a)lf.me.* and require_explicit_destination is yes I believe that should allow email sent to info(a)lf.me to be accepted by the list, maybe I am reading this all wrong? If I am doing this wrong how do I get a google email to send to mailman and be accepted? info(a)lf.me was a real email address and I converted to a group so that all on the list could see it rather than person having to deal with the email. (I could have just forwarded the email in google but I didn;t want to have to deal with the email account that would never be looked at.) -- 'ooroo Stinga...(:)-) --------------------------------------------------- Email: stinga(a)wolf-rock.com o You need only two tools. o ///// A hammer and duct tape. If it /@ `\ /) ~ doesn't move and it should use > (O) X< ~ Fish!! the hammer. If it moves and `\___/' \) ~ shouldn't, use the tape. \\\ ---------------------------------------------------

2 4