Mailman 3 May 2016 - 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

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

changing domains on Mailman implementation
by Keith Seyffarth 20 Sep '18

20 Sep '18

Is there an efficient way to change the domain name that mailman is affiliated with? I have two mailing lists that were created for an organization before that organization had their own domain. At the time the organization was sure they did not want their own domain and would not be getting a domain. Since then, they have chosen to get a domain and set up a web site. I would like to move their mailing lists onto their domain. It looks like the process for this is: 1) get the list of subscribers 2) delete the mailing list from the one domain (losing the archives) 3) create the mailing list on the new domain 4) subscribe the list of subscribers This process doesn't seem too difficult, but I would prefer to keep the archives, if possible. Both domains are on the same server, running CentOS7 and PLESK 12.5, if that makes a difference. Thanks, Keith

2 2

Getting Yahoo to accept Mailman list messages
by Christian F Buser 28 May '16

28 May '16

Hi all I got an error message below from Yahoo: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > xxxxxxxxx(a)yahoo.com > host mta7.am0.yahoodns.net [63.250.192.46] > SMTP error from remote mail server after end of data: > 554 5.7.9 Message not accepted for policy reasons. See > https://help.yahoo.com/kb/postmaster/SLN7253.html > xxxxxxxxxxxxx(a)yahoo.com > host mta7.am0.yahoodns.net [63.250.192.46] > SMTP error from remote mail server after end of data: > 554 5.7.9 Message not accepted for policy reasons. See > https://help.yahoo.com/kb/postmaster/SLN7253.html I asked the provider and here is his answer (which does not help me too much since I have not sufficient knowledge about these techniques): > Hi Christian, > > The messages were rejected because they weren't properly > authenticated. By default, all outgoing messages from xxxx.ch are DKIM > and SPF authenticated. Not sure about the mailing list messages, > though. Perhaps the Mailman needs authentication on its own. This is a cPanel (56.0.21) installation of Mailman 2.1.20. I have looked into the list settings but did not find anything about DKIM or SPF, and I also did not really understand the explanations in <https://wiki.list.org/DEV/DKIM>. And also, I did not find any settings for DKIM or SPF in the list administration pages. Any ideas are most welcome! Thank you, Christian -- Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org

2 2

Remove someone from list of lists but not from child lists?
by Ryan Stasel 28 May '16

28 May '16

All, Just a quick question that I’m sure the answer is “not possible”. I have several lists that are subsets of users (faculty, staff, etc). Then we have a list of lists called “everyone”. But that “everyone” list gets abused by members sending out crap that people really don’t care to see. So, I’ve had some requests to remove people from “everyone” but obviously keep them in their respective “child list”. Is this possible? The everyone list is set up with the child lists being members, then also setting regular_include_lists so that people that are part of multiple child lists don’t get duplicates. btw, running mailman 2.1.14. Thanks! -Ryan Stasel

3 8

per-list email at munging?
by Karl Berry 25 May '16

25 May '16

I just set up some mailman lists for commit archives. I'd like to avoid the "@" -> " at " munging for them (at least in the bodies, though also in the headers is fine/expected), while retaining that minimal munging for the other lists on the server. Looking at HyperArch.py (and Defaults.py), it seems ARCHIVER_OBSCURES_EMAILADDRS is server-wide. Any viable way to make it per-list? I couldn't find anything in web searches or at http://fog.ccsf.cc.ca.us/~msapiro/scripts/ but always easy to miss stuff. It's not so much that I myself think the " at " munging is so wonderfully effective at antispam, but I feel sure that if I turn it off now, my users will complain vociferously and constantly. Such is life. Thanks, Karl P.S. It seems the original author (Richard Barrett) offered to make it per-list back in 2003 but no one asked for it :). https://sourceforge.net/p/mailman/patches/273/

2 1

Mm_cfg.py not setting attribute
by Beu, Ed (DOA) 24 May '16

24 May '16

Hi, We currently have two instances of Mailman running for test purposes. The newlist command along with a customized mm_cfg.py file is producing different results on the two systems. Configurations are as follows on these two test systems. T1 Solaris 10 Mailman 2.1.20 (csw package) T2 CentOS 6.7 (Final) Mailman 2.1.12 (yum package) On the T1 system I am adding the following statement to the mm_cfg.py file: DEFAULT_RESPOND_TO_POST_REQUESTS = No Then, when I run "./newlist -q listname my.email(a)domain.com<mailto:my.email@domain.com> 12345678" the list setting is as desired (respond_to_post_request = No). On the T2 system using the same scenario above, the "respond_to_post_request" attribute does not change from the Defaults.py setting of Yes. On the T2 system I have tried changing the attribute from DEFAULT_RESPOND_TO_POST_REQUESTS to just RESPOND_TO_POST_REQUESTS, changed No to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A number of combinations, and none work on the CentOS machine. Do you have any suggestions or recommendations? Our goal is to use the CentOS system for production, so getting this worked out will be very helpful. Thx, Ed Ed Beu , Systems Programmer Enterprise Technology Services Department of Administration 619 E Shipcreek Ave., Ste 232 Anchorage, AK 99501-1677 [ETSLogo]---------------------------------------- *Desk:(907)269-6790 ?Fax: (907)269-6719 * ed.beu(a)alaska.gov<mailto:ed.beu@alaska.gov> " http://www.doa.alaska.gov/ets/ ----------------------------------------

2 3

Mailman suddenly passing through spam from the -bounces addresses
by Rusty Newton 23 May '16

23 May '16

Hi! New to the list! I'm the community support manager at the Asterisk project. We've used mailman for ages and we are on 2.1.14 at the moment. I rarely get too deep with mailman other than the administration interface. It mostly works and we don't touch much underneath. Recently I started receiving a lot of spam on the mailman-bounces@ addresses where the From address no longer contains the mailman-bounces@ address and instead contains the spammer's address. In this case the spam doesn't look like bounce traffic. I'm wondering if someone can help me identify why mailman might let it through? From reading documentation and the mailman mail archives I get the impression that it should be discarding this traffic. However I can't identify why it isn't discarding this non-bounce traffic. Here is one example of the spam that comes to the owners addresses via mailman-bounces: http://pastebin.com/u2HyNLw6 The list in question has all three bounce notification options set to *no*. That is: bounce_unrecognized_goes_to_list_owner bounce_notify_owner_on_disable bounce_notify_owner_on_removal With these three options disabled - should I expect mailman to relay spam like this to the list owners through mailman-bounces@ ? Is there a way to tell mailman to not send anything from mailman-bounces? Preferably I'd like to have mailman only pass through legitimate bounce messages. If that isn't possible then I'd like to find out how to disable the traffic from mailman-bounces completely. If I haven't provided enough information, let me know and I'll do my best to get it for you. Thanks in advance. -- Rusty Newton

2 1

accept_these_nonmembers and Reg Expression
by Franck Aerts 23 May '16

23 May '16

Hello everyone, I am sorry to bother you with this question, but even though the question has been asked on this list and a answer has been gaven, it doesn’t work for me. I want any email coming from a particular domain to be accepted without moderation. I added a regular expression to accept_these_nonmembers which goes : ^…(a)domain\.com$ and ^.*(a)asana\.com$ but with no success : the emails are still moderated. Is there an option I should change somewhere that overrule the settings in « accept_these_nonmembers » ?? The reason i want to have to accept any email from that domain is that the « user » part of the email is a token that changes all the time. Thanks in advance, Franck

2 1

Mailman-Users May 2016