From daniel-franca at ufscar.br Fri Sep 2 07:47:00 2016 From: daniel-franca at ufscar.br (Daniel Ettore) Date: Fri, 2 Sep 2016 08:47:00 -0300 Subject: [Mailman-Users] Clear list except 10 emails Message-ID: <6f1b9443-346c-18ca-a618-02f19df95a3e@ufscar.br> Hello. I need help to remove all users from a list , except 10 emails . remove_members -a LIST removes all and could not find an alternative. Suggestions ? Thank you Daniel From mark at msapiro.net Fri Sep 2 11:47:34 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 2 Sep 2016 08:47:34 -0700 Subject: [Mailman-Users] Clear list except 10 emails In-Reply-To: <6f1b9443-346c-18ca-a618-02f19df95a3e@ufscar.br> References: <6f1b9443-346c-18ca-a618-02f19df95a3e@ufscar.br> Message-ID: <387f2333-2c1b-8979-5990-a825612be7e5@msapiro.net> On 09/02/2016 04:47 AM, Daniel Ettore via Mailman-Users wrote: > Hello. I need help to remove all users from a list , except 10 emails . > remove_members -a LIST removes all and could not find an alternative. > Suggestions ? Thank you Daniel Put the 10 member addresses in a file and use it as input to sync_members. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Fri Sep 2 11:59:24 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Fri, 2 Sep 2016 11:59:24 -0400 Subject: [Mailman-Users] digest frequency control Message-ID: I think I understand this but I'm hoping someone can help confirm I got it right. 1. In the regular digest options, directly controlling the frequency with which a digest gets sent out isn't possible. It can sort of be hacked, though, by turning off digest_send_periodic and turning on digest_size_threshold. I.e., you can cause the digest not to go too frequently by setting a size threshold that's higher than what you get in a day or a week. [Note: Clearly it wouldn't be exact, but this list only accepts moderated postings, so we can also control when postings are allowed and when we hit the KB threshold, that way.] 2. In order to actually control digest frequency directly, you'd have to reduce the frequency with which cron/anacron runs senddigests. 3. But that will affect all your lists, so you have to use --listname to do it one list at a time. Since there's nothing like --exceptlistname, I guess I'd need to have a separate entry for senddigests in cron for every list that supports digests. Do I have that all correct? Thanks! Matt From minxmertzmomo at gmail.com Fri Sep 2 12:38:49 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Fri, 2 Sep 2016 12:38:49 -0400 Subject: [Mailman-Users] Digest formatting--clickable TOC? Message-ID: One of the lists I'm now running uses Mailman as an aid to generating a periodical email publication. People send in items for topics, and an editor grafts them into a single large message that goes out about twice a month. The eventual publication looks a lot like a mailman digest, and that's what I'm switching it to. The single-most user-requested improvement to this publication is that they want clickable links in the Table of Contents that anchor down to the entries in the list. I understand that mailman can do digests as a series of MIME attachments to the TOC email, one for each posting. I don't think that's going to work for this crowd, although I'm not sure. And I understand that not all email clients support anchors in html-formatted messages. But has anybody done something like this (where a digest's TOC is clickable and links down to the contents)? Are there other options I'm not thinking about? Thanks, Matt From luscheina at yahoo.de Fri Sep 2 14:40:51 2016 From: luscheina at yahoo.de (Christian F Buser) Date: Fri, 2 Sep 2016 20:40:51 +0200 Subject: [Mailman-Users] List is displaying subscriber in header Message-ID: <20160902204051135874.b283ade6@yahoo.de> Hi all A list (Mailman 2.1.21 on cPanel installation) is behaving strangely. In the header of a list message, there appears an "Envelope-To:" header line, which contains 200 (of the approximately 1000) subscribers. I did not find any setting which could be wront, and I think this behaviour is new to that list. But as far as I remember, I did not change anything recently. What is wrong here? Thank you, Christian -- Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org From mark at msapiro.net Fri Sep 2 14:56:52 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 2 Sep 2016 11:56:52 -0700 Subject: [Mailman-Users] digest frequency control In-Reply-To: References: Message-ID: <4396f9d1-75f1-5511-b603-144e54535fa8@msapiro.net> On 09/02/2016 08:59 AM, Matt Morgan wrote: > I think I understand this but I'm hoping someone can help confirm I got it > right. > ... > > Do I have that all correct? Yes. Also, note that the --listname option to senddigests may be repeated to do multiple named lists. You could implement a --exceptlistname option in cron/senddigests. It wouldn't be hard. A patch is attached. I like it so much it will be in 2.1.24 . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: senddigests.patch Type: text/x-diff Size: 1458 bytes Desc: not available URL: From mark at msapiro.net Fri Sep 2 15:13:09 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 2 Sep 2016 12:13:09 -0700 Subject: [Mailman-Users] List is displaying subscriber in header In-Reply-To: <20160902204051135874.b283ade6@yahoo.de> References: <20160902204051135874.b283ade6@yahoo.de> Message-ID: <37164be5-ff39-1b62-5432-6d47b95afdce@msapiro.net> On 09/02/2016 11:40 AM, Christian F Buser via Mailman-Users wrote: > > A list (Mailman 2.1.21 on cPanel installation) is behaving strangely. In the header of a list message, there appears an "Envelope-To:" header line, which contains 200 (of the approximately 1000) subscribers. > > I did not find any setting which could be wront, and I think this behaviour is new to that list. But as far as I remember, I did not change anything recently. Your MTA is adding this header containing all the recipients in the particular SMTP transaction that delivered this message from Mailman to the MTA. You need access to the installation to do anything about this. If this is a hosted Mailman, you'll have to deal with the host. There are two ways to fix this. 1) fix the MTA, probably exim in cPanel, . 2) change Mailman to send only one recipient per transaction. This can be accomplished in multiple ways: a) If personalize is available in Non-Digest options, set it to Yes. b) add VERP_DELIVERY_INTERVAL = 1 to mm_cfg.py c) add SMTP_MAX_RCPTS = 1 to mm_cfg.py (I recommend b) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Fri Sep 2 17:00:38 2016 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Fri, 2 Sep 2016 21:00:38 +0000 Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: Hi, I requested a similar feature a while ago: https://mail.python.org/pipermail/mailman-users/2014-December/078192.html I am still asked for this feature quite often. Andrew. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+andrew=hodgsonfamily.org at python.org] On Behalf Of Matt Morgan Sent: 02 September 2016 17:39 To: Mailman-Users at python.org Subject: [Mailman-Users] Digest formatting--clickable TOC? One of the lists I'm now running uses Mailman as an aid to generating a periodical email publication. People send in items for topics, and an editor grafts them into a single large message that goes out about twice a month. The eventual publication looks a lot like a mailman digest, and that's what I'm switching it to. The single-most user-requested improvement to this publication is that they want clickable links in the Table of Contents that anchor down to the entries in the list. I understand that mailman can do digests as a series of MIME attachments to the TOC email, one for each posting. I don't think that's going to work for this crowd, although I'm not sure. And I understand that not all email clients support anchors in html-formatted messages. But has anybody done something like this (where a digest's TOC is clickable and links down to the contents)? Are there other options I'm not thinking about? Thanks, Matt ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/andrew%40hodgsonfamily.org From mark at msapiro.net Fri Sep 2 18:39:38 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 2 Sep 2016 15:39:38 -0700 Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: On 09/02/2016 02:00 PM, Andrew Hodgson wrote: > > I requested a similar feature a while ago: > > https://mail.python.org/pipermail/mailman-users/2014-December/078192.html And my responses at and still hold. Read the whole thread. Note, this is quite doable in Mailman 3 as MM 3 messages contain an Archived-At: header with a link to the archived message (this is not possible to do in Mailman 2.1 for various technical reasons). You mite consider submitting a feature request for this at . This is still tricky for 'plain' digests as by definition they don't contain html and things like lists.mailman3.org web site. (Mark Sapiro) render like that and not as an active lists.mailman3.org web site. (Mark Sapiro) link. and things like lists.mailman3.org web site. (Mark Sapiro) look ugly even if the MUA renders the URL as an active link. OTOH, in a MIME format digest, the TOC could be a text/html part which would work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From raj at mischievous.us Fri Sep 2 21:48:43 2016 From: raj at mischievous.us (Richard Johnson) Date: Fri, 2 Sep 2016 18:48:43 -0700 Subject: [Mailman-Users] Why do some get digests as a series of attachments? Message-ID: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> This is strange. One of my list users gets digest messages as a series of attachments, while all other users receive digests as all text, with the messages one after the other. The person who gets the attachments has a Cox.net address. Maybe they're doing something to it? /raj (sent from iPhone) From cpz at tuunq.com Fri Sep 2 22:36:37 2016 From: cpz at tuunq.com (Carl Zwanzig) Date: Fri, 2 Sep 2016 19:36:37 -0700 Subject: [Mailman-Users] Why do some get digests as a series of attachments? In-Reply-To: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> References: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> Message-ID: <58a7f5fc-6012-05e9-7e5e-c72f0986563b@tuunq.com> On 9/2/2016 6:48 PM, Richard Johnson wrote: > This is strange. One of my list users gets digest messages as a series > of attachments, while all other users receive digests as all text, with > the messages one after the other. > > The person who gets the attachments has a Cox.net address. Maybe they're > doing something to it? Almost anything in the handling chain can mess with the format. Could be that cox.net's web email doesn't understand digest format, but if the user is reading email via imap from cox it would be OK. I think you need to look closer at how people are getting & reading their email. z! From mark at msapiro.net Fri Sep 2 22:45:39 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 2 Sep 2016 19:45:39 -0700 Subject: [Mailman-Users] Why do some get digests as a series of attachments? In-Reply-To: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> References: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> Message-ID: <17c09c54-fb70-21d6-e51e-85a057bac629@msapiro.net> On 09/02/2016 06:48 PM, Richard Johnson wrote: > This is strange. One of my list users gets digest messages as a series of attachments, while all other users receive digests as all text, with the messages one after the other. > > The person who gets the attachments has a Cox.net address. Maybe they're doing something to it? That has nothing to do with it. There are two digest formats. Plain text is a digest with all non-plain text parts stored aside and replaced by links and flattened into a single plain text message. MIME format is a multipart digest with each original message in its own sub-part. Your user who gets 'attachments' has elected to receive MIME digests. You can see this on the user's options page or the admin membership list pages. Whether a MIME digest is rendered with the message parts inline, only as attachments or not at all is a function of the mail client reading the message. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Sat Sep 3 01:49:26 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Sat, 3 Sep 2016 01:49:26 -0400 Subject: [Mailman-Users] digest frequency control In-Reply-To: <4396f9d1-75f1-5511-b603-144e54535fa8@msapiro.net> References: <4396f9d1-75f1-5511-b603-144e54535fa8@msapiro.net> Message-ID: On Fri, Sep 2, 2016 at 2:56 PM, Mark Sapiro wrote: > On 09/02/2016 08:59 AM, Matt Morgan wrote: > > I think I understand this but I'm hoping someone can help confirm I got > it > > right. > > > ... > > > > Do I have that all correct? > > > Yes. > > Also, note that the --listname option to senddigests may be repeated to > do multiple named lists. > > You could implement a --exceptlistname option in cron/senddigests. It > wouldn't be hard. A patch is attached. I like it so much it will be in > 2.1.24 . > Fantastic! Thanks. From raj at mischievous.us Sat Sep 3 02:23:36 2016 From: raj at mischievous.us (Richard Johnson) Date: Fri, 2 Sep 2016 23:23:36 -0700 Subject: [Mailman-Users] Why do some get digests as a series of attachments? In-Reply-To: <17c09c54-fb70-21d6-e51e-85a057bac629@msapiro.net> References: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> <17c09c54-fb70-21d6-e51e-85a057bac629@msapiro.net> Message-ID: Actually, my list is setup to send all digests in text format. I was toying with the idea of sending in MIME format. Maybe that would be better? But it sounds as if you're saying that a user can specify that they want MIME instead of there configured version, somewhere in their personal config? /raj (sent from iPhone) > On Sep 2, 2016, at 7:45 PM, Mark Sapiro wrote: > >> On 09/02/2016 06:48 PM, Richard Johnson wrote: >> This is strange. One of my list users gets digest messages as a series of attachments, while all other users receive digests as all text, with the messages one after the other. >> >> The person who gets the attachments has a Cox.net address. Maybe they're doing something to it? > > > That has nothing to do with it. There are two digest formats. > > Plain text is a digest with all non-plain text parts stored aside and > replaced by links and flattened into a single plain text message. > > MIME format is a multipart digest with each original message in its own > sub-part. > > Your user who gets 'attachments' has elected to receive MIME digests. > You can see this on the user's options page or the admin membership list > pages. > > Whether a MIME digest is rendered with the message parts inline, only as > attachments or not at all is a function of the mail client reading the > message. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/raj%40mischievous.us From mark at msapiro.net Sat Sep 3 02:50:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 2 Sep 2016 23:50:53 -0700 Subject: [Mailman-Users] Why do some get digests as a series of attachments? In-Reply-To: References: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> <17c09c54-fb70-21d6-e51e-85a057bac629@msapiro.net> Message-ID: <6b4d1404-6122-5103-bb82-500460d5bcbf@msapiro.net> On 09/02/2016 11:23 PM, Richard Johnson wrote: > Actually, my list is setup to send all digests in text format. I was toying with the idea of sending in MIME format. Maybe that would be better? I assume you mean that Digest options -> mime_is_default_digest is set to Plain, but that only sets the default for new subscribers. It's a user option and any user can change her setting. Also, if you change it to MIME, that only affects people who subscribe after the change. It doesn't change any current members. > But it sounds as if you're saying that a user can specify that they want MIME instead of there configured version, somewhere in their personal config? Yes. The user can set it on her options page - "Get MIME or Plain Text Digests?" and the admin can set it for a user with the 'plain' checkbox on the Membership Management... -> Membership List pages (unchecked = MIME) I think MIME digests are better. They have several advantages IF (and it's upper case IF on purpose) the user's mail client deals well with the format. Mobile phone apps as a class are generally quite bad at dealing with MIME digests as are some web mail apps. Each user needs to decide for herself which is preferred based on the client(s) she uses. Personally, I set digest mode to MIME on those few lists I subscribe to in digest form, and I just don't try to read them on my phone or just read the TOC and maybe delete the digest as uninteresting. If I want to read and possibly reply to a message in the digest, I use a real MUA on a real computer. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rb211 at tds.net Sat Sep 3 05:10:34 2016 From: rb211 at tds.net (William Bagwell) Date: Sat, 3 Sep 2016 05:10:34 -0400 Subject: [Mailman-Users] Why do some get digests as a series of attachments? In-Reply-To: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> References: <5CCBCDAC-E355-4042-A5AE-2467D2F53F9F@mischievous.us> Message-ID: <201609030510.34618.rb211@tds.net> On Friday 02 September 2016, Richard Johnson wrote: > This is strange. One of my list users gets digest messages as a series of > attachments, while all other users receive digests as all text, with the > messages one after the other. > > The person who gets the attachments has a Cox.net address. Maybe they're > doing something to it? Remote possibility is the users mail reader is bursting digests back to individual messages. These will have minimal headers, look different and might be mistaken for attachments. Forte Agent defaults to this behavior. -- William From acunha at iff.edu.br Fri Sep 2 16:45:24 2016 From: acunha at iff.edu.br (Andre de Azevedo Cunha) Date: Fri, 02 Sep 2016 17:45:24 -0300 Subject: [Mailman-Users] Automate Moderator Functions Message-ID: 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 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 From ed.beu at alaska.gov Fri Sep 2 18:31:12 2016 From: ed.beu at alaska.gov (Beu, Ed (DOA)) Date: Fri, 2 Sep 2016 22:31:12 +0000 Subject: [Mailman-Users] Some lists no longer archiving new messages Message-ID: <77788B6418FB6E4CB10D483D7DAC164C01142799D4@SOAANCEXMB9.soa.alaska.gov> Hi, The few lists that I have 'imported' mail from Thunderbird into Mailman archives will not archive new messages. I have imported all the messages again, and I have imported one message at a time - then I've run the following command: /bin/arch -wipe listname I've have also run: bin/arch listname /var/lib/mailman/archives/private/listname.mbox/listname.mbox After doing so, new messages sent to the list are not archived and do not show up in the mbox file. We're running Mailman v2.1.12 on Centos 6.7 and using Postfix 2.6.6.. Thanks in advance for any assistance! ~Ed Ed Beu , Systems Programmer Enterprise Technology Services Department of Administration [ETSLogo]---------------------------------------- *Desk:(907)269-6790 ?Fax: (907)269-6719 * ed.beu at alaska.gov " http://www.doa.alaska.gov/ets/ ---------------------------------------- From mark at msapiro.net Sat Sep 3 11:44:06 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 3 Sep 2016 08:44:06 -0700 Subject: [Mailman-Users] Some lists no longer archiving new messages In-Reply-To: <77788B6418FB6E4CB10D483D7DAC164C01142799D4@SOAANCEXMB9.soa.alaska.gov> References: <77788B6418FB6E4CB10D483D7DAC164C01142799D4@SOAANCEXMB9.soa.alaska.gov> Message-ID: On 09/02/2016 03:31 PM, Beu, Ed (DOA) wrote: > > The few lists that I have 'imported' mail from Thunderbird into Mailman archives will not archive new messages. I suspect a permissions issue on archives/private/LIST.mbox/LIST.mbox, but there should be errors and tracebacks in mailman's error log and shunted messages in the shunt queue. If you have the RedHat package, these are /var/log/mailman/error and /var/spool/mailman/shunt respectively. If you can't figure out what the problem is from the error log, post the info here. Once you have fixed the problem you can run unshunt (/usr/lib/mailman/bin/unshunt) to archive the shunted messages, but first you may want to examine them with /usr/lib/mailman/bin/show_qfiles to ensure that all of them should be unshunted and there are none from older, unrelated errors. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From beta at admilon.net Sat Sep 3 11:48:47 2016 From: beta at admilon.net (Matthias Schmidt) Date: Sun, 4 Sep 2016 00:48:47 +0900 Subject: [Mailman-Users] Update mailman MacServer5 Message-ID: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> Hello, I?ve been updating a MacOS10.6 Server to Server 5 (elCapitan). Mailman is not shipped anymore with the current version. So I downloaded 2.1.23, installed the lat version of phyton as well as dnsphyton. Then I copied the old mailman folders over to /usr/local/mailman and /var/mailman Then I ran configure and the installation went through. but when I try to start mailman I get this error: File "/usr/local/mailman/bin/mailmanctl", line 106, in from Mailman import mm_cfg ImportError: No module named Mailman All what I found on google is more about Linux installations ? So I guess I?m missing something here. Thanks for help Matthias -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From mark at msapiro.net Sat Sep 3 12:00:43 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 3 Sep 2016 09:00:43 -0700 Subject: [Mailman-Users] Automate Moderator Functions In-Reply-To: References: Message-ID: On 09/02/2016 01:45 PM, Andre de Azevedo Cunha wrote: > > 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? Logging for rejected messages was added in 2.1.16. See . Prior to that, there won't be a vette log entry. I don't know why there isn't a notice to the user. Is there anything in Mailman's error log? As a test, add some nonmember address to the list's reject_these_nonmembers and send a post from that address. Does that receive a rejection notice? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Sep 3 12:10:41 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 3 Sep 2016 09:10:41 -0700 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> Message-ID: On 09/03/2016 08:48 AM, Matthias Schmidt via Mailman-Users wrote: > > I?ve been updating a MacOS10.6 Server to Server 5 (elCapitan). > Mailman is not shipped anymore with the current version. > So I downloaded 2.1.23, installed the lat version of phyton as well as dnsphyton. > Then I copied the old mailman folders over to /usr/local/mailman and /var/mailman > Then I ran configure and the installation went through. > but when I try to start mailman I get this error: > File "/usr/local/mailman/bin/mailmanctl", line 106, in > from Mailman import mm_cfg > ImportError: No module named Mailman It would appear that there is some confusion, probably due to the '--prefix' and '--with-var-prefix' you configured with not being correct. It looks like they should be --prefix=/usr/local/mailman --with-var-prefix=/var/mailman. What's in /usr/local/mailman/bin/paths.py for 'prefix =' and is there a Mailman directory and a Mailman/__init__.py file in that directory? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mailinglist at samsi.us Sat Sep 3 14:07:26 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Sat, 3 Sep 2016 11:07:26 -0700 Subject: [Mailman-Users] Strange error log entries? Message-ID: <0418C8D6-35D2-49CA-9DD1-D15401225B98@samsi.us> Hi there, I see the following entries in errors log file: Aug 29 22:38:29 2016 (31253) confirm: No such list "seattlegigs"": Aug 31 03:51:19 2016 (15369) admin: No such list "images": Sep 01 12:11:59 2016 (1420) confirm: No such list "seattlegigs"": Sep 03 07:47:55 2016 (26274) admin: No such list "images?: Where is it coming from? and how can I fix them? version 2.1.23 Thanks, Caesar. From mark at msapiro.net Sat Sep 3 14:23:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 3 Sep 2016 11:23:40 -0700 Subject: [Mailman-Users] Strange error log entries? In-Reply-To: <0418C8D6-35D2-49CA-9DD1-D15401225B98@samsi.us> References: <0418C8D6-35D2-49CA-9DD1-D15401225B98@samsi.us> Message-ID: <8bb7fef6-6311-1e33-189f-09693d50842a@msapiro.net> On 09/03/2016 11:07 AM, Caesar Samsi wrote: > > I see the following entries in errors log file: > > Aug 29 22:38:29 2016 (31253) confirm: No such list "seattlegigs"": > Aug 31 03:51:19 2016 (15369) admin: No such list "images": > > Sep 01 12:11:59 2016 (1420) confirm: No such list "seattlegigs"": > Sep 03 07:47:55 2016 (26274) admin: No such list "images?: > > Where is it coming from? and how can I fix them? It's coming from the world wide web. Anyone in the world can go to a url like http://your.list.domain/mailman/admin/images or http://your.list.domain/mailman/confirm/seattlegigs" and produce those messages. Since they repeat with the same list names, it's probably some web crawler. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From beta at admilon.net Sat Sep 3 21:29:42 2016 From: beta at admilon.net (Matthias Schmidt) Date: Sun, 4 Sep 2016 10:29:42 +0900 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> Message-ID: <0953AB41-C960-45EA-9CC1-E906E3E0504B@admilon.net> Mark, thanks. > Am 04.09.2016 um 01:10 schrieb Mark Sapiro : > > On 09/03/2016 08:48 AM, Matthias Schmidt via Mailman-Users wrote: >> >> I?ve been updating a MacOS10.6 Server to Server 5 (elCapitan). >> Mailman is not shipped anymore with the current version. >> So I downloaded 2.1.23, installed the lat version of phyton as well as dnsphyton. >> Then I copied the old mailman folders over to /usr/local/mailman and /var/mailman >> Then I ran configure and the installation went through. >> but when I try to start mailman I get this error: >> File "/usr/local/mailman/bin/mailmanctl", line 106, in >> from Mailman import mm_cfg >> ImportError: No module named Mailman > > > It would appear that there is some confusion, probably due to the > '--prefix' and '--with-var-prefix' you configured with not being > correct. It looks like they should be --prefix=/usr/local/mailman > ?with-var-prefix=/var/mailman. I ran configure again like this: mailman-2.1.23/configure --prefix=/usr/local/mailman --with-var-prefix=/var/mailman > > What?s in /usr/local/mailman/bin/paths.py for 'prefix =' and is there a ah: the old path to the 10.6 installation prefix = ?/usr/share/mailman' and it should be prefix:?/usr/local/mailman? > Mailman directory and a Mailman/__init__.py file in that directory? yes seams mailman at least starts after I corrected the prefix, but it?s not yet working. I guess I have to do some more digging into the postfix setup ;-) thanks again Matthias > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/beta%40admilon.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From beta at admilon.net Sun Sep 4 00:53:17 2016 From: beta at admilon.net (Matthias Schmidt) Date: Sun, 4 Sep 2016 13:53:17 +0900 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> Message-ID: Hello, now I?m stuck here: local[74919]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or directory local is owned by postfix so far I found out. What I can?t find is where this line is to be able to correct it (Spotlight also finds nothing) thanks Matthias > Am 04.09.2016 um 01:10 schrieb Mark Sapiro : > > On 09/03/2016 08:48 AM, Matthias Schmidt via Mailman-Users wrote: >> >> I?ve been updating a MacOS10.6 Server to Server 5 (elCapitan). >> Mailman is not shipped anymore with the current version. >> So I downloaded 2.1.23, installed the lat version of phyton as well as dnsphyton. >> Then I copied the old mailman folders over to /usr/local/mailman and /var/mailman >> Then I ran configure and the installation went through. >> but when I try to start mailman I get this error: >> File "/usr/local/mailman/bin/mailmanctl", line 106, in >> from Mailman import mm_cfg >> ImportError: No module named Mailman > > > It would appear that there is some confusion, probably due to the > '--prefix' and '--with-var-prefix' you configured with not being > correct. It looks like they should be --prefix=/usr/local/mailman > --with-var-prefix=/var/mailman. > > What's in /usr/local/mailman/bin/paths.py for 'prefix =' and is there a > Mailman directory and a Mailman/__init__.py file in that directory? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/beta%40admilon.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From mark at msapiro.net Sun Sep 4 01:06:28 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 3 Sep 2016 22:06:28 -0700 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> Message-ID: <34d1a9ad-d09a-45b2-57fb-3e03dee02157@msapiro.net> On 09/03/2016 09:53 PM, Matthias Schmidt wrote: > > now I?m stuck here: > local[74919]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or directory > > local is owned by postfix so far I found out. > What I can?t find is where this line is to be able to correct it (Spotlight also finds nothing) It's in your Postfix aliases for Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From beta at admilon.net Sun Sep 4 04:56:13 2016 From: beta at admilon.net (Matthias Schmidt) Date: Sun, 4 Sep 2016 17:56:13 +0900 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: <34d1a9ad-d09a-45b2-57fb-3e03dee02157@msapiro.net> References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> <34d1a9ad-d09a-45b2-57fb-3e03dee02157@msapiro.net> Message-ID: <141C85CC-8E3B-4695-BF24-D190E5645017@admilon.net> sorry for being such a pain today _/\_ now the webinterface is not coming up. It looks like the cgi is not executed instead a 404 error is generated my mailman.conf for apache looks like that (it?s basically the same as on 10.6, I just changed the path): ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" Alias /pipermail/ "/var/mailman/archives/public/" Options FollowSymLinks MultiViews Indexes AllowOverride None Order allow,deny Allow from all it is included with http.conf for the site I have a redirect: RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$ RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj [L,R=permanent] and that stuff was working on 10.6 the logs say this: [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing access with matching directory. filename = /WebFolder/dinj/mailman [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 127.0.0.1:59199] AH00128: File does not exist: /WebFolder/dinj/mailman/listinfo/dinj /usr/local/mailman/cgi-bin/ has permissions set to 775 thanks again Matthias > Am 04.09.2016 um 14:06 schrieb Mark Sapiro : > > On 09/03/2016 09:53 PM, Matthias Schmidt wrote: >> >> now I?m stuck here: >> local[74919]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or directory >> >> local is owned by postfix so far I found out. >> What I can?t find is where this line is to be able to correct it (Spotlight also finds nothing) > > > It's in your Postfix aliases for Mailman. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From mark at msapiro.net Sun Sep 4 11:53:58 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 4 Sep 2016 08:53:58 -0700 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: <141C85CC-8E3B-4695-BF24-D190E5645017@admilon.net> References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> <34d1a9ad-d09a-45b2-57fb-3e03dee02157@msapiro.net> <141C85CC-8E3B-4695-BF24-D190E5645017@admilon.net> Message-ID: On 09/04/2016 01:56 AM, Matthias Schmidt via Mailman-Users wrote: > sorry for being such a pain today _/\_ > > now the webinterface is not coming up. > It looks like the cgi is not executed instead a 404 error is generated > > my mailman.conf for apache looks like that (it?s basically the same as on 10.6, I just changed the path): > > ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" This is OK, but ... > Alias /pipermail/ "/var/mailman/archives/public/" > > Options FollowSymLinks MultiViews Indexes > AllowOverride None > Order allow,deny > Allow from all > > > it is included with http.conf > > for the site I have a redirect: > RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$ > RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj [L,R=permanent] > and that stuff was working on 10.6 And all that does is redirect 'http(s)://liste.dinj.de/' to 'https://%{SERVER_NAME}/mailman/listinfo/dinj' > the logs say this: > [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing access with matching directory. filename = /WebFolder/dinj/mailman > [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 127.0.0.1:59199] AH00128: File does not exist: /WebFolder/dinj/mailman/listinfo/dinj So why is Apache looking for /WebFolder/dinj/mailman/listinfo/dinj? Is /WebFolder/dinj the DocumentRoot? Does this happen with any mailman URL? If you go to 'https://liste.dinj.de/mailman/admin/dinj' do you get a similar 404 or only if you go to' https://liste.dinj.de/'. Somehow your 'ScriptAlias /mailman/' directive is not effective. In a more or less normal apache configuration it is not sufficient to put mailman.conf in /etc/apache2/conf.d/, you must also have a symlink to it in /etc/apache2/conf-enabled/. I have no idea if this applies to Mac OX X Server, but you need to look at your Include and IncludeOptional directives in the main apache2.conf or whatever it's called to ensure that mailman.conf is directly or indirectly included. > /usr/local/mailman/cgi-bin/ has permissions set to 775 It should be 2775 (drwxrwsr-w) but the important thing is the files therein should be 2755 (-rwxr-sr-x). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From timothy.d at jasionow.ski Sun Sep 4 13:52:25 2016 From: timothy.d at jasionow.ski (Timothy Jasionowski) Date: Sun, 4 Sep 2016 13:52:25 -0400 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> <34d1a9ad-d09a-45b2-57fb-3e03dee02157@msapiro.net> <141C85CC-8E3B-4695-BF24-D190E5645017@admilon.net> Message-ID: <9195AEB2-358C-4FD2-9214-E64C50762EEB@jasionow.ski> I think I may have sent this directly, but... Mattias, I had good luck installing mailman on El Capitan/Server 5 using MacPorts, as it manages all the dependencies and integrates all the chron jobs and startup stuff, but due to some legacy issues with the MacPorts configuration file, the build appends the .cgi prefix in the URI construction. It, otherwise, works fine. It avoided a lot of the issues you had in configuring it and, more importantly, maintaining it. If you want to get rid of the extension, download macports, refresh the build index, then edit the macports mailman build file, replacing: configure.args --with-cgi-ext=.cgi \ --with-cgi-gid=${cgigroup} \ with configure.args --with-cgi-gid=${cgigroup} \ Thanks again to Marius Schamschula for that tip, as it drove me crazy. Timothy Sent from my iPhone > On Sep 4, 2016, at 11:53, Mark Sapiro wrote: > >> On 09/04/2016 01:56 AM, Matthias Schmidt via Mailman-Users wrote: >> sorry for being such a pain today _/\_ >> >> now the webinterface is not coming up. >> It looks like the cgi is not executed instead a 404 error is generated >> >> my mailman.conf for apache looks like that (it?s basically the same as on 10.6, I just changed the path): >> >> ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > This is OK, but ... > > >> Alias /pipermail/ "/var/mailman/archives/public/" >> >> Options FollowSymLinks MultiViews Indexes >> AllowOverride None >> Order allow,deny >> Allow from all >> >> >> it is included with http.conf >> >> for the site I have a redirect: >> RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$ >> RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj [L,R=permanent] >> and that stuff was working on 10.6 > > > And all that does is redirect 'http(s)://liste.dinj.de/' to > 'https://%{SERVER_NAME}/mailman/listinfo/dinj' > > >> the logs say this: >> [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing access with matching directory. filename = /WebFolder/dinj/mailman >> [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 127.0.0.1:59199] AH00128: File does not exist: /WebFolder/dinj/mailman/listinfo/dinj > > > So why is Apache looking for /WebFolder/dinj/mailman/listinfo/dinj? Is > /WebFolder/dinj the DocumentRoot? > > Does this happen with any mailman URL? If you go to > 'https://liste.dinj.de/mailman/admin/dinj' do you get a similar 404 or > only if you go to' https://liste.dinj.de/'. > > Somehow your 'ScriptAlias /mailman/' directive is not effective. In a > more or less normal apache configuration it is not sufficient to put > mailman.conf in /etc/apache2/conf.d/, you must also have a symlink to it > in /etc/apache2/conf-enabled/. I have no idea if this applies to Mac OX > X Server, but you need to look at your Include and IncludeOptional > directives in the main apache2.conf or whatever it's called to ensure > that mailman.conf is directly or indirectly included. > > >> /usr/local/mailman/cgi-bin/ has permissions set to 775 > > > It should be 2775 (drwxrwsr-w) but the important thing is the files > therein should be 2755 (-rwxr-sr-x). > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski From lucio at lambrate.inaf.it Mon Sep 5 04:32:46 2016 From: lucio at lambrate.inaf.it (Lucio Chiappetti) Date: Mon, 5 Sep 2016 10:32:46 +0200 (CEST) Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: On Fri, 2 Sep 2016, Matt Morgan wrote: > The eventual publication looks a lot like a mailman digest, and that's > what I'm switching it to. I see that over the weekend there was some discussion about digests, not only in this thread ! > I understand that mailman can do digests as a series of MIME attachments > to the TOC email, one for each posting. I don't think that's going to > work for this crowd, although I'm not sure. Personally I do use MIME digests (not plain text ones) for almost all the lists I'm subscribed to (actually ALL which allow it). But then my MUA (Alpine) with some customization (including a formail-based shell script) can turn the MIME digests into a temporary mail folder, where I can access each posting as a normal e-mail. And even if I would not have my scripts, I could still natively view the attachment index and access the RFC822 attachment one by one as a normal e-mail. -- ------------------------------------------------------------------------ Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ Do not like Firefox >=29 ? Get Pale Moon ! http://www.palemoon.org From beta at admilon.net Mon Sep 5 08:56:21 2016 From: beta at admilon.net (Matthias Schmidt) Date: Mon, 5 Sep 2016 21:56:21 +0900 Subject: [Mailman-Users] Update mailman MacServer5 In-Reply-To: <9195AEB2-358C-4FD2-9214-E64C50762EEB@jasionow.ski> References: <817450D8-9D0E-43E5-AA5B-7D499C809642@admilon.net> <34d1a9ad-d09a-45b2-57fb-3e03dee02157@msapiro.net> <141C85CC-8E3B-4695-BF24-D190E5645017@admilon.net> <9195AEB2-358C-4FD2-9214-E64C50762EEB@jasionow.ski> Message-ID: <516D9E37-0958-4C46-B816-4DA15EF14C31@admilon.net> Timothy, thanks for the tip, but I do not intend to install MacPorts as I had different experiences with it in the past. Besides that, mailman is now running fine now. The only problem left is that the include of the cgi link of the mailman config is not working with the current Apache setup. I guess it has something to do with the new way Apple handles every website hosted on the box through a proxy and I still need to find out how that works - will do so tomorrow ;-) If you don?t mind, you could post your config for your website hosting your list. thanks Matthias > Am 05.09.2016 um 02:52 schrieb Timothy Jasionowski : > > I think I may have sent this directly, but... > > Mattias, > > I had good luck installing mailman on El Capitan/Server 5 using MacPorts, as it manages all the dependencies and integrates all the chron jobs and startup stuff, but due to some legacy issues with the MacPorts configuration file, the build appends the .cgi prefix in the URI construction. It, otherwise, works fine. It avoided a lot of the issues you had in configuring it and, more importantly, maintaining it. > > If you want to get rid of the extension, download macports, refresh the build index, then edit the macports mailman build file, replacing: > > configure.args --with-cgi-ext=.cgi \ > --with-cgi-gid=${cgigroup} \ > > with > > configure.args --with-cgi-gid=${cgigroup} \ > > Thanks again to Marius Schamschula for that tip, as it drove me crazy. > > Timothy > > Sent from my iPhone > >> On Sep 4, 2016, at 11:53, Mark Sapiro wrote: >> >>> On 09/04/2016 01:56 AM, Matthias Schmidt via Mailman-Users wrote: >>> sorry for being such a pain today _/\_ >>> >>> now the webinterface is not coming up. >>> It looks like the cgi is not executed instead a 404 error is generated >>> >>> my mailman.conf for apache looks like that (it?s basically the same as on 10.6, I just changed the path): >>> >>> ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" >> >> >> This is OK, but ... >> >> >>> Alias /pipermail/ "/var/mailman/archives/public/" >>> >>> Options FollowSymLinks MultiViews Indexes >>> AllowOverride None >>> Order allow,deny >>> Allow from all >>> >>> >>> it is included with http.conf >>> >>> for the site I have a redirect: >>> RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$ >>> RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj [L,R=permanent] >>> and that stuff was working on 10.6 >> >> >> And all that does is redirect 'http(s)://liste.dinj.de/' to >> 'https://%{SERVER_NAME}/mailman/listinfo/dinj' >> >> >>> the logs say this: >>> [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing access with matching directory. filename = /WebFolder/dinj/mailman >>> [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 127.0.0.1:59199] AH00128: File does not exist: /WebFolder/dinj/mailman/listinfo/dinj >> >> >> So why is Apache looking for /WebFolder/dinj/mailman/listinfo/dinj? Is >> /WebFolder/dinj the DocumentRoot? >> >> Does this happen with any mailman URL? If you go to >> 'https://liste.dinj.de/mailman/admin/dinj' do you get a similar 404 or >> only if you go to' https://liste.dinj.de/'. >> >> Somehow your 'ScriptAlias /mailman/' directive is not effective. In a >> more or less normal apache configuration it is not sufficient to put >> mailman.conf in /etc/apache2/conf.d/, you must also have a symlink to it >> in /etc/apache2/conf-enabled/. I have no idea if this applies to Mac OX >> X Server, but you need to look at your Include and IncludeOptional >> directives in the main apache2.conf or whatever it's called to ensure >> that mailman.conf is directly or indirectly included. >> >> >>> /usr/local/mailman/cgi-bin/ has permissions set to 775 >> >> >> It should be 2775 (drwxrwsr-w) but the important thing is the files >> therein should be 2755 (-rwxr-sr-x). >> >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> ------------------------------------------------------ >> Mailman-Users mailing list Mailman-Users at python.org >> https://mail.python.org/mailman/listinfo/mailman-users >> Mailman FAQ: http://wiki.list.org/x/AgA3 >> Security Policy: http://wiki.list.org/x/QIA9 >> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ >> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/beta%40admilon.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From acunha at iff.edu.br Mon Sep 5 10:10:24 2016 From: acunha at iff.edu.br (Andre de Azevedo Cunha) Date: Mon, 05 Sep 2016 11:10:24 -0300 Subject: [Mailman-Users] Automate Moderator Functions In-Reply-To: References: Message-ID: Mark, the important to me is reject emails to the lists bigger then the value set in MAX_MESSAGE_SIZE in the list`s config. The default behavior is moderate this message, what don`t solve me problem. Exist one way to do this? --- Em 03/09/2016 13:00, Mark Sapiro escreveu: > On 09/02/2016 01:45 PM, Andre de Azevedo Cunha wrote: > >> 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? > > Logging for rejected messages was added in 2.1.16. See > . Prior to that, there > won't be a vette log entry. > > I don't know why there isn't a notice to the user. Is there anything in > Mailman's error log? > > As a test, add some nonmember address to the list's > reject_these_nonmembers and send a post from that address. Does that > receive a rejection notice? From mark at msapiro.net Mon Sep 5 11:57:59 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 5 Sep 2016 08:57:59 -0700 Subject: [Mailman-Users] Automate Moderator Functions In-Reply-To: References: Message-ID: <9b270daf-9f63-f2e4-d232-295141670641@msapiro.net> On 09/05/2016 07:10 AM, Andre de Azevedo Cunha wrote: > Mark, > > > the important to me is reject emails to the lists bigger then the value set in > MAX_MESSAGE_SIZE in the list`s config. The default behavior is moderate this > message, what don`t solve me problem. Exist one way to do this? I understand what you are trying to do and what you have done should work. As I said in my prior reply > Em 03/09/2016 13:00, Mark Sapiro escreveu: > >> On 09/02/2016 01:45 PM, Andre de Azevedo Cunha wrote: >>> >>> The message was rejected, but the sender dont receive any notify about >>> that. The mailman vette log too. How can i solve this? >> >> >> Logging for rejected messages was added in 2.1.16. See >> . Prior to that, there >> won't be a vette log entry. >> >> I don't know why there isn't a notice to the user. Is there anything in >> Mailman's error log? >> >> As a test, add some nonmember address to the list's >> reject_these_nonmembers and send a post from that address. Does that >> receive a rejection notice? In order to help further, I need more information. Did you look in Mailman's error log? Did you do the test suggested above? Send me off list a copy of your modified Mailman/Handlers/Hold.py module and I'll look at it to see if there is a problem there. Also, if you want rejections to be logged in vette, you can apply the attached patch to Mailman/Queue/IncommingRunner.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: IncomingRunner.patch Type: text/x-diff Size: 690 bytes Desc: not available URL: From acunha at iff.edu.br Mon Sep 5 12:16:17 2016 From: acunha at iff.edu.br (Andre de Azevedo Cunha) Date: Mon, 05 Sep 2016 13:16:17 -0300 Subject: [Mailman-Users] Automate Moderator Functions In-Reply-To: <9b270daf-9f63-f2e4-d232-295141670641@msapiro.net> References: <9b270daf-9f63-f2e4-d232-295141670641@msapiro.net> Message-ID: Mark, i solved like this: REPLACED THIS: #default action (moderate) #hold_for_approval(mlist, msg, msgdata, # MessageTooBig(bodylen, mlist.max_message_size)) FOR THIS: #auto rejecting emails bigger then max_message_size f_log=open('/var/log/mailman/reject','a') f_log.write('Message from %s to %s rejected. Size exceed: %s KB\n'% (sender, listname, bodylen/1024)) f_log.close() rej2="Our message was rejected because is bigger then list max value ( %s KB ), please reduce the message to bellow of %s KB and try again"% (bodylen/1024, mlist.max_message_size) raise Errors.RejectMessage, rej2 Thanks for your support and availability. Regards, --- Em 05/09/2016 12:57, Mark Sapiro escreveu: > On 09/05/2016 07:10 AM, Andre de Azevedo Cunha wrote: > >> Mark, >> >> the important to me is reject emails to the lists bigger then the value set in >> MAX_MESSAGE_SIZE in the list`s config. The default behavior is moderate this >> message, what don`t solve me problem. Exist one way to do this? > > I understand what you are trying to do and what you have done should > work. As I said in my prior reply > > Em 03/09/2016 13:00, Mark Sapiro escreveu: > > On 09/02/2016 01:45 PM, Andre de Azevedo Cunha wrote: > The message was rejected, but the sender dont receive any notify about > that. The mailman vette log too. How can i solve this? > > Logging for rejected messages was added in 2.1.16. See > . Prior to that, there > won't be a vette log entry. > > I don't know why there isn't a notice to the user. Is there anything in > Mailman's error log? > > As a test, add some nonmember address to the list's > reject_these_nonmembers and send a post from that address. Does that > receive a rejection notice? In order to help further, I need more information. Did you look in Mailman's error log? Did you do the test suggested above? Send me off list a copy of your modified Mailman/Handlers/Hold.py module and I'll look at it to see if there is a problem there. Also, if you want rejections to be logged in vette, you can apply the attached patch to Mailman/Queue/IncommingRunner.py. From minxmertzmomo at gmail.com Tue Sep 6 08:59:25 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Tue, 6 Sep 2016 08:59:25 -0400 Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: On Mon, Sep 5, 2016 at 4:32 AM, Lucio Chiappetti wrote: > On Fri, 2 Sep 2016, Matt Morgan wrote: > > The eventual publication looks a lot like a mailman digest, and that's >> what I'm switching it to. >> > > I see that over the weekend there was some discussion about digests, not > only in this thread ! > > I understand that mailman can do digests as a series of MIME attachments >> to the TOC email, one for each posting. I don't think that's going to work >> for this crowd, although I'm not sure. >> > > Personally I do use MIME digests (not plain text ones) for almost all the > lists I'm subscribed to (actually ALL which allow it). But then my MUA > (Alpine) with some customization (including a formail-based shell script) > can turn the MIME digests into a temporary mail folder, where I can access > each posting as a normal e-mail. And even if I would not have my scripts, > I could still natively view the attachment index and access the RFC822 > attachment one by one as a normal e-mail. > > I love how you subscribe to a digest then use your mailer to extract individual messages. This is real power-user territory! Now that I understand them, I think I'll start using MIME digests them for myself when I can. And I like offering the option. The question is more, what would I use as the default? And I think honestly that putting everyone on MIME digests would substantially decrease readership on this list. We'd be "hiding" posts in attachments--essentially adding a click or two before people can see them; and since the readers on this list are also the authors, that will discourage writing, too. Too risky! From lucio at lambrate.inaf.it Tue Sep 6 09:24:54 2016 From: lucio at lambrate.inaf.it (Lucio Chiappetti) Date: Tue, 6 Sep 2016 15:24:54 +0200 (CEST) Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: On Tue, 6 Sep 2016, Matt Morgan wrote: > Now that I understand them, I think I'll start using MIME digests them for > myself when I can. And I like offering the option. The question is more, > what would I use as the default? And I think honestly that putting everyone > on MIME digests would substantially decrease readership on this list. On the list I manage I do not use digests as default, although I recommend them. Digests have one advantage which is also a disadvantage under certain situations. - Digests are sent with all mails packed together either at a predefined time (usually once per day at midday) OR when they exceeed a given size - ... so you will NOT receive messages in real time - this can be an advantage on lists with a large traffic and/or a large amount of "noise" (uninteresting messages). I do advise using digests for the internal discussion list of our nationwide organization (several hundred members). Reading messages once per day cools down the discussion. It also diminishes the disturbance of receiving a lot of mail asking for attention (I do use digests for "professional wide-spectrum" lists, like this one where I can discard a fraction of messages as not interesting or not concerning me, usually just by scanning through the subjects) - this is a disadvantage for professional narrow-spectrum lists where quick reply is required. In this case I do avoid digests so that I can receive messages in real time (mailman is still good in providing a common reference archive for all members). Usually these lists have few members, and act orderly (no noise, no flames). From tanstaafl at libertytrek.org Tue Sep 6 10:08:59 2016 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Tue, 6 Sep 2016 10:08:59 -0400 Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: On 9/2/2016 6:39 PM, Mark Sapiro wrote: > On 09/02/2016 02:00 PM, Andrew Hodgson wrote: >> >> I requested a similar feature a while ago: >> >> https://mail.python.org/pipermail/mailman-users/2014-December/078192.html > > > And my responses at > > and > > still hold. Read the whole thread. And an even earlier thread that contained a discussion about this (comments of mine) from December 2009, regarding how Yahoo Digests provided exactly the behavior you are talking about: https://www.mail-archive.com/mailman-users at python.org/msg55751.html From ed.beu at alaska.gov Tue Sep 6 12:38:00 2016 From: ed.beu at alaska.gov (Beu, Ed (DOA)) Date: Tue, 6 Sep 2016 16:38:00 +0000 Subject: [Mailman-Users] Some lists no longer archiving new messages In-Reply-To: References: <77788B6418FB6E4CB10D483D7DAC164C01142799D4@SOAANCEXMB9.soa.alaska.gov> Message-ID: <77788B6418FB6E4CB10D483D7DAC164C011427DA22@SOAANCEXMB9.soa.alaska.gov> Thank you Mark, just had to change owner from Root to Mailman, deleted the shunted messages that I had already imported manually and ran the unshunt command on the rest! Worked like a charm! Regards, ~Ed Ed Beu, System Programmer Dept. of Administration, ETS (907)269-6790 ed.beu at alaska.gov -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska.gov at python.org] On Behalf Of Mark Sapiro Sent: Saturday, September 03, 2016 7:44 AM To: mailman-users at python.org Subject: Re: [Mailman-Users] Some lists no longer archiving new messages On 09/02/2016 03:31 PM, Beu, Ed (DOA) wrote: > > The few lists that I have 'imported' mail from Thunderbird into Mailman archives will not archive new messages. I suspect a permissions issue on archives/private/LIST.mbox/LIST.mbox, but there should be errors and tracebacks in mailman's error log and shunted messages in the shunt queue. If you have the RedHat package, these are /var/log/mailman/error and /var/spool/mailman/shunt respectively. If you can't figure out what the problem is from the error log, post the info here. Once you have fixed the problem you can run unshunt (/usr/lib/mailman/bin/unshunt) to archive the shunted messages, but first you may want to examine them with /usr/lib/mailman/bin/show_qfiles to ensure that all of them should be unshunted and there are none from older, unrelated errors. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ From mark at msapiro.net Tue Sep 6 21:41:21 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 6 Sep 2016 18:41:21 -0700 Subject: [Mailman-Users] Digest formatting--clickable TOC? In-Reply-To: References: Message-ID: <5e126c71-76d3-5a2e-f058-517b51bc7d6b@msapiro.net> On 09/06/2016 05:59 AM, Matt Morgan wrote: > > Now that I understand them, I think I'll start using MIME digests them for > myself when I can. And I like offering the option. The question is more, > what would I use as the default? And I think honestly that putting everyone > on MIME digests would substantially decrease readership on this list. We'd > be "hiding" posts in attachments--essentially adding a click or two before > people can see them; and since the readers on this list are also the > authors, that will discourage writing, too. Too risky! As I've posted before, how the MIME digest is rendered is highly dependent upon the user's MUA (aka mail client, aka mail reader). Some MUAs do an excelent job of displaying all the messages inline while allowing opening and replying to individual messages just as if they'd been received individually. Others are a complete disaster. Mane are in between. Thus, each user has to see how MIME digests are rendered in her preferred MUA and chose MIME or plain accordingly. On my digestable lists, I default to MIME on the theory that those that don't like it will complain and I can tell them how to switch. If you default to plain, digest members may never know there is another choice that they may prefer. However, this decision is also dependent on the list and its user community and defaulting to MIME may not be appropriate in situations other than mine. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cnulk at scu.edu Wed Sep 7 17:54:26 2016 From: cnulk at scu.edu (Chris Nulk) Date: Wed, 7 Sep 2016 14:54:26 -0700 Subject: [Mailman-Users] A quick question about slicing outgoing qrunner Message-ID: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> Hello all, I have read the archives regarding slicing the qrunner queues. Mailman here runs on a single system (virtual) along with the local MTA and web server. Our outgoing queue recently got bogged down. I would like to increase the number of queues for the outgoing qrunner to three instead of one. My question is will I encounter any problems with changing (in mm_cfg.py) the QRUNNERS entry to: QRUNNERS = [ ('ArchRunner', 1), # messages for the archiver ('BounceRunner', 1), # for processing the qfile/bounces directory ('CommandRunner', 1), # commands and bounces from the outside world ('IncomingRunner', 1), # posts from the outside world ('NewsRunner', 1), # outgoing messages to the nntpd ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to three '3' queues) ('VirginRunner', 1), # internally crafted (virgin birth) messages ('RetryRunner', 1), # retry temporarily failed deliveries ] I also plan on performance tuning of the MTA. Thanks, Chris From mark at msapiro.net Wed Sep 7 19:23:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 7 Sep 2016 16:23:46 -0700 Subject: [Mailman-Users] A quick question about slicing outgoing qrunner In-Reply-To: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> References: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> Message-ID: <5ea7f16a-3198-7ca9-79c1-a9943d0f63e9@msapiro.net> On 09/07/2016 02:54 PM, Chris Nulk wrote: > > I have read the archives regarding slicing the qrunner queues. Mailman > here runs on a single system (virtual) along with the local MTA and web > server. Our outgoing queue recently got bogged down. I would like to > increase the number of queues for the outgoing qrunner to three instead > of one. The first thing you need to understand is why the outgoing queue got "bogged down". Depending on the actual cause, increasing the number of OutgoingRunner slices may not help. Usually, doing things in the MTA is more effective. The most effective thing often is setting up a separate submission port for Mailman that bypasses lot of checks. > My question is will I encounter any problems with changing (in > mm_cfg.py) the QRUNNERS entry to: > > QRUNNERS = [ > ('ArchRunner', 1), # messages for the archiver > ('BounceRunner', 1), # for processing the qfile/bounces directory > ('CommandRunner', 1), # commands and bounces from the outside world > ('IncomingRunner', 1), # posts from the outside world > ('NewsRunner', 1), # outgoing messages to the nntpd > ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to > three '3' queues) > ('VirginRunner', 1), # internally crafted (virgin birth) messages > ('RetryRunner', 1), # retry temporarily failed deliveries > ] That should be fine assuming you haven't set USE_MAILDIR = No but see caveat. Another way which doesn't depend on USE_MAILDIR or a future release not adding or deleting a new queue is QRUNNERS.remove(('OutgoingRunner', 1)) QRUNNERS.append(('OutgoingRunner', 3)) The QRUNNERS list is not order sensitive so you don't need to insert the new entry where the old one was removed. Caveat: Documentation says the number of slices must be a power of two. This is based on the theory that slice membership is based on the last bits of the queue entry name (hash), but it hasn't been that way for ages if ever. I'm certain the code works with 3 slices, but that's relatively untested. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jimpop at gmail.com Thu Sep 8 08:15:27 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Thu, 8 Sep 2016 08:15:27 -0400 Subject: [Mailman-Users] A quick question about slicing outgoing qrunner In-Reply-To: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> References: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> Message-ID: On Wed, Sep 7, 2016 at 5:54 PM, Chris Nulk wrote: > Hello all, > > I have read the archives regarding slicing the qrunner queues. Mailman here > runs on a single system (virtual) along with the local MTA and web server. > Our outgoing queue recently got bogged down. I would like to increase the > number of queues for the outgoing qrunner to three instead of one. > > My question is will I encounter any problems with changing (in mm_cfg.py) > the QRUNNERS entry to: > > QRUNNERS = [ > ('ArchRunner', 1), # messages for the archiver > ('BounceRunner', 1), # for processing the qfile/bounces directory > ('CommandRunner', 1), # commands and bounces from the outside world > ('IncomingRunner', 1), # posts from the outside world > ('NewsRunner', 1), # outgoing messages to the nntpd > ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to three > '3' queues) > ('VirginRunner', 1), # internally crafted (virgin birth) messages > ('RetryRunner', 1), # retry temporarily failed deliveries > ] > FWIW, I've been using the following in mm_cfg.py for years without any problems. Mailman v2.1.23 (but probably started using those settings in v2.1.15), with postifx on debian. QRUNNERS = [ ('ArchRunner', 4), ('BounceRunner', 1), ('CommandRunner', 1), ('IncomingRunner', 4), ('NewsRunner', 1), ('OutgoingRunner', 4), ('VirginRunner', 2), ('RetryRunner', 1), ] -Jim P. From steve at tunedinweb.com Thu Sep 8 11:03:36 2016 From: steve at tunedinweb.com (Steve Wehr) Date: Thu, 8 Sep 2016 11:03:36 -0400 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <576ABB3A.20804@msapiro.net> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> Message-ID: <07c301d209e2$2d0d4930$8727db90$@com> I am picking up this old thread that I never solved. Sorry for the delay. To answer your questions Mark... > This almost certainly is not a Mailman thing. I suspect the issue is because the mail > arrives from localhost[127.0.0.1], not because it's from Mailman. Well... There are several other PHP programs on my server that also send email to steve at tunedinweb.com, and those all work fine -- the /etc/postfix/transport file is respected and the mail routed off-platform. Only the mail sent by Mailman is being rejected with postfix errors I included below. What information could I provide to help figure out why? _____________________ Steve Wehr Tunedin Web Design -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+steve=tunedinweb.com at python.org] On Behalf Of Mark Sapiro Sent: Wednesday, June 22, 2016 12:22 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 06/22/2016 07:53 AM, Steve Wehr wrote: > > The issue is that my email address steve at tunedinweb.com is also a > member of several mailing lists. When mailman tries to send to > steve at tunedinweb.com I see this error message in the postfix log /var/log/maillog: > > Jun 6 17:02:08 166941-web1 postfix/smtpd[25836]: NOQUEUE: reject: > RCPT from > localhost[127.0.0.1]: 550 5.1.1 : Recipient > address > rejected: User unknown in local recipient table; > from= > to= proto=ESMTP > helo=<166941-web1.tunedinweb.com> > > So it seems that mailman is not respecting the /etc/postfix transport > file settings. I want mailman to send mail for those addresses > specified in the transport file to the server where that email is hosted. Well, yes and no. Something is causing the mail from Mailman lists to be rejected by Postfix for "User unknown in local recipient table" before transport_maps is consulted for this user. This almost certainly is not a Mailman thing. I suspect the issue is because the mail arrives from localhost[127.0.0.1], not because it's from Mailman. What do you have for Postfix mynetworks and smtpd_recipient_restrictions? (The output from 'postconf -n' might be useful.) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/steve%40tunedinweb.com From mark at msapiro.net Thu Sep 8 11:20:57 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 8 Sep 2016 08:20:57 -0700 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <07c301d209e2$2d0d4930$8727db90$@com> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> Message-ID: <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> On 09/08/2016 08:03 AM, Steve Wehr wrote: > > To answer your questions Mark... ... > What information could I provide to help figure out why? How about > What do you have for Postfix mynetworks and smtpd_recipient_restrictions? > (The output from 'postconf -n' might be > useful.) > -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at list.org Thu Sep 8 14:51:27 2016 From: barry at list.org (Barry Warsaw) Date: Fri, 9 Sep 2016 06:51:27 +1200 Subject: [Mailman-Users] A quick question about slicing outgoing qrunner In-Reply-To: References: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> Message-ID: <20160909065127.57ede7b6.barry@wooz.org> On Sep 08, 2016, at 08:15 AM, Jim Popovitch wrote: >> ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to three >> '3' queues) Slices must be a power of 2. Cheers, -Barry From mark at msapiro.net Thu Sep 8 15:27:36 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 8 Sep 2016 12:27:36 -0700 Subject: [Mailman-Users] A quick question about slicing outgoing qrunner In-Reply-To: <20160909065127.57ede7b6.barry@wooz.org> References: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> <20160909065127.57ede7b6.barry@wooz.org> Message-ID: On 09/08/2016 11:51 AM, Barry Warsaw wrote: > On Sep 08, 2016, at 08:15 AM, Jim Popovitch wrote: > >>> ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to three >>> '3' queues) > > Slices must be a power of 2. As I wrote in my reply at > Caveat: Documentation says the number of slices must be a power of two. > This is based on the theory that slice membership is based on the last > bits of the queue entry name (hash), but it hasn't been that way for > ages if ever. I'm certain the code works with 3 slices, but that's > relatively untested. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cnulk at scu.edu Thu Sep 8 15:53:58 2016 From: cnulk at scu.edu (Chris Nulk) Date: Thu, 8 Sep 2016 12:53:58 -0700 Subject: [Mailman-Users] A quick question about slicing outgoing qrunner In-Reply-To: <5ea7f16a-3198-7ca9-79c1-a9943d0f63e9@msapiro.net> References: <6c380df0-fa79-163c-6c29-fcc0d4153cab@scu.edu> <5ea7f16a-3198-7ca9-79c1-a9943d0f63e9@msapiro.net> Message-ID: <90db47de-3e48-a4ce-3669-2e473d990b47@scu.edu> Hi Mark, Thanks for the information. I plan on looking at the MTA. Unfortunately, when we migrated Mailman to a new server, I don't have the same abilities to effect changes as I did on the old server. The server is now managed by a different group and I just run an "application" on their server. Makes identifying and fixing problems a major pain in ... No problem setting the number of queues to a power of two. I used 3 as an example. Thanks for you input, Barry, for clarifying it. Jim, the settings you are using look interesting. I will have to think on it. The biggest issue I have right now is modifications to the MTA. We are using sendmail (it was used on the old server). When we migrated Mailman to the new server, I had to help them setup sendmail since I set it up on the old server. The admins don't know sendmail or postfix except on a very minimal level. It is not part of their normal responsibilities. Anyone willing to take this off-list and help me figure out how to switch from sendmail to postfix? Every time I have tried postfix, it has ended very miserably. :) Thanks, Chris On 9/7/2016 4:23 PM, Mark Sapiro wrote: > On 09/07/2016 02:54 PM, Chris Nulk wrote: >> I have read the archives regarding slicing the qrunner queues. Mailman >> here runs on a single system (virtual) along with the local MTA and web >> server. Our outgoing queue recently got bogged down. I would like to >> increase the number of queues for the outgoing qrunner to three instead >> of one. > > The first thing you need to understand is why the outgoing queue got > "bogged down". Depending on the actual cause, increasing the number of > OutgoingRunner slices may not help. Usually, doing things in the MTA is > more effective. The most effective thing often is setting up a separate > submission port for Mailman that bypasses lot of checks. > > >> My question is will I encounter any problems with changing (in >> mm_cfg.py) the QRUNNERS entry to: >> >> QRUNNERS = [ >> ('ArchRunner', 1), # messages for the archiver >> ('BounceRunner', 1), # for processing the qfile/bounces directory >> ('CommandRunner', 1), # commands and bounces from the outside world >> ('IncomingRunner', 1), # posts from the outside world >> ('NewsRunner', 1), # outgoing messages to the nntpd >> ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to >> three '3' queues) >> ('VirginRunner', 1), # internally crafted (virgin birth) messages >> ('RetryRunner', 1), # retry temporarily failed deliveries >> ] > > That should be fine assuming you haven't set > > USE_MAILDIR = No > > but see caveat. Another way which doesn't depend on USE_MAILDIR or a > future release not adding or deleting a new queue is > > QRUNNERS.remove(('OutgoingRunner', 1)) > QRUNNERS.append(('OutgoingRunner', 3)) > > The QRUNNERS list is not order sensitive so you don't need to insert the > new entry where the old one was removed. > > Caveat: Documentation says the number of slices must be a power of two. > This is based on the theory that slice membership is based on the last > bits of the queue entry name (hash), but it hasn't been that way for > ages if ever. I'm certain the code works with 3 slices, but that's > relatively untested. > From steve at tunedinweb.com Thu Sep 8 17:02:38 2016 From: steve at tunedinweb.com (Steve Wehr) Date: Thu, 8 Sep 2016 17:02:38 -0400 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> Message-ID: <07e001d20a14$5535ab50$ffa101f0$@com> Here it is.... /etc/postfix>postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 home_mailbox = Maildir/ html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailbox_command = /usr/bin/procmail mailbox_size_limit = 256000000 mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man message_size_limit = 68157440 mydestination = hash:/etc/postfix/mydomains myhostname = tunedinweb.com mynetworks = 23.253.149.133/32, 127.0.0.0/8, 10.208.195.27/32 newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES recipient_delimiter = + sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_sasl_security_options = noplaintext smtp_tls_loglevel = 1 smtpd_banner = $myhostname ESMTP $mail_name smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client sbl.spamhaus.org, reject_rbl_client xbl.spamhaus.org, reject_unauth_destination, check_policy_service unix:postgrey/socket smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_security_options = noanonymous smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/postfix/postfix.crt smtpd_tls_key_file = /etc/postfix/postfix.key smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_use_tls = yes transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 virtual_alias_maps = hash:/etc/postfix/virtual _____________________ Steve Wehr Tunedin Web Design 845-246-9643 -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Thursday, September 08, 2016 11:21 AM To: Steve Wehr Cc: Mailman-Users at python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/08/2016 08:03 AM, Steve Wehr wrote: > > To answer your questions Mark... ... > What information could I provide to help figure out why? How about > What do you have for Postfix mynetworks and smtpd_recipient_restrictions? > (The output from 'postconf -n' might be > useful.) > -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Sep 8 17:51:27 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 8 Sep 2016 14:51:27 -0700 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <07e001d20a14$5535ab50$ffa101f0$@com> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> Message-ID: On 09/08/2016 02:02 PM, Steve Wehr wrote: > Here it is.... > > /etc/postfix>postconf -n ... > mydestination = hash:/etc/postfix/mydomains What's in /etc/postfix/mydomains ... > transport_maps = hash:/etc/postfix/transport What's in /etc/postfix/transport And what's in Mailman's Defaults.py/mm_cfg.py for SMTPPORT Before answering the above try the following: Assuming the Defaults.py settings are: SMTPHOST = 'localhost' SMTPPORT = 0 and they aren't overridden in mm_cfg.py, try the following shell session (postfix replies not shown) $ telnet localhost 25 EHLO tunedinweb.com MAIL FROM: RCPT TO: DATA . QUIT If that gives the error, try the same thing, but do $ telnet 127.0.0.1 25 to start. If that works but 'localhost' gives the reject try adding localhost to mynetworks = 23.253.149.133/32, 127.0.0.0/8, 10.208.195.27/32 and if that doesn't solve it, add SMTPHOST = '127.0.0.1' to mm_cfg.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From steve at tunedinweb.com Fri Sep 9 10:33:39 2016 From: steve at tunedinweb.com (Steve Wehr) Date: Fri, 9 Sep 2016 10:33:39 -0400 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> Message-ID: <07f601d20aa7$28264aa0$7872dfe0$@com> Thanks Mark, Here are the results of the tests you suggested. Both attempts at telnet failed. Tried your experiment: /etc/postfix>telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: 250 2.1.0 Ok RCPT TO: 550 5.1.1 : Recipient address rejected: User unknown in local recipient table quit 221 2.0.0 Bye Connection closed by foreign host. /etc/postfix>telnet 127.0.0.1 25 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: 250 2.1.0 Ok RCPT TO: 550 5.1.1 : Recipient address rejected: User unknown in local recipient table quit 221 2.0.0 Bye Connection closed by foreign host. from Defaults.py. Not in mm_cfg.py SMTPHOST = 'localhost' SMTPPORT = 0 /etc/postfix/mydomains: localhost OK tunedin OK # Always keep tunedinweb.com as a local domain, so that we can process mailman # email commands tunedinweb.com OK /etc/postfix/transport: steve at tunedinweb.com smtp:mx.emailsrvr.com steves at tunedinweb.com smtp:mx.emailsrvr.com stevew at tunedinweb.com smtp:mx.emailsrvr.com wehr at tunedinweb.com smtp:mx.emailsrvr.com stiert at tunedinweb.com smtp:mx.emailsrvr.com admin at tunedinweb.com smtp:mx.emailsrvr.com errors at tunedinweb.com smtp:mx.emailsrvr.com events at tunedinweb.com smtp:mx.emailsrvr.com feedback at tunedinweb.com smtp:mx.emailsrvr.com email at tunedinweb.com smtp:mx.emailsrvr.com ideachamp_order at tunedinweb.com smtp:mx.emailsrvr.com inquiry at tunedinweb.com smtp:mx.emailsrvr.com mailman at tunedinweb.com smtp:mx.emailsrvr.com mailman_admin at tunedinweb.com smtp:mx.emailsrvr.com mailman-owner at tunedinweb.com smtp:mx.emailsrvr.com orders at tunedinweb.com smtp:mx.emailsrvr.com payments at tunedinweb.com smtp:mx.emailsrvr.com root at tunedinweb.com smtp:mx.emailsrvr.com security at tunedinweb.com smtp:mx.emailsrvr.com tunedin at tunedinweb.com smtp:mx.emailsrvr.com verify at tunedinweb.com smtp:mx.emailsrvr.com abuse at tunedinweb.com smtp:mx.emailsrvr.com postmaster at tunedinweb.com smtp:mx.emailsrvr.com (mx.emailsrvr.com is the rackspace email server where the mailbox for tunedinweb.com is hosted.) _____________________ Steve Wehr Tunedin Web Design 845-246-9643 -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Thursday, September 08, 2016 5:51 PM To: Steve Wehr Cc: Mailman-Users at python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/08/2016 02:02 PM, Steve Wehr wrote: > Here it is.... > > /etc/postfix>postconf -n ... > mydestination = hash:/etc/postfix/mydomains What's in /etc/postfix/mydomains ... > transport_maps = hash:/etc/postfix/transport What's in /etc/postfix/transport And what's in Mailman's Defaults.py/mm_cfg.py for SMTPPORT Before answering the above try the following: Assuming the Defaults.py settings are: SMTPHOST = 'localhost' SMTPPORT = 0 and they aren't overridden in mm_cfg.py, try the following shell session (postfix replies not shown) $ telnet localhost 25 EHLO tunedinweb.com MAIL FROM: RCPT TO: DATA . QUIT If that gives the error, try the same thing, but do $ telnet 127.0.0.1 25 to start. If that works but 'localhost' gives the reject try adding localhost to mynetworks = 23.253.149.133/32, 127.0.0.0/8, 10.208.195.27/32 and if that doesn't solve it, add SMTPHOST = '127.0.0.1' to mm_cfg.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 9 13:38:25 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 9 Sep 2016 10:38:25 -0700 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <07f601d20aa7$28264aa0$7872dfe0$@com> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> <07f601d20aa7$28264aa0$7872dfe0$@com> Message-ID: <4a7ae6d9-bda1-0d07-682b-3758cc2c1278@msapiro.net> On 09/09/2016 07:33 AM, Steve Wehr wrote: > Thanks Mark, Here are the results of the tests you suggested. Both attempts > at telnet failed. > > Tried your experiment: > > /etc/postfix>telnet localhost 25 > Trying ::1... > telnet: connect to address ::1: Connection refused > Trying 127.0.0.1... > Connected to localhost. Interesting. I suggest you put SMTPHOST = '127.0.0.1' in mm_cfg.py since 'localhost' seems to resolve at least first to an IPv6 address on which Postfix isn't listening. I don't see exactly how this will help, but it might. Now, given that Postfix doesn't like steve at tunedinweb.com, the question is what are the PHP scripts that mail to this address doing. Are they connecting to this Postfix differently or even at all (maybe they connect to mx.emailsrvr.com). > /etc/postfix/transport: > steve at tunedinweb.com smtp:mx.emailsrvr.com > steves at tunedinweb.com smtp:mx.emailsrvr.com > stevew at tunedinweb.com smtp:mx.emailsrvr.com > wehr at tunedinweb.com smtp:mx.emailsrvr.com > stiert at tunedinweb.com smtp:mx.emailsrvr.com > admin at tunedinweb.com smtp:mx.emailsrvr.com > errors at tunedinweb.com smtp:mx.emailsrvr.com > events at tunedinweb.com smtp:mx.emailsrvr.com > feedback at tunedinweb.com smtp:mx.emailsrvr.com > email at tunedinweb.com smtp:mx.emailsrvr.com > ideachamp_order at tunedinweb.com smtp:mx.emailsrvr.com > inquiry at tunedinweb.com smtp:mx.emailsrvr.com > mailman at tunedinweb.com smtp:mx.emailsrvr.com > mailman_admin at tunedinweb.com smtp:mx.emailsrvr.com > mailman-owner at tunedinweb.com smtp:mx.emailsrvr.com > orders at tunedinweb.com smtp:mx.emailsrvr.com > payments at tunedinweb.com smtp:mx.emailsrvr.com > root at tunedinweb.com smtp:mx.emailsrvr.com > security at tunedinweb.com smtp:mx.emailsrvr.com > tunedin at tunedinweb.com smtp:mx.emailsrvr.com > verify at tunedinweb.com smtp:mx.emailsrvr.com > abuse at tunedinweb.com smtp:mx.emailsrvr.com > postmaster at tunedinweb.com smtp:mx.emailsrvr.com If you add local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps to Postfix main.cf, I think that will work. This is actually only adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are the defaults. This will ensure that none of the addresses in transport_maps (/etc/postfix/transport) is rejected as an unknown local recipient. It appears that Postfix is doing the local recipient check before consulting transport_maps for a transport. I'm not that knowledgeable about the details of Postfix to fully understand this, but I think adding $transport_maps to local_recipient_maps in this case will solve your issue without causing other problems, but I suggest you test and be prepared to reverse when you do this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From steve at tunedinweb.com Sat Sep 10 10:21:37 2016 From: steve at tunedinweb.com (Steve Wehr) Date: Sat, 10 Sep 2016 10:21:37 -0400 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <4a7ae6d9-bda1-0d07-682b-3758cc2c1278@msapiro.net> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> <07f601d20aa7$28264aa0$7872dfe0$@com> <4a7ae6d9-bda1-0d07-682b-3758cc2c1278@msapiro.net> Message-ID: <086601d20b6e$a47fc230$ed7f4690$@com> Here's another clue Mark... I had noticed that on some mailing lists I was subscribed as steve at tunedinweb.com, and on some others as tunedin at tunedinweb.com. The former are failing as per my origilam problem, but the latter are sent successfully. So I tried: telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: 250 2.1.0 Ok RCPT TO: 250 2.1.5 Ok quit 221 2.0.0 Bye Connection closed by foreign host. This works! Why?? Both steve at tunedinweb.com and tunedin at tunedinweb.com are defined exactly the same in /etc/postfix/transport. _____________________ Steve Wehr Tunedin Web Design 845-246-9643 -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, September 09, 2016 1:38 PM To: Steve Wehr Cc: Mailman-Users at python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/09/2016 07:33 AM, Steve Wehr wrote: > Thanks Mark, Here are the results of the tests you suggested. Both > attempts at telnet failed. > > Tried your experiment: > > /etc/postfix>telnet localhost 25 > Trying ::1... > telnet: connect to address ::1: Connection refused Trying 127.0.0.1... > Connected to localhost. Interesting. I suggest you put SMTPHOST = '127.0.0.1' in mm_cfg.py since 'localhost' seems to resolve at least first to an IPv6 address on which Postfix isn't listening. I don't see exactly how this will help, but it might. Now, given that Postfix doesn't like steve at tunedinweb.com, the question is what are the PHP scripts that mail to this address doing. Are they connecting to this Postfix differently or even at all (maybe they connect to mx.emailsrvr.com). > /etc/postfix/transport: > steve at tunedinweb.com smtp:mx.emailsrvr.com > steves at tunedinweb.com smtp:mx.emailsrvr.com > stevew at tunedinweb.com smtp:mx.emailsrvr.com > wehr at tunedinweb.com smtp:mx.emailsrvr.com > stiert at tunedinweb.com smtp:mx.emailsrvr.com > admin at tunedinweb.com smtp:mx.emailsrvr.com > errors at tunedinweb.com smtp:mx.emailsrvr.com > events at tunedinweb.com smtp:mx.emailsrvr.com > feedback at tunedinweb.com smtp:mx.emailsrvr.com > email at tunedinweb.com smtp:mx.emailsrvr.com > ideachamp_order at tunedinweb.com smtp:mx.emailsrvr.com > inquiry at tunedinweb.com smtp:mx.emailsrvr.com > mailman at tunedinweb.com smtp:mx.emailsrvr.com > mailman_admin at tunedinweb.com smtp:mx.emailsrvr.com > mailman-owner at tunedinweb.com smtp:mx.emailsrvr.com > orders at tunedinweb.com smtp:mx.emailsrvr.com > payments at tunedinweb.com smtp:mx.emailsrvr.com > root at tunedinweb.com smtp:mx.emailsrvr.com > security at tunedinweb.com smtp:mx.emailsrvr.com > tunedin at tunedinweb.com smtp:mx.emailsrvr.com > verify at tunedinweb.com smtp:mx.emailsrvr.com > abuse at tunedinweb.com smtp:mx.emailsrvr.com > postmaster at tunedinweb.com smtp:mx.emailsrvr.com If you add local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps to Postfix main.cf, I think that will work. This is actually only adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are the defaults. This will ensure that none of the addresses in transport_maps (/etc/postfix/transport) is rejected as an unknown local recipient. It appears that Postfix is doing the local recipient check before consulting transport_maps for a transport. I'm not that knowledgeable about the details of Postfix to fully understand this, but I think adding $transport_maps to local_recipient_maps in this case will solve your issue without causing other problems, but I suggest you test and be prepared to reverse when you do this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From steve at tunedinweb.com Sat Sep 10 10:35:18 2016 From: steve at tunedinweb.com (Steve Wehr) Date: Sat, 10 Sep 2016 10:35:18 -0400 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> <07f601d20aa7$28264aa0$7872dfe0$@com> <4a7ae6d9-bda1-0d07-682b-3758cc2c1278@msapiro.net> Message-ID: <087a01d20b70$8dc200b0$a9460210$@com> I tried almost all the email addresses defined in /etc/postfix/transport Many of them succeed in the telnet test below, but many of them fail. There is no pattern I can find to success or failure. I thought maybe there was some hidden characters in the file that were preventing the hashing working when the file is compiled. So I was looking to see if all the ones above a certain spot in the file failed, and all those below succeeded, but that is not the case. Ideas? _____________________ Steve Wehr Tunedin Web Design 845-246-9643 -----Original Message----- From: Steve Wehr [mailto:steve at tunedinweb.com] Sent: Saturday, September 10, 2016 10:22 AM To: 'Mark Sapiro' Cc: 'Mailman-Users at python.org' Subject: RE: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? Here's another clue Mark... I had noticed that on some mailing lists I was subscribed as steve at tunedinweb.com, and on some others as tunedin at tunedinweb.com. The former are failing as per my origilam problem, but the latter are sent successfully. So I tried: telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix EHLO tunedinweb.com 250-tunedinweb.com 250-PIPELINING 250-SIZE 68157440 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN MAIL FROM: 250 2.1.0 Ok RCPT TO: 250 2.1.5 Ok quit 221 2.0.0 Bye Connection closed by foreign host. This works! Why?? Both steve at tunedinweb.com and tunedin at tunedinweb.com are defined exactly the same in /etc/postfix/transport. _____________________ Steve Wehr Tunedin Web Design 845-246-9643 -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, September 09, 2016 1:38 PM To: Steve Wehr Cc: Mailman-Users at python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/09/2016 07:33 AM, Steve Wehr wrote: > Thanks Mark, Here are the results of the tests you suggested. Both > attempts at telnet failed. > > Tried your experiment: > > /etc/postfix>telnet localhost 25 > Trying ::1... > telnet: connect to address ::1: Connection refused Trying 127.0.0.1... > Connected to localhost. Interesting. I suggest you put SMTPHOST = '127.0.0.1' in mm_cfg.py since 'localhost' seems to resolve at least first to an IPv6 address on which Postfix isn't listening. I don't see exactly how this will help, but it might. Now, given that Postfix doesn't like steve at tunedinweb.com, the question is what are the PHP scripts that mail to this address doing. Are they connecting to this Postfix differently or even at all (maybe they connect to mx.emailsrvr.com). > /etc/postfix/transport: > steve at tunedinweb.com smtp:mx.emailsrvr.com > steves at tunedinweb.com smtp:mx.emailsrvr.com > stevew at tunedinweb.com smtp:mx.emailsrvr.com > wehr at tunedinweb.com smtp:mx.emailsrvr.com > stiert at tunedinweb.com smtp:mx.emailsrvr.com > admin at tunedinweb.com smtp:mx.emailsrvr.com > errors at tunedinweb.com smtp:mx.emailsrvr.com > events at tunedinweb.com smtp:mx.emailsrvr.com > feedback at tunedinweb.com smtp:mx.emailsrvr.com > email at tunedinweb.com smtp:mx.emailsrvr.com > ideachamp_order at tunedinweb.com smtp:mx.emailsrvr.com > inquiry at tunedinweb.com smtp:mx.emailsrvr.com > mailman at tunedinweb.com smtp:mx.emailsrvr.com > mailman_admin at tunedinweb.com smtp:mx.emailsrvr.com > mailman-owner at tunedinweb.com smtp:mx.emailsrvr.com > orders at tunedinweb.com smtp:mx.emailsrvr.com > payments at tunedinweb.com smtp:mx.emailsrvr.com > root at tunedinweb.com smtp:mx.emailsrvr.com > security at tunedinweb.com smtp:mx.emailsrvr.com > tunedin at tunedinweb.com smtp:mx.emailsrvr.com > verify at tunedinweb.com smtp:mx.emailsrvr.com > abuse at tunedinweb.com smtp:mx.emailsrvr.com > postmaster at tunedinweb.com smtp:mx.emailsrvr.com If you add local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps to Postfix main.cf, I think that will work. This is actually only adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are the defaults. This will ensure that none of the addresses in transport_maps (/etc/postfix/transport) is rejected as an unknown local recipient. It appears that Postfix is doing the local recipient check before consulting transport_maps for a transport. I'm not that knowledgeable about the details of Postfix to fully understand this, but I think adding $transport_maps to local_recipient_maps in this case will solve your issue without causing other problems, but I suggest you test and be prepared to reverse when you do this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From apadmaraju at guidewire.com Fri Sep 9 21:06:07 2016 From: apadmaraju at guidewire.com (Anilkumar Padmaraju) Date: Sat, 10 Sep 2016 01:06:07 +0000 Subject: [Mailman-Users] Mailman delays sending emails Message-ID: Hi, I have an issue where the mailman server is delaying to send emails, which happened for the first time. It is not our mail server as mails other than mailman are going fine. The delay is over 6 hours. Can someone please suggest something to check. Regards, Anil. From apadmaraju at guidewire.com Fri Sep 9 21:16:21 2016 From: apadmaraju at guidewire.com (Anilkumar Padmaraju) Date: Sat, 10 Sep 2016 01:16:21 +0000 Subject: [Mailman-Users] Mailman delays sending emails Message-ID: There are lot of .pck files under /usr/local/mailman/qfiles/in Any suggestion would be very helpful. Regards, Anil. From: Anilkumar Padmaraju Sent: Friday, September 09, 2016 6:06 PM To: 'Mailman-Users at python.org' Subject: Mailman delays sending emails Hi, I have an issue where the mailman server is delaying to send emails, which happened for the first time. It is not our mail server as mails other than mailman are going fine. The delay is over 6 hours. Can someone please suggest something to check. Regards, Anil. From mark at msapiro.net Sat Sep 10 11:32:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Sep 2016 08:32:12 -0700 Subject: [Mailman-Users] Mailman delays sending emails In-Reply-To: References: Message-ID: <4507e1ec-e771-905c-c7ae-0c2088591846@msapiro.net> On 09/09/2016 06:16 PM, Anilkumar Padmaraju wrote: > There are lot of .pck files under /usr/local/mailman/qfiles/in This is unusual. Normally the queue that is backlogged is qfiles/out because of slow delivery from Mailman to the MTA. See some of the hits at I have never seen a backlogged 'in' queue unless Mailman is not running at all. > I have an issue where the mailman server is delaying to send emails, which happened for the first time. > It is not our mail server as mails other than mailman are going fine. > > The delay is over 6 hours. > > Can someone please suggest something to check. However, in this case, messages are being delivered so Mailman is running. You say it is not your server, yet you seem to at least have access to Mailman's files. Have you checked Mailman's logs (/usr/local/mailman/logs/*). What Mailman version is this? If it is 2.1.18 or newer and a list has dmarc_moderation_action set to other than Accept, it could be long delays in DNS lookups of the From: domain's DMARC policy. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Sep 10 12:23:31 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Sep 2016 09:23:31 -0700 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: <087a01d20b70$8dc200b0$a9460210$@com> References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> <07f601d20aa7$28264aa0$7872dfe0$@com> <4a7ae6d9-bda1-0d07-682b-3758cc2c1278@msapiro.net> <087a01d20b70$8dc200b0$a9460210$@com> Message-ID: On 09/10/2016 07:35 AM, Steve Wehr wrote: > I tried almost all the email addresses defined in /etc/postfix/transport > > Many of them succeed in the telnet test below, but many of them fail. There > is no pattern I can find to success or failure. I thought maybe there was > some hidden characters in the file that were preventing the hashing working > when the file is compiled. So I was looking to see if all the ones above a > certain spot in the file failed, and all those below succeeded, but that is > not the case. Ideas? Are the ones that work in /etc/passwd and or /etc/aliases and the ones that fail not? I wrote: > Now, given that Postfix doesn't like steve at tunedinweb.com, the question is > what are the PHP scripts that mail to this address doing. Are they > connecting to this Postfix differently or even at all (maybe they connect to > mx.emailsrvr.com). The answer to this may still be of interest. > If you add > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps > > to Postfix main.cf, I think that will work. This is actually only adding > $transport_maps as proxy:unix:passwd.byname and $alias_maps are the > defaults. This will ensure that none of the addresses in transport_maps > (/etc/postfix/transport) is rejected as an unknown local recipient. Have you tried this? I think it will work. If the answer to my first question above is yes, I'm sure it will work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From steve at tunedinweb.com Sun Sep 11 10:30:39 2016 From: steve at tunedinweb.com (Steve Wehr) Date: Sun, 11 Sep 2016 10:30:39 -0400 Subject: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? In-Reply-To: References: <01a701d1cc95$cdbd6570$69383050$@com> <576ABB3A.20804@msapiro.net> <07c301d209e2$2d0d4930$8727db90$@com> <7f857c60-f2f0-c033-2a3b-9b3374cec9c3@msapiro.net> <07e001d20a14$5535ab50$ffa101f0$@com> <07f601d20aa7$28264aa0$7872dfe0$@com> <4a7ae6d9-bda1-0d07-682b-3758cc2c1278@msapiro.net> <087a01d20b70$8dc200b0$a9460210$@com> Message-ID: <08ba01d20c39$121411a0$363c34e0$@com> Hi Mark -- I think it is fixed.... I updated /etc/postfix/main.cf with local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps Then I sent out a mailing from a test mailing list I have that includes my email address -- steve at tunedinweb.com. --> I received this mailing. YEAH! I did look in /etc/passwd and /etc/aliases... and did find "tunedin" in /etc/passwd, so is that why Mailman was able to deliver to tunedin at tunedinweb.com ?? (I didn't find any of the other email addresses listed in /etc/postfix/transport in either of those files, so I don't know why some of those passed the telnet test and others did not) FYI... steve at tunedinweb.com now passes the telnet test: telnet localhost 25 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 tunedinweb.com ESMTP Postfix MAIL FROM: 250 2.1.0 Ok RCPT TO: 250 2.1.5 Ok quit 221 2.0.0 Bye Connection closed by foreign host. _____________________ Steve Wehr Tunedin Web Design 845-246-9643 -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Saturday, September 10, 2016 12:24 PM To: Steve Wehr Cc: Mailman-Users at python.org Subject: Re: [Mailman-Users] mailman not respecting /etc/postfix/transport ??? On 09/10/2016 07:35 AM, Steve Wehr wrote: > I tried almost all the email addresses defined in > /etc/postfix/transport > > Many of them succeed in the telnet test below, but many of them fail. > There is no pattern I can find to success or failure. I thought maybe > there was some hidden characters in the file that were preventing the > hashing working when the file is compiled. So I was looking to see if > all the ones above a certain spot in the file failed, and all those > below succeeded, but that is not the case. Ideas? Are the ones that work in /etc/passwd and or /etc/aliases and the ones that fail not? I wrote: > Now, given that Postfix doesn't like steve at tunedinweb.com, the > question is what are the PHP scripts that mail to this address doing. > Are they connecting to this Postfix differently or even at all (maybe > they connect to mx.emailsrvr.com). The answer to this may still be of interest. > If you add > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > $transport_maps > > to Postfix main.cf, I think that will work. This is actually only > adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are > the defaults. This will ensure that none of the addresses in > transport_maps > (/etc/postfix/transport) is rejected as an unknown local recipient. Have you tried this? I think it will work. If the answer to my first question above is yes, I'm sure it will work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Sun Sep 11 18:14:50 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Sun, 11 Sep 2016 18:14:50 -0400 Subject: [Mailman-Users] Too many digests, at unexpected times Message-ID: I'm trying to set up a list that's going to go out only as digests, once a week. The list is called "consdistlist." Right now I just have three subscribers, all different email addresses belonging to me. I have applied Mark Sapiro's recent patch that allows the -e option (aka --exceptlist) on mailman/cron/senddigests. In cron, as of an hour ago or so, I have # Mail digests for lists that do periodic as well as threshhold delivery. # this one does everything except consdistlist daily at noon 0 12 * * * /usr/bin/python -S /usr/local/mailman/cron/senddigests -e consdistlist # this one does only consdistlist on Mondays at 4AM 0 4 * * 1 /usr/bin/python -S /usr/local/mailman/cron/senddigests -l consdistlist So I made that change and then sent a four test emails in to the list, one or two from each of the three subscriber accounts. I then went into the moderation panel and accepted the four messages (all postings must be moderated). Moments later, not tomorrow at 4AM, in two of the three accounts I got four separate digests (volume 1 issues 3, 4, 5, and 6--this is not my first attempt), each with one of the four new messages in it. I then went back 20 minutes later after checking everything, and sent two more messages, and accepted them. Again, they came right away, as separate digests with one message each in them. So I got something very wrong. But I don't understand ... senddigests shouldn't even be running right now. Here's my digest config on consdistlist: digestable=Yes digest_is_default=Digest mime_is_default_digest=Plain digest_size_threshold=0 digest_send_periodic=No (I don't think the rest is relevant, but I haven't tried adding anything to the header or footer yet, and digest_volume_frequency=Monthly). What can I try next? Thanks, Matt From mark at msapiro.net Sun Sep 11 18:35:36 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 11 Sep 2016 15:35:36 -0700 Subject: [Mailman-Users] Too many digests, at unexpected times In-Reply-To: References: Message-ID: <4c220dc7-e07d-0335-90be-d9ee0af53776@msapiro.net> On 09/11/2016 03:14 PM, Matt Morgan wrote: > > digestable=Yes > digest_is_default=Digest > mime_is_default_digest=Plain > digest_size_threshold=0 > digest_send_periodic=No Two things: If digest_send_periodic=No, cron/senddigests will never send a digest for this list. You want digest_send_periodic=Yes. More importantly, if your Mailman is older than 2.1.16, digest_size_threshold=0 means send a digest with every post rather than unlimited size. See . You can fix it with the attached patch or just set digest_size_threshold=1000 or some other big number. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: ToDigest.patch Type: text/x-diff Size: 851 bytes Desc: not available URL: From jewel.brueggeman-makda at washburn.edu Mon Sep 12 09:45:58 2016 From: jewel.brueggeman-makda at washburn.edu (Jewel Brueggeman-Makda) Date: Mon, 12 Sep 2016 13:45:58 +0000 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 Message-ID: Good Morning, I am in the process of setting up a replacement mailman server and so far things are going well. I did have 2.1.22 and upgraded to 2.1.23. The point where I am stuck is when I try to post to the mailman list I receive the following error below. When I setup mailman I used the following command: ./configure --with-mail-gid=mailman --with-cgi-gid=apache Upon seeing the error below I reran the configure command with the 'nobody' and reran the make, make install but that broke the web interface. I have searched online but cannot find a solution. : Command died with status 2: "/usr/local/mailman/mail/mailman post mailman". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mailman", but the system's mail server executed the mail script as group "nobody". Try tweaking the mail server to run the script as group "mailman", or re-run configure, providing the command line option `--with-mail-gid=nobody'. Jewel Makda From Hagedorn at uni-koeln.de Mon Sep 12 15:02:32 2016 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Mon, 12 Sep 2016 21:02:32 +0200 Subject: [Mailman-Users] What does "Possible malformed path attack" actually mean? Message-ID: <48B87F9F0B24D52A430FF9C1@Sebbis-iMac-2.local> Hi, today I updated our installation of Mailman to version 2.1.23. Prior to the upgrade there were "Possible malformed path attack" log entries, but without any further details I never bothered to look for their cause. After the update I can now see where they are coming from, and it's our own Google Search Appliance (GSA). So far I haven't been able to understand what is going on. I can't find any questionable requests in Apache's access log from the GSA. Any ideas what could be causing this? Thanks Sebastian -- Sebastian Hagedorn - Weyertal 121, Zimmer 2.02 Regionales Rechenzentrum (RRZK) Universit?t zu K?ln / Cologne University - Tel. +49-221-470-89578 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: not available URL: From mark at msapiro.net Mon Sep 12 21:06:14 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 12 Sep 2016 18:06:14 -0700 Subject: [Mailman-Users] What does "Possible malformed path attack" actually mean? In-Reply-To: <48B87F9F0B24D52A430FF9C1@Sebbis-iMac-2.local> References: <48B87F9F0B24D52A430FF9C1@Sebbis-iMac-2.local> Message-ID: <6dbfdb63-4efc-dc83-0a8d-c1f4ef465e7c@msapiro.net> On 09/12/2016 12:02 PM, Sebastian Hagedorn wrote: > > So far I haven't been able to understand what is going on. I can't find > any questionable requests in Apache's access log from the GSA. Any ideas > what could be causing this? It is caused by an attempt to get a mailman URL that contains spaces or characters not in the printable ascii set [\x21-\x7e]. The reason behind this is to disallow CR and LF in particular. This was a security enhancement in Mailman 2.1.9. From the NEWS - A malicious user could visit a specially crafted URI and inject an apparent log message into Mailman's error log which might induce an unsuspecting administrator to visit a phishing site. This has been blocked. Thanks to Moritz Naumann for its discovery. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Mon Sep 12 21:46:34 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 12 Sep 2016 18:46:34 -0700 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 In-Reply-To: References: Message-ID: On 09/12/2016 06:45 AM, Jewel Brueggeman-Makda wrote: > Good Morning, > I am in the process of setting up a replacement mailman server and so far things are going well. I did have 2.1.22 and upgraded to 2.1.23. The point where I am stuck is when I try to post to the mailman list I receive the following error below. When I setup mailman I used the following command: > ./configure --with-mail-gid=mailman --with-cgi-gid=apache > > Upon seeing the error below I reran the configure command with the 'nobody' and reran the make, make install but that broke the web interface. I have searched online but cannot find a solution. Is the MTA Postfix? If so, the problem is your Mailman aliases.db file is not owned by 'mailman' (probably by root) and --with-mail-gid=mailman should be correct. What does "broke the web interface" mean? If you look in apache's error log, there may be a group mismatch error there. Are you shure the web server runs as user 'apache' and not 'www-data' or something else. Try ps -fwwA|egrep '(apache|httpd)' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Hagedorn at uni-koeln.de Tue Sep 13 06:51:58 2016 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Tue, 13 Sep 2016 12:51:58 +0200 Subject: [Mailman-Users] What does "Possible malformed path attack" actually mean? In-Reply-To: <6dbfdb63-4efc-dc83-0a8d-c1f4ef465e7c@msapiro.net> References: <48B87F9F0B24D52A430FF9C1@Sebbis-iMac-2.local> <6dbfdb63-4efc-dc83-0a8d-c1f4ef465e7c@msapiro.net> Message-ID: <545CB1B1498746622B56F254@tyrion.rrz.uni-koeln.de> --On 12. September 2016 um 18:06:14 -0700 Mark Sapiro wrote: > On 09/12/2016 12:02 PM, Sebastian Hagedorn wrote: >> >> So far I haven't been able to understand what is going on. I can't find >> any questionable requests in Apache's access log from the GSA. Any ideas >> what could be causing this? > > > It is caused by an attempt to get a mailman URL that contains spaces or > characters not in the printable ascii set [\x21-\x7e]. > > The reason behind this is to disallow CR and LF in particular. This was > a security enhancement in Mailman 2.1.9. From the NEWS > > - A malicious user could visit a specially crafted URI and inject an > apparent log message into Mailman's error log which might induce an > unsuspecting administrator to visit a phishing site. This has been > blocked. Thanks to Moritz Naumann for its discovery. Thanks. I figured out that the GSA is appending %20 to one of our many lists name: 134.95.x.x - - [13/Sep/2016:11:33:22 +0200] "GET /mailman/listinfo/list-name%20 HTTP/1.0" 200 7630 "-" "gsa-crawler (Enterprise; T4-XXXXXXXXX; redacted at uni-koeln.de)" Now we only have to understand why ... -- .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: not available URL: From jewel.brueggeman-makda at washburn.edu Tue Sep 13 12:02:33 2016 From: jewel.brueggeman-makda at washburn.edu (Jewel Brueggeman-Makda) Date: Tue, 13 Sep 2016 16:02:33 +0000 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 In-Reply-To: References: Message-ID: -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+jewel.makda=washburn.edu at python.org] On Behalf Of Mark Sapiro Sent: Monday, September 12, 2016 8:47 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Unable to post to list - Command died with status 2 On 09/12/2016 06:45 AM, Jewel Brueggeman-Makda wrote: > Good Morning, > I am in the process of setting up a replacement mailman server and so far things are going well. I did have 2.1.22 and upgraded to 2.1.23. The point where I am stuck is when I try to post to the mailman list I receive the following error below. When I setup mailman I used the following command: > ./configure --with-mail-gid=mailman --with-cgi-gid=apache > > Upon seeing the error below I reran the configure command with the 'nobody' and reran the make, make install but that broke the web interface. I have searched online but cannot find a solution. Is the MTA Postfix? If so, the problem is your Mailman aliases.db file is not owned by 'mailman' (probably by root) and --with-mail-gid=mailman should be correct. Yes, I am running Postfix. The /usr/local/mailman/data/aliases file showed the owner as root and group as mailman. I ran: chown mailman:mailman aliases and also: chmod g+w This so far didn't resolve the issue. What does "broke the web interface" mean? If you look in apache's error log, there may be a group mismatch error there. Are you shure the web server runs as user 'apache' and not 'www-data' or something else. Try My web interface works now. It was a Mailman CGI Error! Message. Once I ran ./configure back to using apache it worked. ps -fwwA|egrep '(apache|httpd)' root 14389 14278 0 09:59 pts/1 00:00:00 egrep (apache|httpd) apache 18760 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18761 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18762 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18763 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18764 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18765 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18766 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 18767 21506 0 Sep11 ? 00:00:02 /usr/sbin/httpd apache 20542 21506 0 Sep11 ? 00:00:01 /usr/sbin/httpd root 21506 1 0 Mar15 ? 00:00:07 /usr/sbin/httpd -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/jewel.makda%40washburn.edu From mark at msapiro.net Tue Sep 13 12:39:22 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Sep 2016 09:39:22 -0700 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 In-Reply-To: References: Message-ID: <5ae4e9b3-31d6-1368-85c5-a233b20481ab@msapiro.net> On 09/13/2016 09:02 AM, Jewel Brueggeman-Makda wrote: > Yes, I am running Postfix. The /usr/local/mailman/data/aliases file showed the owner as root and group as mailman. > I ran: chown mailman:mailman aliases and also: chmod g+w > This so far didn't resolve the issue. It is the aliases.db file that MUST be owned (not just group) by 'mailman'. See the DELIVERY RIGHTS section in 'man local' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jewel.brueggeman-makda at washburn.edu Tue Sep 13 13:11:05 2016 From: jewel.brueggeman-makda at washburn.edu (Jewel Brueggeman-Makda) Date: Tue, 13 Sep 2016 17:11:05 +0000 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 In-Reply-To: <5ae4e9b3-31d6-1368-85c5-a233b20481ab@msapiro.net> References: <5ae4e9b3-31d6-1368-85c5-a233b20481ab@msapiro.net> Message-ID: -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Tuesday, September 13, 2016 11:39 AM To: Jewel Brueggeman-Makda ; mailman-users at python.org Subject: Re: [Mailman-Users] Unable to post to list - Command died with status 2 On 09/13/2016 09:02 AM, Jewel Brueggeman-Makda wrote: > Yes, I am running Postfix. The /usr/local/mailman/data/aliases file showed the owner as root and group as mailman. > I ran: chown mailman:mailman aliases and also: chmod g+w > This so far didn't resolve the issue. It is the aliases.db file that MUST be owned (not just group) by 'mailman'. See the DELIVERY RIGHTS section in 'man local' I changed the owner to mailman and reloaded postfix: chown mailman:mailman /usr/local/mailman/data/aliases* chmod g+w /usr/local/mailman/data/aliases* postfix reload I continue to get the same Group Mismatch error: : Command died with status 2: "/usr/local/mailman/mail/mailman post mailman". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mailman", but the system's mail server executed the mail script as group "nobody". Try tweaking the mail server to run the script as group "mailman", or re-run configure, providing the command line option `--with-mail-gid=nobody'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 13 13:45:34 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Sep 2016 10:45:34 -0700 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 In-Reply-To: References: <5ae4e9b3-31d6-1368-85c5-a233b20481ab@msapiro.net> Message-ID: <13B3DEBE-A267-4533-B02B-48A8FEDF3F39@msapiro.net> On September 13, 2016 10:11:05 AM PDT, Jewel Brueggeman-Makda wrote: > >I continue to get the same Group Mismatch error: > >: Command died with status 2: > "/usr/local/mailman/mail/mailman post mailman". Command output: Group >mismatch error. Mailman expected the mail wrapper script to be >executed as >group "mailman", but the system's mail server executed the mail script >as >group "nobody". What's in postfix main.cf alias_maps? Look in those files in the order listed for list aliases. Ensure they are only in Mailman's data/aliases. -- Mark Sapiro Sent from my Not_an_iThing with standards compliant, open source software. From jewel.brueggeman-makda at washburn.edu Wed Sep 14 10:46:35 2016 From: jewel.brueggeman-makda at washburn.edu (Jewel Brueggeman-Makda) Date: Wed, 14 Sep 2016 14:46:35 +0000 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 - RESOLVED Message-ID: Resolved. I had two entries and removed all but the reference to mailman aliases and it worked. I then reloaded postfix. OLD ENTRY: alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases NEW ENTRY: alias_maps - hash:/usr/local/mailman/data/aliases Thank you! -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Tuesday, September 13, 2016 12:46 PM To: Jewel Brueggeman-Makda ; mailman-users at python.org Subject: RE: [Mailman-Users] Unable to post to list - Command died with status 2 On September 13, 2016 10:11:05 AM PDT, Jewel Brueggeman-Makda wrote: > >I continue to get the same Group Mismatch error: > >: Command died with status 2: > "/usr/local/mailman/mail/mailman post mailman". Command output: Group >mismatch error. Mailman expected the mail wrapper script to be >executed as group "mailman", but the system's mail server executed the >mail script as group "nobody". What's in postfix main.cf alias_maps? Look in those files in the order listed for list aliases. Ensure they are only in Mailman's data/aliases. -- Mark Sapiro Sent from my Not_an_iThing with standards compliant, open source software. From mark at msapiro.net Wed Sep 14 11:34:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 14 Sep 2016 08:34:12 -0700 Subject: [Mailman-Users] Unable to post to list - Command died with status 2 - RESOLVED In-Reply-To: References: Message-ID: <24b1c306-c748-55ba-f8a3-a97d9155e8f4@msapiro.net> On 09/14/2016 07:46 AM, Jewel Brueggeman-Makda wrote: > Resolved. I had two entries and removed all but the reference to mailman aliases and it worked. I then reloaded postfix. > OLD ENTRY: alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases > NEW ENTRY: alias_maps - hash:/usr/local/mailman/data/aliases The problem is you had mailman aliases in /etc/aliases and /etc/aliases.db was not owned by mailman. The correct solution is to remove the mailman aliases from /etc/aliases, run 'sudo postalias /etc/aliases' and restore the old alias_maps. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Wed Sep 14 14:09:35 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Wed, 14 Sep 2016 14:09:35 -0400 Subject: [Mailman-Users] subscribe users by email from list admin? Message-ID: Is there any way, in mailman, to subscribe a user (or users) via an email from an email address other than the one being signed up? E.g., I imagine a simple online form, including an email entry field, that fires off an email upon successful submission, that subscribes that user to a list. But I can't set the from: address of this email to the subscriber's address. I can set it to a list-admin address, if that helps. By the way, I realize there are commands in /bin that do the equivalent. As far as I know, I can't easily get the place I have the online form (Wufoo.com) to kick off those commands. Thanks, Matt From mark at msapiro.net Wed Sep 14 18:49:55 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 14 Sep 2016 15:49:55 -0700 Subject: [Mailman-Users] subscribe users by email from list admin? In-Reply-To: References: Message-ID: <3d800933-f116-680b-ab60-c6b0585d6905@msapiro.net> On 09/14/2016 11:09 AM, Matt Morgan wrote: > Is there any way, in mailman, to subscribe a user (or users) via an email > from an email address other than the one being signed up? If you send a 'help' command (Subject: or first body line) to LIST-request at ... the response will include > subscribe [password] [digest|nodigest] [address=
] > Subscribe to this mailing list. Your password must be given to > unsubscribe or change your options, but if you omit the password, one > will be generated for you. You may be periodically reminded of your > password. > > The next argument may be either: `nodigest' or `digest' (no quotes!). > If you wish to subscribe an address other than the address you sent > this request from, you may specify `address=
' (no brackets > around the email address, and no quotes!) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Thu Sep 15 10:15:58 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Thu, 15 Sep 2016 10:15:58 -0400 Subject: [Mailman-Users] subscribe users by email from list admin? In-Reply-To: <3d800933-f116-680b-ab60-c6b0585d6905@msapiro.net> References: <3d800933-f116-680b-ab60-c6b0585d6905@msapiro.net> Message-ID: On Wed, Sep 14, 2016 at 6:49 PM, Mark Sapiro wrote: > On 09/14/2016 11:09 AM, Matt Morgan wrote: > > Is there any way, in mailman, to subscribe a user (or users) via an email > > from an email address other than the one being signed up? > > > If you send a 'help' command (Subject: or first body line) to > LIST-request at ... the response will include > > > subscribe [password] [digest|nodigest] [address=
] > > Subscribe to this mailing list. Your password must be given to > > unsubscribe or change your options, but if you omit the > password, one > > will be generated for you. You may be periodically reminded of > your > > password. > > > > The next argument may be either: `nodigest' or `digest' (no > quotes!). > > If you wish to subscribe an address other than the address you > sent > > this request from, you may specify `address=
' (no > brackets > > around the email address, and no quotes!) > Apologies: I saw that help text and somehow skipped right over the relevant part. Argh. From minxmertzmomo at gmail.com Thu Sep 15 10:32:51 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Thu, 15 Sep 2016 10:32:51 -0400 Subject: [Mailman-Users] subscribe users by email from list admin? In-Reply-To: References: <3d800933-f116-680b-ab60-c6b0585d6905@msapiro.net> Message-ID: On Thu, Sep 15, 2016 at 10:15 AM, Matt Morgan wrote: > On Wed, Sep 14, 2016 at 6:49 PM, Mark Sapiro wrote: > >> On 09/14/2016 11:09 AM, Matt Morgan wrote: >> > Is there any way, in mailman, to subscribe a user (or users) via an >> email >> > from an email address other than the one being signed up? >> >> >> If you send a 'help' command (Subject: or first body line) to >> LIST-request at ... the response will include >> >> > subscribe [password] [digest|nodigest] [address=
] >> > Subscribe to this mailing list. Your password must be given to >> > unsubscribe or change your options, but if you omit the >> password, one >> > will be generated for you. You may be periodically reminded of >> your >> > password. >> > >> > The next argument may be either: `nodigest' or `digest' (no >> quotes!). >> > If you wish to subscribe an address other than the address you >> sent >> > this request from, you may specify `address=
' (no >> brackets >> > around the email address, and no quotes!) >> > > Apologies: I saw that help text and somehow skipped right over the > relevant part. Argh. > At risk of beating a dead horse: now I understand actually I didn't see that text. I read the users and admin guides in the online docs, and this mechanism isn't mentioned. I think it would be worth putting it in the admin guide--some kind of section devoted to programatically subscribing & unsubscribing people. From mark at msapiro.net Thu Sep 15 14:28:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Sep 2016 11:28:12 -0700 Subject: [Mailman-Users] subscribe users by email from list admin? In-Reply-To: References: <3d800933-f116-680b-ab60-c6b0585d6905@msapiro.net> Message-ID: <53036c68-fe43-7fa8-0e4a-f68409f1e6a4@msapiro.net> On 09/15/2016 07:32 AM, Matt Morgan wrote: > > At risk of beating a dead horse: now I understand actually I didn't see > that text. I read the users and admin guides in the online docs, and > this mechanism isn't mentioned. I think it would be worth putting it in > the admin guide--some kind of section devoted to programatically > subscribing & unsubscribing people. I realize that this doesn't address your suggestion, but the members manual contains a note in the 'subscribing' section that says 'Note: Subscribing can be done in other ways as well. See Appendix A for more advanced email subscribing commands.' and Appendix A does contain the full doc of the subscribe command. (I just made the 'Appendix A' reference a link.) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fmouse at fmp.com Thu Sep 15 16:00:16 2016 From: fmouse at fmp.com (Lindsay Haisley) Date: Thu, 15 Sep 2016 15:00:16 -0500 Subject: [Mailman-Users] Status of sibling lists Message-ID: <1473969616.7412.78.camel@fmp.com> I'm running Mailman 2.1.18-1 on a server here. I'm setting up announcement only lists for an organization which logically needs several sibling lists under an umbrella list. I did a Google search for Mailman and sibling lists and most of the information I turned up is years out of date and I'm wondering if any progress has been made on this front. ?Here are some considerations. Only a _single copy_ of posts to the umbrella list should be sent out to members of the?regular_include_lists list of sibling lists, regardless of how many times an address occurs in the several lists included in the configuration - master and include lists - or what the To or CC headers in the original post contain. I understand that this is how regular_include_lists works. >From ?I understand that information about unsubscribing relates to the umbrella list, so that I'm running Mailman 2.1.18-1 on a server here. I'm setting up announcement only lists for an organization which logically needs several sibling lists under an umbrella list. I did a Google search for Mailman and sibling lists and most of the information I turned up is years out of date and I'm wondering if any progress has been made on this front. ?Here are some considerations. Only a _single copy_ of posts to the umbrella list should be sent out to members of the?regular_include_lists list of sibling lists, regardless of how many times an address occurs in the several lists included in the configuration - master and include lists - or what the To or CC headers in the original post contain. I understand that this is how regular_include_lists works. >From ?I understand that information about unsubscribing relates to the umbrella list, so that an unsubscribe request won't percolate down to the sibling list(s) on which the unsubscribing I'm running Mailman 2.1.18-1 on a server here. I'm setting up announcement only lists for an organization which logically needs several sibling lists under an umbrella list. I did a Google search for Mailman and sibling lists and most of the information I turned up is years out of date and I'm wondering if any progress has been made on this front. ?Here are some considerations. Only a _single copy_ of posts to the umbrella list should be sent out to members of the?regular_include_lists list of sibling lists, regardless of how many times an address occurs in the several lists included in the configuration - master and include lists - or what the To or CC headers in the original post contain. I understand that this is how regular_include_lists works. >From ?I understand that information about unsubscribing relates to the umbrella list, so that I'm running Mailman 2.1.18-1 on a server here. I'm setting up announcement only lists for an organization which logically needs several sibling lists under an umbrella list. I did a Google search for Mailman and sibling lists and most of the information I turned up is years out of date and I'm wondering if any progress has been made on this front. ?Here are some considerations. Only a _single copy_ of posts to the umbrella list should be sent out to members of the?regular_include_lists list of sibling lists, regardless of how many times an address occurs in the several lists included in the configuration - master and include lists - or what the To or CC headers in the original post contain. I understand that this is how regular_include_lists works. >From ?I understand that information about unsubscribing on list posts relates to the umbrella list. Ideally, since one of the sibling lists will be a paid-members list, the unsubscribing address should individually be blocked from receiving posts to the master unbrella list without being removed, or disabled in the sibling paid-members (or other) list. Bounce processing should be handled properly so that bouncing addresses are handled correctly and automatic removal of subscriber addresses will percolate down to the sibling lists. How do we stand on this? I could easily do this kind of thing in a relational database setup, and a lot of it with separate lists, scripts and cron jobs, but I'd like to use as much of the native abilities of Mailman as possible. -- Lindsay Haisley | "The first casualty when FMP Computer Services | war comes is truth." 512-259-1190 | http://www.fmp.com | -- Hiram W Johnson From mark at msapiro.net Thu Sep 15 16:40:45 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Sep 2016 13:40:45 -0700 Subject: [Mailman-Users] Status of sibling lists In-Reply-To: <1473969616.7412.78.camel@fmp.com> References: <1473969616.7412.78.camel@fmp.com> Message-ID: <323b0013-457c-16b9-d79e-7d5e7e3decbb@msapiro.net> On 09/15/2016 01:00 PM, Lindsay Haisley wrote: > I'm running Mailman 2.1.18-1 on a server here. I'm setting up > announcement only lists for an organization which logically needs > several sibling lists under an umbrella list. I did a Google search for > Mailman and sibling lists and most of the information I turned up is > years out of date and I'm wondering if any progress has been made on > this front. Here are some considerations. This post was garbled with multiple insertions of the same text in random places. It is also confusing to me because I am unable to determine always whether it is referring to an umbrella list as a list whose members are other lists (the actual definition) or a list with regular_include_lists set up as a pseudo umbrella list. Please repost without the multiple text insertions and with clarification as to what the intended list configuration is. Also, when referring to wiki articles, the TinyURL (e.g. ) is much preferred to a URL like -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Thu Sep 15 16:43:11 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Thu, 15 Sep 2016 16:43:11 -0400 Subject: [Mailman-Users] subscribe users by email from list admin? In-Reply-To: <53036c68-fe43-7fa8-0e4a-f68409f1e6a4@msapiro.net> References: <3d800933-f116-680b-ab60-c6b0585d6905@msapiro.net> <53036c68-fe43-7fa8-0e4a-f68409f1e6a4@msapiro.net> Message-ID: On Thu, Sep 15, 2016 at 2:28 PM, Mark Sapiro wrote: > On 09/15/2016 07:32 AM, Matt Morgan wrote: > > > > At risk of beating a dead horse: now I understand actually I didn't see > > that text. I read the users and admin guides in the online docs, and > > this mechanism isn't mentioned. I think it would be worth putting it in > > the admin guide--some kind of section devoted to programatically > > subscribing & unsubscribing people. > > > I realize that this doesn't address your suggestion, but the members > manual contains a note in the 'subscribing' section that says 'Note: > Subscribing can be done in other ways as well. See Appendix A for more > advanced email subscribing commands.' and Appendix A does contain the > full doc of the subscribe command. (I just made the 'Appendix A' > reference a link.) > Perfect solution, thanks. From fmouse at fmp.com Thu Sep 15 17:35:13 2016 From: fmouse at fmp.com (Lindsay Haisley) Date: Thu, 15 Sep 2016 16:35:13 -0500 Subject: [Mailman-Users] Status of sibling lists In-Reply-To: <323b0013-457c-16b9-d79e-7d5e7e3decbb@msapiro.net> References: <1473969616.7412.78.camel@fmp.com> <323b0013-457c-16b9-d79e-7d5e7e3decbb@msapiro.net> Message-ID: <1473975313.13838.32.camel@fmp.com> On Thu, 2016-09-15 at 13:40 -0700, Mark Sapiro wrote: > On 09/15/2016 01:00 PM, Lindsay Haisley wrote: > > I'm running Mailman 2.1.18-1 on a server here. I'm setting up > > announcement only lists for an organization which logically needs > > several sibling lists under an umbrella list. I did a Google search for > > Mailman and sibling lists and most of the information I turned up is > > years out of date and I'm wondering if any progress has been made on > > this front.? Here are some considerations. > > > This post was garbled with multiple insertions of the same text in > random places. Hmmm. I don't know what happened, Mark. I didn't get a copy so I can't see it. The copy saved (via IMAP) to my mail server looked OK, so the problem may have been with the SMTP transfer. I'll try again. I just copied and pasted the URLs from my browser location widget, but the long URL may have confused my MUA and caused the problem. I didn't see the TinyURL URL. Sorry!! The configuration will be: Master List ("umbrella list") - linked to siblings via regular_include_lists: sibling list 1 sibling list 2 etc. Posts to the Master List will deliver _one_ copy only to each of the subscribers on the several sibling lists, regardless of CCs or duplicate addresses across these lists. I believe this is a feature of regular_include_lists. I understand that unsubscribe instructions on posts distributed via (addressed to) the Master List will be relevant to the Master List, although the address to be "unsubscribed" may exist on one or more sibling lists. Since at least one of the sibling lists will contain the email addresses of dues-paying members, it's necessary that the unsubscribe request be processed on the Master List as an instruction to _not_ distribute to the unsubscribing address rather than as an instruction to unsubscribe the address from any or all sibling lists. Disablement or removal of addresses due to bounces, on the other hand, should propagate to all sibling lists and cause them to be disabled or expunged in every list on which they occur. I hope this is clear this time :) Can Mailman do these things?? -- Lindsay Haisley | "The first casualty when FMP Computer Services | war comes is truth." 512-259-1190 | http://www.fmp.com | -- Hiram W Johnson From mark at msapiro.net Thu Sep 15 18:13:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Sep 2016 15:13:13 -0700 Subject: [Mailman-Users] Status of sibling lists In-Reply-To: <1473975313.13838.32.camel@fmp.com> References: <1473969616.7412.78.camel@fmp.com> <323b0013-457c-16b9-d79e-7d5e7e3decbb@msapiro.net> <1473975313.13838.32.camel@fmp.com> Message-ID: <3e6de5ed-abfa-b36a-5024-0b773e108901@msapiro.net> On 09/15/2016 02:35 PM, Lindsay Haisley wrote: > On Thu, 2016-09-15 at 13:40 -0700, Mark Sapiro wrote: >> >> This post was garbled with multiple insertions of the same text in >> random places. > > Hmmm. I don't know what happened, Mark. I didn't get a copy so I can't > see it. You can see it at > The configuration will be: > > Master List ("umbrella list") - linked to siblings via regular_include_lists: > sibling list 1 > sibling list 2 > etc. > > Posts to the Master List will deliver _one_ copy only to each of the > subscribers on the several sibling lists, regardless of CCs or > duplicate addresses across these lists. I believe this is a feature of > regular_include_lists. That is not completely correct. for example if a post to master list is Ccd to sib1 and sib2, a member of all three lists will receive a copy from each of the three lists for a total of three, but a member of say only sib1 will only receive the one copy from that list. For a post to only master list with no Cc, both the above members will receive only the master list copy. It works like this. The recipient list for the master list post are all the members of the master list plus all the members of those regular_include_lists not also directly addressed in To: or Cc:, but that recipient list is built as a set so there are no duplicates in it. > I understand that unsubscribe instructions on posts distributed via > (addressed to) the Master List will be relevant to the Master List, > although the address to be "unsubscribed" may exist on one or more > sibling lists. Since at least one of the sibling lists will contain the > email addresses of dues-paying members, it's necessary that the > unsubscribe request be processed on the Master List as an instruction > to _not_ distribute to the unsubscribing address rather than as an > instruction to unsubscribe the address from any or all sibling lists. This is not possible for sibling lists. If an address is a member of both the 'master' and one of the regular_include_lists, and it is unsubscribed from the master, it will still be sent copies of posts to the master because of its membership in the included list. There's no way for the master to know that any member of an included list should not be included. > Disablement or removal of addresses due to bounces, on the other hand, > should propagate to all sibling lists and cause them to be disabled or > expunged in every list on which they occur. This doesn't happen either. If a member of an included list is bouncing posts from the master list, the bounce goes to the master list and is ignored because it's for a non-member. > I hope this is clear this time :) > > Can Mailman do these things? It could probably be enhanced to do the things it currently doesn't do, but there are no plans to do so. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fmouse at fmp.com Thu Sep 15 18:40:06 2016 From: fmouse at fmp.com (Lindsay Haisley) Date: Thu, 15 Sep 2016 17:40:06 -0500 Subject: [Mailman-Users] Status of sibling lists In-Reply-To: <3e6de5ed-abfa-b36a-5024-0b773e108901@msapiro.net> References: <1473969616.7412.78.camel@fmp.com> <323b0013-457c-16b9-d79e-7d5e7e3decbb@msapiro.net> <1473975313.13838.32.camel@fmp.com> <3e6de5ed-abfa-b36a-5024-0b773e108901@msapiro.net> Message-ID: On 09/15/2016 05:13 PM, Mark Sapiro wrote: > It works like this. The recipient list for the master list post are all > the members of the master list plus all the members of those > regular_include_lists not also directly addressed in To: or Cc:, but > that recipient list is built as a set so there are no duplicates in it. Actually, that works fine. Posters to the lists will be BoD members and educated volunteers who will have instructions. All other posters will have their posts silently sent to the cosmic bit bucket. >> I understand that unsubscribe instructions on posts distributed via >> (addressed to) the Master List will be relevant to the Master List, >> although the address to be "unsubscribed" may exist on one or more >> sibling lists. Since at least one of the sibling lists will contain the >> email addresses of dues-paying members, it's necessary that the >> unsubscribe request be processed on the Master List as an instruction >> to _not_ distribute to the unsubscribing address rather than as an >> instruction to unsubscribe the address from any or all sibling lists. > > This is not possible for sibling lists. If an address is a member of > both the 'master' and one of the regular_include_lists, and it is > unsubscribed from the master, it will still be sent copies of posts to > the master because of its membership in the included list. There's no > way for the master to know that any member of an included list should > not be included. This is turning into a relational database exercise :) There are creative ways to deal with it outside of Mailman and I can figure it out. withlist may be my friend here. >> Can Mailman do these things? > > > It could probably be enhanced to do the things it currently doesn't do, > but there are no plans to do so. Mailman very kindly provides most of the hooks necessary to do a lot of processing outside of the Mailman environment. One thing that would be useful would be an option in Mailman to execute an arbitrary program or callback each time an action is taken, such as every time a name is subscribed or unsubscribed. This would could be used to trigger any external processing scripts. Thanks for your response. -- Lindsay Haisley | "We have met the enemy and he is us." FMP Computer Services | 512-259-1190 | -- Pogo http://www.fmp.com | From mark at msapiro.net Thu Sep 15 18:47:37 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Sep 2016 15:47:37 -0700 Subject: [Mailman-Users] Status of sibling lists In-Reply-To: References: <1473969616.7412.78.camel@fmp.com> <323b0013-457c-16b9-d79e-7d5e7e3decbb@msapiro.net> <1473975313.13838.32.camel@fmp.com> <3e6de5ed-abfa-b36a-5024-0b773e108901@msapiro.net> Message-ID: <154353cd-e01e-3693-ab3b-a70dc23f18bd@msapiro.net> On 09/15/2016 03:40 PM, Lindsay Haisley wrote: > > One thing that would be useful would be an option in Mailman to execute > an arbitrary program or callback each time an action is taken, such as > every time a name is subscribed or unsubscribed. This would could be > used to trigger any external processing scripts. This mechanism exists in Mailman 3. It is not likely to be added to Mailman 2.x. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From limperis at cti.gr Fri Sep 16 05:58:15 2016 From: limperis at cti.gr (Limperis Antonis) Date: Fri, 16 Sep 2016 09:58:15 +0000 Subject: [Mailman-Users] Mailman archive creation problem Message-ID: Hello mailman users We have a mailman version 2.1.22 installation. We try to reconstruct a mail list archive with command 'arch --wipe listname' and receive the following error. #00000 ????????????? ????????? ???? ?????????? ??????????? 2013-February Pickling archive state into /var/mailman/archives/private/tenders/pipermail.pck Traceback (most recent call last): File "/var/mailman/bin/arch", line 201, in main() File "/var/mailman/bin/arch", line 189, in main archiver.processUnixMailbox(fp, start, end) File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox Is there some suggestion or experience on this problem? Thank you, for your attention. ?Antonis Limperis ? From mark at msapiro.net Fri Sep 16 11:30:30 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 16 Sep 2016 08:30:30 -0700 Subject: [Mailman-Users] Mailman archive creation problem In-Reply-To: References: Message-ID: <4b3936a2-fab1-95fa-81fe-dd4cdc75e7d1@msapiro.net> On 09/16/2016 02:58 AM, Limperis Antonis wrote: > > Hello mailman users > > We have a mailman version 2.1.22 installation. > We try to reconstruct a mail list archive with command 'arch --wipe listname' and receive the following error. > > #00000 > ????????????? ????????? ???? > ?????????? ??????????? There seems to be some character encoding issue here, but ... > 2013-February Pickling archive state into /var/mailman/archives/private/tenders/pipermail.pck > Traceback (most recent call last): > File "/var/mailman/bin/arch", line 201, in > main() > File "/var/mailman/bin/arch", line 189, in main > archiver.processUnixMailbox(fp, start, end) > File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox This traceback is incomplete. Please post the complete traceback, and if possible, the correct rendering of the ????????????? ????????? ???? ... stuff. Or is that perhaps some garbled rendering of ???????? ?????? ????????? ??????? Also, is other stuff missing. I.e., is there more between "2013-February" and "Pickling archive state into ..." Normally, I would expect three lines like #nnnnnn figuring article archives yyyy-Month for each message in the mbox followed by something like Updating index files for archive [yyyy-Month] Date Subject Author Thread Computing threaded index Updating HTML for article n1 Updating HTML for article n2 ... for each month in the archive and then finally, the Pickling archive state into ... line. I really need the complete traceback to begin to say more. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mmlists at ds-gmbh.de Sat Sep 17 17:52:17 2016 From: mmlists at ds-gmbh.de (Martin Schulte) Date: Sat, 17 Sep 2016 23:52:17 +0200 Subject: [Mailman-Users] State of the ARC Message-ID: <20160917235217.1667d7079bdc21f638480a45@ds-gmbh.de> Hello, in the archives of the developer mailing list I read that there have been efforts to implement the Authenticated Received Chain (ARC) Protocol in Mailman. Can anyone tell me about the state of this? Thanks a lot for all the work you are doing, Martin From eko.budiharto at gmail.com Sun Sep 18 02:05:59 2016 From: eko.budiharto at gmail.com (Eko Budiharto) Date: Sun, 18 Sep 2016 13:05:59 +0700 Subject: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail Message-ID: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> dear all, I have a list using mailman. It cannot send mails to yahoo, hotmail and gmail. I check all setting in the mailman, but I still cannot find the problem yet. Please help me if someone who ever experience like this. I am looking forward to a favorable reply from you. Thank you. regards, Eko From mark at msapiro.net Sun Sep 18 11:19:55 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 18 Sep 2016 08:19:55 -0700 Subject: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail In-Reply-To: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> References: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> Message-ID: <670e8920-15dc-81d4-78c2-bed9ad2183dc@msapiro.net> On 09/17/2016 11:05 PM, Eko Budiharto wrote: > dear all, > I have a list using mailman. It cannot send mails to yahoo, hotmail and gmail. I check all setting in the mailman, but I still cannot find the problem yet. Please help me if someone who ever experience like this. It's hard to tell without more information such as bounce messages or log messages, but this could be a DMARC issue. See and . It is also possible your server is on one or more blacklists. Check at, e.g., Also see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From guest2 at sgeinc.com Sun Sep 18 11:26:53 2016 From: guest2 at sgeinc.com (Richard Shetron) Date: Sun, 18 Sep 2016 11:26:53 -0400 Subject: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail In-Reply-To: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> References: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> Message-ID: <07e6f399-827d-9cad-e91c-911e77b54886@sgeinc.com> The problem is more likely in the MTA rather then mailman. Have you checked the mailman logs? Do you have access to the MTA logs? Have you tried sending an email outside of mailman? Do you know aht the MTA is? common ones include postfix, sendmail, qmail, and exim. On 9/18/2016 2:05 AM, Eko Budiharto wrote: > dear all, > I have a list using mailman. It cannot send mails to yahoo, hotmail and gmail. I check all setting in the mailman, but I still cannot find the problem yet. Please help me if someone who ever experience like this. > > I am looking forward to a favorable reply from you. Thank you. > > regards, > Eko > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com > From timothy.d at jasionow.ski Sun Sep 18 11:39:27 2016 From: timothy.d at jasionow.ski (Timothy Jasionowski) Date: Sun, 18 Sep 2016 17:39:27 +0200 Subject: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail In-Reply-To: <670e8920-15dc-81d4-78c2-bed9ad2183dc@msapiro.net> References: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> <670e8920-15dc-81d4-78c2-bed9ad2183dc@msapiro.net> Message-ID: You may also want to make sure that you're configured SPF for your domain... I know that Google can be suspicious of new or small domains unless SPF (or even DKIM) is implemented. SPF is easy to implement. You just need to put a TXT entry into DNS. Timothy Sent from my iPhone > On Sep 18, 2016, at 17:19, Mark Sapiro wrote: > >> On 09/17/2016 11:05 PM, Eko Budiharto wrote: >> dear all, >> I have a list using mailman. It cannot send mails to yahoo, hotmail and gmail. I check all setting in the mailman, but I still cannot find the problem yet. Please help me if someone who ever experience like this. > > > It's hard to tell without more information such as bounce messages or > log messages, but this could be a DMARC issue. See > and . > > It is also possible your server is on one or more blacklists. Check at, > e.g., > > Also see . > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski From turnbull.stephen.fw at u.tsukuba.ac.jp Sun Sep 18 23:51:16 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Mon, 19 Sep 2016 12:51:16 +0900 Subject: [Mailman-Users] State of the ARC In-Reply-To: <20160917235217.1667d7079bdc21f638480a45@ds-gmbh.de> References: <20160917235217.1667d7079bdc21f638480a45@ds-gmbh.de> Message-ID: <22495.24756.983015.733593@turnbull.sk.tsukuba.ac.jp> Martin Schulte writes: > in the archives of the developer mailing list I read that there > have been efforts to implement the Authenticated Received Chain > (ARC) Protocol in Mailman. Then that's where you should be asking about it. It hasn't been mentioned on this list because it's not ready for prime time, and may never be (see below). That said, it's a GSoC project. The protocol implementation is complete, and Mailman integration is well along, but it has not yet been tested against other implementations for interoperability. This is for Mailman 3 only. Most of the code is quite independent of Mailman, so could probably be installed as a Handler in Mailman 2, but we have made no effort in that direction, and probably won't. However, this implementation is really just a proof of concept. You not want to be implementing this protocol in Mailman if you can possibly avoid it. You want to be doing it in your MTA because Mailman can't validate SPF (it will always be receiving mail from localhost, not the remote boundary system). Worse, it requires rather high privileges on the host system. You need access to the DNS to provide public keys to verify the signatures you add, and to the private keys to add those signatures. These are the same keys used for DKIM signatures, which means Mailman can be used to impersonate any user of that system. As far as I know, taking over Mailman to that extent is pretty much as difficult as taking over the MTA itself, but why double the attack surface? Note that this is *different* from the argument against doing spam- checking in Mailman. Spam-checking is Mailman is inefficient and less friendly to the mail system compared to doing it in the MTA, but the risks involved are just those of doing a poor job of spam-checking (including backscatter, etc). This facility gives new powers to the successful attacker. From andy.goldzweig at oswego.edu Sun Sep 18 20:56:04 2016 From: andy.goldzweig at oswego.edu (Andy Goldzweig) Date: Sun, 18 Sep 2016 20:56:04 -0400 Subject: [Mailman-Users] members mail is getting marked rejected Message-ID: in the vette log I see: LISTNAME: Refused posting: From: MEMBER at MYDOMAIN Subject: SUBJECT Reason: Your message was deemed inappropriate by the moderator. This person is a member of the list. The sender filter for moderated members is hold So why is the message getting rejected? How else can I track down what is causing this so I can help the user to send a 'good' message? Andy From turnbull.stephen.fw at u.tsukuba.ac.jp Mon Sep 19 10:49:55 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Mon, 19 Sep 2016 23:49:55 +0900 Subject: [Mailman-Users] members mail is getting marked rejected In-Reply-To: References: Message-ID: <22495.64275.450013.896237@turnbull.sk.tsukuba.ac.jp> Andy Goldzweig writes: > in the vette log I see: > LISTNAME: Refused posting: > From: MEMBER at MYDOMAIN > Subject: SUBJECT > Reason: Your message was deemed inappropriate by the moderator. > This person is a member of the list. > The sender filter for moderated members is hold > So why is the message getting rejected? The first guess is: A moderator rejected it, as the "Reason" says. This can happen inadvertantly if there are a lot of spam messages. Second guess: A moderator set the user to be rejected. Check the user's membership screen. This can also happen inadvertantly to a member, if a moderator accidentally ticks the wrong boxes on the moderation screen. Third guess: The message fell afoul of a different privacy filter. Note that the privacy filter can be triggered on "hidden" content, such as HTML tags and header fields that are not displayed by typical user agents. This kind of thing is reported occasionally, and it's always a matter of local configuration or moderator action, at least for the last decade that I can remember. But maybe Mark has some additional avenues you can explore. From apadmaraju at guidewire.com Mon Sep 19 14:29:05 2016 From: apadmaraju at guidewire.com (Anilkumar Padmaraju) Date: Mon, 19 Sep 2016 18:29:05 +0000 Subject: [Mailman-Users] Checking the Database Message-ID: Where can I check which Database our mailman server is using. As per the link https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html our mailman server does not have file /etc/mailman.cfg On our mailman server dir is under /usr/local/mailman and has below dirs. archives cron lists mail pythonlib spam unsubscribes.log bin data locks Mailman qfiles templates cgi-bin icons logs messages scripts tests The mailman.cfg is not in that dir as well. Is there any other file I need to check to see which database it is using. Thank you, Anil. From mark at msapiro.net Mon Sep 19 21:35:43 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 19 Sep 2016 18:35:43 -0700 Subject: [Mailman-Users] Checking the Database In-Reply-To: References: Message-ID: On 09/19/2016 11:29 AM, Anilkumar Padmaraju wrote: > > As per the link https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html our mailman server does not have file /etc/mailman.cfg This document describes Mailman 3. > On our mailman server dir is under /usr/local/mailman and has below dirs. > archives cron lists mail pythonlib spam unsubscribes.log > bin data locks Mailman qfiles templates > cgi-bin icons logs messages scripts tests > > The mailman.cfg is not in that dir as well. Is there any other file I need to check to see which database it is using. Your installation is Mailman 2.1. Mailman 2.1, at least as distributed, does not use a database. All persistent data for a list is in a Python pickle at lists/LISTNAME/config.pck. There are 3rd party add-ons to use LDAP or MySQL for membership data, but you almost certainly aren'tusing either of those. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From apadmaraju at guidewire.com Mon Sep 19 21:58:14 2016 From: apadmaraju at guidewire.com (Anilkumar Padmaraju) Date: Tue, 20 Sep 2016 01:58:14 +0000 Subject: [Mailman-Users] Checking the Database In-Reply-To: References: Message-ID: Thank you, Mark! We have over 100 lists in our mailman server, out of those 10 lists we are moving to another application and seeing how to move. The mails are archived under /usr/local/mailman/archives/public//. Under that directory there is database directory containing files like below. How that is related to lists/LISTNAME/config.pck or any advice on moving this database files to that new application. 2016-September-article 2016-September-author 2016-September-date 2016-September-subject 2016-September-thread Thank you, Anil. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+apadmaraju=guidewire.com at python.org] On Behalf Of Mark Sapiro Sent: Monday, September 19, 2016 6:36 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Checking the Database On 09/19/2016 11:29 AM, Anilkumar Padmaraju wrote: > > As per the link > https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html our > mailman server does not have file /etc/mailman.cfg This document describes Mailman 3. > On our mailman server dir is under /usr/local/mailman and has below dirs. > archives cron lists mail pythonlib spam unsubscribes.log > bin data locks Mailman qfiles templates > cgi-bin icons logs messages scripts tests > > The mailman.cfg is not in that dir as well. Is there any other file I need to check to see which database it is using. Your installation is Mailman 2.1. Mailman 2.1, at least as distributed, does not use a database. All persistent data for a list is in a Python pickle at lists/LISTNAME/config.pck. There are 3rd party add-ons to use LDAP or MySQL for membership data, but you almost certainly aren'tusing either of those. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/apadmaraju%40guidewire.com From mark at msapiro.net Mon Sep 19 23:44:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 19 Sep 2016 20:44:12 -0700 Subject: [Mailman-Users] members mail is getting marked rejected In-Reply-To: References: Message-ID: <79fddfca-fbe9-56b2-40d1-eb404c30b2d0@msapiro.net> On 09/18/2016 05:56 PM, Andy Goldzweig wrote: > in the vette log I see: > LISTNAME: Refused posting: > From: MEMBER at MYDOMAIN > Subject: SUBJECT > Reason: Your message was deemed inappropriate by the moderator. > This person is a member of the list. > The sender filter for moderated members is hold > So why is the message getting rejected? If there is a preceding message in the vette log saying this message was held, it was rejected by moderator action. If not, there are only a couple of possibilities. The most likely is it is an HTML only post, the list's content filtering doesn't accept HTML and filter_action is Reject. Note that convert_html_to_plaintext = Yes doesn't happen unless you also accept text/html in pass_mime_types. Otherwise, the message may match a header_filter_rules rule with reject action. There are other possibilities, but they are unlikely in this case. However, the log message you quote above is in the format written when a moderator rejects the post and not in the format written when a post is automatically rejected by a handler. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 20 00:51:49 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 19 Sep 2016 21:51:49 -0700 Subject: [Mailman-Users] Checking the Database In-Reply-To: References: Message-ID: <16d5e98e-663c-9a9b-59f3-a9c44a6c6c7e@msapiro.net> On 09/19/2016 06:58 PM, Anilkumar Padmaraju wrote: > > The mails are archived under /usr/local/mailman/archives/public//. Under that directory there is database directory containing files like below. How that is related to lists/LISTNAME/config.pck or any advice on moving this database files to that new application. > 2016-September-article > 2016-September-author > 2016-September-date > 2016-September-subject > 2016-September-thread The archives a separate thing. The important things are lists/LISTNAME/config.pck which has all the list configuration and membership info. archives/private/LISTNAME/* which is the pipermail archives for the list archives/private/LISTNAME.mbox/LISTNAME.mbox which is a cumulative mbox containing all archived posts and which can be used to rebuild the pipermail archive. For info on moving lists and archives, see and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From apadmaraju at guidewire.com Mon Sep 19 21:20:10 2016 From: apadmaraju at guidewire.com (Anilkumar Padmaraju) Date: Tue, 20 Sep 2016 01:20:10 +0000 Subject: [Mailman-Users] Checking the Database Message-ID: Can you please let me know regarding below email on how to check which database it is using. Thank you, Anil. From: Anilkumar Padmaraju Sent: Monday, September 19, 2016 11:29 AM To: 'mailman-users at python.org' Subject: Checking the Database Where can I check which Database our mailman server is using. As per the link https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html our mailman server does not have file /etc/mailman.cfg On our mailman server dir is under /usr/local/mailman and has below dirs. archives cron lists mail pythonlib spam unsubscribes.log bin data locks Mailman qfiles templates cgi-bin icons logs messages scripts tests The mailman.cfg is not in that dir as well. Is there any other file I need to check to see which database it is using. Thank you, Anil. From mark at msapiro.net Tue Sep 20 12:15:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 20 Sep 2016 09:15:53 -0700 Subject: [Mailman-Users] Checking the Database In-Reply-To: References: Message-ID: <6171de4f-9e4a-8ea5-e14c-2aa7abd86365@msapiro.net> On 09/19/2016 06:20 PM, Anilkumar Padmaraju wrote: > Can you please let me know regarding below email on how to check which database it is using. What part of the reply at do you not understand? If you are referring to files in archives/private/LISTNAME/, these are all files built and maintained by the pipermail archiver. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gao at pztop.com Tue Sep 20 13:53:20 2016 From: gao at pztop.com (Gao) Date: Tue, 20 Sep 2016 10:53:20 -0700 Subject: [Mailman-Users] Wrong "From" in header, Why? Message-ID: Hi, I have a strange thing happened and I could not figure it out what is going on. Here is what happened: 1. Syd V sent an email to our mailing list sjv-geosupport at mydomain.com 2. Trent replied to the list 3. All list members received Trent's reply, BUT with wrong FROM address. It appears Trent's reply is from Syd. ??? 4. I talked to Trent and asked him to do another reply to list, and this time everything is correct. He can not re-produce this error. I post the header section from Trent's reply as well as the maillog here. I am using mailman 2.1.15 on a CentOS7+Postfix. Could someone give me some hints on how this happened and how to fix it? Thanks. Gao ================ header: ---------------- Return-Path: X-Original-To: gao at mydomain.com Delivered-To: gao at mydomain.com Received: by zeta.mydomain.com (Postfix, from userid 5001) id D92DA2015FD6E; Tue, 20 Sep 2016 09:18:18 -0700 (PDT) Received: from zeta.mydomain.com (localhost [IPv6:::1]) by zeta.mydomain.com (Postfix) with ESMTP id E3B7120158EC5; Tue, 20 Sep 2016 09:18:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.com; s=szeta; t=1474388291; bh=tiwZ4VEiU1RZzIFTSx2DZbnLAXPUQDkUd1sc9ss5YiM=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To; b=jq8Dilf8Kcjca3CTkC/LVSrii3G2RTO6z6TYQXPhWWqDlM1Q0DNS3WSco0TgV6PPY 7p/AObLxO/cOyvDbtf9ejQ7XDTipWhCicV7Qq/7fi+7q2J9p/xPqIweTqci0gBeIQR sXE1AvP7V7e94W+FGQoYsBnQBV6jmHsGo4shrRp4= X-Original-To: sjv-geosupport at zeta.mydomain.com Delivered-To: sjv-geosupport at zeta.mydomain.com Received: by zeta.mydomain.com (Postfix, from userid 5001) id EB63E20158EC6; Tue, 20 Sep 2016 09:18:04 -0700 (PDT) Received: from [192.168.123.87] (vpn.mydomain.com [111.111.111.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by zeta.mydomain.com (Postfix) with ESMTPSA id 36FFF20158EC6 for ; Tue, 20 Sep 2016 09:18:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.com; s=szeta; t=1474388282; bh=ABUiYP5lz8c1gfzYye+PUoTjcGicHkgvhh6PstHMBZ4=; h=From:Subject:Reply-To:To:Date; b=tHH79YeXgMzTwDugmsEGJ6yIIaTYOjjbse4jy1P99gW8AE7cvd8SEWqiC/xEcShZc RlvFvIrL3Bub8w7RfL+4k+JURE0YHRIhKlEx4LHo+TSic2tBEY06oXUrZuvQEMcn3T r9VpzkEcV5BWytqZgYvxRarJOv7Huh2vP8LuZBGE= From: Syd V To: sjv-geosupport at mydomain.com Message-ID: Date: Tue, 20 Sep 2016 09:17:56 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------677E4034B35AA62A233129E2" X-mydomain-MailScanner: Found to be clean, Found to be clean X-mydomain-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-6.095, required 4, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10), not spam, SpamAssassin (not cached, score=-6.095, required 4, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) X-Spam-Status: No, No Subject: [Sjv-geosupport] Update on timing and instrumentation files X-BeenThere: sjv-geosupport at mydomain.com X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Syd Visser Errors-To: sjv-geosupport-bounces at mydomain.com Sender: "Sjv-geosupport" X-mydomain-MailScanner-Information: Please contact the IT Administrator for more information X-mydomain-MailScanner-ID: E3B7120158EC5.ABE01 X-mydomain-MailScanner-From: sjv-geosupport-bounces at mydomain.com ============================= maillog: ----------------------------- Sep 20 09:18:02 zeta postfix/smtpd[24662]: connect from vpn.mydomain.com[111.111.111.111] Sep 20 09:18:02 zeta postfix/smtpd[24662]: Anonymous TLS connection established from vpn.mydomain.com[111.111.111.111]: TLSv1.2 with ciphe r ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Sep 20 09:18:02 zeta postfix/smtpd[24662]: 36FFF20158EC6: client=vpn.mydomain.com[111.111.111.111], sasl_method=PLAIN, sasl_username=trent at mydomain.com Sep 20 09:18:02 zeta postfix/cleanup[24538]: 36FFF20158EC6: hold: header Received: from [192.168.123.87] (vpn.mydomain.com [111.111.111.111])??(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))??(No client certificate requested)??by zeta.mydomain. from vpn.mydomain.com[111.111.111.111]; from= to= proto=ESMTP helo=<[192.168.123.87]> Sep 20 09:18:02 zeta postfix/cleanup[24538]: 36FFF20158EC6: message-id= Sep 20 09:18:02 zeta opendkim[3099]: 36FFF20158EC6: DKIM-Signature field added (s=szeta, d=mydomain.com) Sep 20 09:18:02 zeta postfix/smtpd[24662]: disconnect from vpn.mydomain.com[111.111.111.111] Sep 20 09:18:02 zeta MailScanner[20657]: New Batch: Scanning 1 messages, 18122 bytes Sep 20 09:18:02 zeta MailScanner[20657]: Virus and Content Scanning: Starting Sep 20 09:18:02 zeta MailScanner[20657]: Spam Checks: Starting Sep 20 09:18:04 zeta MailScanner[20657]: Message 36FFF20158EC6.A07F8 from 111.111.111.111 (trent at mydomain.com) to mydomain.com is not spam, SpamAssassin (not cached, score=-6.095, required 4, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) Sep 20 09:18:04 zeta MailScanner[20657]: Requeue: 36FFF20158EC6.A07F8 to 3603320158ECB Sep 20 09:18:04 zeta postfix/qmgr[6820]: 3603320158ECB: from=, size=16818, nrcpt=1 (queue active) Sep 20 09:18:04 zeta MailScanner[20657]: Uninfected: Delivered 1 messages Sep 20 09:18:04 zeta MailScanner[20657]: Deleted 1 messages from processing-database Sep 20 09:18:04 zeta MailScanner[20657]: Logging message 36FFF20158EC6.A07F8 to SQL Sep 20 09:18:04 zeta MailScanner[22108]: 36FFF20158EC6.A07F8: Logged to MailWatch SQL Sep 20 09:18:04 zeta postfix/pickup[21381]: EB63E20158EC6: uid=5001 from= Sep 20 09:18:04 zeta postfix/pipe[24825]: 3603320158ECB: to=, orig_to=, relay=autoresponder, delay=2.7, delays=2.7/0/0/0.02, dsn=2.0.0, status=sent (delivered via autoresponder service) Sep 20 09:18:04 zeta postfix/qmgr[6820]: 3603320158ECB: removed Sep 20 09:18:04 zeta postfix/cleanup[24407]: EB63E20158EC6: hold: header Received: by zeta.mydomain.com (Postfix, from userid 5001)??id EB63E20158EC6; Tue, 20 Sep 2016 09:18:04 -0700 (PDT) from local; from= to= Sep 20 09:18:04 zeta postfix/cleanup[24407]: EB63E20158EC6: message-id= Sep 20 09:18:10 zeta MailScanner[22098]: New Batch: Scanning 1 messages, 18148 bytes Sep 20 09:18:10 zeta MailScanner[22098]: Requeue: EB63E20158EC6.A4FB8 to BE0D320158ECB Sep 20 09:18:10 zeta MailScanner[22098]: Unscanned: Delivered 1 messages Sep 20 09:18:10 zeta postfix/qmgr[6820]: BE0D320158ECB: from=, size=17844, nrcpt=1 (queue active) Sep 20 09:18:10 zeta MailScanner[22098]: Spam Checks: Starting Sep 20 09:18:10 zeta MailScanner[22098]: Deleted 1 messages from processing-database Sep 20 09:18:10 zeta MailScanner[22098]: Logging message EB63E20158EC6.A4FB8 to SQL Sep 20 09:18:10 zeta MailScanner[22108]: EB63E20158EC6.A4FB8: Logged to MailWatch SQL Sep 20 09:18:10 zeta postfix/local[25085]: BE0D320158ECB: to=, relay=local, delay=5.5, delays=5.4/0.01/0/0.1, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post sjv-geosupport) Sep 20 09:18:10 zeta postfix/qmgr[6820]: BE0D320158ECB: removed Sep 20 09:18:11 zeta postfix/smtpd[24800]: connect from localhost[::1] Sep 20 09:18:11 zeta postfix/smtpd[24800]: E3B7120158EC5: client=localhost[::1] Sep 20 09:18:11 zeta postfix/cleanup[24538]: E3B7120158EC5: hold: header Received: from zeta.mydomain.com (localhost [IPv6:::1])??by zeta.mydomain.com (Postfix) with ESMTP id E3B7120158EC5;??Tue, 20 Sep 2016 09:18:11 -0700 (PDT) from localhost[::1]; from= to= proto=ESMTP helo= Sep 20 09:18:11 zeta postfix/cleanup[24538]: E3B7120158EC5: message-id= Sep 20 09:18:11 zeta opendkim[3099]: E3B7120158EC5: DKIM-Signature field added (s=szeta, d=mydomain.com) Sep 20 09:18:12 zeta postfix/smtpd[24800]: disconnect from localhost[::1] Sep 20 09:18:16 zeta MailScanner[22098]: Virus and Content Scanning: Starting Sep 20 09:18:16 zeta MailScanner[22098]: Spam Checks: Starting Sep 20 09:18:16 zeta MailScanner[22098]: Message E3B7120158EC5.ABE01 from ::1 (sjv-geosupport-bounces at mydomain.com) ignored whitelist, had 33 recipients (>20) Sep 20 09:18:18 zeta MailScanner[22098]: Message E3B7120158EC5.ABE01 from ::1 (sjv-geosupport-bounces at mydomain.com) to mydomain.com is not spam, SpamAssassin (not cached, score=-6.095, required 4, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) Sep 20 09:18:18 zeta MailScanner[22098]: Requeue: E3B7120158EC5.ABE01 to 0233620158EC0 Sep 20 09:18:18 zeta MailScanner[22098]: Uninfected: Delivered 1 messages Sep 20 09:18:18 zeta postfix/qmgr[6820]: 0233620158EC0: from=, size=19224, nrcpt=33 (queue active) Sep 20 09:18:18 zeta MailScanner[22098]: Deleted 1 messages from processing-database ..... From turnbull.stephen.fw at u.tsukuba.ac.jp Tue Sep 20 14:47:41 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Wed, 21 Sep 2016 03:47:41 +0900 Subject: [Mailman-Users] Wrong "From" in header, Why? In-Reply-To: References: Message-ID: <22497.33869.371364.7302@turnbull.sk.tsukuba.ac.jp> This almost certainly has nothing to do with Mailman, if I'm reading the spamassassin reports correctly. It says that the DKIM signature validated on the way out of Mailman, which means that the From that you all received is the From that Trent sent. Gao writes: > Hi, > > I have a strange thing happened and I could not figure it out what is going on. Here is what happened: > 1. Syd V sent an email to our mailing list sjv-geosupport at mydomain.com > 2. Trent replied to the list > 3. All list members received Trent's reply, BUT with wrong FROM address. It appears Trent's reply is from Syd. ??? > 4. I talked to Trent and asked him to do another reply to list, and this time everything is correct. He can not re-produce this error. > > I post the header section from Trent's reply as well as the maillog here. > > I am using mailman 2.1.15 on a CentOS7+Postfix. > > Could someone give me some hints on how this happened and how to fix it? > > Thanks. > > Gao > > ================ > header: > ---------------- > Return-Path: > X-Original-To: gao at mydomain.com > Delivered-To: gao at mydomain.com > Received: by zeta.mydomain.com (Postfix, from userid 5001) > id D92DA2015FD6E; Tue, 20 Sep 2016 09:18:18 -0700 (PDT) > Received: from zeta.mydomain.com (localhost [IPv6:::1]) > by zeta.mydomain.com (Postfix) with ESMTP id E3B7120158EC5; > Tue, 20 Sep 2016 09:18:11 -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.com; > s=szeta; t=1474388291; > bh=tiwZ4VEiU1RZzIFTSx2DZbnLAXPUQDkUd1sc9ss5YiM=; > h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: > List-Post:List-Help:List-Subscribe:Reply-To; > b=jq8Dilf8Kcjca3CTkC/LVSrii3G2RTO6z6TYQXPhWWqDlM1Q0DNS3WSco0TgV6PPY > 7p/AObLxO/cOyvDbtf9ejQ7XDTipWhCicV7Qq/7fi+7q2J9p/xPqIweTqci0gBeIQR > sXE1AvP7V7e94W+FGQoYsBnQBV6jmHsGo4shrRp4= > X-Original-To: sjv-geosupport at zeta.mydomain.com > Delivered-To: sjv-geosupport at zeta.mydomain.com > Received: by zeta.mydomain.com (Postfix, from userid 5001) > id EB63E20158EC6; Tue, 20 Sep 2016 09:18:04 -0700 (PDT) > Received: from [192.168.123.87] (vpn.mydomain.com [111.111.111.111]) > (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) > (No client certificate requested) > by zeta.mydomain.com (Postfix) with ESMTPSA id 36FFF20158EC6 > for ; Tue, 20 Sep 2016 09:18:02 -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mydomain.com; > s=szeta; t=1474388282; > bh=ABUiYP5lz8c1gfzYye+PUoTjcGicHkgvhh6PstHMBZ4=; > h=From:Subject:Reply-To:To:Date; > b=tHH79YeXgMzTwDugmsEGJ6yIIaTYOjjbse4jy1P99gW8AE7cvd8SEWqiC/xEcShZc > RlvFvIrL3Bub8w7RfL+4k+JURE0YHRIhKlEx4LHo+TSic2tBEY06oXUrZuvQEMcn3T > r9VpzkEcV5BWytqZgYvxRarJOv7Huh2vP8LuZBGE= > From: Syd V > To: sjv-geosupport at mydomain.com > Message-ID: > Date: Tue, 20 Sep 2016 09:17:56 -0700 > User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 > Thunderbird/45.2.0 > MIME-Version: 1.0 > Content-Type: multipart/mixed; boundary="------------677E4034B35AA62A233129E2" > X-mydomain-MailScanner: Found to be clean, Found to be clean > X-mydomain-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, > score=-6.095, required 4, autolearn=not spam, ALL_TRUSTED -1.00, > BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, > DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10), not spam, SpamAssassin (not cached, > score=-6.095, required 4, ALL_TRUSTED -1.00, BAYES_00 -1.90, > DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, > HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) > X-Spam-Status: No, No > Subject: [Sjv-geosupport] Update on timing and instrumentation files > X-BeenThere: sjv-geosupport at mydomain.com > X-Mailman-Version: 2.1.15 > Precedence: list > List-Id: > List-Unsubscribe: , > > List-Archive: > List-Post: > List-Help: > List-Subscribe: , > > Reply-To: Syd Visser > Errors-To: sjv-geosupport-bounces at mydomain.com > Sender: "Sjv-geosupport" > X-mydomain-MailScanner-Information: Please contact the IT Administrator for more information > X-mydomain-MailScanner-ID: E3B7120158EC5.ABE01 > X-mydomain-MailScanner-From: sjv-geosupport-bounces at mydomain.com > > > ============================= > maillog: > ----------------------------- > Sep 20 09:18:02 zeta postfix/smtpd[24662]: connect from vpn.mydomain.com[111.111.111.111] > Sep 20 09:18:02 zeta postfix/smtpd[24662]: Anonymous TLS connection established from vpn.mydomain.com[111.111.111.111]: TLSv1.2 with ciphe > r ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) > Sep 20 09:18:02 zeta postfix/smtpd[24662]: 36FFF20158EC6: client=vpn.mydomain.com[111.111.111.111], sasl_method=PLAIN, sasl_username=trent at mydomain.com > Sep 20 09:18:02 zeta postfix/cleanup[24538]: 36FFF20158EC6: hold: header Received: from [192.168.123.87] (vpn.mydomain.com [111.111.111.111])??(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))??(No client certificate requested)??by zeta.mydomain. from vpn.mydomain.com[111.111.111.111]; from= to= proto=ESMTP helo=<[192.168.123.87]> > Sep 20 09:18:02 zeta postfix/cleanup[24538]: 36FFF20158EC6: message-id= > Sep 20 09:18:02 zeta opendkim[3099]: 36FFF20158EC6: DKIM-Signature field added (s=szeta, d=mydomain.com) > Sep 20 09:18:02 zeta postfix/smtpd[24662]: disconnect from vpn.mydomain.com[111.111.111.111] > Sep 20 09:18:02 zeta MailScanner[20657]: New Batch: Scanning 1 messages, 18122 bytes > Sep 20 09:18:02 zeta MailScanner[20657]: Virus and Content Scanning: Starting > Sep 20 09:18:02 zeta MailScanner[20657]: Spam Checks: Starting > Sep 20 09:18:04 zeta MailScanner[20657]: Message 36FFF20158EC6.A07F8 from 111.111.111.111 (trent at mydomain.com) to mydomain.com is not spam, SpamAssassin (not cached, score=-6.095, required 4, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) > Sep 20 09:18:04 zeta MailScanner[20657]: Requeue: 36FFF20158EC6.A07F8 to 3603320158ECB > Sep 20 09:18:04 zeta postfix/qmgr[6820]: 3603320158ECB: from=, size=16818, nrcpt=1 (queue active) > Sep 20 09:18:04 zeta MailScanner[20657]: Uninfected: Delivered 1 messages > Sep 20 09:18:04 zeta MailScanner[20657]: Deleted 1 messages from processing-database > Sep 20 09:18:04 zeta MailScanner[20657]: Logging message 36FFF20158EC6.A07F8 to SQL > Sep 20 09:18:04 zeta MailScanner[22108]: 36FFF20158EC6.A07F8: Logged to MailWatch SQL > Sep 20 09:18:04 zeta postfix/pickup[21381]: EB63E20158EC6: uid=5001 from= > Sep 20 09:18:04 zeta postfix/pipe[24825]: 3603320158ECB: to=, orig_to=, relay=autoresponder, delay=2.7, delays=2.7/0/0/0.02, dsn=2.0.0, status=sent (delivered via autoresponder service) > Sep 20 09:18:04 zeta postfix/qmgr[6820]: 3603320158ECB: removed > Sep 20 09:18:04 zeta postfix/cleanup[24407]: EB63E20158EC6: hold: header Received: by zeta.mydomain.com (Postfix, from userid 5001)??id EB63E20158EC6; Tue, 20 Sep 2016 09:18:04 -0700 (PDT) from local; from= to= > Sep 20 09:18:04 zeta postfix/cleanup[24407]: EB63E20158EC6: message-id= > Sep 20 09:18:10 zeta MailScanner[22098]: New Batch: Scanning 1 messages, 18148 bytes > Sep 20 09:18:10 zeta MailScanner[22098]: Requeue: EB63E20158EC6.A4FB8 to BE0D320158ECB > Sep 20 09:18:10 zeta MailScanner[22098]: Unscanned: Delivered 1 messages > Sep 20 09:18:10 zeta postfix/qmgr[6820]: BE0D320158ECB: from=, size=17844, nrcpt=1 (queue active) > Sep 20 09:18:10 zeta MailScanner[22098]: Spam Checks: Starting > Sep 20 09:18:10 zeta MailScanner[22098]: Deleted 1 messages from processing-database > Sep 20 09:18:10 zeta MailScanner[22098]: Logging message EB63E20158EC6.A4FB8 to SQL > Sep 20 09:18:10 zeta MailScanner[22108]: EB63E20158EC6.A4FB8: Logged to MailWatch SQL > Sep 20 09:18:10 zeta postfix/local[25085]: BE0D320158ECB: to=, relay=local, delay=5.5, delays=5.4/0.01/0/0.1, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post sjv-geosupport) > Sep 20 09:18:10 zeta postfix/qmgr[6820]: BE0D320158ECB: removed > Sep 20 09:18:11 zeta postfix/smtpd[24800]: connect from localhost[::1] > Sep 20 09:18:11 zeta postfix/smtpd[24800]: E3B7120158EC5: client=localhost[::1] > Sep 20 09:18:11 zeta postfix/cleanup[24538]: E3B7120158EC5: hold: header Received: from zeta.mydomain.com (localhost [IPv6:::1])??by zeta.mydomain.com (Postfix) with ESMTP id E3B7120158EC5;??Tue, 20 Sep 2016 09:18:11 -0700 (PDT) from localhost[::1]; from= to= proto=ESMTP helo= > Sep 20 09:18:11 zeta postfix/cleanup[24538]: E3B7120158EC5: message-id= > Sep 20 09:18:11 zeta opendkim[3099]: E3B7120158EC5: DKIM-Signature field added (s=szeta, d=mydomain.com) > Sep 20 09:18:12 zeta postfix/smtpd[24800]: disconnect from localhost[::1] > Sep 20 09:18:16 zeta MailScanner[22098]: Virus and Content Scanning: Starting > Sep 20 09:18:16 zeta MailScanner[22098]: Spam Checks: Starting > Sep 20 09:18:16 zeta MailScanner[22098]: Message E3B7120158EC5.ABE01 from ::1 (sjv-geosupport-bounces at mydomain.com) ignored whitelist, had 33 recipients (>20) > Sep 20 09:18:18 zeta MailScanner[22098]: Message E3B7120158EC5.ABE01 from ::1 (sjv-geosupport-bounces at mydomain.com) to mydomain.com is not spam, SpamAssassin (not cached, score=-6.095, required 4, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) > Sep 20 09:18:18 zeta MailScanner[22098]: Requeue: E3B7120158EC5.ABE01 to 0233620158EC0 > Sep 20 09:18:18 zeta MailScanner[22098]: Uninfected: Delivered 1 messages > Sep 20 09:18:18 zeta postfix/qmgr[6820]: 0233620158EC0: from=, size=19224, nrcpt=33 (queue active) > Sep 20 09:18:18 zeta MailScanner[22098]: Deleted 1 messages from processing-database > ..... > > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/turnbull.stephen.fw%40u.tsukuba.ac.jp > > From mark at msapiro.net Tue Sep 20 14:48:22 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 20 Sep 2016 11:48:22 -0700 Subject: [Mailman-Users] Wrong "From" in header, Why? In-Reply-To: References: Message-ID: <4fff1b17-8215-3063-26ff-1f211da78f73@msapiro.net> On 09/20/2016 10:53 AM, Gao wrote: > > I have a strange thing happened and I could not figure it out what is > going on. Here is what happened: > 1. Syd V sent an email to our mailing list > sjv-geosupport at mydomain.com > 2. Trent replied to the list > 3. All list members received Trent's reply, BUT with wrong FROM address. > It appears Trent's reply is from Syd. ??? > 4. I talked to Trent and asked him to do another reply to list, and this > time everything is correct. He can not re-produce this error. > > I post the header section from Trent's reply as well as the maillog here. It is clear from your maillog that the message received with queue ID 36FFF20158EC6 was sent (envelope from) from trent, but this says nothing about the headers in the body of the message. The headers in the body have From: and Reply-To: as 'Syd V ' and 'Syd Visser ' respectively. Since I can think of no way that Mailman would rewrite these headers and even if it did, I would think the two headers would have the same display name, I have to think the somehow Trent's MUA (Thunderbird/45.2.0) is responsible. I can't say how this happened, but I think the message arrived with those headers, and even if they were somehow changed in your server, there are other, more likely suspects than Mailman. >From your mail log, I see the message arrives with ID 36FFF20158EC6, is scanned by MailScanner, requeued with ID 3603320158ECB and '(delivered via autoresponder service)'. Then a message is received, presumably from the autoresponder service, with ID EB63E20158EC6, scanned by MailScanner, requeued with ID BE0D320158ECB and delivered to Mailman. I.e., the message has been through MailScanner twice and "autoresponder service" before it ever gets to Mailman. Both 36FFF20158EC6.A07F8 and EB63E20158EC6.A4FB8 were logged to MailWatch. I don't use MailWatch and don't know what's in those logs, but perhaps there is a clue there. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 20 15:07:26 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 20 Sep 2016 12:07:26 -0700 Subject: [Mailman-Users] Wrong "From" in header, Why? In-Reply-To: <22497.33869.371364.7302@turnbull.sk.tsukuba.ac.jp> References: <22497.33869.371364.7302@turnbull.sk.tsukuba.ac.jp> Message-ID: <91c0652c-ca2c-aadd-2304-ed3e9d6206fc@msapiro.net> On 09/20/2016 11:47 AM, Stephen J. Turnbull wrote: > This almost certainly has nothing to do with Mailman, if I'm reading > the spamassassin reports correctly. It says that the DKIM signature > validated on the way out of Mailman, which means that the From that > you all received is the From that Trent sent. I agree with the conclusion, but DKIM doesn't prove it. There are two DKIN signatures in the headers and they were both added by the Mailman server. The first > Sep 20 09:18:02 zeta opendkim[3099]: 36FFF20158EC6: DKIM-Signature field added (s=szeta, d=mydomain.com) added to the inbound message before MailScanner and delivery via "autoresponder service". This one validated > Sep 20 09:18:04 zeta MailScanner[20657]: Message 36FFF20158EC6.A07F8 from 111.111.111.111 (trent at mydomain.com) to mydomain.com is not spam, SpamAssassin (not cached, score=-6.095, required 4, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) but it was added after the message was received. The second > Sep 20 09:18:11 zeta opendkim[3099]: E3B7120158EC5: DKIM-Signature field added (s=szeta, d=mydomain.com) was added after Mailman but before MailScanner on the outbound message and it also validated > Sep 20 09:18:18 zeta MailScanner[22098]: Message E3B7120158EC5.ABE01 from ::1 (sjv-geosupport-bounces at mydomain.com) to mydomain.com is not spam, SpamAssassin (not cached, score=-6.095, required 4, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, RP_MATCHES_RCVD -3.10) But both these signatures were validated almost immediately after they were locally added, so they really say nothing about the headers in the message as originally sent. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gao at pztop.com Tue Sep 20 15:42:33 2016 From: gao at pztop.com (Gao) Date: Tue, 20 Sep 2016 12:42:33 -0700 Subject: [Mailman-Users] Wrong "From" in header, Why? In-Reply-To: <4fff1b17-8215-3063-26ff-1f211da78f73@msapiro.net> References: <4fff1b17-8215-3063-26ff-1f211da78f73@msapiro.net> Message-ID: <59292e49-f108-59b1-5477-72458e353adb@pztop.com> On 2016-09-20 11:48 AM, Mark Sapiro wrote: > > Since I can think of no way that Mailman would rewrite these headers and > even if it did, I would think the two headers would have the same > display name, I have to think the somehow Trent's MUA > (Thunderbird/45.2.0) is responsible. I can't say how this happened, but > I think the message arrived with those headers, and even if they were > somehow changed in your server, there are other, more likely suspects > than Mailman. I thought this too but Trent can't re-produce this issue through the same Thunderbird while I watched him made the 2nd reply to list. So I ruled out Thunderbird. > From your mail log, I see the message arrives with ID 36FFF20158EC6, is > scanned by MailScanner, requeued with ID 3603320158ECB and '(delivered > via autoresponder service)'. Then a message is received, presumably from > the autoresponder service, with ID EB63E20158EC6, scanned by > MailScanner, requeued with ID BE0D320158ECB and delivered to Mailman. > > I.e., the message has been through MailScanner twice and "autoresponder > service" before it ever gets to Mailman. autoresponse is a perl script which postfix pipe in to handle vacation replies. I know it is not a perfect solution and no longer supported. But I've use this for quite a while without issue, until today. > Both 36FFF20158EC6.A07F8 and EB63E20158EC6.A4FB8 were logged to > MailWatch. I don't use MailWatch and don't know what's in those logs, > but perhaps there is a clue there. > What MailWatch does is just get information from maillog and save in mysql, then present as web page report. In this case MailWatch correctly shows the email is from Trent. I also looked mailman log files: [root at zeta mailman]# grep "Sep 20 09:18" post Sep 20 09:18:12 2016 (2929) post to sjv-geosupport from sydv at mydomain.com, size=18655, message-id=, success [root at zeta mailman]# grep "Sep 20 09:18" smtp Sep 20 09:18:12 2016 (2929) smtp to sjv-geosupport for 33 recips, completed in 0.131 seconds So I see here in log file "post" it's already from Syd. If MailMan did not change the header, then I think the autoreponse script is highly suspicious. My problem now is I can't re-produce this. In fact, we have other people(include me) replied Syd's original email, all seems correct. Thank you for the help. Gao From mark at msapiro.net Tue Sep 20 16:43:43 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 20 Sep 2016 13:43:43 -0700 Subject: [Mailman-Users] Wrong "From" in header, Why? In-Reply-To: <59292e49-f108-59b1-5477-72458e353adb@pztop.com> References: <4fff1b17-8215-3063-26ff-1f211da78f73@msapiro.net> <59292e49-f108-59b1-5477-72458e353adb@pztop.com> Message-ID: <707dbd27-8e2d-0189-d298-ce17fe079a5c@msapiro.net> On 09/20/2016 12:42 PM, Gao wrote: >> > What MailWatch does is just get information from maillog and save in > mysql, then present as web page report. In this case MailWatch correctly > shows the email is from Trent. But if it's getting the info from maillog, it is only seeing the envelope from, not the From: header, so this doesn't indicate that the incoming From: is Trent. > I also looked mailman log files: > [root at zeta mailman]# grep "Sep 20 09:18" post > Sep 20 09:18:12 2016 (2929) post to sjv-geosupport from > sydv at mydomain.com, size=18655, > message-id=, success ... > So I see here in log file "post" it's already from Syd. If MailMan did > not change the header, then I think the autoreponse script is highly > suspicious. Actually, the post log entry is written as the message is sent from Mailman, the same time as the smtp log entry, so this really only says MailScanner didn't do it on the way out. > My problem now is I can't re-produce this. In fact, we have other > people(include me) replied Syd's original email, all seems correct. > > Thank you for the help. Yes, problems that can't be reproduced are hard to diagnose, but I a as certain as I can be that Mailman didn't do this, and I am fairly familiar with MailScanner, and I don't think it did it either. I still think the most likely thing is the message arrived that way at your server, but I can't say how that happened. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From limperis at cti.gr Tue Sep 20 23:36:21 2016 From: limperis at cti.gr (Limperis Antonis) Date: Wed, 21 Sep 2016 03:36:21 +0000 Subject: [Mailman-Users] Mailman archive creation problem In-Reply-To: <4b3936a2-fab1-95fa-81fe-dd4cdc75e7d1@msapiro.net> References: <4b3936a2-fab1-95fa-81fe-dd4cdc75e7d1@msapiro.net> Message-ID: Hello mark This is the complete trace: [root at mailman ~]# /var/mailman/bin/arch --wipe testlist #00000 <002f01c4a17b$0e714490$c7eb3fc2 at avgoulea> ???????? ?????? ????????? ??????? 2004-September #00001 <24BA97B6F4C0E84999709C650C255C2E604D92 at amfithea.cti.gr> ???????? ?????? ????????? ??????? 2004-September ???????? ??? ??????? ????????? ??? ?? ???????? ?????? [2004-September] Date Subject Author ????????? ????????? ??????? ??????????? ??? ???????????? ???????? ??? HTML ??? ?? ????? 0 Pickling archive state into /var/mailman/archives/private/testlist/pipermail.pck Traceback (most recent call last): File "/var/mailman/bin/arch", line 201, in main() File "/var/mailman/bin/arch", line 189, in main archiver.processUnixMailbox(fp, start, end) File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox self.add_article(a) File "/var/mailman/Mailman/Archiver/pipermail.py", line 640, in add_article author = fixAuthor(article.decoded['author']) File "/var/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor while i>0 and (L[i-1][0] in lowercase or UnicodeDecodeError: 'ascii' codec can't decode byte 0xdc in position 26: ordinal not in range(128) I found that the reconstruction works properly if set locale to el_GR.utf8 with " export LC_ALL=el_GR.utf8". The original system locale environment was: LANG=el_GR.ISO8859-7 LC_CTYPE=el_GR.ISO8859-7 LC_NUMERIC=el_GR.ISO8859-7 LC_TIME=el_GR.ISO8859-7 LC_COLLATE=el_GR.ISO8859-7 LC_MONETARY=el_GR.ISO8859-7 LC_MESSAGES=C LC_PAPER="el_GR.ISO8859-7" LC_NAME="el_GR.ISO8859-7" LC_ADDRESS="el_GR.ISO8859-7" LC_TELEPHONE="el_GR.ISO8859-7" LC_MEASUREMENT="el_GR.ISO8859-7" LC_IDENTIFICATION="el_GR.ISO8859-7" LC_ALL= Thank you for your attention. Antonis -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+limperis=cti.gr at python.org] On Behalf Of Mark Sapiro Sent: Friday, September 16, 2016 6:31 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Mailman archive creation problem On 09/16/2016 02:58 AM, Limperis Antonis wrote: > > Hello mailman users > > We have a mailman version 2.1.22 installation. > We try to reconstruct a mail list archive with command 'arch --wipe listname' and receive the following error. > > #00000 > ????????????? ????????? ???? > ?????????? ??????????? There seems to be some character encoding issue here, but ... > 2013-February Pickling archive state into /var/mailman/archives/private/tenders/pipermail.pck > Traceback (most recent call last): > File "/var/mailman/bin/arch", line 201, in > main() > File "/var/mailman/bin/arch", line 189, in main > archiver.processUnixMailbox(fp, start, end) > File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox This traceback is incomplete. Please post the complete traceback, and if possible, the correct rendering of the ????????????? ????????? ???? ... stuff. Or is that perhaps some garbled rendering of ???????? ?????? ????????? ??????? Also, is other stuff missing. I.e., is there more between "2013-February" and "Pickling archive state into ..." Normally, I would expect three lines like #nnnnnn figuring article archives yyyy-Month for each message in the mbox followed by something like Updating index files for archive [yyyy-Month] Date Subject Author Thread Computing threaded index Updating HTML for article n1 Updating HTML for article n2 ... for each month in the archive and then finally, the Pickling archive state into ... line. I really need the complete traceback to begin to say more. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/limperis%40cti.gr From mark at msapiro.net Wed Sep 21 02:30:54 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 20 Sep 2016 23:30:54 -0700 Subject: [Mailman-Users] Mailman archive creation problem In-Reply-To: References: <4b3936a2-fab1-95fa-81fe-dd4cdc75e7d1@msapiro.net> Message-ID: <3df906e1-7e42-8e53-a8fe-096200e64a46@msapiro.net> On 09/20/2016 08:36 PM, Limperis Antonis wrote: > Traceback (most recent call last): > File "/var/mailman/bin/arch", line 201, in > main() > File "/var/mailman/bin/arch", line 189, in main > archiver.processUnixMailbox(fp, start, end) > File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox > self.add_article(a) > File "/var/mailman/Mailman/Archiver/pipermail.py", line 640, in add_article > author = fixAuthor(article.decoded['author']) > File "/var/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor > while i>0 and (L[i-1][0] in lowercase or > UnicodeDecodeError: 'ascii' codec can't decode byte 0xdc in position 26: ordinal not in range(128) Pipermail is trying to canonicalize the display name in the From: header of a message into "Last, First" form and it is trying to see if the initial character of a "word" in the name is in the string of lower case characters for the locale. At this point, the name is a unicode and Python is trying to decode the "lowercase" string to unicode for the comparison. For some reason, the "lowercase" string appears to be iso-8859-7, but the decoding is being done as if it were ascii. > I found that the reconstruction works properly if set locale to el_GR.utf8 with " export LC_ALL=el_GR.utf8". > The original system locale environment was: > > LANG=el_GR.ISO8859-7 > LC_CTYPE=el_GR.ISO8859-7 > LC_NUMERIC=el_GR.ISO8859-7 > LC_TIME=el_GR.ISO8859-7 > LC_COLLATE=el_GR.ISO8859-7 > LC_MONETARY=el_GR.ISO8859-7 > LC_MESSAGES=C > LC_PAPER="el_GR.ISO8859-7" > LC_NAME="el_GR.ISO8859-7" > LC_ADDRESS="el_GR.ISO8859-7" > LC_TELEPHONE="el_GR.ISO8859-7" > LC_MEASUREMENT="el_GR.ISO8859-7" > LC_IDENTIFICATION="el_GR.ISO8859-7" > LC_ALL= I'm guessing that Python is confused because most of the locale stuff is "el_GR.ISO8859-7", but LC_ALL is not. In any case, it appears you have solved the problem by "export LC_ALL=el_GR.utf8". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From apadmaraju at guidewire.com Tue Sep 20 14:28:53 2016 From: apadmaraju at guidewire.com (Anilkumar Padmaraju) Date: Tue, 20 Sep 2016 18:28:53 +0000 Subject: [Mailman-Users] Checking the Database In-Reply-To: <16d5e98e-663c-9a9b-59f3-a9c44a6c6c7e@msapiro.net> References: <16d5e98e-663c-9a9b-59f3-a9c44a6c6c7e@msapiro.net> Message-ID: Thank you, Mark. This information is helpful. Does /usr/local/mailman/archives/private/LISTNAME/database/ is also pipermail archives. The directory name says database, so not sure what database is it. I see below files under that database directory: 2016-September-article 2016-September-author 2016-September-date 2016-September-subject 2016-September-thread Regards, Anil. -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Monday, September 19, 2016 9:52 PM To: Anilkumar Padmaraju ; mailman-users at python.org Subject: Re: [Mailman-Users] Checking the Database On 09/19/2016 06:58 PM, Anilkumar Padmaraju wrote: > > The mails are archived under /usr/local/mailman/archives/public//. Under that directory there is database directory containing files like below. How that is related to lists/LISTNAME/config.pck or any advice on moving this database files to that new application. > 2016-September-article > 2016-September-author > 2016-September-date > 2016-September-subject > 2016-September-thread The archives a separate thing. The important things are lists/LISTNAME/config.pck which has all the list configuration and membership info. archives/private/LISTNAME/* which is the pipermail archives for the list archives/private/LISTNAME.mbox/LISTNAME.mbox which is a cumulative mbox containing all archived posts and which can be used to rebuild the pipermail archive. For info on moving lists and archives, see and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From clare at catspaw.plus.com Wed Sep 21 12:26:20 2016 From: clare at catspaw.plus.com (Clare Redstone) Date: Wed, 21 Sep 2016 17:26:20 +0100 Subject: [Mailman-Users] Name or address showing in cc header? Message-ID: <001301d21424$e78d48e0$b6a7daa0$@catspaw.plus.com> I administer a Mailman discussion group and don't understand what's showing up in the CC box of messages in the group. One member is concerned as her messages display her email address in the CC box. For most of us, our name is displayed in the CC box. (In Outlook I can right-click on that and it shows the sender's email address but I don't think she realised our addresses are accessible, just not so obvious.) Why are her messages behaving differently in this way and how can I change it? I wondered whether it was to do with whether members had registered with both their names and email addresses. But when I looked in membership management, some people have a name showing in the box below their email address & others don't. Whether or not their messages display name or address doesn't seem related to this setting. I don't understand all the list settings fully so not sure which might be relevant to working out what's going on, so here are a few settings I thought might be relevant. To keep discussion in the group instead of branching out privately, replies go to the group, not to the sender. And group discussion can become confusing if the senders aren't identified. "Replace the From: header address with the list's posting address to mitigate issues stemming from the original From: domain's DMARC or similar policies.." Setting: Munge From "Hide the sender of a message, replacing it with the list address." Setting: No "Should any existing Reply-To: header found in the original message be stripped?..." Setting: Yes "Where are replies to list messages directed?..." Setting: This list Any ideas what's going on and how to stop this member's address displaying openly? Thanks. Clare From mark at msapiro.net Wed Sep 21 13:39:18 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 21 Sep 2016 10:39:18 -0700 Subject: [Mailman-Users] Name or address showing in cc header? In-Reply-To: <001301d21424$e78d48e0$b6a7daa0$@catspaw.plus.com> References: <001301d21424$e78d48e0$b6a7daa0$@catspaw.plus.com> Message-ID: <7b9f3023-2327-8009-ae06-111f286776e6@msapiro.net> On 09/21/2016 09:26 AM, Clare Redstone wrote: > I administer a Mailman discussion group and don't understand what's showing > up in the CC box of messages in the group. One member is concerned as her > messages display her email address in the CC box. For most of us, our name > is displayed in the CC box. (In Outlook I can right-click on that and it > shows the sender's email address but I don't think she realised our > addresses are accessible, just not so obvious.) Probably, what's in the Cc: header in all cases is something like Real Name or maybe just rn at example.com How this is displayed by the email program reading the mail is a function of that program (Outlook or whatever). > Why are her messages behaving differently in this way and how can I change > it? ... > "Replace the From: header address with the list's posting address to > mitigate issues stemming from the original From: domain's DMARC or similar > policies.." Setting: Munge From ... > "Where are replies to list messages directed?..." Setting: This list > > > > Any ideas what's going on and how to stop this member's address displaying > openly? When from_is_list = Munge From, the original From: header is replaced by From: user_name via list_name and the original From: is placed in Reply-To: or since Mailman 2.1.19, if reply_goes_to_list = This list, in Cc: to expose the original sender's address and facilitate replying to that address. I suspect the difference in this user's case is that for her posts, here original From: header has just her email address rather than her name and address, so just the bare email address gets put in Cc: Also note, that from_is_list = Munge From is currently deprecated in favor of from_is_list = No, and Privacy options... -> Sender filters -> dmarc_moderation_action = Munge From. This will apply DMARC mitigations only to those mesages From: a domain that publishes a DMARC p=reject (or quarantine) policy. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 21 13:46:15 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 21 Sep 2016 10:46:15 -0700 Subject: [Mailman-Users] Name or address showing in cc header? In-Reply-To: <7b9f3023-2327-8009-ae06-111f286776e6@msapiro.net> References: <001301d21424$e78d48e0$b6a7daa0$@catspaw.plus.com> <7b9f3023-2327-8009-ae06-111f286776e6@msapiro.net> Message-ID: On 09/21/2016 10:39 AM, Mark Sapiro wrote: > > I suspect the difference in this user's case is that for her posts, here > original From: header has just her email address rather than her name > and address, so just the bare email address gets put in Cc: That should have said "her original From:", rather than "here original From:", but more importantly, if the above is correct, the solution is for her to set her own email program so it sends her messages From: Her Name rather than From: user at example.com -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Thu Sep 22 21:58:29 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Thu, 22 Sep 2016 21:58:29 -0400 Subject: [Mailman-Users] illegible message in moderation approval queue Message-ID: I have a message in a moderation queue. It's from a member (everyone is moderated on this list) so I think it's not spam or other junk. But when I click to review it, it's not legible. This is all I see in the message excerpt: IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ I feel like I've seen other messages that look encoded/illegible in moderation, though I don't have other examples right now. What can cause this? For what it's worth, the sender is a speaker of a language that uses a different character set, so if that's possible cause, that might be the reason here. Thanks, Matt From bryan at skiblack.com Thu Sep 22 22:05:49 2016 From: bryan at skiblack.com (Bryan Blackwell) Date: Thu, 22 Sep 2016 22:05:49 -0400 Subject: [Mailman-Users] illegible message in moderation approval queue In-Reply-To: References: Message-ID: On Sep 22, 2016, at 9:58 PM, Matt Morgan wrote: > > I have a message in a moderation queue. It's from a member (everyone is > moderated on this list) so I think it's not spam or other junk. But when I > click to review it, it's not legible. This is all I see in the message > excerpt: > > IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ > > I feel like I've seen other messages that look encoded/illegible in > moderation, though I don't have other examples right now. What can cause > this? > > For what it's worth, the sender is a speaker of a language that uses a > different character set, so if that's possible cause, that might be the > reason here. > Hi Matt, Sometimes it's the encoding. Selecting "Additionally, forward this message" and sending it to yourself for review can be very helpful. Of course, it's also possible it's got a forged address and is spam/malware. --Bryan From guest2 at sgeinc.com Thu Sep 22 22:59:25 2016 From: guest2 at sgeinc.com (Richard Shetron) Date: Thu, 22 Sep 2016 22:59:25 -0400 Subject: [Mailman-Users] illegible message in moderation approval queue In-Reply-To: References: Message-ID: <57E49A8D.1030107@sgeinc.com> From a quick look, it looks like base64 encoding. Invented back in the dialup/uucp days when transport was not always 8bit clean so things were encoded to make sure only transportable characters were used. On 9/22/2016 9:58 PM, Matt Morgan wrote: > I have a message in a moderation queue. It's from a member (everyone is > moderated on this list) so I think it's not spam or other junk. But when I > click to review it, it's not legible. This is all I see in the message > excerpt: > > IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ > > I feel like I've seen other messages that look encoded/illegible in > moderation, though I don't have other examples right now. What can cause > this? > > For what it's worth, the sender is a speaker of a language that uses a > different character set, so if that's possible cause, that might be the > reason here. > > Thanks, > Matt > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com > From johnl at taugh.com Thu Sep 22 23:40:25 2016 From: johnl at taugh.com (John Levine) Date: 23 Sep 2016 03:40:25 -0000 Subject: [Mailman-Users] illegible message in moderation approval queue In-Reply-To: <57E49A8D.1030107@sgeinc.com> Message-ID: <20160923034025.99977.qmail@ary.lan> In article <57E49A8D.1030107 at sgeinc.com> you write: > From a quick look, it looks like base64 encoding. Invented back in the >dialup/uucp days when transport was not always 8bit clean so things were >encoded to make sure only transportable characters were used. Well, actually, we uucp users used something called uuencode, and base64 was invented for Internet MIME messages in the 1990s. But if you can forward the message to your mail program, it can probably decode the base64 and you can see what it is. Your hint about the different character set is spot on, that's likely why it's base64 encoded. R's, John > >On 9/22/2016 9:58 PM, Matt Morgan wrote: >> I have a message in a moderation queue. It's from a member (everyone is >> moderated on this list) so I think it's not spam or other junk. But when I >> click to review it, it's not legible. This is all I see in the message >> excerpt: >> >> IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ >> >> I feel like I've seen other messages that look encoded/illegible in >> moderation, though I don't have other examples right now. What can cause >> this? >> >> For what it's worth, the sender is a speaker of a language that uses a >> different character set, so if that's possible cause, that might be the >> reason here. From mark at msapiro.net Fri Sep 23 02:34:00 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 22 Sep 2016 23:34:00 -0700 Subject: [Mailman-Users] illegible message in moderation approval queue In-Reply-To: References: Message-ID: <83d014f0-15b6-e245-dbf4-1f1495da3d25@msapiro.net> On 09/22/2016 06:58 PM, Matt Morgan wrote: > I have a message in a moderation queue. It's from a member (everyone is > moderated on this list) so I think it's not spam or other junk. But when I > click to review it, it's not legible. This is all I see in the message > excerpt: > > IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ Others have given advice as to how to see the decoded message. I just want to point out that this is a bug that was fixed in Mailman 2.1.14 (6 years ago). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Fri Sep 23 09:43:13 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Fri, 23 Sep 2016 09:43:13 -0400 Subject: [Mailman-Users] illegible message in moderation approval queue In-Reply-To: <83d014f0-15b6-e245-dbf4-1f1495da3d25@msapiro.net> References: <83d014f0-15b6-e245-dbf4-1f1495da3d25@msapiro.net> Message-ID: On Fri, Sep 23, 2016 at 2:34 AM, Mark Sapiro wrote: > On 09/22/2016 06:58 PM, Matt Morgan wrote: > > I have a message in a moderation queue. It's from a member (everyone is > > moderated on this list) so I think it's not spam or other junk. But when > I > > click to review it, it's not legible. This is all I see in the message > > excerpt: > > > > IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ > > > Others have given advice as to how to see the decoded message. I just > want to point out that this is a bug > that was fixed in > Mailman 2.1.14 (6 years ago). Thanks, everyone. Yes, this is an old server I inherited recently, so good call on the version issue. From jewel.brueggeman-makda at washburn.edu Fri Sep 23 17:50:35 2016 From: jewel.brueggeman-makda at washburn.edu (Jewel Brueggeman-Makda) Date: Fri, 23 Sep 2016 21:50:35 +0000 Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain) Message-ID: TGIF Mailman Gurus, My current Mailman 2.1.12 server is lists.washlaw.edu and is running on a RedHat vm. I need to move it onto a new server which already has a new instance of Mailman 2.1.22 also on a RedHat vm. I already ran the ./configure command to be the same setup as the OLD server. I have searched the discussion list archives on the steps and am not fully understanding what needs to be done. Below are the steps I do know I need to take but then I am at a loss. 1. Post Postfix, Apache and Mialman on OLD server and NEW servers 2. Tar up the lists and archives from the mailman directory and copy the tar files to the new server a. tar xvfx /usr/local/mailman/lists b. tar xvfz /usr/local/mailman/archives 3. Untar the lists and archives onto NEW server a. tar -xvf lists.tgz b. tar -xvf archives.tgz c. Run from /usr/local/mailman/bin ./check_perms -f 4. Run newaliases Thanks, Jewel From susanfitzm at gmail.com Fri Sep 23 14:44:53 2016 From: susanfitzm at gmail.com (Susan Fitzmaurice) Date: Fri, 23 Sep 2016 14:44:53 -0400 Subject: [Mailman-Users] Major conflict will resolving hosting of DNU Maiman Message-ID: I hope you guys can help me, when I really am unsure what to even ask. 1. Host A was hosting our website and Mailman lists. 2. Host B/MacHighway was going to host our website and Host A was just going to host the email. This did not work as Mailman evidently requires access to both the website domain and the lists.domain. Host B/Machighway does not have the required software to host Mailman on a shared server. What options do we have? 1. Have Host company A have 2 domains hosted. 1 domain will exist for the sole purpose of making Mailman work. The other domain will be for mail. MacHighway will have the website. 2. Stop using Mailman and use something else. MacHighway will host website. 3. ?????????? Is there any "reseller" for Mailman who can host our Mailman and provide some tech support? I want to continue to use MacHighway. They provide amazing tech support to a person like me who gets way in over the head on tech stuff. Thanks, Susan From mark at msapiro.net Sat Sep 24 12:06:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Sep 2016 09:06:40 -0700 Subject: [Mailman-Users] Major conflict will resolving hosting of DNU Maiman In-Reply-To: References: Message-ID: On 09/23/2016 11:44 AM, Susan Fitzmaurice wrote: > > What options do we have? > 1. Have Host company A have 2 domains hosted. 1 domain will exist for the > sole purpose of making Mailman work. The other domain will be for mail. > MacHighway will have the website. That's possible. > 2. Stop using Mailman and use something else. MacHighway will host website. That's also an option, but we are the wrong people to ask about "something else". > 3. ?????????? Is there any "reseller" for Mailman who can host our > Mailman and provide some tech support? Yes. See . Based on their participation on this list, I can recommend EMWD Mailman Hosting, but this is not a negative review of any of the other listed services with which I have little or no experience. > I want to continue to use MacHighway. They provide amazing tech support to > a person like me who gets way in over the head on tech stuff. Possibly you could get them to install or help you install Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Sep 24 12:36:21 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 24 Sep 2016 09:36:21 -0700 Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain) In-Reply-To: References: Message-ID: On 09/23/2016 02:50 PM, Jewel Brueggeman-Makda wrote: > TGIF Mailman Gurus, > > My current Mailman 2.1.12 server is lists.washlaw.edu and is running on a RedHat vm. I need to move it onto a new server which already has a new instance of Mailman 2.1.22 also on a RedHat vm. I already ran the ./configure command to be the same setup as the OLD server. I have searched the discussion list archives on the steps and am not fully understanding what needs to be done. Below are the steps I do know I need to take but then I am at a loss. > > > 1. Post Postfix, Apache and Mialman on OLD server and NEW servers > > 2. Tar up the lists and archives from the mailman directory and copy the tar files to the new server > > a. tar xvfx /usr/local/mailman/lists should be 'tar cpvzf lists.tgz /usr/local/mailman/lists' > b. tar xvfz /usr/local/mailman/archives should be 'tar cpvzf archives.tgz /usr/local/mailman/archives' caveat: do not use the -h/--dereference option because archives/public contains only symlinks, and if it winds up with actual files, they don't get updated. > 3. Untar the lists and archives onto NEW server > > a. tar -xvf lists.tgz > > b. tar -xvf archives.tgz Or instead of 2 and 3, if the two servers can talk to each other, use 'rsync -a'. > c. Run from /usr/local/mailman/bin ./check_perms -f > > 4. Run newaliases You don't need to run newaliases, but you do need to run Mailman's bin/genaliases. Assuming the new server will ultimately be accessed via the old servers mail and web domain names, that's all you need. If domain names will change, you will need to run fix_url after moving the lists. See . And, for the archives, in order to fix URLs to listinfo pages in the archives, the easiest thing is to just move the /usr/local/mailman/archives/private/LIST.mbox/LIST.mbox files and rebuild the pipermail archives with 'bin/arch --wipe' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jhs at berklix.com Sun Sep 25 05:32:54 2016 From: jhs at berklix.com (Julian H. Stacey) Date: Sun, 25 Sep 2016 11:32:54 +0200 Subject: [Mailman-Users] Siblings list usage ? Message-ID: <201609250933.u8P9WsDX087060@fire.js.berklix.net> Hi mailman-users at mail.python.org I recently moved 50 lists from majordomo to mailman (succesfuly, thanks :-). Question: Under majordomo I had various pairs of lists, eg event-announce@ Large list, low traffic, event announcements none but organisers could post. event-org@ Small list, free unmoderated discussion among organisers, all on event-announce@ could post feedback such as event bookings back to organisers. My majordomo list configurationss included: event-announce.config restrict_post = event-org other-event-org .domain-trusted-posters event-org.config restrict_post = event-announce event-org other-event-org \ .domain-trusted-posters On mailman lit configs, On event-announce@ I asserted default moderated bit on all new & existing members of event-announce@, & removed moderated bit on individual organisers. My main problem: No one on event-announce@ can now respond to event-org@ with "Count me in for event! / Who is organiser next week? etc" My lesser problem: When someone joins event-org@ I have to manually remove moderator bit from their personal membership entry in event-announce@ (& re-assert if they leave). Are Sibling lists a solution? How please ?, I've never used them yet. Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From mark at msapiro.net Sun Sep 25 11:10:44 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 25 Sep 2016 08:10:44 -0700 Subject: [Mailman-Users] Siblings list usage ? In-Reply-To: <201609250933.u8P9WsDX087060@fire.js.berklix.net> References: <201609250933.u8P9WsDX087060@fire.js.berklix.net> Message-ID: <6db3b41b-5353-b6be-ed63-e289b7a2d197@msapiro.net> On 09/25/2016 02:32 AM, Julian H. Stacey wrote: > > On mailman lit configs, On event-announce@ I asserted default > moderated bit on all new & existing members of event-announce@, & > removed moderated bit on individual organisers. This is not a secure way to restrict posts to event-announce because anyone can post by spoofing the address of an unmoderated member whose address is known by virtue of having posted to the list. See the sections "How to restrict the list so only authorized persons can post:" and "How to post to the announcement list:" at . However, this may not be viable in your case depending on the logistics of distributing the lists poster password to the authorized posters. > My main problem: > No one on event-announce@ can now respond to event-org@ with > "Count me in for event! / Who is organiser next week? etc" Add '@event-announce' to accept_these_nonmembers of the event-org list. This will allow anyone who is a member of event-announce, and not a member of event-org to post to event.org without moderation. This will not affect event-org posts from a member of event-org. > My lesser problem: > When someone joins event-org@ I have to manually remove moderator > bit from their personal membership entry in event-announce@ (& > re-assert if they leave). You could add @event-org to accept_these_nonmembers of the event-announce list. This would allow any member of event-org to post to event-announce, but it is subject to the same spoofing vulnerability as noted for 'un-moderation', and members of event-org who are not members of event-announce won't receive event-announce posts. > Are Sibling lists a solution? How please ?, I've never used them yet. Sibling lists may help some of this. If you add event-org at ... to regular_include_lists of event-announce that will solve the potential issue of event-org members who are not members of event-announce not receiving event-announce posts. So, there are choices depending on whether or not you are concerned about unauthorized posts to event-announce by spoofing authorized senders. If you aren't concerned: Add '@event-announce' to accept_these_nonmembers of event-org. Add '@event-org' to accept_these_nonmembers of event-announce. Add event-org at ... to regular_include_lists of event-announce. Ensure that anyone who is a member of both event-announce and event-org is not moderated on event-announce or posts to event-announce with an Approved: header. Easiest is to ensure members of event-org aren't members of event-announce. If you are concerned: Add '@event-announce' to accept_these_nonmembers of event-org. Do not add '@event-org' to accept_these_nonmembers of event-announce. Moderate everyone on event-announce and authorized posters can post to event-announce with an Approved: header, instructions for which can be posted to the event-org list if its archives are private. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Sun Sep 25 06:42:21 2016 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Sun, 25 Sep 2016 10:42:21 +0000 Subject: [Mailman-Users] Major conflict will resolving hosting of DNU Maiman In-Reply-To: References: Message-ID: Hi, One option which I always use when hosting Mailman lists is to host lists in a subdomain, i.e, lists.domain.com. This means the website hosting is untouched, and saves the cost of a separate domain. Andrew. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+andrew=hodgsonfamily.org at python.org] On Behalf Of Susan Fitzmaurice Sent: 23 September 2016 19:45 To: mailman-users at python.org Subject: [Mailman-Users] Major conflict will resolving hosting of DNU Maiman I hope you guys can help me, when I really am unsure what to even ask. 1. Host A was hosting our website and Mailman lists. 2. Host B/MacHighway was going to host our website and Host A was just going to host the email. This did not work as Mailman evidently requires access to both the website domain and the lists.domain. Host B/Machighway does not have the required software to host Mailman on a shared server. What options do we have? 1. Have Host company A have 2 domains hosted. 1 domain will exist for the sole purpose of making Mailman work. The other domain will be for mail. MacHighway will have the website. 2. Stop using Mailman and use something else. MacHighway will host website. 3. ?????????? Is there any "reseller" for Mailman who can host our Mailman and provide some tech support? I want to continue to use MacHighway. They provide amazing tech support to a person like me who gets way in over the head on tech stuff. Thanks, Susan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/andrew%40hodgsonfamily.org From fmouse at fmp.com Sun Sep 25 11:48:48 2016 From: fmouse at fmp.com (Lindsay Haisley) Date: Sun, 25 Sep 2016 10:48:48 -0500 Subject: [Mailman-Users] Major conflict will resolving hosting of DNU Maiman In-Reply-To: References: Message-ID: <1474818528.6801.125.camel@fmp.com> FWIW, a subdomain is fully as valid for almost all purposes as its parent SLD.TLD. I can, offhand, think of no exceptions. One of my company's list customers has a commercial website hosted and maintained by a company which specializes in websites for book stores (my customer owns a book store). They very kindly delegated the "lists" subdomain to me in their DNS (A and MX records), and I run a Mailman distribution list on it for my customer. On Sat, 2016-09-24 at 09:06 -0700, Mark Sapiro wrote: > On 09/23/2016 11:44 AM, Susan Fitzmaurice wrote: > > > > > > What options do we have? > > 1. Have Host company A have 2 domains hosted. 1 domain will exist > > for the > > sole purpose of making Mailman work. The other domain will be for > > mail. > > MacHighway will have the website. > That's possible. > > > > > > 2. Stop using Mailman and use something else. MacHighway will host > > website. > That's also an option, but we are the wrong people to ask about > "something else". > > > > > > 3.????????????????Is there any "reseller" for Mailman who can host > > our > > Mailman??and provide some tech support? > Yes. See . > > Based on their participation on this list, I can recommend EMWD > Mailman > Hosting, but this is not a negative review of any of the other listed > services with which I have little or no experience. > > > > > > I want to continue to use MacHighway. They provide amazing tech > > support to > > a person like me who gets way in over the head on tech stuff. > Possibly you could get them to install or help you install Mailman. > -- Lindsay Haisley | "The first casualty when FMP Computer Services | war comes is truth." 512-259-1190 | http://www.fmp.com | -- Hiram W Johnson From beta at admilon.net Sun Sep 25 20:13:43 2016 From: beta at admilon.net (Matthias Schmidt) Date: Mon, 26 Sep 2016 09:13:43 +0900 Subject: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail In-Reply-To: References: <7A2FF5A2-4F87-4C6A-8013-6ADF4CB859CC@gmail.com> <670e8920-15dc-81d4-78c2-bed9ad2183dc@msapiro.net> Message-ID: > Am 19.09.2016 um 00:39 schrieb Timothy Jasionowski : > > You may also want to make sure that you're configured SPF for your domain... I know that Google can be suspicious of new or small domains unless SPF (or even DKIM) is implemented. > > SPF is easy to implement. You just need to put a TXT entry into DNS. as others said before, your MTA needs to be configured correctly. Besides SPF and DMARK your server has to have a reverse pointer, which resolves properly. In mailman either set the reply-to to the original sender or the FROM to the list itself. If that all is given and you?re not blacklisted, contact the postmasters via their help page. If all is OK, they will white-list your server. cheers Matthias > > Timothy > > Sent from my iPhone > >> On Sep 18, 2016, at 17:19, Mark Sapiro wrote: >> >>> On 09/17/2016 11:05 PM, Eko Budiharto wrote: >>> dear all, >>> I have a list using mailman. It cannot send mails to yahoo, hotmail and gmail. I check all setting in the mailman, but I still cannot find the problem yet. Please help me if someone who ever experience like this. >> >> >> It's hard to tell without more information such as bounce messages or >> log messages, but this could be a DMARC issue. See >> and . >> >> It is also possible your server is on one or more blacklists. Check at, >> e.g., >> >> Also see . >> >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> ------------------------------------------------------ >> Mailman-Users mailing list Mailman-Users at python.org >> https://mail.python.org/mailman/listinfo/mailman-users >> Mailman FAQ: http://wiki.list.org/x/AgA3 >> Security Policy: http://wiki.list.org/x/QIA9 >> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ >> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/beta%40admilon.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From weinstock at conjelco.com Sun Sep 25 22:57:47 2016 From: weinstock at conjelco.com (Chuck Weinstock) Date: Sun, 25 Sep 2016 22:57:47 -0400 Subject: [Mailman-Users] Need Help with Mailman Mail Delivery Message-ID: Version: 2.1.15 Yum installed on CENTOS 7 Postfix This was working on an older server that I retired because the OS had reached EOL. I cannot seem to get it to work on the new server. I went through the troubleshooting steps that applied. An email to my list abc at xyz.co does not get distributed to members of the list. A look at maillog shows: Sep 25 22:37:20 personal2 postfix/smtpd[13113]: connect from mail-qk0-x22e.google.com[2607:f8b0:400d:c09::22e] Sep 25 22:37:21 personal2 postfix/smtpd[13113]: 03AE7177B: client=mail-qk0-x22e.google.com[2607:f8b0:400d:c09::22e] Sep 25 22:37:21 personal2 postfix/cleanup[13146]: 03AE7177B: message-id=<0A56C786-DC31-42C7-8791-8595FAE7B3AE at conjelco.com> Sep 25 22:37:21 personal2 postfix/qmgr[3822]: 03AE7177B: from=, size=2737, nrcpt=1 (queue active) Sep 25 22:37:21 personal2 postfix/smtpd[13113]: disconnect from mail-qk0-x22e.google.com[2607:f8b0:400d:c09::22e] Sep 25 22:37:21 personal2 postfix/local[13147]: 03AE7177B: to=, relay=local, delay=0.14, delays=0.05/0.01/0/0.09, dsn=2.0.\ 0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post abc) Sep 25 22:37:21 personal2 postfix/qmgr[3822]: 03AE7177B: removed Nothing shows up in any of the log/mailman logs. All of the qrunners etc. are running. Any help would be appreciated. Chuck From weinstock at conjelco.com Mon Sep 26 09:27:13 2016 From: weinstock at conjelco.com (Chuck Weinstock) Date: Mon, 26 Sep 2016 09:27:13 -0400 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" Message-ID: Not sure this is relevant but I see this in the qrunner log: Sep 26 01:03:28 2016 (12454) Qrunner VirginRunner reached maximum restart limit of 10, not restarting. (And a bunch of similar messages.) From andrew at hodgsonfamily.org Sun Sep 25 10:56:57 2016 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Sun, 25 Sep 2016 14:56:57 +0000 Subject: [Mailman-Users] Moderator v list owner Message-ID: Hi, Just wondering what the difference is between the moderator and owner addresses in Mailman? Is there a way of getting the owner to receive bounce messages, subscription/unsubscription mail etc., and the moderator just receiving the held messages notification? Thanks. Andrew. From heller at deepsoft.com Mon Sep 26 14:45:15 2016 From: heller at deepsoft.com (Robert Heller) Date: Mon, 26 Sep 2016 14:45:15 -0400 (EDT) Subject: [Mailman-Users] Moderator v list owner In-Reply-To: References: Message-ID: <20160926184515.AB39B73235A@sharky3.deepsoft.com> At Sun, 25 Sep 2016 14:56:57 +0000 Andrew Hodgson wrote: > > Hi, > > Just wondering what the difference is between the moderator and owner > addresses in Mailman? Is there a way of getting the owner to receive bounce > messages, subscription/unsubscription mail etc., and the moderator just > receiving the held messages notification? Both the "owner" and "moderator" receive bounce messages, subscription/unsubscription mail etc. The moderator can deal with subscription/unsubscription and moderation messages (moderation chores) as can the owner. The owner can do additional things (deal with all of the list config stuff). Mailman basicly has two priviledge levels (three if you count the overall list admin), with each higher level incorporating all of the lower level's privs. > > Thanks. > Andrew. > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com > > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller at deepsoft.com -- Webhosting Services From jhs at berklix.com Mon Sep 26 15:11:01 2016 From: jhs at berklix.com (Julian H. Stacey) Date: Mon, 26 Sep 2016 21:11:01 +0200 Subject: [Mailman-Users] Siblings list usage ? In-Reply-To: Your message "Sun, 25 Sep 2016 08:10:44 -0700." <6db3b41b-5353-b6be-ed63-e289b7a2d197@msapiro.net> Message-ID: <201609261911.u8QJB1vp098765@fire.js.berklix.net> Thanks for your reply Mark, very useful, Mark Sapiro wrote: > On 09/25/2016 02:32 AM, Julian H. Stacey wrote: > > > > On mailman lit configs, On event-announce@ I asserted default > > moderated bit on all new & existing members of event-announce@, & > > removed moderated bit on individual organisers. > > > This is not a secure way to restrict posts to event-announce because > anyone can post by spoofing the address of an unmoderated member whose > address is known by virtue of having posted to the list. Yes; Spoofing hasn't been a problem here so far thanks, (perhaps as most lists for technicaly competent here are open to all members umoderated anyway; Mostly it's just non tech. lists here are announce- only, to block noise many lazy & clueless. I had administrivia filters turned on in majordomo & now with mailman, I needed to add to MJ regexp filters, so if I do with MM, I'll hope to contribute back to MM devs. > See the > sections "How to restrict the list so only authorized persons can post:" > and "How to post to the announcement list:" at > . > > However, this may not be viable in your case depending on the logistics > of distributing the lists poster password to the authorized posters. Yes, not viable here, many event organisers on the non tech lists woundn't cope inserting a password in header. So later, if I have to. > > My main problem: > > No one on event-announce@ can now respond to event-org@ with > > "Count me in for event! / Who is organiser next week? etc" > > > Add '@event-announce' to accept_these_nonmembers of the event-org list. > This will allow anyone who is a member of event-announce, and not a > member of event-org to post to event.org without moderation. This will > not affect event-org posts from a member of event-org. OK Found under http://mailman.berklix.org/mailman/admin/event-org/privacy/sender Non-member filters. > > My lesser problem: > > When someone joins event-org@ I have to manually remove moderator > > bit from their personal membership entry in event-announce@ (& > > re-assert if they leave). > > > You could add @event-org to accept_these_nonmembers of the > event-announce list. This would allow any member of event-org to post to > event-announce, but it is subject to the same spoofing vulnerability as > noted for 'un-moderation', and members of event-org who are not members > of event-announce won't receive event-announce posts. OK Thanks, Done, last bit no prob. I have (up to now) required all members of *-org@ to be on *-announce@ (but I think per your post below I'll switch to include event-announce@ traffic to event-org@) I asserted wrong record via wrong box on web form first go, but then confirmed I have right one with this check: cd /usr/local ; \ mailman/bin/dumpdb mailman/lists/event-org/config.pck | grep accept_these { 'accept_these_nonmembers': ['@event', '@event-chat'], > > Are Sibling lists a solution? How please ?, I've never used them yet. > > > Sibling lists may help some of this. If you add event-org at ... to > regular_include_lists of event-announce that will solve the potential > issue of event-org members who are not members of event-announce not > receiving event-announce posts. > > So, there are choices depending on whether or not you are concerned > about unauthorized posts to event-announce by spoofing authorized senders. > > If you aren't concerned: > Add '@event-announce' to accept_these_nonmembers of event-org. > Add '@event-org' to accept_these_nonmembers of event-announce. > Add event-org at ... to regular_include_lists of event-announce. > Ensure that anyone who is a member of both event-announce and event-org > is not moderated on event-announce or posts to event-announce with an > Approved: header. Easiest is to ensure members of event-org > aren't members of event-announce. > > If you are concerned: > Add '@event-announce' to accept_these_nonmembers of event-org. > Do not add '@event-org' to accept_these_nonmembers of event-announce. > Moderate everyone on event-announce and authorized posters can post to > event-announce with an Approved: header, instructions for > which can be posted to the event-org list if its archives are private. Thanks Mark :-) If you ever visit Munich, there's a bunch of lists on http://berklix.org where you can find me to buy you a beer :-) Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From mark at msapiro.net Mon Sep 26 21:04:32 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 26 Sep 2016 18:04:32 -0700 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: References: Message-ID: On 09/26/2016 06:27 AM, Chuck Weinstock wrote: > Not sure this is relevant but I see this in the qrunner log: > > Sep 26 01:03:28 2016 (12454) Qrunner VirginRunner reached maximum restart limit of 10, not restarting. > > (And a bunch of similar messages.) It is absolutely relevant, but it contradicts your prior "All of the qrunners etc. are running." statement. It says that VirginRunner encountered a fatal error, died and was restarted 10 times and the master (mailmanctl) has given up on it. What is the sig and sts from messages in the qrunner log like Master qrunner detected subprocess exit (pid: 5651, sig: None, sts: 15, class: RetryRunner, slice: 1/1) and what's in Mailman's error log from the same times that qrunners are dying. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Sep 26 21:24:59 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 26 Sep 2016 18:24:59 -0700 Subject: [Mailman-Users] Moderator v list owner In-Reply-To: <20160926184515.AB39B73235A@sharky3.deepsoft.com> References: <20160926184515.AB39B73235A@sharky3.deepsoft.com> Message-ID: <2204dbc0-a1fb-97ed-68b0-a23a91fe2ea0@msapiro.net> On 09/26/2016 11:45 AM, Robert Heller wrote: > At Sun, 25 Sep 2016 14:56:57 +0000 Andrew Hodgson wrote: > >> >> Hi, >> >> Just wondering what the difference is between the moderator and owner >> addresses in Mailman? Is there a way of getting the owner to receive bounce >> messages, subscription/unsubscription mail etc., and the moderator just >> receiving the held messages notification? > > Both the "owner" and "moderator" receive bounce messages, > subscription/unsubscription mail etc. The moderator can deal with > subscription/unsubscription and moderation messages (moderation chores) as can > the owner. The owner can do additional things (deal with all of the list > config stuff). Mailman basicly has two priviledge levels (three if you count > the overall list admin), with each higher level incorporating all of the lower > level's privs. There is a FAQ on this at , but to be precise, owner and moderator roles have nothing to do with email addresses that may or may not be in the owner or moderator settings of a list. These roles are determined by who knows what password. As Robert indicates, the moderator password for a list can be used to authenticate for the lists admindb interface only. The owner password for a list can be used to authenticate for the lists admindb interface and the lists admin interface, and the site password can be used to authenticate for the admindb interface and the admin interface for any list in the installation. To return to Andrew's question, the answer is no. Both the 'owner' addresses and the 'moderator' addresses receive all mail to the list's -owner address and this includes most notifications. There are a (very) few notices that are sent only to the 'owner' addresses and none sent only to the 'moderator' addresses. Yes, it would be good if the 'moderator' addresses only received notices about admindb things (held posts, subscriptions and unsubscriptions), but I think it's too late to change. Also, it's tricky because in general id is very difficult to programmatically determine if a message from outside to -owner should or should not go to a moderator address if there even is one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From weinstock at conjelco.com Mon Sep 26 21:28:08 2016 From: weinstock at conjelco.com (Chuck Weinstock) Date: Mon, 26 Sep 2016 21:28:08 -0400 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: References: Message-ID: <5F9A7CB4-A690-4352-A4C5-462D1788E05E@conjelco.com> When I looked originally all of the qrunners were running. I believe I have solved my problem by nuking the old install of Mailman and reinstalling from scratch (and reusing the config.pck, etc files.) If you are interested I can still supply the information asked for below, but I won?t waste your time otherwise. I appreciate the response. Chuck > On Sep 26, 2016, at 9:04 PM, Mark Sapiro wrote: > > On 09/26/2016 06:27 AM, Chuck Weinstock wrote: >> Not sure this is relevant but I see this in the qrunner log: >> >> Sep 26 01:03:28 2016 (12454) Qrunner VirginRunner reached maximum restart limit of 10, not restarting. >> >> (And a bunch of similar messages.) > > > It is absolutely relevant, but it contradicts your prior "All of the > qrunners etc. are running." statement. > > It says that VirginRunner encountered a fatal error, died and was > restarted 10 times and the master (mailmanctl) has given up on it. > > What is the sig and sts from messages in the qrunner log like > > Master qrunner detected subprocess exit > (pid: 5651, sig: None, sts: 15, class: RetryRunner, slice: 1/1) > > and what's in Mailman's error log from the same times that qrunners are > dying. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/weinstock%40conjelco.com From mark at msapiro.net Mon Sep 26 21:35:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 26 Sep 2016 18:35:53 -0700 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: <5F9A7CB4-A690-4352-A4C5-462D1788E05E@conjelco.com> References: <5F9A7CB4-A690-4352-A4C5-462D1788E05E@conjelco.com> Message-ID: <1acc5a7d-7dec-aa6b-fa0a-e8f3d0f2805f@msapiro.net> On 09/26/2016 06:28 PM, Chuck Weinstock wrote: > When I looked originally all of the qrunners were running. Probably because it took a message to trigger the exception and there hadn't at that point been enough messages to hit the retry limit. > I believe I have solved my problem by nuking the old install of Mailman and reinstalling from scratch (and reusing the config.pck, etc files.) > > If you are interested I can still supply the information asked for below, but I won?t waste your time otherwise. If you're satisfied that you've solved the issue, I'm happy. Thanks for offering, but I only wanted that info to help you find a solution. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lists at damorris.com Tue Sep 27 00:55:30 2016 From: lists at damorris.com (Adam Morris) Date: Tue, 27 Sep 2016 14:55:30 +1000 Subject: [Mailman-Users] unbanning a member? Message-ID: Hello, Wondering if someone can tell me where to go in mailman to unban a members email address? Under privacy I found a list of banned addresses but removing them didn't unban the member. -- Adam Morris Jaws certified 2016 email: adam at damorris.com From turnbull.stephen.fw at u.tsukuba.ac.jp Tue Sep 27 05:40:33 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Tue, 27 Sep 2016 18:40:33 +0900 Subject: [Mailman-Users] unbanning a member? In-Reply-To: References: Message-ID: <22506.16017.754975.228553@turnbull.sk.tsukuba.ac.jp> Adam Morris writes: > Wondering if someone can tell me where to go in mailman to unban a > members email address? What do you mean by "banned"? That is, what is the member trying to do? Subscribe? Post? Something else? What happens that lets you know they are "banned"? Is the email address subscribed? -- Associate Professor Department of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull at sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN From mark at msapiro.net Tue Sep 27 09:53:05 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 06:53:05 -0700 Subject: [Mailman-Users] unbanning a member? In-Reply-To: <22506.16017.754975.228553@turnbull.sk.tsukuba.ac.jp> References: <22506.16017.754975.228553@turnbull.sk.tsukuba.ac.jp> Message-ID: <2039f54d-2478-2dba-37f8-3ce31fa15b5d@msapiro.net> On 09/27/2016 02:40 AM, Stephen J. Turnbull wrote: > Adam Morris writes: > > > Wondering if someone can tell me where to go in mailman to unban a > > members email address? > > What do you mean by "banned"? That is, what is the member trying to > do? Subscribe? Post? Something else? What happens that lets you > know they are "banned"? Is the email address subscribed? +1 Also, if the address is a member, the ban_list has no effect. The ban list only prevents a subscription, invitation or change of address to. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From weinstock at conjelco.com Tue Sep 27 09:55:20 2016 From: weinstock at conjelco.com (Chuck Weinstock) Date: Tue, 27 Sep 2016 09:55:20 -0400 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: References: Message-ID: Whoops. The reinstalled Mailman stopped working with the same problem overnight. Two of the eight qrunners crashed. I have 3-4 lists and one of them will not open in the web admin interface. It times out as per the apache log: [Tue Sep 27 09:45:53.591373 2016] [cgi:warn] [pid 2483] [client 128.237.211.152:49581] AH01220: Timeout waiting for output from CGI script /usr/lib/mailman/cgi-bin/admin, referer: http://www.conjel.co/mailman/admin/fttc [Tue Sep 27 09:45:53.592426 2016] [cgi:error] [pid 2483] [client 128.237.211.152:49581] Script timed out before returning headers: admin, referer: http://www.conjel.co/mailman/admin/fttc [Tue Sep 27 09:46:53.639699 2016] [cgi:warn] [pid 2483] [client 128.237.211.152:49581] AH01220: Timeout waiting for output from CGI script /usr/lib/mailman/cgi-bin/admin, referer: http://www.conjel.co/mailman/admin/fttc [Tue Sep 27 09:46:53.640524 2016] [reqtimeout:info] [pid 2483] [client 128.237.211.152:49581] AH01382: Request body read timeout Here is the access log from the same time frame: 128.237.211.152 - - [27/Sep/2016:09:44:51 -0400] "GET /mailman/admin/fttc HTTP/1.1" 200 2078 128.237.211.152 - - [27/Sep/2016:09:44:53 -0400] "POST /mailman/admin/fttc HTTP/1.1" 504 247 Here is the qrunner log (from earlier when the two qrunners stopped): Sep 27 06:09:59 2016 (7136) Master qrunner detected subprocess exit (pid: 1194, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:09:59 2016 (1439) VirginRunner qrunner started. Sep 27 06:13:22 2016 (7136) Master qrunner detected subprocess exit (pid: 1246, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:13:23 2016 (1564) IncomingRunner qrunner started. Sep 27 06:15:09 2016 (7136) Master qrunner detected subprocess exit (pid: 1439, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:15:09 2016 (1679) VirginRunner qrunner started. Sep 27 06:18:00 2016 (7136) Master qrunner detected subprocess exit (pid: 1564, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:18:00 2016 (1786) IncomingRunner qrunner started. Sep 27 06:20:30 2016 (7136) Master qrunner detected subprocess exit (pid: 1679, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:20:31 2016 (1917) VirginRunner qrunner started. Sep 27 06:21:56 2016 (7136) Master qrunner detected subprocess exit (pid: 1786, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:21:56 2016 (1980) IncomingRunner qrunner started. Sep 27 06:24:28 2016 (7136) Master qrunner detected subprocess exit (pid: 1917, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:24:29 2016 (2048) VirginRunner qrunner started. Sep 27 06:25:55 2016 (7136) Master qrunner detected subprocess exit (pid: 1980, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:25:56 2016 (2160) IncomingRunner qrunner started. Sep 27 06:28:06 2016 (7136) Master qrunner detected subprocess exit (pid: 2048, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:28:06 2016 (2223) VirginRunner qrunner started. Sep 27 06:30:03 2016 (7136) Master qrunner detected subprocess exit (pid: 2160, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:30:03 2016 (2317) IncomingRunner qrunner started. Sep 27 06:32:36 2016 (7136) Master qrunner detected subprocess exit (pid: 2223, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:32:37 2016 (2443) VirginRunner qrunner started. Sep 27 06:34:03 2016 (7136) Master qrunner detected subprocess exit (pid: 2317, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:34:04 2016 (2494) IncomingRunner qrunner started. Sep 27 06:36:44 2016 (7136) Master qrunner detected subprocess exit (pid: 2443, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] Sep 27 06:36:44 2016 (7136) Qrunner VirginRunner reached maximum restart limit of 10, not restarting. Sep 27 06:45:04 2016 (7136) Master qrunner detected subprocess exit (pid: 2494, sig: 9, sts: None, class: IncomingRunner, slice: 1/1) [restarting] Sep 27 06:45:04 2016 (7136) Qrunner IncomingRunner reached maximum restart limit of 10, not restarting. Finally this is the only error in the Mailman error file since the reinstall last night. Sep 26 20:59:51 2016 admin(8885): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(8885): [----- Mailman Version: 2.1.15 -----] admin(8885): [----- Traceback ------] admin(8885): Traceback (most recent call last): admin(8885): File "/usr/lib/mailman/scripts/driver", line 112, in run_main admin(8885): main() admin(8885): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 198, in main admin(8885): mlist.Save() admin(8885): File "/usr/lib/mailman/Mailman/MailList.py", line 578, in Save admin(8885): self.__save(dict) admin(8885): File "/usr/lib/mailman/Mailman/MailList.py", line 555, in __save admin(8885): os.link(fname, fname_last) admin(8885): OSError: [Errno 1] Operation not permitted admin(8885): [----- Python Information -----] admin(8885): sys.version = 2.7.5 (default, Sep 15 2016, 22:37:39) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] admin(8885): sys.executable = /usr/bin/python admin(8885): sys.prefix = /usr admin(8885): sys.exec_prefix = /usr admin(8885): sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/li b64/python27.zip', '/usr/lib64/python2.7/', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old ', '/usr/lib64/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(8885): sys.platform = linux2 admin(8885): [----- Environment Variables -----] admin(8885): HTTP_REFERER: http://conjel.co/mailman/admindb/dsn admin(8885): CONTEXT_DOCUMENT_ROOT: /usr/lib/mailman/cgi-bin/ admin(8885): SERVER_SOFTWARE: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 admin(8885): CONTEXT_PREFIX: /mailman/ admin(8885): SERVER_SIGNATURE: admin(8885): REQUEST_METHOD: POST admin(8885): PATH_INFO: /dsn admin(8885): HTTP_ORIGIN: http://conjel.co admin(8885): SERVER_PROTOCOL: HTTP/1.1 admin(8885): QUERY_STRING: admin(8885): CONTENT_LENGTH: 39 admin(8885): HTTP_USER_AGENT: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 admin(8885): HTTP_CONNECTION: keep-alive admin(8885): HTTP_COOKIE: mailman+admin=280200000069afc0e95773280000003665333231613538636235383833376661383331666565643265333961653063313 3366130663062 admin(8885): SERVER_NAME: conjel.co admin(8885): REMOTE_ADDR: 2601:547:f00:cf2c:8c4a:63df:fcba:58e9 admin(8885): PATH_TRANSLATED: /home/personal/htdocs/dsn admin(8885): SERVER_PORT: 80 admin(8885): SERVER_ADDR: 2001:4800:7818:103:be76:4eff:fe04:5321 admin(8885): DOCUMENT_ROOT: /home/personal/htdocs admin(8885): PYTHONPATH: /usr/lib/mailman admin(8885): SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/admindb admin(8885): SERVER_ADMIN: root at localhost admin(8885): HTTP_HOST: conjel.co admin(8885): SCRIPT_NAME: /mailman/admindb admin(8885): HTTP_UPGRADE_INSECURE_REQUESTS: 1 admin(8885): HTTP_CACHE_CONTROL: max-age=0 admin(8885): REQUEST_URI: /mailman/admindb/dsn admin(8885): HTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 admin(8885): GATEWAY_INTERFACE: CGI/1.1 admin(8885): REMOTE_PORT: 63197 admin(8885): HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.8 admin(8885): REQUEST_SCHEME: http admin(8885): CONTENT_TYPE: application/x-www-form-urlencoded admin(8885): HTTP_ACCEPT_ENCODING: gzip, deflate admin(8885): UNIQUE_ID: V at nEh3AeyVpBSf2Pn@BbogAAAAI > On Sep 26, 2016, at 9:04 PM, Mark Sapiro wrote: > > On 09/26/2016 06:27 AM, Chuck Weinstock wrote: >> Not sure this is relevant but I see this in the qrunner log: >> >> Sep 26 01:03:28 2016 (12454) Qrunner VirginRunner reached maximum restart limit of 10, not restarting. >> >> (And a bunch of similar messages.) > > > It is absolutely relevant, but it contradicts your prior "All of the > qrunners etc. are running." statement. > > It says that VirginRunner encountered a fatal error, died and was > restarted 10 times and the master (mailmanctl) has given up on it. > > What is the sig and sts from messages in the qrunner log like > > Master qrunner detected subprocess exit > (pid: 5651, sig: None, sts: 15, class: RetryRunner, slice: 1/1) > > and what's in Mailman's error log from the same times that qrunners are > dying. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/weinstock%40conjelco.com From mark at msapiro.net Tue Sep 27 10:29:30 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 07:29:30 -0700 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: References: Message-ID: <04fa70ec-1d63-f66f-e20b-dbed7bc9842a@msapiro.net> On 09/27/2016 06:55 AM, Chuck Weinstock wrote: > Whoops. The reinstalled Mailman stopped working with the same problem > overnight. Two of the eight qrunners crashed. > > I have 3-4 lists and one of them will not open in the web admin > interface. It times out as per the apache log: > > [Tue Sep 27 09:45:53.591373 2016] [cgi:warn] [pid 2483] [client > 128.237.211.152:49581] AH01220: Timeout waiting for output from CGI > script /usr/lib/mailman/cgi-bin/admin, referer: > http://www.conjel.co/mailman/admin/fttc > [Tue Sep 27 09:45:53.592426 2016] [cgi:error] [pid 2483] [client > 128.237.211.152:49581] Script timed out before returning headers: admin, > referer: http://www.conjel.co/mailman/admin/fttc > [Tue Sep 27 09:46:53.639699 2016] [cgi:warn] [pid 2483] [client > 128.237.211.152:49581] AH01220: Timeout waiting for output from CGI > script /usr/lib/mailman/cgi-bin/admin, referer: > http://www.conjel.co/mailman/admin/fttc > [Tue Sep 27 09:46:53.640524 2016] [reqtimeout:info] [pid 2483] [client > 128.237.211.152:49581] AH01382: Request body read timeout The CGIs are timing out. This is normally caused by a locked list. > Here is the access log from the same time frame: > > 128.237.211.152 - - [27/Sep/2016:09:44:51 -0400] "GET > /mailman/admin/fttc HTTP/1.1" 200 2078 > 128.237.211.152 - - [27/Sep/2016:09:44:53 -0400] "POST > /mailman/admin/fttc HTTP/1.1" 504 247 > > Here is the qrunner log (from earlier when the two qrunners stopped): > > Sep 27 06:09:59 2016 (7136) Master qrunner detected subprocess exit > (pid: 1194, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] sig: 9 is a SIGKILL. This seems to say that something external is killing the runner. This is likely the same or a similar underlying cause as the CGI timeouts, but is different as the CGIs are independent of the qrunners. > > Finally this is the only error in the Mailman error file since the > reinstall last night. > > Sep 26 20:59:51 2016 admin(8885): > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > admin(8885): [----- Mailman Version: 2.1.15 -----] > admin(8885): [----- Traceback ------] > admin(8885): Traceback (most recent call last): > admin(8885): File "/usr/lib/mailman/scripts/driver", line 112, in run_main > admin(8885): main() > admin(8885): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 198, > in main > admin(8885): mlist.Save() > admin(8885): File "/usr/lib/mailman/Mailman/MailList.py", line 578, in > Save > admin(8885): self.__save(dict) > admin(8885): File "/usr/lib/mailman/Mailman/MailList.py", line 555, in > __save > admin(8885): os.link(fname, fname_last) > admin(8885): OSError: [Errno 1] Operation not permitted This is a permission or security manager (SELinux, apparmor, ?) issue. First try running Mailman's 'bin/check_perms -f` as root. If that fixes things, it may help. Also, see . Note that Mailman's CGI wrappers must be group mailman and SETGID. In particular, these files must not be on a file system mounted with 'nosuid'. If none of this helps, try disabling SELinux. The qrunners being SIGKILLed is still a bit mysterious, but that could be related to a permissions or SELinux issue. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From weinstock at conjelco.com Tue Sep 27 10:54:14 2016 From: weinstock at conjelco.com (Chuck Weinstock) Date: Tue, 27 Sep 2016 10:54:14 -0400 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: <04fa70ec-1d63-f66f-e20b-dbed7bc9842a@msapiro.net> References: <04fa70ec-1d63-f66f-e20b-dbed7bc9842a@msapiro.net> Message-ID: Mark, I referred to https://wiki.list.org/x/17891756 before I even contacted the list. All of the cgi wrappers are suid. check_perms run as root finds no problems. One thing I noticed is that there was no locks directory anywhere in the installation. Is this normal? (Places I looked: /var/lib/mailman /usr/lib/mailman and /etc/mailman.) Also the /var/log/mailman/lock was empty but now shows: Sep 27 10:51:45 2016 (12700) fttc.lock lifetime has expired, breaking Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/bin/qrunner", line 278, in Sep 27 10:51:45 2016 (12700) main() Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/bin/qrunner", line 238, in main Sep 27 10:51:45 2016 (12700) qrunner.run() Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 70, in run Sep 27 10:51:45 2016 (12700) filecnt = self._oneloop() Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop Sep 27 10:51:45 2016 (12700) self._onefile(msg, msgdata) Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile Sep 27 10:51:45 2016 (12700) keepqueued = self._dispose(mlist, msg, msgdata) Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose Sep 27 10:51:45 2016 (12700) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock Sep 27 10:51:45 2016 (12700) self.__lock.lock(timeout) Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/LockFile.py", line 306, in lock Sep 27 10:51:45 2016 (12700) important=True) Sep 27 10:51:45 2016 (12700) File "/usr/lib/mailman/Mailman/LockFile.py", line 416, in __writelog Sep 27 10:51:45 2016 (12700) traceback.print_stack(file=logf) (Which is referencing the list in question.) Thanks again, Chuck > On Sep 27, 2016, at 10:29 AM, Mark Sapiro wrote: > > On 09/27/2016 06:55 AM, Chuck Weinstock wrote: >> Whoops. The reinstalled Mailman stopped working with the same problem >> overnight. Two of the eight qrunners crashed. >> >> I have 3-4 lists and one of them will not open in the web admin >> interface. It times out as per the apache log: >> >> [Tue Sep 27 09:45:53.591373 2016] [cgi:warn] [pid 2483] [client >> 128.237.211.152:49581] AH01220: Timeout waiting for output from CGI >> script /usr/lib/mailman/cgi-bin/admin, referer: >> http://www.conjel.co/mailman/admin/fttc >> [Tue Sep 27 09:45:53.592426 2016] [cgi:error] [pid 2483] [client >> 128.237.211.152:49581] Script timed out before returning headers: admin, >> referer: http://www.conjel.co/mailman/admin/fttc >> [Tue Sep 27 09:46:53.639699 2016] [cgi:warn] [pid 2483] [client >> 128.237.211.152:49581] AH01220: Timeout waiting for output from CGI >> script /usr/lib/mailman/cgi-bin/admin, referer: >> http://www.conjel.co/mailman/admin/fttc >> [Tue Sep 27 09:46:53.640524 2016] [reqtimeout:info] [pid 2483] [client >> 128.237.211.152:49581] AH01382: Request body read timeout > > > The CGIs are timing out. This is normally caused by a locked list. > > >> Here is the access log from the same time frame: >> >> 128.237.211.152 - - [27/Sep/2016:09:44:51 -0400] "GET >> /mailman/admin/fttc HTTP/1.1" 200 2078 >> 128.237.211.152 - - [27/Sep/2016:09:44:53 -0400] "POST >> /mailman/admin/fttc HTTP/1.1" 504 247 >> >> Here is the qrunner log (from earlier when the two qrunners stopped): >> >> Sep 27 06:09:59 2016 (7136) Master qrunner detected subprocess exit >> (pid: 1194, sig: 9, sts: None, class: VirginRunner, slice: 1/1) [restarting] > > sig: 9 is a SIGKILL. This seems to say that something external is > killing the runner. > > This is likely the same or a similar underlying cause as the CGI > timeouts, but is different as the CGIs are independent of the qrunners. > > >> >> Finally this is the only error in the Mailman error file since the >> reinstall last night. >> >> Sep 26 20:59:51 2016 admin(8885): >> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> admin(8885): [----- Mailman Version: 2.1.15 -----] >> admin(8885): [----- Traceback ------] >> admin(8885): Traceback (most recent call last): >> admin(8885): File "/usr/lib/mailman/scripts/driver", line 112, in run_main >> admin(8885): main() >> admin(8885): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 198, >> in main >> admin(8885): mlist.Save() >> admin(8885): File "/usr/lib/mailman/Mailman/MailList.py", line 578, in >> Save >> admin(8885): self.__save(dict) >> admin(8885): File "/usr/lib/mailman/Mailman/MailList.py", line 555, in >> __save >> admin(8885): os.link(fname, fname_last) >> admin(8885): OSError: [Errno 1] Operation not permitted > > > This is a permission or security manager (SELinux, apparmor, ?) issue. > > First try running Mailman's 'bin/check_perms -f` as root. If that fixes > things, it may help. Also, see . > > Note that Mailman's CGI wrappers must be group mailman and SETGID. In > particular, these files must not be on a file system mounted with 'nosuid'. > > If none of this helps, try disabling SELinux. > > The qrunners being SIGKILLed is still a bit mysterious, but that could > be related to a permissions or SELinux issue. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 27 11:06:26 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 08:06:26 -0700 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: References: <04fa70ec-1d63-f66f-e20b-dbed7bc9842a@msapiro.net> Message-ID: <0fbc436e-420a-0f89-7888-f73eea584265@msapiro.net> On 09/27/2016 07:54 AM, Chuck Weinstock wrote: > > One thing I noticed is that there was no locks directory anywhere in the > installation. Is this normal? (Places I looked: /var/lib/mailman > /usr/lib/mailman and /etc/mailman.) Your mailman locks directory is /var/lock/mailman/. See . I suspect the problem with the CGIs has to do with the qrunners being KILLed and leaving the list locked. That still doesn't explain why the qrunners are being SIGKILLed. Is there anything in /var/spool/mailman/shunt, /var/spool/mailman/retry or /var/spool/mailman/in? If so, what does Mailman's 'bin/dumpdb -p' produce on those files? I'm looking for some kind of message corruption and also the metadata. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From weinstock at conjelco.com Tue Sep 27 11:20:06 2016 From: weinstock at conjelco.com (Chuck Weinstock) Date: Tue, 27 Sep 2016 11:20:06 -0400 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: <0fbc436e-420a-0f89-7888-f73eea584265@msapiro.net> References: <04fa70ec-1d63-f66f-e20b-dbed7bc9842a@msapiro.net> <0fbc436e-420a-0f89-7888-f73eea584265@msapiro.net> Message-ID: <0AADDAE1-B9DF-4ABA-8D4D-5E050FC38297@conjelco.com> Ok, there were a whole bunch of lock files that I cleared and now I can access the admin page. The shunt directory contains 591 different lines of the form: -rw-rw---- 1 mailman mailman 1196 Sep 26 20:25 1474919192.85809+72fc7bd3e80b280fe5def1b842936d832e60126f.pck All from around the same time. The other two directories are empty. Applying dumpdb to a few of them I see that they are each spam. (No indication of corruption that I can see.) Here?s part of an example: [----- start pickle file -----] <----- start object 1 -----> From Cora4 at only-4u.com Thu Sep 22 08:58:08 2016 Return-Path: X-Original-To: wg10.4 at dependability.org Delivered-To: wg10.4 at dependability.org Received: from [103.206.131.149] (unknown [103.206.131.149]) by personal2.localdomain (Postfix) with ESMTP id ED0984762 for ; Thu, 22 Sep 2016 08:58:07 -0400 (EDT) Content-type: multipart/mixed; boundary=Apple-Mail-D4D73760-E06639FC-B9B1373-86986B42-2365F1462A7E2E3657B Content-transfer-encoding: 7bit From: "Cora wilkes" MIME-version: 1.0 (1.0) Date: Thu, 22 Sep 2016 18:28:05 +0530 Subject: Invoice INV00001226 Message-id: <2BD4D6-22C09DB0-F12148EE-B60C5033-85FB1AE4E06B6427C130 at only-4u.com> To: wg10.4 at dependability.org X-Mailer: iPhone Mail (13G35) Envelope-To: --Apple-Mail-D4D73760-E06639FC-B9B1373-86986B42-2365F1462A7E2E3657B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Please find our invoice attached. --Apple-Mail-D4D73760-E06639FC-B9B1373-86986B42-2365F1462A7E2E3657B Content-Type: application/zip; name=Invoice_INV00001226.zip; x-apple-part-url=D654925-14D6BA-BC29666A-033E-AB15C1B5891F982D3F0C Content-Disposition: attachment; filename=Invoice_INV00001226.zip Content-Transfer-Encoding: base64 [base64 content] --Apple-Mail-D4D73760-E06639FC-B9B1373-86986B42-2365F1462A7E2E3657B-- <----- start object 2 -----> { '_parsemsg': False, 'listname': 'wg10.4', 'received_time': 1474549089.019715, 'tolist': 1, 'version': 3} [----- end pickle file -----] > On Sep 27, 2016, at 11:06 AM, Mark Sapiro wrote: > > On 09/27/2016 07:54 AM, Chuck Weinstock wrote: >> >> One thing I noticed is that there was no locks directory anywhere in the >> installation. Is this normal? (Places I looked: /var/lib/mailman >> /usr/lib/mailman and /etc/mailman.) > > > Your mailman locks directory is /var/lock/mailman/. See > . > > I suspect the problem with the CGIs has to do with the qrunners being > KILLed and leaving the list locked. > > That still doesn't explain why the qrunners are being SIGKILLed. > > Is there anything in /var/spool/mailman/shunt, /var/spool/mailman/retry > or /var/spool/mailman/in? > > If so, what does Mailman's 'bin/dumpdb -p' produce on those files? I'm > looking for some kind of message corruption and also the metadata. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 27 12:02:57 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 09:02:57 -0700 Subject: [Mailman-Users] Further to "Need Help with Mailman Mail Delivery" In-Reply-To: <0AADDAE1-B9DF-4ABA-8D4D-5E050FC38297@conjelco.com> References: <04fa70ec-1d63-f66f-e20b-dbed7bc9842a@msapiro.net> <0fbc436e-420a-0f89-7888-f73eea584265@msapiro.net> <0AADDAE1-B9DF-4ABA-8D4D-5E050FC38297@conjelco.com> Message-ID: <51ab01e2-5be7-8173-6568-f7ea5ccb6579@msapiro.net> On 09/27/2016 08:20 AM, Chuck Weinstock wrote: > Ok, there were a whole bunch of lock files that I cleared and now I can > access the admin page. OK. > The shunt directory contains 591 different lines of the form: > > -rw-rw---- 1 mailman mailman 1196 Sep 26 20:25 > 1474919192.85809+72fc7bd3e80b280fe5def1b842936d832e60126f.pck > > All from around the same time. > > The other two directories are empty. > > Applying dumpdb to a few of them I see that they are each spam. (No > indication of corruption that I can see.) Maybe you were hit with a massive spam attack and that triggered something that caused the qrunners to die, but there normally would also be error log messages. Did you check for a rotated log? If these are older shunt entries (before you reinstalled), possibly there was a permissions issue at that time that prevented writing the error log and maybe caused other issues. The one you posted had a received time from last Thursday, 22 Sept. The spam message entries in the shunt queue can just be deleted. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From minxmertzmomo at gmail.com Tue Sep 27 17:51:09 2016 From: minxmertzmomo at gmail.com (Matt Morgan) Date: Tue, 27 Sep 2016 17:51:09 -0400 Subject: [Mailman-Users] suppress the "an html attachment was scrubbed" message in digests Message-ID: Can I suppress the -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ bit that's showing up in my digests? Or can I do something that cuts out the HTML before the scrubbing is necessary? Thanks, Matt From mark at msapiro.net Tue Sep 27 18:41:18 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 15:41:18 -0700 Subject: [Mailman-Users] suppress the "an html attachment was scrubbed" message in digests In-Reply-To: References: Message-ID: <951b2eb2-8761-4b98-b8e8-0d9214db069d@msapiro.net> On 09/27/2016 02:51 PM, Matt Morgan wrote: > Can I suppress the > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > bit that's showing up in my digests? Or can I do something that cuts out > the HTML before the scrubbing is necessary? In the list's Content filtering section, be sure that filter_content is Yes and convert_html_to plaintext is Yes. In Addition, I recommend the following: pass_mime:types: multipart message/rfc822 text/plain text/html collapse_alternatives: Yes Although you could also omit text/html from pass_mime:types in which case an HTML only message without a text/plain alternative will be handled per filter_action instead of being converted to plain text by HTML_TO_PLAIN_TEXT_COMMAND the default for which is '/usr/bin/lynx -dump' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Tue Sep 27 19:31:08 2016 From: adamsca at gmail.com (Christopher Adams) Date: Tue, 27 Sep 2016 16:31:08 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search Message-ID: Hello, I have a list with nearly 45,000 subscribers. When a list owner searches for a subscriber through the admin interface, she gets a list of addresses, then a link to follow to get the next 'chunk'. The link leads to something like the following if I were searching for 'stephanie'. http://mydomain.com/mailman/admin/mylist/u'http:// mydomain.com/mailman/admin/mylist/members?letter=s&chunk= 1&findmember=stephanie So, the first chunk is '0' and then the link goes to chunk '1', but it links back to the top-level admin page. If you click the chunks of addresses by the alphabetical letters, it will successfully take you to each section. Is this a Feature or a Bug ? -- Christopher Adams adamsca at gmail.com From mark at msapiro.net Tue Sep 27 20:31:57 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 17:31:57 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: Message-ID: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> On 09/27/2016 04:31 PM, Christopher Adams wrote: > > So, the first chunk is '0' and then the link goes to chunk '1', but it > links back to the top-level admin page. ... > Is this a Feature or a Bug ? It is this bug which was fixed by the attached patch. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: admin.patch Type: text/x-diff Size: 612 bytes Desc: not available URL: From turnbull.stephen.fw at u.tsukuba.ac.jp Tue Sep 27 22:10:30 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Wed, 28 Sep 2016 11:10:30 +0900 Subject: [Mailman-Users] unbanning a member? In-Reply-To: References: <22506.16017.754975.228553@turnbull.sk.tsukuba.ac.jp> Message-ID: <22507.9878.914858.812265@turnbull.sk.tsukuba.ac.jp> I'm going to assume you meant to post to the list, and send there myself. For security reasons, Mailman lists do not munge reply-to. Frequently messages contain private information (IP addresses, domain names, email addresses, and even passwords) that the sender would not want broadcasted to a publicly archived list. Adam Morris writes: > I'm referring to someone who I have banned from subscribing to a mailing > list. > > If I try and subscribe the banned address I get a message saying member > is banned. How do you try to subscribe that address? By web or by mail? In the admin page Privacy Options, there is a ban_list option near the bottom of the page (this is version 2.1.21, I believe yours was older so there may be variations). AFAIK that is the only way to ban an address from subscribing in "stock" Mailman. Make sure that the member is not in that list. I believe you reported that you have cleared out that list already, in which case it's possible that you didn't click the Submit button at the bottom of the page, and it's still there. I guess it's barely possible that you cleared the ban_list for a different list than the one you're trying to subscribe that address to. If the web interface reports an empty ban list and you attempted to subscribe by mail, it's possible that there are two Mailman installations, one handling mail, and the other web (and this one has no effect on actual list operation). Multiple installations can arise for a number of reasons such as an incomplete upgrade where either the mailserver or the webserver was not properly configured. Otherwise, I don't know what's going on. Perhaps Mark has an idea. Regards, From mark at msapiro.net Tue Sep 27 23:51:14 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 27 Sep 2016 20:51:14 -0700 Subject: [Mailman-Users] unbanning a member? In-Reply-To: <22507.9878.914858.812265@turnbull.sk.tsukuba.ac.jp> References: <22506.16017.754975.228553@turnbull.sk.tsukuba.ac.jp> <22507.9878.914858.812265@turnbull.sk.tsukuba.ac.jp> Message-ID: <72c6b26c-c263-2127-9cb4-566f97c341e9@msapiro.net> On 09/27/2016 07:10 PM, Stephen J. Turnbull wrote: > > Adam Morris writes: > > I'm referring to someone who I have banned from subscribing to a mailing > > list. > > > > If I try and subscribe the banned address I get a message saying member > > is banned. I am a bit lost, but I think a summary of the issue is 1) an address was added to the ban_list of a list. 2) the address was subsequently removed from the ban_list. 3) subsequent attempts to subscribe the formerly banned address get an "address is banned" response. Everything Steve said in his reply is relevant and possible, but let's assume you now go to the web admin UI for the list and Privacy options -> Subscription rules -> ban_list is empty and you then go to Membership Management... -> Mass Subscription and subscribe the address and get the banned response. The actual response should look something like Error subscribing: jdoe at apot.com -- Banned address (matched ^.*[@.]apot(mail)?\.com$) with a different address and match of course (at least since Mailman 2.1.7). Is that what happens? If all the above describes what happens, then I think the issue must be that the address/pattern that matched is in the GLOBAL_BAN_LIST that was added in Mailman 2.1.21. Have you set GLOBAL_BAN_LIST in mm_cfg.py (or Defaults.py)? If the above does not describe what happens, where does the actual result differ? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lists at damorris.com Tue Sep 27 23:46:12 2016 From: lists at damorris.com (Adam Morris) Date: Wed, 28 Sep 2016 13:46:12 +1000 Subject: [Mailman-Users] unbanning a member? In-Reply-To: <22507.9878.914858.812265@turnbull.sk.tsukuba.ac.jp> References: <22506.16017.754975.228553@turnbull.sk.tsukuba.ac.jp> <22507.9878.914858.812265@turnbull.sk.tsukuba.ac.jp> Message-ID: <6014db3c-449d-89dc-1bf5-c8c2b1048f2b@damorris.com> Hi Stephen and all, I didn't realise I hadn't clicked the submit changes after deleting the name from the banned list. All sorted, thanks! On 28/09/16 12:10, Stephen J. Turnbull wrote: > I'm going to assume you meant to post to the list, and send there > myself. For security reasons, Mailman lists do not munge reply-to. > Frequently messages contain private information (IP addresses, domain > names, email addresses, and even passwords) that the sender would not > want broadcasted to a publicly archived list. > > Adam Morris writes: > > I'm referring to someone who I have banned from subscribing to a mailing > > list. > > > > If I try and subscribe the banned address I get a message saying member > > is banned. > > How do you try to subscribe that address? By web or by mail? > > In the admin page Privacy Options, there is a ban_list option near the > bottom of the page (this is version 2.1.21, I believe yours was older > so there may be variations). AFAIK that is the only way to ban an > address from subscribing in "stock" Mailman. > > Make sure that the member is not in that list. I believe you reported > that you have cleared out that list already, in which case it's > possible that you didn't click the Submit button at the bottom of the > page, and it's still there. I guess it's barely possible that you > cleared the ban_list for a different list than the one you're trying > to subscribe that address to. > > If the web interface reports an empty ban list and you attempted to > subscribe by mail, it's possible that there are two Mailman > installations, one handling mail, and the other web (and this one has > no effect on actual list operation). Multiple installations can arise > for a number of reasons such as an incomplete upgrade where either the > mailserver or the webserver was not properly configured. > > Otherwise, I don't know what's going on. Perhaps Mark has an idea. > > Regards, -- Adam Morris Jaws certified 2016 email: adam at damorris.com From adamsca at gmail.com Wed Sep 28 14:04:59 2016 From: adamsca at gmail.com (Christopher Adams) Date: Wed, 28 Sep 2016 11:04:59 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> Message-ID: Thank you for the reply and the attached patch. Do I need to patch Mailman and then follow the process as I would for installing/upgrading Mailman ? When I patch, should I be in the Mailman build/source directory and not in the current Mailman directory ? Would 'patch < admin.patch' work ? Many thanks. On Tue, Sep 27, 2016 at 5:31 PM, Mark Sapiro wrote: > On 09/27/2016 04:31 PM, Christopher Adams wrote: > > > > So, the first chunk is '0' and then the link goes to chunk '1', but it > > links back to the top-level admin page. > ... > > Is this a Feature or a Bug ? > > > It is this bug which > was fixed by the attached patch. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/ > mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/ > adamsca%40gmail.com > -- Christopher Adams adamsca at gmail.com From MGraves at acog.org Wed Sep 28 16:29:32 2016 From: MGraves at acog.org (Mark Graves) Date: Wed, 28 Sep 2016 20:29:32 +0000 Subject: [Mailman-Users] Cull_Bad_Shunt Message-ID: I'm using Mailman v2.1.21 on openSUSE Leap 42.1 and received the following email from Cron Daemon: [Mailman] Cron /usr/bin/python -S /usr/lib/mailman/cron/cull_bad_shunt Traceback (most recent call last): File "/usr/lib/mailman/cron/cull_bad_shunt", line 126, in main() File "/usr/lib/mailman/cron/cull_bad_shunt", line 121, in main os.remove(pathname) OSError: [Errno 2] No such file or directory: '/var/lib/mailman/qfiles/shunt/1474407372.553232+5932f7df2b1dccdd77f92f45a8271e33e8f945d8.pck' Just passing it along in case it's a bug. From mark at msapiro.net Wed Sep 28 19:12:29 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 28 Sep 2016 16:12:29 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> Message-ID: <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> On 09/28/2016 11:04 AM, Christopher Adams wrote: > > Do I need to patch Mailman and then follow the process as I would for > installing/upgrading Mailman ? You could, but it isn't necessary. > When I patch, should I be in the Mailman build/source directory and not > in the current Mailman directory ? The easiest thing is to just patch the active Mailman, not the build/source. > Would 'patch < admin.patch' work ? It will if you are in the $prefix directory. Since this patch only affects the admin CGI which is not a persistent process, it is only necessary to apply the patch to $prefix/Mailman/Cgi/admin.py. It is not necessary to restart Mailman. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 28 19:27:59 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 28 Sep 2016 16:27:59 -0700 Subject: [Mailman-Users] Cull_Bad_Shunt In-Reply-To: References: Message-ID: On 09/28/2016 01:29 PM, Mark Graves wrote: > I'm using Mailman v2.1.21 on openSUSE Leap 42.1 and received the following email from Cron Daemon: > > [Mailman] Cron /usr/bin/python -S /usr/lib/mailman/cron/cull_bad_shunt > > > Traceback (most recent call last): > > File "/usr/lib/mailman/cron/cull_bad_shunt", line 126, in > > main() > > File "/usr/lib/mailman/cron/cull_bad_shunt", line 121, in main > > os.remove(pathname) > > OSError: [Errno 2] No such file or directory: '/var/lib/mailman/qfiles/shunt/1474407372.553232+5932f7df2b1dccdd77f92f45a8271e33e8f945d8.pck' > > > Just passing it along in case it's a bug. This can occur only if some other process removed the /var/lib/mailman/qfiles/shunt/1474407372.553232+5932f7df2b1dccdd77f92f45a8271e33e8f945d8.pck file after this process listed the directory contents but before it tried to remove the file. The most likely way for this to occur is by cron running cull_bad_shunt twice. I suspect that what's going on is there is both a mailman user crontab in /var/spool/cron/mailman or wherever user crontabs are stored and a system crontab in /etc/cron.d/mailman and both are running the same jobs at the same times. This would also cause other anomalies such as duplicate "nn moderator requests" messages to list owners/moderators. There should be only one crontab running Mailman's crons. Which one doesn't matter. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Wed Sep 28 19:28:10 2016 From: adamsca at gmail.com (Christopher Adams) Date: Wed, 28 Sep 2016 16:28:10 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: Thank you. I did patch the admin.py file and I can see the changes. However, if I go to the list subscribers, the link to the next group of addresses takes me back to the main admin page. I did notice that the URL includes < u'http://.... > which I thought was the problem that this was supposed to remedy. I then restarted Mailman, but that made no difference. On Wed, Sep 28, 2016 at 4:12 PM, Mark Sapiro wrote: > On 09/28/2016 11:04 AM, Christopher Adams wrote: > > > > Do I need to patch Mailman and then follow the process as I would for > > installing/upgrading Mailman ? > > > You could, but it isn't necessary. > > > > When I patch, should I be in the Mailman build/source directory and not > > in the current Mailman directory ? > > > The easiest thing is to just patch the active Mailman, not the > build/source. > > > > Would 'patch < admin.patch' work ? > > > It will if you are in the $prefix directory. > > Since this patch only affects the admin CGI which is not a persistent > process, it is only necessary to apply the patch to > $prefix/Mailman/Cgi/admin.py. It is not necessary to restart Mailman. > See . > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Christopher Adams adamsca at gmail.com From mark at msapiro.net Wed Sep 28 19:36:58 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 28 Sep 2016 16:36:58 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: On 09/28/2016 04:28 PM, Christopher Adams wrote: > Thank you. I did patch the admin.py file and I can see the changes. > However, if I go to the list subscribers, the link to the next group of > addresses takes me back to the main admin page. > > I did notice that the URL includes < u'http://.... > which I thought > was the problem that this was supposed to remedy. I then restarted > Mailman, but that made no difference. It is exactly that issue that the patch fixes. What admin.py file did you patch? You should be patching Mailman/Cgi/admin.py where the 'Mailman' directory is the actual installed Mailman, maybe something like /usr/local/mailman/Mailman, but this depends on how Mailman was installed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From willi.uebelherr at gmail.com Wed Sep 28 19:58:48 2016 From: willi.uebelherr at gmail.com (willi uebelherr) Date: Wed, 28 Sep 2016 19:58:48 -0400 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: 2016-09-28 19:12 GMT-04:00 Mark Sapiro : > ,,, > You could, but it isn't necessary. Dear i follow your discussion with Christopher. Your short answer " it isn't necessary". Can you explain this? greetings, willi Asuncion, Paraguay From mark at msapiro.net Wed Sep 28 20:11:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 28 Sep 2016 17:11:13 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: On 09/28/2016 04:58 PM, willi uebelherr wrote: > 2016-09-28 19:12 GMT-04:00 Mark Sapiro : >> ,,, >> You could, but it isn't necessary. > > Dear > > i follow your discussion with Christopher. Your short answer " it > isn't necessary". Can you explain this? He asked if he should apply the patch to the source directory. My answer was intended to say he could, but if he did, he would then need to rerun 'configure' and 'make install'. While that is one way to do it and would ensure that if 'make install' were run in the future, it wouldn't reverse the patch, it isn't necessary to do that. It is sufficient to just apply the patch directly to the installed Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Thu Sep 29 00:34:34 2016 From: adamsca at gmail.com (Christopher Adams) Date: Wed, 28 Sep 2016 21:34:34 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: I did patch the installed instance of Mailman (/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that it made, but the result is the same when looking at the subscriber list. On Sep 28, 2016 4:37 PM, "Mark Sapiro" wrote: > On 09/28/2016 04:28 PM, Christopher Adams wrote: > > Thank you. I did patch the admin.py file and I can see the changes. > > However, if I go to the list subscribers, the link to the next group of > > addresses takes me back to the main admin page. > > > > I did notice that the URL includes < u'http://.... > which I thought > > was the problem that this was supposed to remedy. I then restarted > > Mailman, but that made no difference. > > > It is exactly that issue that the patch fixes. What admin.py file did > you patch? You should be patching Mailman/Cgi/admin.py where the > 'Mailman' directory is the actual installed Mailman, maybe something > like /usr/local/mailman/Mailman, but this depends on how Mailman was > installed. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From mark at msapiro.net Thu Sep 29 00:57:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 28 Sep 2016 21:57:12 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: On 09/28/2016 09:34 PM, Christopher Adams wrote: > I did patch the installed instance of Mailman > (/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that > it made, but the result is the same when looking at the subscriber list. The patch converts a unicode URL to the character set of the list's preferred language. The result should not be a u'http://... string. I can only guess that your web server is not executing the script you think it is. Or possibly you are looking at an older, cached version of the page. Have you tried reloading the page in your browser? What is the path in the web server's ScriptAlias (if it's apache or whatever it is in your web server). Is it /usr/local/mailman/cgi-bin/ or something else? If it is /usr/local/mailman/cgi-bin/, what does strings /usr/local/mailman/cgi-bin/admin | grep scripts show? and if you look in the paths.py file in that directory, what is the value in the prefix = statement? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Thu Sep 29 11:04:49 2016 From: adamsca at gmail.com (Christopher Adams) Date: Thu, 29 Sep 2016 08:04:49 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: I cleared browser cache and reloaded. Same problem. Here are answers to your questions. ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" strings /usr/local/mailman/cgi-bin/admin | grep scripts /usr/local/mailman/scripts/ prefix = '/usr/local/mailman' On Wed, Sep 28, 2016 at 9:57 PM, Mark Sapiro wrote: > On 09/28/2016 09:34 PM, Christopher Adams wrote: > > I did patch the installed instance of Mailman > > (/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that > > it made, but the result is the same when looking at the subscriber list. > > > The patch converts a unicode URL to the character set of the list's > preferred language. The result should not be a u'http://... string. > > I can only guess that your web server is not executing the script you > think it is. Or possibly you are looking at an older, cached version of > the page. Have you tried reloading the page in your browser? > > What is the path in the web server's ScriptAlias (if it's apache or > whatever it is in your web server). Is it /usr/local/mailman/cgi-bin/ or > something else? > > If it is /usr/local/mailman/cgi-bin/, what does > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > > show? and if you look in the paths.py file in that directory, what is > the value in the > > prefix = > > statement? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Christopher Adams adamsca at gmail.com From mark at msapiro.net Thu Sep 29 11:35:26 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 29 Sep 2016 08:35:26 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> Message-ID: <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> On 09/29/2016 08:04 AM, Christopher Adams wrote: > I cleared browser cache and reloaded. Same problem. Here are answers to > your questions. > > ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > /usr/local/mailman/scripts/ > > prefix = '/usr/local/mailman' OK. Send me (off list) a copy of /usr/local/mailman/Mailman/Cgi/admin.py Also, what does ls -l /usr/local/mailman/Mailman/Cgi/admin.py* show? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Thu Sep 29 11:50:23 2016 From: adamsca at gmail.com (Christopher Adams) Date: Thu, 29 Sep 2016 08:50:23 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> Message-ID: ls -l /usr/local/mailman/Mailman/Cgi/admin.py* -rw-r--r--. 1 mailman mailman 72139 Sep 28 16:19 /usr/local/mailman/Mailadmin.py -rw-r--r--. 1 apache mailman 46447 Sep 28 16:20 /usr/local/mailman/Mailadmin.pyc -rw-r--r--. 1 mailman mailman 71971 Sep 28 14:31 /usr/local/mailman/Mailadmin.py.old -rw-r--r--. 1 mailman mailman 71971 Sep 28 16:18 /usr/local/mailman/Mailadmin.py.orig I will send a copy of admin.py off list. Thanks. On Thu, Sep 29, 2016 at 8:35 AM, Mark Sapiro wrote: > On 09/29/2016 08:04 AM, Christopher Adams wrote: > > I cleared browser cache and reloaded. Same problem. Here are answers to > > your questions. > > > > ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > > /usr/local/mailman/scripts/ > > > > prefix = '/usr/local/mailman' > > > OK. > > Send me (off list) a copy of /usr/local/mailman/Mailman/Cgi/admin.py > > Also, what does > > ls -l /usr/local/mailman/Mailman/Cgi/admin.py* > > show? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Christopher Adams adamsca at gmail.com From adamsca at gmail.com Thu Sep 29 11:57:08 2016 From: adamsca at gmail.com (Christopher Adams) Date: Thu, 29 Sep 2016 08:57:08 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> References: <6fab3888-21fc-d115-b8d6-c85db4b1a0c4@msapiro.net> <0925e4cc-0d37-d391-e7ec-d8a45b5b5d30@msapiro.net> <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> Message-ID: Sorry, lines were truncated. This is more accurate. -rw-r--r--. 1 mailman mailman 72139 Sep 28 16:19 /usr/local/mailman/Mailman/admin.py -rw-r--r--. 1 apache mailman 46447 Sep 28 16:20 /usr/local/mailman/Mailman/admin.pyc -rw-r--r--. 1 mailman mailman 71971 Sep 28 14:31 /usr/local/mailman/Mailman/admin.py.old -rw-r--r--. 1 mailman mailman 71971 Sep 28 16:18 /usr/local/mailman/Mailman/admin.py.orig On Thu, Sep 29, 2016 at 8:35 AM, Mark Sapiro wrote: > On 09/29/2016 08:04 AM, Christopher Adams wrote: > > I cleared browser cache and reloaded. Same problem. Here are answers to > > your questions. > > > > ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > > /usr/local/mailman/scripts/ > > > > prefix = '/usr/local/mailman' > > > OK. > > Send me (off list) a copy of /usr/local/mailman/Mailman/Cgi/admin.py > > Also, what does > > ls -l /usr/local/mailman/Mailman/Cgi/admin.py* > > show? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Christopher Adams adamsca at gmail.com From mark at msapiro.net Thu Sep 29 15:19:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 29 Sep 2016 12:19:46 -0700 Subject: [Mailman-Users] problems linking to successive chunks of addresses in admin user search In-Reply-To: <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> References: <3e774357-88ad-c09c-fd45-c334ec671671@msapiro.net> Message-ID: Upon further investigation, I found that the prior fix was incomplete. It only fixed the 'letter' links at the top of the Membership List. It didn't fix the links to subsequent chunks at the bottom of the list. Attached is a patch to the 2.1.23 base to fix that. For older versions both this and the patch posted earlier in this thread need to be applied. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: admin.patch Type: text/x-diff Size: 836 bytes Desc: not available URL: