Mailman-Users

mailman-users@python.org

9 participants
33806 discussions

by Mark Dale

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

1 day, 18 hours

Moderators and admins not getting notifications of held posts

by Bruce Johnson

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 days, 2 hours

Mailman 2.1 security release

by Mark Sapiro

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

2 days, 3 hours

Mailman3 default list types

by bob.bader＠cchmc.org

So my mailman3 environment is up (in docker) and I am testing and learning but had a question What do the default styles do? "Announce only" - sets the option of "allow_list_posts" to "false" and has public archives enabled. However I created a test list and I sent a post to it (as a user on the list) and it went through. I was not expecting this So what does "allow_list_posts" do? "Ordinary discussion" -basically just has public archives enables. 'Discussion with private archives" of course has private archives enables. Is there a chart that explains the differences between these styles?

6 days, 11 hours

Change email host name via withlist?

by Bruce Johnson

due to changes in our mail infrastructure I need to make sure all lists are set to our mail exchanger host name; is this changeable via a wishlist script? host_name (general): Host name this list prefers for email. The "host_name" is the preferred name for email to mailman-related addresses on this host, and generally should be the mail host's exchanger address, if any. This setting can be useful for selecting among alternative names of a host that has multiple addresses. -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs

6 days, 19 hours

Viewing bounces from Mailman-generated messages?

by Jayson Smith

Hi, Here's the situation, MM 2.1.26. Last night I received an Email from a list member. She's trying to change her Email address, and isn't receiving the confirmation request message at her new address. At that point I didn't know her new address so couldn't check logs. I told her to try subscribing with the new address instead, and to give me her new address. This morning she said she'd do that. Now that I have her new Email address, I can check my server logs and…the confirmation request is being rejected by her incoming SMTP server with a "Service Unavailable" error. However, since Sendmail logs don't actually show the full rejection message, that's all I know, and it's not enough to go on. I know the bounce report would contain the entire rejection message, but at this point I don't have access to that since it went to listname-bounces and Mailman happily gobbled it up, then did nothing with it. I ended up having to temporarily change the listname-bounces alias to point to a real account on the server, then try to subscribe her again, in order to see the bounce. Turns out her ISP thinks Mailman request messages are spam and is rejecting them. Of course I put the alias back like it was. My question is, is there a more eloquent way to see or get a log of the actual bounce in a situation like this in order to see the entire error text as opposed to just "Service Unavailable" or similar? Thanks, Jayson

1 week, 3 days

Configuration for lists subscribed to other lists?

by McGuire, Tommy M. (MSFC-IS90)[EAST2]

Suppose you have two lists: source(a)example.com and destination(a)example.com and that you want destination to be subscribed to source. In addition to making destination a member of source (so source sends email to destination), what do you need to put as a non-member in destination? Should it be 'source(a)example.com' or 'source-bounces(a)example.com'? Email that source sends out has a from address of "source-bounces@..." but is the "-bounces" stripped off before the moderation processing? Yes, I'm trying to figure out why one particular sub-list isn't getting email. Thanks! Tommy M. McGuire Tommy.M.McGuire(a)nasa.gov

2 weeks, 1 day

Strange error with Mailman

by Odhiambo Washington

When I try to access the web UI, I get this strange error: [Fri Oct 01 21:39:52.732148 2021] [cgi:error] [pid 7164] [client 197.232.81.246:1025] AH01215: File "/usr/local/mailman2/scripts/driver", line 112: /usr/local/mailman2/cgi-bin/admin [Fri Oct 01 21:39:52.732207 2021] [cgi:error] [pid 7164] [client 197.232.81.246:1025] AH01215: print 'Status: 405 Method not allowed': /usr/local/mailman2/cgi-bin/admin [Fri Oct 01 21:39:52.732217 2021] [cgi:error] [pid 7164] [client 197.232.81.246:1025] AH01215: ^: /usr/local/mailman2/cgi-bin/admin [Fri Oct 01 21:39:52.732269 2021] [cgi:error] [pid 7164] [client 197.232.81.246:1025] AH01215: SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Status: 405 Method not allowed')?: /usr/local/mailman2/cgi-bin/admin [Fri Oct 01 21:39:52.733570 2021] [cgi:error] [pid 7164] [client 197.232.81.246:1025] End of script output before headers: admin I am a bit perplexed. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

2 weeks, 6 days

How to Hide List from Public 100%

by Darth Vader

Hello, I created a brand new mailman list on dreamhost. The list is supposed to be private and not visible online or to the public at all. Currently there are general list info pages, archives, etc. This is what I need: testlist(a)example.org <mailto:testlist@example.org> When one of the members emails that list, their email gets sent to all the members (obviously). Members cannot see names/email addresses of any members. When they reply to a message, the reply goes to the sender. I as the admin can only add/remove members. There is not supposed to be a web interface for any members. Nobody can change any of their own settings. No messages get posted publicly at all. No one on the internet can view them - the only way to see them is logged in as admin or in the member’s email inboxes. Once again, no propagation/archives/news etc. at all anywhere else. The goal for this is to be a simple private communications list between members (less than 40). I am new to mailman so I would really appreciate anyone’s help with this. Thank you D.V.

3 weeks, 3 days

Re: Can not delete a mailing list with error.

by Mark Sapiro

Please keep this thread on the list. On 9/21/21 6:36 PM, Masaharu Kawada wrote: > Hello Mark, > > Thanks again for your help. > > >What does `ls -la` on Mailman's data/ directory show and what is the > >content of Mailman's data/aliases file? > > The /var/lib/mailman/data only shows the following file. > > ]# ls -l /var/lib/mailman/data > lrwxrwxrwx 1 root mailman 25 Sep 30 2020 sitelist.cfg -> > /etc/mailman/sitelist.cfg > > As for the aliases, please take a look at below results. > > ]# ls -l /etc/mailman/aliases > -rw-rw-rw- 1 root mailman 2840 Sep 21 12:41 /etc/mailman/aliases Not the issue, but this probably shouldn't be other writable. > ]# cat /etc/mailman/aliases > > ~~~~~ > # The ultimate loop stopper address > mailman-loop: /var/lib/mailman/data/owner-bounces.mbox ... If this is a RHEL mailman package, please see <https://wiki.list.org/x/12812344> As far as I know, in the RHEL package, Mailman's aliases are in /etc/mailman/ as you show. I think the problem may be that the `mailman` group does not have write permission on /etc/mailman/. Permissions should be `drwxrwsr-x` and group mailman. Try running Mailman's bin/check_perms to check and `bin/check_perms -f` as root to fix errors, but don't worry about symlinks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 weeks

Jump to page: