From dandrews at visi.com Sun Feb 1 01:55:42 2015 From: dandrews at visi.com (David Andrews) Date: Sat, 31 Jan 2015 18:55:42 -0600 Subject: [Mailman-Users] Sending a File Message-ID: With Mailman, is there a way to have all subscribers to a list sent a file, when they subscribe. Automatically, of course. I have a list where the moderator has text he wants new subscribers to receive, but it seems a little long to me, for the Welcome message. Thanks! Dave David Andrews and long white cane Harry. E-Mail: dandrews at visi.com or david.andrews at nfbnet.org From mark at msapiro.net Sun Feb 1 02:57:29 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 31 Jan 2015 17:57:29 -0800 Subject: [Mailman-Users] Moving lists with large archives to new server In-Reply-To: References: Message-ID: <54CD8809.9080106@msapiro.net> On 01/30/2015 03:09 PM, Andrew Hodgson wrote: > > My question revolves around the list archives. If I start Mailman up before they are copied across, it is likely there will be waiting messages and these will get archived to a new mbox file. I want to reduce downtime in moving the lists, but the mbox files are around 25GB, and there are a couple of lists which take the majority of that. I was going to index the messages once the mbox files are copied over, but what is the smartest way to get these moved without downing Mailman for too long? It seems like you are planning to just move the archives/private/LIST.mbox/LIST.mbox files and rebuild the archives with bin/arch --wipe after the .mbox files are moved. This in fact is the recommended procedure. One consideration is whether you want to preserve the message numbers in the new archive. If you don't do this, and someone has a saved URL to an archived message, that URL will return a different message from the new archive. So let's assume you do want to do this. The second consideration is whether your .mbox files are "good". They probably are, but if they go back several years and you haven't previously checked, they may contain unescaped "From " lines in message bodies. bin/arch is very lax about validating "From " separators. Any line that begins with those 5 characters is considered a message separator and can result in trailing parts of messages being in the archive without headers and separately from the leading parts. This is normally not an issue with .mbox files written only by 2.1.x versions of Mailman. Mailman's bin/cleanarch script can help detect and fix such problems. OK. Now we'll assume you have a bunch of good LIST.mbox files on the old server which you just stopped. I think there are two ways to proceed. You'll have to decide which works better for you. While typing, I decided Way 2. is better. Way 1. Bring up the new server and start Mailman. Let the lists operate and messages archive. These messages will ultimately be renumbered, but this is a relatively short window so it may not be an issue. Bring the LIST.mbox files as say LIST.mbox/List.mbox.old After you have the files moved, find the PID of ArchRunner via something like ps -fwwC python and kill it with SIGTERM OR SIGINT. Do not use SIGKILL or the master will just restart it. Then do something to the effect of cat LIST.mbox/List.mbox >> LIST.mbox/List.mbox.old mv LIST.mbox/List.mbox LIST.mbox/List.mbox.new mv LIST.mbox/List.mbox.old LIST.mbox/List.mbox And verify the ownership and permissions on LIST.mbox/List.mbox which now should have all the messages with the new ones at the end. Then copy the ArchRunner command from the previous ps command output and issue that command with sudo -u mailman's_uid and a trailing & to restart ArchRunner. If You don't start in in the background, it will remain attached to your terminal and breaking out will SIGINT it and it will die again. Command is like sudo -u mailman /usr/bin/python /var/MM/21/bin/qrunner \ --runner=ArchRunner:0:1 -s& Now your mbox is good and new messages are being archived and you can run bin/arch --wipe LIST to build the pipermail archive. This should be OK as bin/arch will lock the archive to prevent conflicts with incoming messages. Way 2. I think this is better. Bring up the new server, start Mailman and immediately stop ArchRunner as above before any new messages arrive, perhaps before starting the MTA. Now you can just bring the LIST.mbox/List.mbox files over and check permissions and rebuild the archives with bin/arch with --wipe or not as the pipermail archive should be empty anyway. Meanwhile lists are running and messages for the archive are queued. Then when the pipermail archives have been rebuilt, start ArchRunner as above. Now there are potentially some cleanup things to do. It is possible, depending on how many posts arrived while ArchRunner was not running, the qfiles/archive directory grew large. This can be a performance issue. See the last paragraph in the FAQ at . You can shrink the queue directory by waiting until it's empty, stopping Mailman, moving the directory aside and recreating it with the same ownership and permissions and restarting Mailman. and if by chance, one or two entries snuck in to the old, moved aside directory, move them individually back to the new directory. Finally, see the script at (mirrored at ) if you care about the modification times of the archived message files. Caveat: I just typed this out. I'm *sure* it will work, but I've been wrong before. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Feb 1 03:14:37 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 31 Jan 2015 18:14:37 -0800 Subject: [Mailman-Users] Sending a File In-Reply-To: References: Message-ID: <54CD8C0D.9090104@msapiro.net> On 01/31/2015 04:55 PM, David Andrews wrote: > With Mailman, is there a way to have all subscribers to a list sent a > file, when they subscribe. Automatically, of course. I have a list > where the moderator has text he wants new subscribers to receive, but it > seems a little long to me, for the Welcome message. You have a few choices. Actually including the file as an attachment to the list welcome message or as a separate message all together would not be hard, but would require code modification, and doing it generically would require a new list attribute for the message. So, you can put it in the list's info which is added to the web listinfo page or put it on the web somewhere and link to it from the list's info (HTML tags work here), and the put something in the welcome_msg text that emphasizes they should go to the listinfo page (a URL is already in the message) and read it or follow the link to it. Or, just put it in welcome_msg. If you're going to mail it to them anyway, what's the difference unless you feel it will distract them from other important stuff in the welcome message in which case, put it on the web and put a URL in welcome_msg. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cs at web-analysts.net Sun Feb 1 17:31:07 2015 From: cs at web-analysts.net (Web Analysts) Date: Sun, 1 Feb 2015 08:31:07 -0800 Subject: [Mailman-Users] check_perms generated error Message-ID: <014401d03e3c$82b51610$881f4230$@web-analysts.net> What does this mean? [root at zarathustra mailman]# bin/check_perms Traceback (most recent call last): File "bin/check_perms", line 391, in checkall() File "bin/check_perms", line 204, in checkall os.path.walk(d, checkwalk, STATE) File "/usr/lib/python2.7/posixpath.py", line 237, in walk walk(name, func, arg) File "/usr/lib/python2.7/posixpath.py", line 237, in walk walk(name, func, arg) File "/usr/lib/python2.7/posixpath.py", line 237, in walk walk(name, func, arg) File "/usr/lib/python2.7/posixpath.py", line 229, in walk func(arg, top, names) File "bin/check_perms", line 112, in checkwalk mode, gid = statgidmode(path) File "bin/check_perms", line 85, in statgidmode stat = os.stat(path) OSError: [Errno 40] Too many levels of symbolic links: '/usr/lib/mailman/archives/private/listname/listname' [root at zarathustra mailman]# This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. From dannys1 at mac.com Sun Feb 1 21:59:16 2015 From: dannys1 at mac.com (Dan Speranzo) Date: Sun, 01 Feb 2015 15:59:16 -0500 Subject: [Mailman-Users] Need help Message-ID: <25C7B7D0-E647-4822-9C3D-F397E3F9D502@mac.com> i am attempting to create a new email address to be used for posting. Please help. From dikim at indiana.edu Sun Feb 1 19:12:37 2015 From: dikim at indiana.edu (Kim, DongInn) Date: Sun, 1 Feb 2015 18:12:37 +0000 Subject: [Mailman-Users] master list to allow users to subscribe all the other lists without admin approval Message-ID: <3E7AA2D9-94EC-4B07-BA95-806FFD3B49C3@indiana.edu> Hi, Is there a way to setup a master list to allow any users in the master list to subscribe all the other lists in the same domain without admin approval? Note that the master list is a real list but it does not have to have any discussions through this list just like normal mailing list. Maybe, it would be like an announce mailing list. The reason that we want to do this is because we have a lot of lists in the same domain and the list administrators are annoyed with lots of redundant approval of user subscriptions. So if this master list works, the list administrators do not have to approve all the other lists but only master list. Is it possible? Regards, -- - DongInn -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 204 bytes Desc: Message signed with OpenPGP using GPGMail URL: From Ralf.Hildebrandt at charite.de Mon Feb 2 12:59:22 2015 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Mon, 2 Feb 2015 12:59:22 +0100 Subject: [Mailman-Users] check_perms generated error In-Reply-To: <014401d03e3c$82b51610$881f4230$@web-analysts.net> References: <014401d03e3c$82b51610$881f4230$@web-analysts.net> Message-ID: <20150202115922.GN21818@charite.de> * Web Analysts : > OSError: [Errno 40] Too many levels of symbolic links: > '/usr/lib/mailman/archives/private/listname/listname' Sounds like you have circular symlink somewhere around /usr/lib/mailman/archives/private/listname/listname -- Ralf Hildebrandt Charite Universit?tsmedizin Berlin ralf.hildebrandt at charite.de Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 From mark at msapiro.net Mon Feb 2 13:22:29 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 02 Feb 2015 04:22:29 -0800 Subject: [Mailman-Users] Need help In-Reply-To: <25C7B7D0-E647-4822-9C3D-F397E3F9D502@mac.com> References: <25C7B7D0-E647-4822-9C3D-F397E3F9D502@mac.com> Message-ID: <54CF6C05.80600@msapiro.net> On 02/01/2015 12:59 PM, Dan Speranzo wrote: > i am attempting to create a new email address to be used for posting. Please help. See the FAQ at . If that doesn't help, please post more details about your list and how authorized posters post to it now, e.g. do they post with an Approved: password header/pseudo-header or are they members who are not moderated. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Mon Feb 2 13:35:22 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 02 Feb 2015 21:35:22 +0900 Subject: [Mailman-Users] Need help In-Reply-To: <25C7B7D0-E647-4822-9C3D-F397E3F9D502@mac.com> References: <25C7B7D0-E647-4822-9C3D-F397E3F9D502@mac.com> Message-ID: <87y4ogpk39.fsf@uwakimon.sk.tsukuba.ac.jp> Dan Speranzo writes: > i am attempting to create a new email address to be used for > posting. Please help. This is a personal address, so that you can send mail to a mailing list? We can't help you with that. Or is this a mailing list that can have mail addressed to it and will be delivered to the subscriber list? Perhaps we can help. If so, what resources (domain, host, shell access to install software, etc) do you have to support this list? From stephen at xemacs.org Mon Feb 2 13:30:26 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 02 Feb 2015 21:30:26 +0900 Subject: [Mailman-Users] master list to allow users to subscribe all the other lists without admin approval In-Reply-To: <3E7AA2D9-94EC-4B07-BA95-806FFD3B49C3@indiana.edu> References: <3E7AA2D9-94EC-4B07-BA95-806FFD3B49C3@indiana.edu> Message-ID: <87zj8wpkbh.fsf@uwakimon.sk.tsukuba.ac.jp> Kim, DongInn writes: > Is there a way to setup a master list to allow any users in the > master list to subscribe all the other lists in the same domain > without admin approval? Not exactly that without altering the code. Such a facility will probably be available in Mailman 3. (If it isn't already -- probably it isn't, yet -- I'll file an RFE in about 5 minutes. :-) How much do you care about ensuring that only legitimate users be allowed to subscribe? You could always just not advertise the list but allow users to subscribe with user confirmation only. From mark at msapiro.net Mon Feb 2 14:09:59 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 02 Feb 2015 05:09:59 -0800 Subject: [Mailman-Users] master list to allow users to subscribe all the other lists without admin approval In-Reply-To: <87zj8wpkbh.fsf@uwakimon.sk.tsukuba.ac.jp> References: <3E7AA2D9-94EC-4B07-BA95-806FFD3B49C3@indiana.edu> <87zj8wpkbh.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <54CF7727.2030504@msapiro.net> On 02/02/2015 04:30 AM, Stephen J. Turnbull wrote: > Kim, DongInn writes: > > > Is there a way to setup a master list to allow any users in the > > master list to subscribe all the other lists in the same domain > > without admin approval? > > Not exactly that without altering the code. Such a facility will > probably be available in Mailman 3. (If it isn't already -- probably > it isn't, yet -- I'll file an RFE in about 5 minutes. :-) Steve is correct, but in Mailman 2.1.19 for which the first candidate has been released last week, there is a new Privacy options... -> Subscription rules -> subscribe_auto_approval feature that allows providing email addresses and ^regexps matching email addresses that are exempt from admin approval when subscribing. It would not be hard to extend this feature to accept the @listname syntax as well. I will consider doing this for the 2.1.19 final release, but at a minimum, I'd have to add a new i18n string or change the ones I added with this feature, and I'd like to consider i18n frozen for 2.1.19 at this point. (deep sigh ...) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Tue Feb 3 12:54:45 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 3 Feb 2015 13:54:45 +0200 Subject: [Mailman-Users] another logo images? Message-ID: Hello! I have upgraded Mailman from 2.12 to 2.18-1 and found that now we have different logo image which have white background and look? inaccurate on my gray one. Ar? the?? any image library for Mailman where I could select proper logo image? Thanks. Danil From mark at msapiro.net Tue Feb 3 17:21:47 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 03 Feb 2015 08:21:47 -0800 Subject: [Mailman-Users] another logo images? In-Reply-To: References: Message-ID: <54D0F59B.7000103@msapiro.net> On 02/03/2015 03:54 AM, Danil Smirnov wrote: > Hello! > > I have upgraded Mailman from 2.12 to 2.18-1 and found that now we have > different logo image which have white background and look? inaccurate > on my gray one. > > Ar? the?? any image library for Mailman where I could select proper logo image? See . Also see and for info on the change. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mpascal at gmail.com Tue Feb 3 19:46:39 2015 From: mpascal at gmail.com (Marino Pascal) Date: Tue, 03 Feb 2015 10:46:39 -0800 Subject: [Mailman-Users] Help with regular expression filters Message-ID: <54D1178F.1050507@gmail.com> I have a filter to block the word "test" from Subject because some people won't receive list mail for a few hours and think it's broken so they post "test" And once one person does it everybody else feels obligated to "test". So I use Subject: .*test Problem with that is that it also blocks "latest" and "testimony". I suck at regular expressions and would appreciate some help. I also don't have a test list to test this :) Thanks Marino Pascal From eminmn at sysmatrix.net Tue Feb 3 21:08:56 2015 From: eminmn at sysmatrix.net (e.c.) Date: Tue, 3 Feb 2015 14:08:56 -0600 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: <54D1178F.1050507@gmail.com> References: <54D1178F.1050507@gmail.com> Message-ID: At least in Emacs the following regexp works \_ that finds 'test' but not 'fastest' or 'testy' bash, perl, ruby, etc. may have different ways of doing the same thing. ed On Tue, Feb 3, 2015 at 12:46 PM, Marino Pascal wrote: > I have a filter to block the word "test" from Subject because some people > won't receive list mail for a few hours and think it's broken so they post > "test" > And once one person does it everybody else feels obligated to "test". > So I use > Subject: .*test > Problem with that is that it also blocks "latest" and "testimony". > I suck at regular expressions and would appreciate some help. > I also don't have a test list to test this :) > > Thanks > Marino Pascal > ------------------------------------------------------ > 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/eminmn%40sysmatrix.net From mark at msapiro.net Tue Feb 3 22:43:09 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 03 Feb 2015 13:43:09 -0800 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: References: <54D1178F.1050507@gmail.com> Message-ID: <54D140ED.6090507@msapiro.net> On 02/03/2015 12:08 PM, e.c. wrote: > At least in Emacs the following regexp works > > \_ > > that finds 'test' but not 'fastest' or 'testy' > > bash, perl, ruby, etc. may have different ways of doing the same thing. In Mailman, with Python regexps , I would use ^Subject:.*\Wtest\W \W matches any 'non-word' character and is equivalent to [^a-zA-Z0-9_], i.e. anything including new-line which is not a letter, digit or underscore. >>> import re >>> cre = re.compile('^Subject:.*\Wtest\W', re.IGNORECASE) >>> s1 = """Subject: This is a test of mailman.""" >>> s2 = """Subject: This is a test.""" >>> s3 = """Subject: I am testing...""" >>> s4 = """Subject: This is a test ... """ >>> cre.search(s1) <_sre.SRE_Match object at 0x7f740d0abac0> >>> cre.search(s2) <_sre.SRE_Match object at 0x7f740d0abb28> >>> cre.search(s3) >>> cre.search(s4) <_sre.SRE_Match object at 0x7f740d0abac0> -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Wed Feb 4 12:14:38 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 4 Feb 2015 13:14:38 +0200 Subject: [Mailman-Users] subscribers classes? Message-ID: Hi! Are there any way to send different welcome messages to subscribers which depend of their class? For example, I have announcement list with two classes of subscribers: - posters, who are allowed to post to the list (subscribed by admin) - silent members who just receive posts from the first class members (subscribed by theirselves) It would be great if I can send different welcome message tho this two classes of subscribers. Are there any chance it will be implemented? Thanks. Danil From malcolm.austen at weald.org.uk Wed Feb 4 12:38:44 2015 From: malcolm.austen at weald.org.uk (Malcolm Austen) Date: Wed, 04 Feb 2015 11:38:44 -0000 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: <54D140ED.6090507@msapiro.net> References: <54D1178F.1050507@gmail.com> <54D140ED.6090507@msapiro.net> Message-ID: On Tue, 03 Feb 2015 21:43:09 -0000, Mark Sapiro wrote: > In Mailman, with Python regexps > , I would use > > ^Subject:.*\Wtest\W > > \W matches any 'non-word' character and is equivalent to [^a-zA-Z0-9_], > i.e. anything including new-line which is not a letter, digit or > underscore. I trap with - ^subject:.*\btest.* - accepting \W is the better option, I tail it with .* as I want to catch 'testing' as well as 'test' :-) I also have traps - ^subject:.*virus.* - on 'virus', 'spam' and 'digest' :-) What I would really like is a (simple) way to trap the absence of a subject header but I think, we can (understandably) only trap on the content of something that is present :-( = Malcolm. -- Malcolm Austen GENUKI trustee Pedigree User Group Oxfordshire FHS FFHS Communications Officer From danil at smirnov.la Wed Feb 4 14:14:44 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 4 Feb 2015 15:14:44 +0200 Subject: [Mailman-Users] subscribers classes? In-Reply-To: References: Message-ID: I have an idea to create another list whose members can post to the first list without moderation. Now I can configure different welcome messages, right? :) Any advices/warns? 2015-02-04 13:14 GMT+02:00 Danil Smirnov : > Hi! > > Are there any way to send different welcome messages > to subscribers which depend of their class? > > For example, I have announcement list with two classes of subscribers: > - posters, who are allowed to post to the list (subscribed by admin) > - silent members who just receive posts from the first class members > (subscribed by theirselves) > > It would be great if I can send different welcome message tho > this two classes of subscribers. > > Are there any chance it will be implemented? > > Thanks. > > Danil From dap1 at bellsouth.net Wed Feb 4 14:25:31 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Wed, 04 Feb 2015 08:25:31 -0500 Subject: [Mailman-Users] Admin Requests Not Working In-Reply-To: <54C7E5B7.3070505@bellsouth.net> References: <54C79300.7040803@bellsouth.net> <54C7E1C7.2030601@msapiro.net> <54C7E391.3040909@msapiro.net> <54C7E5B7.3070505@bellsouth.net> Message-ID: <54D21DCB.1040805@bellsouth.net> On 1/27/2015 2:23 PM, Dennis Putnam wrote: > Hi Mark, > > They both worked for me. In any case, yes I did all those things in > the faq. However, all the requests have magically disappeared. I am > thinking it may be a caching problem as they were gone after I logged > off and back on. As long as I kept going to that page without a new > login request, they stayed on the page. Shouldn't there have at least > been an error when it tried to process requests that no longer existed? > > On 1/27/2015 2:14 PM, Mark Sapiro wrote: >> On 01/27/2015 11:06 AM, Mark Sapiro wrote: >>> See the FAQ at >>> >> That's a bit too looong... >> >> It works, but this one is a bit better >> >> > changes and may or may not ask me to re-enter my password -- what is wrong?> >> >> We need a way to generate short URLs for this wiki. The old Confluence >> tiny URLs work through a remapping process, but we don't yet have a way >> to generate new ones. It's on my list ... >> >> >> Hi Mark, Well, I thought the requests had disappeared but I was wrong. I'm not sure why they seemed to be gone other than operator error. In any case I searched through the logs and found nothing except this: 192.168.0.102 - - [02/Feb/2015:15:51:30 -0500] "POST /mailman/admindb/mailman HTTP/1.1" 302 222 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0" Which is perfectly normal. I guess I need to turn on some kind of debug to see what this thing is doing. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From lac at openend.se Wed Feb 4 14:52:27 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 4 Feb 2015 14:52:27 +0100 Subject: [Mailman-Users] How to configure mailman to only deliver mail a few times a day? Message-ID: <201502041352.t14DqRJI026736@fido.openend.se> My google-foo is not working today. I am the member of a very ancient mailing list that would like to modernise. To that end, somebody made a list of requirements that they would need to have to just have the functionality they have now ... the thing went on for pages and pages but since I am quite familiar with mailman, I was able to say yep .... yep .... yep ... let me check, ok, yep ... and so on down their long list. Until I hit this requirement. Currently what we receive is one digest every day. It can be a very long digest. While some people want to continue receiving digests, and some people don't, everybody is in favour of having the mail only go out in batches at set intervals during the day. So maybe once a day is too infrequent, and 3 times a day would be nicer, but what is not wanted is 'deliver this as soon as it arrives'. I'm not finding the correct place for figuring out how frequently mailman decides to send mail. Where should I be looking? Thanks very much, Laura Creighton From stephen at xemacs.org Wed Feb 4 15:04:07 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 04 Feb 2015 23:04:07 +0900 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: References: <54D1178F.1050507@gmail.com> <54D140ED.6090507@msapiro.net> Message-ID: <87r3u5pyco.fsf@uwakimon.sk.tsukuba.ac.jp> Malcolm Austen writes: > What I would really like is a (simple) way to trap the absence of a > subject header but I think, we can (understandably) only trap on the > content of something that is present :-( As a workaround, procmail supports negative assertions of that kind: :0: * ! ^Subject no-subject-bitbucket would do what you want. That may not be acceptable to you, of course, depending on the facilities available to you, or convenience. Just throwing it out there, somebody might find it useful. I don't think it would be hard to add this feature if there's no way to do it, although Mark may not want to do it in 2.1.x. Wait for Mark and if he says it can't be done in current Mailman, I'd suggest filing an RFE at https://launchpad.net/mailman. Steve From adam-mailman at amyl.org.uk Wed Feb 4 15:09:28 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Wed, 4 Feb 2015 14:09:28 +0000 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: <54D1178F.1050507@gmail.com> References: <54D1178F.1050507@gmail.com> Message-ID: <20150204140928.GA11902@hendricks.amyl.org.uk> On Tue, Feb 03, 2015 at 10:46:39AM -0800, Marino Pascal wrote: > I have a filter to block the word "test" from Subject because some > people won't receive list mail for a few hours and think it's broken > so they post "test" People who send test mails to lists I manage usually find themselves moderated. -- "I am firm. You are obstinate. He is a pig-headed fool." -- Katharine Whitehorn From stephen at xemacs.org Wed Feb 4 16:33:19 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 05 Feb 2015 00:33:19 +0900 Subject: [Mailman-Users] How to configure mailman to only deliver mail a few times a day? In-Reply-To: <201502041352.t14DqRJI026736@fido.openend.se> References: <201502041352.t14DqRJI026736@fido.openend.se> Message-ID: <87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> Laura Creighton writes: Hi Laura! > While some people want to continue receiving digests, and some > people don't, everybody is in favour of having the mail only go out > in batches at set intervals during the day. So maybe once a day is > too infrequent, and 3 times a day would be nicer, but what is not > wanted is 'deliver this as soon as it arrives'. Mailman delivers as soon as the mail arrives, except for digests. This is not configurable in Mailman. You might be able to run a cron job which starts Mailman at 0, 8, and 16 hours, and stops it at 1, 9, and 17 hours. Seems kinda kludgy but should work (untested, of course). I thought about just stopping the outgoing runner, but that's going to be really messy. Digests are delivered when the size limit is reached (if digest_size_threshold > 0), or once a day (if digest_send_periodic is set), which ever comes first. The size limit is set on the "Digest Options" view of the "Administration" page for the list. I suppose it might be possible to modify Mailman to hang on to posts for a few hours and send them out in batches, but this might cause a large load on the mail server during that period. From mark at msapiro.net Wed Feb 4 16:56:14 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 07:56:14 -0800 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: <87r3u5pyco.fsf@uwakimon.sk.tsukuba.ac.jp> References: <54D1178F.1050507@gmail.com> <54D140ED.6090507@msapiro.net> <87r3u5pyco.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <54D2411E.6010004@msapiro.net> On 02/04/2015 06:04 AM, Stephen J. Turnbull wrote: > Malcolm Austen writes: > > > What I would really like is a (simple) way to trap the absence of a > > subject header but I think, we can (understandably) only trap on the > > content of something that is present :-( ... > > I don't think it would be hard to add this feature if there's no way > to do it, although Mark may not want to do it in 2.1.x. Wait for Mark > and if he says it can't be done in current Mailman, I'd suggest filing > an RFE at https://launchpad.net/mailman. In my production Mailman, I do it as part of the tests in a custom handler, but see the FAQ at for a way to do it with header_filter_rules. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lac at openend.se Wed Feb 4 17:05:31 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 04 Feb 2015 17:05:31 +0100 Subject: [Mailman-Users] How to configure mailman to only deliver mail a few times a day? In-Reply-To: Message from "Stephen J. Turnbull" of "Thu, 05 Feb 2015 00:33:19 +0900." <87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> References: <201502041352.t14DqRJI026736@fido.openend.se><87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <201502041605.t14G5VQn021989@fido.openend.se> In a message of Thu, 05 Feb 2015 00:33:19 +0900, "Stephen J. Turnbull" writes: >Laura Creighton writes: > >Hi Laura! > > > While some people want to continue receiving digests, and some > > people don't, everybody is in favour of having the mail only go out > > in batches at set intervals during the day. So maybe once a day is > > too infrequent, and 3 times a day would be nicer, but what is not > > wanted is 'deliver this as soon as it arrives'. > >Mailman delivers as soon as the mail arrives, except for digests. >This is not configurable in Mailman. You might be able to run a cron >job which starts Mailman at 0, 8, and 16 hours, and stops it at 1, 9, >and 17 hours. Seems kinda kludgy but should work (untested, of >course). I thought about just stopping the outgoing runner, but >that's going to be really messy. Okay then. Nice to know I wasn't finding anything because it wasn't there to be found. :) >Digests are delivered when the size limit is reached (if >digest_size_threshold > 0), or once a day (if digest_send_periodic is >set), which ever comes first. The size limit is set on the "Digest >Options" view of the "Administration" page for the list. This was the place I was sort of hoping that 'once a day' could be changed to 'once every 6 hours', but my rather cursory glance at the code made me conclude -- nope, not here. >I suppose it might be possible to modify Mailman to hang on to posts >for a few hours and send them out in batches, but this might cause a >large load on the mail server during that period. I can guarantee that this would not be a problem for our particular user community. ;) Even if every one of us decided to passionately wade in and post to the max on a huge-and-pointless flame war -- there still aren't enough of us to provide a large load. But your point is well-taken. The flame-war part is precisely why people want deliveries to be once, or a few times a day. The belief is that people who have to think about what they are writing -- as they only get one crack at it every 24 hours -- produce more reasoned responses than those people who are more accustomed to shooting from the hip and then apologising later if they turn out to be wrong. Thus in the eternal 'give mailman 3.0 everything that we cannot do now' discussion, a 'cool-down' period has just now shown up as a thing that real users have been asking for, and which would have ended up as a blocker for moving from 25 year old software to mailman -- except that if I cannot convince them I know how to hack a cron job, then I am just rubbish as a spokesman, and that's all. :) Thanks very much Stephen. Always a pleasure. Laura From mark at msapiro.net Wed Feb 4 17:07:07 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 08:07:07 -0800 Subject: [Mailman-Users] How to configure mailman to only deliver mail a few times a day? In-Reply-To: <87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> References: <201502041352.t14DqRJI026736@fido.openend.se> <87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <54D243AB.2090406@msapiro.net> On 02/04/2015 07:33 AM, Stephen J. Turnbull wrote: > Laura Creighton writes: > > Hi Laura! > > > While some people want to continue receiving digests, and some > > people don't, everybody is in favour of having the mail only go out > > in batches at set intervals during the day. So maybe once a day is > > too infrequent, and 3 times a day would be nicer, but what is not > > wanted is 'deliver this as soon as it arrives'. > > Mailman delivers as soon as the mail arrives, except for digests. > This is not configurable in Mailman. You might be able to run a cron > job which starts Mailman at 0, 8, and 16 hours, and stops it at 1, 9, > and 17 hours. Seems kinda kludgy but should work (untested, of > course). I thought about just stopping the outgoing runner, but > that's going to be really messy. See the FAQ at . I don't think you could use the throttle.patch directly, but you could use the idea perhaps to do what you want, but it would probably be a kludge. > Digests are delivered when the size limit is reached (if > digest_size_threshold > 0), or once a day (if digest_send_periodic is > set), which ever comes first. The size limit is set on the "Digest > Options" view of the "Administration" page for the list. You can adjust Mailman's crontab to run cron/senddigests more frequently which could help, but then people who want a less frequent digest wouldn't have that option. > I suppose it might be possible to modify Mailman to hang on to posts > for a few hours and send them out in batches, but this might cause a > large load on the mail server during that period. That's what I was getting at above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Feb 4 17:09:13 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 08:09:13 -0800 Subject: [Mailman-Users] How to configure mailman to only deliver mail a few times a day? In-Reply-To: <201502041605.t14G5VQn021989@fido.openend.se> References: <201502041352.t14DqRJI026736@fido.openend.se><87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> <201502041605.t14G5VQn021989@fido.openend.se> Message-ID: <54D24429.2040007@msapiro.net> On 02/04/2015 08:05 AM, Laura Creighton wrote: > > This was the place I was sort of hoping that 'once a day' could be > changed to 'once every 6 hours', but my rather cursory glance at the > code made me conclude -- nope, not here. In Mailman's crontab - see my last reply. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From malcolm.austen at weald.org.uk Wed Feb 4 17:16:09 2015 From: malcolm.austen at weald.org.uk (Malcolm Austen) Date: Wed, 04 Feb 2015 16:16:09 -0000 Subject: [Mailman-Users] Help with regular expression filters In-Reply-To: <54D2411E.6010004@msapiro.net> References: <54D1178F.1050507@gmail.com> <54D140ED.6090507@msapiro.net> <87r3u5pyco.fsf@uwakimon.sk.tsukuba.ac.jp> <54D2411E.6010004@msapiro.net> Message-ID: On Wed, 04 Feb 2015 15:56:14 -0000, Mark Sapiro wrote: >> Malcolm Austen writes: >> >> > What I would really like is a (simple) way to trap the absence of a >> > subject header but I think, we can (understandably) only trap on the >> > content of something that is present :-( > ... > > In my production Mailman, I do it as part of the tests in a custom > handler, but see the FAQ at for a way > to do it with header_filter_rules. Thank you Mark, I had missed that in the FAQ (slaps wrist). It makes perfect sense once explained! = Malcolm. -- Malcolm Austen GENUKI trustee Pedigree User Group Oxfordshire FHS FFHS Communications Officer From danil at smirnov.la Wed Feb 4 17:37:52 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 4 Feb 2015 18:37:52 +0200 Subject: [Mailman-Users] encoding of bin/script output Message-ID: Hello! I've noticed that output of bin scripts depends on $LANG environment variable. I can switch languages of output by issue "export LANG=en_US (or ru_RU)". But what I could not find is how to switch a charset of output. I tried to issue "export LANG=ru_RU.UTF-8", "export LANG=ru_RU.koi8-r" but output remains the same. For example, nano text editor reacts on commands listed above and become unreadable in any encoding other than "ru_RU.UTF-8". Thanks, Danil From lac at openend.se Wed Feb 4 17:55:35 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 04 Feb 2015 17:55:35 +0100 Subject: [Mailman-Users] How to configure mailman to only deliver mail a few times a day? In-Reply-To: Message from Mark Sapiro of "Wed, 04 Feb 2015 08:09:13 -0800." <54D24429.2040007@msapiro.net> References: <201502041352.t14DqRJI026736@fido.openend.se><87mw4tpu80.fsf@uwakimon.sk.tsukuba.ac.jp> <201502041605.t14G5VQn021989@fido.openend.se><54D24429.2040007@msapiro.net> Message-ID: <201502041655.t14GtZ0p032328@fido.openend.se> In a message of Wed, 04 Feb 2015 08:09:13 -0800, Mark Sapiro writes: >> This was the place I was sort of hoping that 'once a day' could be >> changed to 'once every 6 hours', but my rather cursory glance at the >> code made me conclude -- nope, not here. > > >In Mailman's crontab - see my last reply. Thanks Mark. Laura From subads at gmail.com Wed Feb 4 20:26:39 2015 From: subads at gmail.com (cha charle) Date: Wed, 4 Feb 2015 13:26:39 -0600 Subject: [Mailman-Users] Mailman on Google App Message-ID: Hello, Currently, we have Postfix and Mailman on our server, but will migrate our server to Google App. From what I read, Mailman will not work with Google App. So, does anyone have any suggestion how should I proceed with Mailman? Thanks! From lac at openend.se Wed Feb 4 20:42:21 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 04 Feb 2015 20:42:21 +0100 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: Message from cha charle of "Wed, 04 Feb 2015 13:26:39 -0600." References: Message-ID: <201502041942.t14JgLVb002297@fido.openend.se> Unless Google App Engine has changed recently, it cannot receive any mail at all. So you need to move your mailing list software to someplace else, mailman friendly. There is no hope of doing what you want. Sorry about that, Laura Creighton From xie.47 at osu.edu Wed Feb 4 20:37:30 2015 From: xie.47 at osu.edu (Xie, Wei) Date: Wed, 4 Feb 2015 19:37:30 +0000 Subject: [Mailman-Users] Monthly email reminder of what mailman lists they were subscribed to and the password for each list. Message-ID: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA5DF6@CIO-KRC-D1MBX06.osuad.osu.edu> Mark, If in mailman server configuration file mm_cfg.py we turn off the sending monthly password reminders below, DEFAULT_SEND_REMINDERS = No but the setting " Send monthly password reminders?" for one mailman mailing list is set to "Yes", Can each subscriber of this list receive a monthly email reminder of what mailman lists they were subscribed to and the password for this list? Thanks, Carl Xie (Wei Xie) From danil at smirnov.la Wed Feb 4 21:18:15 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 4 Feb 2015 22:18:15 +0200 Subject: [Mailman-Users] encoding of bin/script output In-Reply-To: References: Message-ID: It seems I forgot to type my question: how could I force bin scripts to change encoding of their output? Thanks. 2015-02-04 18:37 GMT+02:00 Danil Smirnov : > Hello! > > I've noticed that output of bin scripts depends on $LANG environment variable. > I can switch languages of output by issue "export LANG=en_US (or ru_RU)". > > But what I could not find is how to switch a charset of output. > > I tried to issue "export LANG=ru_RU.UTF-8", "export LANG=ru_RU.koi8-r" > but output remains the same. > > For example, nano text editor reacts on commands listed above and become > unreadable in any encoding other than "ru_RU.UTF-8". > > Thanks, > Danil From subads at gmail.com Wed Feb 4 22:50:54 2015 From: subads at gmail.com (cha charle) Date: Wed, 4 Feb 2015 15:50:54 -0600 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: <201502041942.t14JgLVb002297@fido.openend.se> References: <201502041942.t14JgLVb002297@fido.openend.se> Message-ID: Hi, Thanks for your quick reply; then is it possible to continue run a Mailman server and still have my email move to Google App. Thanks! On Wed, Feb 4, 2015 at 1:42 PM, Laura Creighton wrote: > Unless Google App Engine has changed recently, it cannot receive any > mail at all. So you need to move your mailing list software to > someplace else, mailman friendly. There is no hope of doing what you > want. > > Sorry about that, > Laura Creighton > From lac at openend.se Wed Feb 4 23:10:42 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 04 Feb 2015 23:10:42 +0100 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: Message from cha charle of "Wed, 04 Feb 2015 15:50:54 -0600." References: <201502041942.t14JgLVb002297@fido.openend.se> Message-ID: <201502042210.t14MAg47032758@fido.openend.se> In a message of Wed, 04 Feb 2015 15:50:54 -0600, cha charle writes: >Hi, > >Thanks for your quick reply; then is it possible to continue run a Mailman >server and still have my email move to Google App. Thanks! > >On Wed, Feb 4, 2015 at 1:42 PM, Laura Creighton wrote: > >> Unless Google App Engine has changed recently, it cannot receive any >> mail at all. So you need to move your mailing list software to >> someplace else, mailman friendly. There is no hope of doing what you >> want. >> >> Sorry about that, >> Laura Creighton I don't know what you mean by 'have my email move to Google App'. As far as I know, you cannot have your email move to Google app engine, at all, period, and this is the #1 limitation of such a thing. So you move your mailing list software someplace else that is mailman-friendly, and then you run the rest of your app with AppEngine, assuming this is what you want to do. Someone will correct me if things have changed since the last time I looked. Laura Creighton From lac at openend.se Wed Feb 4 23:27:44 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 04 Feb 2015 23:27:44 +0100 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: Message from Laura Creighton of "Wed, 04 Feb 2015 23:10:42 +0100." <201502042210.t14MAg47032758@fido.openend.se> References: <201502041942.t14JgLVb002297@fido.openend.se><201502042210.t14MAg47032758@fido.openend.se> Message-ID: <201502042227.t14MRiZj003823@fido.openend.se> I just checked. read https://cloud.google.com/appengine/docs/python/mail/receivingmail My apologies. Google App Engine used to be set up so that no email could be recevied at all. Now that is the default, but it can be overwritten. Can we get mailman to work under these Google App Engine restrictions? I don't know anybody who has done this, but I don't know everybody on this planet, 'natch. Somebody else will be sure to speak up now that I have put my foot in it. sorry again, Laura From subads at gmail.com Thu Feb 5 01:05:10 2015 From: subads at gmail.com (cha charle) Date: Wed, 4 Feb 2015 18:05:10 -0600 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: <201502042227.t14MRiZj003823@fido.openend.se> References: <201502041942.t14JgLVb002297@fido.openend.se> <201502042210.t14MAg47032758@fido.openend.se> <201502042227.t14MRiZj003823@fido.openend.se> Message-ID: Laura, Thanks for all the information--it is very helpful. On Wed, Feb 4, 2015 at 4:27 PM, Laura Creighton wrote: > I just checked. > > read https://cloud.google.com/appengine/docs/python/mail/receivingmail > > My apologies. Google App Engine used to be set up so that no email > could be recevied at all. Now that is the default, but it can > be overwritten. > > Can we get mailman to work under these Google App Engine restrictions? > I don't know anybody who has done this, but I don't know everybody on > this planet, 'natch. Somebody else will be sure to speak up now that > I have put my foot in it. > > sorry again, > Laura > > > From anitacorr at gmail.com Wed Feb 4 18:21:58 2015 From: anitacorr at gmail.com (Ana Cutillas) Date: Wed, 4 Feb 2015 18:21:58 +0100 Subject: [Mailman-Users] Upgrading to MM3 Message-ID: Hi, I have a list using MM2 and I'm wondering, if I started using MM3, would I be able to just plug in the same database that I'm using with MM2? Or would I have to do anything different to keep the archives? Thanks! Ana From jsceets at beau.org Wed Feb 4 18:10:52 2015 From: jsceets at beau.org (James Sceets) Date: Wed, 04 Feb 2015 11:10:52 -0600 Subject: [Mailman-Users] Mailman Bug Message-ID: <1423069852.4348.23.camel@catchfly.library.beau.org> Ok we are running version 2.1.5 on an old White Box server and are encountering this bug which is preventing us from accessing the membership management pages for some (but not all) of our mailing lists. "if bucket not in digits + '_' + lowercase: TypeError: 'in ' requires character as left operand" I added the '_' to the first line thinking maybe someone used an underscore as the first character in the address and mailman didn't like that but no joy. I asked the Google overlords for an answer with no help (maybe my google-fu needs honing) so I apologize if this is an issue that's been fixed 100 times over. Any help on what to twiddle would be helpful. It can't be as simple as something like adding '' to the if statement right? My Python skills are quite rudimentary (read: neanderthal). -- James Sceets BPL Helpdesk From mark at msapiro.net Thu Feb 5 01:49:43 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 16:49:43 -0800 Subject: [Mailman-Users] Monthly email reminder of what mailman lists they were subscribed to and the password for each list. In-Reply-To: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA5DF6@CIO-KRC-D1MBX06.osuad.osu.edu> References: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA5DF6@CIO-KRC-D1MBX06.osuad.osu.edu> Message-ID: <54D2BE27.90402@msapiro.net> On 02/04/2015 11:37 AM, Xie, Wei wrote: > > If in mailman server configuration file mm_cfg.py we turn off the sending monthly password reminders below, > > DEFAULT_SEND_REMINDERS = No That setting only affects the default value of send_reminders (Send monthly password reminders?) for lists created after you make the change. > but the setting " Send monthly password reminders?" for one mailman mailing list is set to "Yes", Can each subscriber of this list receive a monthly email reminder of what mailman lists they were subscribed to and the password for this list? If only one list has send_reminders = Yes, the members of that one list who have their own "Get password reminder email for this list?" set to Yes will receive a monthly reminder for that list only. I.e., as long as cron/mailpasswds is being run monthly a user will receive a monthly reminder which includes the options page link and password for each list in the domain of which she is a member for which both the list's send_reminders = Yes and the her "Get password reminder email for this list?" = Yes and only those lists, unless there are no such lists in which case no reminder is sent. So if your question is will this reminder include the list name but not the password (or the list name and password) for lists of which she is a member but for which send_reminders = No, the answer is No. Lists for which send_reminders = No will not be mentioned in any way in the monthly reminder email. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 02:14:02 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 17:14:02 -0800 Subject: [Mailman-Users] encoding of bin/script output In-Reply-To: References: Message-ID: <54D2C3DA.3040909@msapiro.net> On 02/04/2015 12:18 PM, Danil Smirnov wrote: > It seems I forgot to type my question: > how could I force bin scripts to change encoding of their output? You can't. You say "output of bin scripts depends on $LANG environment variable". I don't think that's correct. I think it depends, in those cases where it isn't English only, on Mailman's setting for DEFAULT_SERVER_LANGUAGE. In any case Mailman has a character encoding for each language it knows and it always uses that encoding. For Russian, this encoding is koi8-r because that is the encoding that was used when the Russian translation was first developed. If you think the encoding should be utf-8, you can change it for your own site by putting add_language('ru', 'Russian', 'utf-8', 'ltr') in mm_cfg.py and recoding all of templates/ru/* and the messages/ru/LC_MESSAGES/mailman.po file to utf-8 and regenerating the messages/ru/LC_MESSAGES/mailman.mo file. If you want us to change it for a future release, file a bug at and try to make a good argument for it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 02:36:03 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 17:36:03 -0800 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: References: <201502041942.t14JgLVb002297@fido.openend.se> Message-ID: <54D2C903.8080407@msapiro.net> On 02/04/2015 01:50 PM, cha charle wrote: > > Thanks for your quick reply; then is it possible to continue run a Mailman > server and still have my email move to Google App. Thanks! As long as the domain in which you have your email lists is distinct from, perhaps a subdomain of, your main domain, e.g. lists.example.com or mm.example.com where the main domain is example.com, it should be no problem to have a separate MX for that domain pointing to the Mailman server. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 02:43:36 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 17:43:36 -0800 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: <201502042227.t14MRiZj003823@fido.openend.se> References: <201502041942.t14JgLVb002297@fido.openend.se><201502042210.t14MAg47032758@fido.openend.se> <201502042227.t14MRiZj003823@fido.openend.se> Message-ID: <54D2CAC8.9070808@msapiro.net> On 02/04/2015 02:27 PM, Laura Creighton wrote: > > My apologies. Google App Engine used to be set up so that no email > could be recevied at all. Now that is the default, but it can > be overwritten. > > Can we get mailman to work under these Google App Engine restrictions? > I don't know anybody who has done this, but I don't know everybody on > this planet, 'natch. I don't know everyone on the planet either nor do I know everyone who's ever installed Mailman, but I'm more likely than most to have heard of someone trying to install a Mailman instance under Google Apps and running into problems, so it's likely one of two things; it's easy or no one's tried it. I suspect the latter, but since I know nothing about Google Apps, I really have no idea whether it is possible, and if so, how difficult it would be. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 03:33:13 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 18:33:13 -0800 Subject: [Mailman-Users] Mailman Bug In-Reply-To: <1423069852.4348.23.camel@catchfly.library.beau.org> References: <1423069852.4348.23.camel@catchfly.library.beau.org> Message-ID: <54D2D669.4000706@msapiro.net> On 02/04/2015 09:10 AM, James Sceets wrote: > Ok we are running version 2.1.5 on an old White Box server and are > encountering this bug which is preventing us from accessing the > membership management pages for some (but not all) of our mailing > lists. > > "if bucket not in digits + '_' + lowercase: > TypeError: 'in ' requires character as left operand" > > I added the '_' to the first line ... There were some changes in 2.1.12 to allow members whose address begins with a non-alphanumeric character to be visible and retrievable, but before that, such members were just not seen, no bug occurred. Looking at the 2.1.5 code, it seems the error will maybe occur only if the URL accessing the page has a query fragment of the form 'letter=' or 'letter'. I.e. a URL similar to http://example.com/mailman/admin/listname/members?letter= The specific code in 2.1.5 is: qsenviron = os.environ.get('QUERY_STRING') if qsenviron: qs = cgi.parse_qs(qsenviron) bucket = qs.get('letter', 'a')[0].lower() if bucket not in digits + lowercase: bucket = None The TypeError says that bucket is not a character (i.e. string of length 1). It is difficult to see how this could occur at all. If the value of 'letter' exists and does not have length at least 1, qs.get('letter', 'a')[0] will throw an IndexError, and if it's not a string it won't have a .lower() method and that will throw an AttributeError. So I have to conclude this code is modified in some way beyond adding just the underscore. In any case, the full error log message with the complete traceback and python and environment info may help me say more. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 03:40:07 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 18:40:07 -0800 Subject: [Mailman-Users] subscribers classes? In-Reply-To: References: Message-ID: <54D2D807.3020408@msapiro.net> On 02/04/2015 03:14 AM, Danil Smirnov wrote: > > Are there any way to send different welcome messages > to subscribers which depend of their class? > > For example, I have announcement list with two classes of subscribers: > - posters, who are allowed to post to the list (subscribed by admin) > - silent members who just receive posts from the first class members > (subscribed by theirselves) > > It would be great if I can send different welcome message tho > this two classes of subscribers. > > Are there any chance it will be implemented? Little to none beyond what's currently there, but consider this. You can have the standard list welcome be the one for users who subscribe themselves. Then for the ones added by the admin, the admin can use the Membership Management... -> Mass Subscription page and either add additional text in the "Below, enter additional text to be added to the top of your invitation or the subscription notification. Include at least one blank line at the end..." box, or if that isn't satisfactory, select No for "Send welcome messages to new subscribees?" and then send a separate email to the new user(s). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 03:44:53 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 18:44:53 -0800 Subject: [Mailman-Users] subscribers classes? In-Reply-To: References: Message-ID: <54D2D925.4020803@msapiro.net> On 02/04/2015 05:14 AM, Danil Smirnov wrote: > I have an idea to create another list whose members can post to the > first list without moderation. > Now I can configure different welcome messages, right? :) Yes, but how do they receive the posts from the first list? You probably want everyone on the second list to be moderated so they can't post there, and you probably want the second list to be in the first list's Non-digest options -> regular_include_lists so that the members of the second list receive posts to the first list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 06:40:29 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 04 Feb 2015 21:40:29 -0800 Subject: [Mailman-Users] Admin Requests Not Working In-Reply-To: <54D21DCB.1040805@bellsouth.net> References: <54C79300.7040803@bellsouth.net> <54C7E1C7.2030601@msapiro.net> <54C7E391.3040909@msapiro.net> <54C7E5B7.3070505@bellsouth.net> <54D21DCB.1040805@bellsouth.net> Message-ID: <54D3024D.40203@msapiro.net> On 02/04/2015 05:25 AM, Dennis Putnam wrote: > > Well, I thought the requests had disappeared but I was wrong. I'm not > sure why they seemed to be gone other than operator error. In any case I > searched through the logs and found nothing except this: > > 192.168.0.102 - - [02/Feb/2015:15:51:30 -0500] "POST > /mailman/admindb/mailman HTTP/1.1" 302 222 "-" "Mozilla/5.0 (Windows NT > 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0" > > Which is perfectly normal. I guess I need to turn on some kind of debug > to see what this thing is doing. Thanks. When you go to the admindb page for the list, look at the exact URL of the page in the address bar. Then depending on what you actually do, i.e. accept/reject/discard message(s) from the summary page or go to a detail link and accept/reject/discard message(s) from there, look at the exact URL of any other pages in the address bar and also look at the source of all the pages you visit for the URLs in action= elements in form tags and the URLs in links you visit. Do all these have the exact same host name (relative actions/links are the same host as that of the URL of the page and are OK) and scheme? You are looking for anything different, i.e. a different host or scheme (http vs. https). One common way this occurs is the form action on an https page is an http url which gets redirected by the web server to https. The redirect loses the POST data. This is covered in the FAQ at but you may have missed it. If you need more than that, you'll have to add debug logging to Mailman/Cgi/admindb.py such as after def main(): global ssort <- you may not have this line # Figure out which list is being requested parts = Utils.GetPathPieces() add for p in parts: syslog('debug', 'Part from Utils.GetPathPieces(): %s', p) and after # Make sure the user is authorized to see this page. cgidata = cgi.FieldStorage(keep_blank_values=1) add for k, v in cgidata.items(): syslog('debug', 'cgidata: %s: %s', k, v) This will write entries to a 'debug' log in Mailman's logs/ directory (or /var/log/mailman/debug in RHEL/CentOS) and you can then see if the script is actually getting the things it should be getting. -- 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 dap1 at bellsouth.net Thu Feb 5 14:25:42 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Thu, 05 Feb 2015 08:25:42 -0500 Subject: [Mailman-Users] Admin Requests Not Working In-Reply-To: <54D3024D.40203@msapiro.net> References: <54C79300.7040803@bellsouth.net> <54C7E1C7.2030601@msapiro.net> <54C7E391.3040909@msapiro.net> <54C7E5B7.3070505@bellsouth.net> <54D21DCB.1040805@bellsouth.net> <54D3024D.40203@msapiro.net> Message-ID: <54D36F56.10205@bellsouth.net> On 2/5/2015 12:40 AM, Mark Sapiro wrote: > On 02/04/2015 05:25 AM, Dennis Putnam wrote: >> Well, I thought the requests had disappeared but I was wrong. I'm not >> sure why they seemed to be gone other than operator error. In any case I >> searched through the logs and found nothing except this: >> >> 192.168.0.102 - - [02/Feb/2015:15:51:30 -0500] "POST >> /mailman/admindb/mailman HTTP/1.1" 302 222 "-" "Mozilla/5.0 (Windows NT >> 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0" >> >> Which is perfectly normal. I guess I need to turn on some kind of debug >> to see what this thing is doing. Thanks. > > When you go to the admindb page for the list, look at the exact URL of > the page in the address bar. Then depending on what you actually do, > i.e. accept/reject/discard message(s) from the summary page or go to a > detail link and accept/reject/discard message(s) from there, look at the > exact URL of any other pages in the address bar and also look at the > source of all the pages you visit for the URLs in action= elements in > form tags and the URLs in links you visit. > > Do all these have the exact same host name (relative actions/links are > the same host as that of the URL of the page and are OK) and scheme? You > are looking for anything different, i.e. a different host or scheme > (http vs. https). > > One common way this occurs is the form action on an https page is an > http url which gets redirected by the web server to https. The redirect > loses the POST data. This is covered in the FAQ at > but you may have missed it. > > If you need more than that, you'll have to add debug logging to > Mailman/Cgi/admindb.py such as > > after > > def main(): > global ssort <- you may not have this line > # Figure out which list is being requested > parts = Utils.GetPathPieces() > > > add > > for p in parts: > syslog('debug', 'Part from Utils.GetPathPieces(): %s', p) > > and after > > # Make sure the user is authorized to see this page. > cgidata = cgi.FieldStorage(keep_blank_values=1) > > > add > > for k, v in cgidata.items(): > syslog('debug', 'cgidata: %s: %s', k, v) > > This will write entries to a 'debug' log in Mailman's logs/ directory > (or /var/log/mailman/debug in RHEL/CentOS) and you can then see if the > script is actually getting the things it should be getting. > > Hi Mark, They all look consistent to me. https://server/mailman/admindb/... I will try your debug sometime this weekend. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From xie.47 at osu.edu Thu Feb 5 15:59:58 2015 From: xie.47 at osu.edu (Xie, Wei) Date: Thu, 5 Feb 2015 14:59:58 +0000 Subject: [Mailman-Users] Monthly email reminder of what mailman lists they were subscribed to and the password for each list. In-Reply-To: <54D2BE27.90402@msapiro.net> References: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA5DF6@CIO-KRC-D1MBX06.osuad.osu.edu> <54D2BE27.90402@msapiro.net> Message-ID: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA646B@CIO-KRC-D1MBX06.osuad.osu.edu> >>If only one list has send_reminders = Yes, the members of that one list who have their own "Get password reminder email for this list?" set to Yes will receive a monthly >>reminder for that list only. Got it. >>I.e., as long as cron/mailpasswds is being run monthly a user will receive a monthly reminder which includes the options page link and password for each list in the domain >>of which she is a member for which both the list's send_reminders = Yes and the her "Get password reminder email for this list?" = Yes and only those lists, unless there >>are no such lists in which case no reminder is sent. We obviously comment out this cron job. We have over 4,200 mailing lists and over 854,100 subscribers. If password reminders are sent out all subscribers at 5AM on the first of each month, this will be heavy email burden to our mailman servers. # 5 AM on the first of each month, mail out password reminders. #0 5 1 * * /usr/bin/python -S /usr/local/mailman/cron/mailpasswds Thanks, Carl -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Wednesday, February 04, 2015 7:50 PM To: Xie, Wei; mailman-users at python.org Subject: Re: Monthly email reminder of what mailman lists they were subscribed to and the password for each list. On 02/04/2015 11:37 AM, Xie, Wei wrote: > > If in mailman server configuration file mm_cfg.py we turn off the > sending monthly password reminders below, > > DEFAULT_SEND_REMINDERS = No That setting only affects the default value of send_reminders (Send monthly password reminders?) for lists created after you make the change. > but the setting " Send monthly password reminders?" for one mailman mailing list is set to "Yes", Can each subscriber of this list receive a monthly email reminder of what mailman lists they were subscribed to and the password for this list? If only one list has send_reminders = Yes, the members of that one list who have their own "Get password reminder email for this list?" set to Yes will receive a monthly reminder for that list only. I.e., as long as cron/mailpasswds is being run monthly a user will receive a monthly reminder which includes the options page link and password for each list in the domain of which she is a member for which both the list's send_reminders = Yes and the her "Get password reminder email for this list?" = Yes and only those lists, unless there are no such lists in which case no reminder is sent. So if your question is will this reminder include the list name but not the password (or the list name and password) for lists of which she is a member but for which send_reminders = No, the answer is No. Lists for which send_reminders = No will not be mentioned in any way in the monthly reminder email. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 5 18:56:48 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 05 Feb 2015 09:56:48 -0800 Subject: [Mailman-Users] Monthly email reminder of what mailman lists they were subscribed to and the password for each list. In-Reply-To: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA646B@CIO-KRC-D1MBX06.osuad.osu.edu> References: <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA5DF6@CIO-KRC-D1MBX06.osuad.osu.edu> <54D2BE27.90402@msapiro.net> <2F60D2B899AFBC4FAF660B2D9845BE8F0DDA646B@CIO-KRC-D1MBX06.osuad.osu.edu> Message-ID: <54D3AEE0.9010707@msapiro.net> On 02/05/2015 06:59 AM, Xie, Wei wrote: > >>> I.e., as long as cron/mailpasswds is being run monthly a user will receive a monthly reminder which includes the options page link and password for each list in the domain >>of which she is a member for which both the list's send_reminders = Yes and the her "Get password reminder email for this list?" = Yes and only those lists, unless there >>are no such lists in which case no reminder is sent. > > We obviously comment out this cron job. We have over 4,200 mailing lists and over 854,100 subscribers. If password reminders are sent out all subscribers at 5AM on the first of each month, this will be heavy email burden to our mailman servers. > > # 5 AM on the first of each month, mail out password reminders. > #0 5 1 * * /usr/bin/python -S /usr/local/mailman/cron/mailpasswds In that case, no one receives any monthly reminder regardless of any list settings or member options. Also note that if you did send reminders, it isn't one reminder per subscription, it is one reminder per address regardless of how many lists that address is subscribed to. Running this Mailman script pipe bin/find_member . | grep 'found in:' | wc -l will tell you how many reminders would be sent if everyone was sent one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From subads at gmail.com Fri Feb 6 17:27:49 2015 From: subads at gmail.com (cha charle) Date: Fri, 6 Feb 2015 10:27:49 -0600 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: <54D2C903.8080407@msapiro.net> References: <201502041942.t14JgLVb002297@fido.openend.se> <54D2C903.8080407@msapiro.net> Message-ID: Mark, Thank you so much for the suggestion, and will give it a try; however, my question is: how do I point to the new subdomain though. Now, my domain is example.com( for mails and Maillman), and will create a subdomain list.example.com, just for mailman; and the example.com will move to Google app. Once the process is done, what do I need to do in Mailman to change all my current lists to the new subdomain, list.example.com though? Once again, thanks for your help. On Wed, Feb 4, 2015 at 7:36 PM, Mark Sapiro wrote: > On 02/04/2015 01:50 PM, cha charle wrote: > > > > Thanks for your quick reply; then is it possible to continue run a > Mailman > > server and still have my email move to Google App. Thanks! > > > As long as the domain in which you have your email lists is distinct > from, perhaps a subdomain of, your main domain, e.g. lists.example.com > or mm.example.com where the main domain is example.com, it should be no > problem to have a separate MX for that domain pointing to the Mailman > server. > > -- > 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/subads%40gmail.com > From lac at openend.se Fri Feb 6 18:34:42 2015 From: lac at openend.se (Laura Creighton) Date: Fri, 6 Feb 2015 18:34:42 +0100 Subject: [Mailman-Users] Internationalisation bug in 2.1.15 Message-ID: <201502061734.t16HYgn9017834@fido.openend.se> Recently Tin Tvrtkovi?? tried to subscribe to the pypy-dev mailing list. He got the "Bug in Mailman version 2.1.15 We're sorry, we hit a bug!" message. When he tried to reply to the confirmation message, he got it again. It looks like it could possibly be this 10 year old bug that Mark was unable to reproduce at the time .... https://bugs.launchpad.net/mailman/+bug/266223 but we don't have a traceback, so maybe not. We can reproduce the problem all we like; it is with the last character in Tin's name, which is U+0107. Tin is Croatian, so I assume that is what his character set is on his machine, but I get this here, too. pypy-dev is configured with a default lanaguage of English(USA). Should I make a bug report, or is this already fixed in later versions of mailman? Laura Creighton From fmouse at fmp.com Fri Feb 6 18:32:25 2015 From: fmouse at fmp.com (Lindsay Haisley) Date: Fri, 06 Feb 2015 11:32:25 -0600 Subject: [Mailman-Users] Removing arbitrary headers Message-ID: <1423243945.108370.85.camel@pudina.fmp.com> We recently set up an announcement mailing list (MM 2.1.18) for a local music non-profit organization for which my wife is the treasurer, and at this point the sole authorized (un-moderated) poster to the list. She wants to be able to post completely anonymously, and so we've set the list up as an anonymous list, with the Reply-To address of the organization. MM duly posted her first post to the list, and all the required headers are fine and as expected, but her original post to the list had the Organization header set to the name of her bookkeeping business, and this was preserved in the distributed announcement. Is there, and if not, shouldn't there be a way to _completely_ anonymize a post to a list? There should be some way to have MM remove the Organization header and replace it with an arbitrary one, in this case the name of the organization on behalf of which the announcement was sent. Granted, she could set up a special account, w.o. an organization name for posting to the list, or temporarily remove this from her account profile, but she may have others posting to this list as well, and there needs to be some way of dealing with this on a general basis. -- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com | From mark at msapiro.net Fri Feb 6 19:21:09 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 10:21:09 -0800 Subject: [Mailman-Users] Internationalisation bug in 2.1.15 In-Reply-To: <201502061734.t16HYgn9017834@fido.openend.se> References: <201502061734.t16HYgn9017834@fido.openend.se> Message-ID: <54D50615.7060401@msapiro.net> On 02/06/2015 09:34 AM, Laura Creighton wrote: > Recently Tin Tvrtkovi?? tried to subscribe to the pypy-dev mailing list. > > He got the "Bug in Mailman version 2.1.15 We're sorry, we hit a bug!" message. > When he tried to reply to the confirmation message, he got it again. > > It looks like it could possibly be this 10 year old bug that Mark was > unable to reproduce at the time .... > https://bugs.launchpad.net/mailman/+bug/266223 I don't think so. That specific traceback occurred in logging the held subscription request to the vette log, but only the email address is logged, not the real name. > but we don't have a traceback, so maybe not. Why not? There should be tracebacks in Mailman's error log. > We can reproduce the problem all we like; it is with the last character > in Tin's name, which is U+0107. Tin is Croatian, so I assume that is what > his character set is on his machine, but I get this here, too. pypy-dev > is configured with a default lanaguage of English(USA). I cannot reproduce this in Mailman 2.1.19, and I don't think there's been any change in this area since 2.1.15. I was able to request subscription and confirm the request bug free on an English language list. Here's the resulting Userdesc instance from the subscribe request. >>> u.__dict__ {'fullname': u'Tin Tvrtkovi\u0107', 'password': 'z', 'language': 'en', 'digest': 0, 'address': 'mark at ms2.msapiro.net'} I also tried subscribing the email address Tvrtkovi?@ms2.msapiro.net and got Subscription results Your subscription is not allowed because the email address you gave is insecure. In order to go further with this, I need to see the full Mailman error log entry for the "bug". Can you provide it? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Fri Feb 6 19:59:18 2015 From: ournet.biz at gmail.com (EyeLand) Date: Fri, 6 Feb 2015 20:59:18 +0200 Subject: [Mailman-Users] Wrong encoding Message-ID: Hello, I setup on VPS many mailman lists and on info page of all the public mailing lists on ?Description? I see wrong russian encoding like ?????? ??????, there you can see error http://list.ournet.biz/cgi-bin/mailman/ listinfo, can you consult? Thank you. From mark at msapiro.net Fri Feb 6 21:09:11 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 12:09:11 -0800 Subject: [Mailman-Users] Removing arbitrary headers In-Reply-To: <1423243945.108370.85.camel@pudina.fmp.com> References: <1423243945.108370.85.camel@pudina.fmp.com> Message-ID: <54D51F67.70500@msapiro.net> On 02/06/2015 09:32 AM, Lindsay Haisley wrote: > We recently set up an announcement mailing list (MM 2.1.18) for a local > music non-profit organization for which my wife is the treasurer, and at > this point the sole authorized (un-moderated) poster to the list. She should also moderate herself and post with an Approved: header or pseudo header using the list's 'poster' password. > Is there, and if not, shouldn't there be a way to _completely_ anonymize > a post to a list? There should be some way to have MM remove the > Organization header and replace it with an arbitrary one, in this case > the name of the organization on behalf of which the announcement was > sent. >From the NEWS for Mailman 2.1.17: There is a new mm_cfg.py setting ANONYMOUS_LIST_KEEP_HEADERS. Since it is not possible to know which non-standard headers in a message might reveal sender information, we now remove all headers from incoming posts to anonymous lists except those which match regular expressions in this list. The default setting keeps non X- headers except those known to reveal sender information, Mailman added X- headers and x-Spam- headers. See the description in Defaults.py for more information. (LP: #1246039) Some obvious headers are always removed, but Organization: isn't one of them. The default setting is ANONYMOUS_LIST_KEEP_HEADERS = ['^(?!x-)', '^x-mailman-', '^x-content-filtered-by:', '^x-topics:', '^x-ack:', '^x-beenthere:', '^x-list-administrivia:', '^x-spam-', ] If you were to put ANONYMOUS_LIST_KEEP_HEADERS = ['^(?!(x-|organization))', '^x-mailman-', '^x-content-filtered-by:', '^x-topics:', '^x-ack:', '^x-beenthere:', '^x-list-administrivia:', '^x-spam-', ] in mm_cfg.py, that would remove the Organization: header, but I consider that a workaround and will add Organization: to the always removed headers for 2.1.19. Note, in testing the above I found another bug in that the headers in the above list that end with ':' aren't kept because the colon isn't part of the name we're matching against. I'm fixing that in Cleanse.py to replace a trailing ':' with '$'. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fmouse at fmp.com Fri Feb 6 21:24:32 2015 From: fmouse at fmp.com (Mitra IMAP) Date: Fri, 6 Feb 2015 14:24:32 -0600 Subject: [Mailman-Users] Removing arbitrary headers In-Reply-To: <54D51F67.70500@msapiro.net> References: <1423243945.108370.85.camel@pudina.fmp.com> <54D51F67.70500@msapiro.net> Message-ID: <326F8385-6B77-4EB0-B9D3-90DB662E8667@fmp.com> On Feb 6, 2015, at 2:09 PM, Mark Sapiro wrote: > She should also moderate herself and post with an Approved: > header or pseudo header using the list's 'poster' password. This would be ideal, but in real world situations it can be problematic. I have a list hosting customer who, when her announcement list was first set up, had a lot of trouble with this. The pseudo-header was getting munged in various ways by her MUA, and she'd email me in a panic to help her get her list out! She was using HTML email for her list, which I discourage, but she's a customer and that's what she wants. Lindsay Haisley (512) 259-1190 (land line) (512) 496-7118 (mobile) Sent from my iPhone From mark at msapiro.net Fri Feb 6 21:39:37 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 12:39:37 -0800 Subject: [Mailman-Users] Mailman on Google App In-Reply-To: References: <201502041942.t14JgLVb002297@fido.openend.se> <54D2C903.8080407@msapiro.net> Message-ID: <54D52689.4080402@msapiro.net> On 02/06/2015 08:27 AM, cha charle wrote: > > Now, my domain is example.com ( for mails and > Maillman), and will create a subdomain list.example.com > , just for mailman; and the example.com > will move to Google app. Once the process is done, > what do I need to do in Mailman to change all my current lists to the > new subdomain, list.example.com though? Once > again, thanks for your help. At a minimum, you need an A record in DNS for lists.example.com with the server's IP address. In Mailman, it depends what you have in mm_cfg.py currently. If you have something like DEFAULT_EMAIL_HOST = 'example.com' DEFAULT_URL_HOST = 'example.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) you want to change the first two lines to DEFAULT_EMAIL_HOST = 'list.example.com' DEFAULT_URL_HOST = 'list.example.com' If you have nothing in mm_cfg.py, add DEFAULT_EMAIL_HOST = 'list.example.com' DEFAULT_URL_HOST = 'list.example.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) You can also add VIRTUAL_HOSTS.clear() ahead of any add_virtualhost line(s) to remove whatever was put there by Defaults.py. Then you need to run fix_url to fix your lists. See the FAQs at and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Fri Feb 6 22:23:24 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 6 Feb 2015 23:23:24 +0200 Subject: [Mailman-Users] Wrong encoding In-Reply-To: References: Message-ID: Hello EyeLand! You can add 'AddDefaultCharset koi8-r' directive to your list.ournet.biz virtual host configuration and restart Apache webserver. This force server to return main listinfo page in koi8-r encoding, as well as all list-specific listinfo pages. This should help because server encoding has higher priority than tag with 'charset=us-ascii' in page html code, which I think is hard-coded in Mailman core files and could not be easily changed/removed. (Mark, please correct me if I wrong.) Danil 2015-02-06 20:59 GMT+02:00 EyeLand : > Hello, I setup on VPS many mailman lists and on info page of all the public > mailing lists on ?Description? I see wrong russian encoding like ?????? > ??????, there you can see error http://list.ournet.biz/cgi-bin/mailman/ > listinfo, can you consult? Thank you. > ------------------------------------------------------ > 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/danil%40smirnov.la From mark at msapiro.net Fri Feb 6 23:18:57 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 14:18:57 -0800 Subject: [Mailman-Users] Wrong encoding In-Reply-To: References: Message-ID: <54D53DD1.5000704@msapiro.net> On 02/06/2015 10:59 AM, EyeLand wrote: > Hello, I setup on VPS many mailman lists and on info page of all the public > mailing lists on ?Description? I see wrong russian encoding like ?????? > ??????, there you can see error http://list.ournet.biz/cgi-bin/mailman/ > listinfo, can you consult? Thank you. It looks like you may have entered the list's description attributes and probably other things in UTF-8 encoding. It also appears the your Mailman installation's default language is English. In Mailman 2.1.15, the encoding for Russian is koi8-r and data for the web UI needs to be entered in that character set. Also, non-ascii descriptions will never look right on admin and listinfo overviews unless the default language for the installation supports the lists encoding. Note that the encoding for Russian is changing in 2.1.19 to utf-8. That is a hard decision because of impacts on existing lists. Note that the reply from Danil about changing your web server's default charset is probably also relevant. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fmouse at fmp.com Fri Feb 6 23:35:53 2015 From: fmouse at fmp.com (Lindsay Haisley) Date: Fri, 06 Feb 2015 16:35:53 -0600 Subject: [Mailman-Users] Removing arbitrary headers In-Reply-To: <54D51F67.70500@msapiro.net> References: <1423243945.108370.85.camel@pudina.fmp.com> <54D51F67.70500@msapiro.net> Message-ID: <1423262153.31712.5.camel@indra.fmp.com> On Fri, 2015-02-06 at 12:09 -0800, Mark Sapiro wrote: > '^(?!(x-|organization))' Thanks! I assume the re.IGNORECASE flag is set :) -- Lindsay Haisley | "We have met the enemy and he is us." FMP Computer Services | 512-259-1190 | -- Pogo http://www.fmp.com | From danil at smirnov.la Fri Feb 6 23:39:07 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 7 Feb 2015 00:39:07 +0200 Subject: [Mailman-Users] Wrong encoding In-Reply-To: <54D53DD1.5000704@msapiro.net> References: <54D53DD1.5000704@msapiro.net> Message-ID: > Note that the reply from Danil about changing your web server's default > charset is probably also relevant. Unfortunately it is not. :( After some testing I've found that AddDefaultCharset does not help - it seems like Mailman changes default server's header to its own default header for US English language: us-ascii. You can change this for list-specific pages by selecting another language but not for common lists index page which is always in us-ascii encoding. 2015-02-07 0:18 GMT+02:00 Mark Sapiro : > It looks like you may have entered the list's description attributes and > probably other things in UTF-8 encoding. It also appears the your > Mailman installation's default language is English. It is not true, because you can see correct Russian text on page provided if you change page's encoding to Cyrillic KOI8-R in your browser. In this case I can only suggest quite ugly workaround: to add to /Mailman/mm_cfg.py file this line and restart Mailman: add_language('en', 'English (USA)', 'koi8-r', 'ltr') This line will force Mailman to output all English pages including server list index page with KOI8-R encoding. It will be okay for English and Russian text both. Danil > In Mailman 2.1.15, the encoding for Russian is koi8-r and data for the > web UI needs to be entered in that character set. Also, non-ascii > descriptions will never look right on admin and listinfo overviews > unless the default language for the installation supports the lists > encoding. > > Note that the encoding for Russian is changing in 2.1.19 to utf-8. That > is a hard decision because of impacts on existing lists. > > Note that the reply from Danil about changing your web server's default > charset is probably also relevant. > > -- > 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/danil%40smirnov.la From mark at msapiro.net Sat Feb 7 00:48:35 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 15:48:35 -0800 Subject: [Mailman-Users] Removing arbitrary headers In-Reply-To: <1423262153.31712.5.camel@indra.fmp.com> References: <1423243945.108370.85.camel@pudina.fmp.com> <54D51F67.70500@msapiro.net> <1423262153.31712.5.camel@indra.fmp.com> Message-ID: <54D552D3.60905@msapiro.net> On 02/06/2015 02:35 PM, Lindsay Haisley wrote: > On Fri, 2015-02-06 at 12:09 -0800, Mark Sapiro wrote: >> '^(?!(x-|organization))' > > Thanks! I assume the re.IGNORECASE flag is set :) Yes, it is. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Feb 7 00:55:51 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 15:55:51 -0800 Subject: [Mailman-Users] Wrong encoding In-Reply-To: References: <54D53DD1.5000704@msapiro.net> Message-ID: <54D55487.5090800@msapiro.net> On 02/06/2015 02:39 PM, Danil Smirnov wrote: > > You can change this for list-specific pages by selecting another > language but not for common lists index page which is always in > us-ascii encoding. Only if DEFAULT_SERVER_LANGUAGE = 'en'. If you set DEFAULT_SERVER_LANGUAGE = 'ru' in mm_cfg.py the listinfo overview will be in Russian and in Mailman's character set fo Russian. > In this case I can only suggest quite ugly workaround: to add to > /Mailman/mm_cfg.py file this line and restart Mailman: > > add_language('en', 'English (USA)', 'koi8-r', 'ltr') > > This line will force Mailman to output all English pages including > server list index page with KOI8-R encoding. > It will be okay for English and Russian text both. Do not do this. Just set DEFAULT_SERVER_LANGUAGE = 'ru' as I suggest above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Feb 7 06:05:05 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 Feb 2015 21:05:05 -0800 Subject: [Mailman-Users] Mailman 2.1.19 release Message-ID: <54D59D01.6070209@msapiro.net> I am pleased to announce the second release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features since 2.1.18-1, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. There are also bug fixes. See the attached README for more details. The differences between this and the first 2.1.19 candidate are the following. The subscribe_auto_approval feature in the first candidate has been augmented to accept @listname to auto approve members of another list. (LP: #1417093) Organization: headers are unconditionally removed from posts to anonymous lists and a bug involving ANONYMOUS_LIST_KEEP_HEADERS has been fixed. (LP: #1419132) The admindb interface display of a held message body has been fixed to not stop in the middle of a multi-byte character and not fail to convert to the display character set message bodies with invalid characters. (LP: #1415406) Additionally, and the main reason for this second candidate, Mailman's character set for both Romanian and Russian has been changed to utf-8. (LP: #1418735) and (LP: #1418448). This may be disruptive in that following this change, some archive pages and some list attributes for lists whose preferred_language is one of those two languages may not display correctly. Archives can be fixed by running 'bin/arch --wipe' for the affected lists, but list attributes will probably have to be fixed manually. I hope the benefits of this change will outweigh the pain, and I encourage anyone with Romanian or Russian Language lists to try this release and report your experience. It may be possible to fix at least some list attributes programmatically as part of the version update process. I plan to release the final 2.1.19 release at the end of February, and it would be good to have as many i18n updates as possible by then. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see: http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.19rc2 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- 2.2 Branch Backports (released in conjunction with 2.1.19) The following New Features and Bug Fixes have been in an "unofficial, never to be released" Mailman 2.2 branch for several years. Until now, they were never implemented on the official 2.1 branch because of their i18n impacts. Given that there have been a number of i18n impacting changes due to DMARC mitigations in the last few releases, it has been decided to backport these as well. All of these changes have been running in production on several lists for years without problems other than untranslated strings, so they should be reasonably "bug free". New Features - There is a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. (LP: #266609) - Confirmed member change of address is logged in the 'subscribe' log, and if admin_notify_mchanges is true, a notice is sent to the list owner using a new adminaddrchgack.txt template. - Added an 'automate' option to bin/newlist to send the notice to the admin without the prompt. - The processing of Topics regular expressions has changed. Previously the Topics regexp was compiled in verbose mode but not documented as such which caused some confusion. Also, the documentation indicated that topic keywords could be entered one per line, but these entries were not handled properly. Topics regexps are now compiled in non-verbose mode and multi-line entries are 'ored'. Existing Topics regexps will be converted when the list is updated so they will continue to work. - Added real name display to the web roster. (LP: #266754) Bug fixes and other patches - Changed the response to an invalid confirmation to be more generic. Not all confirmations are subscription requests. - Changed the default nonmember_rejection_notice to be more user friendly. (LP: #418728) - Added "If you are a list member" qualification to some messages from the options login page. (LP: #266442) - Changed the 'Approve' wording in the admindbdetails.html template to 'Accept/Approve' for better agreement with the button labels. - Added '(by thread)' to the previous and next message links in the archive to emphasize that even if you got to the message from a subject, date or author index, previous and next are still by thread. 2.1.19rc2 (06-Feb-2015) New Features - The subscribe_auto_approval feature backported from the 2.2 branch and described above has been enhanced to accept entries of the form @listname to auto approve members of another list. (LP: #1417093) - There is a new list attribute dmarc_wrapped_message_text and a DEFAULT_DMARC_WRAPPED_MESSAGE_TEXT setting to set the default for new lists. This text is added to a message which is wrapped because of dmarc_moderation_action in a separate text/plain part that precedes the message/rfc822 part containing the original message. It can be used to provide an explanation of why the message was wrapped or similar info. - There is a new list attribute equivalent_domains and a DEFAULT_EQUIVALENT_DOMAINS setting to set the default for new lists which in turn defaults to the empty string. This provides a way to specify one or more groups of domains, e.g., mac.com, me.com, icloud.com, which are considered equivalent for validating list membership for posting and moderation purposes. - There is a new WEB_HEAD_ADD setting to specify text to be added to the section of Mailman's internally generated web pages. This doesn't apply to pages built from templates, but in those cases, custom templates can be created. (LP: #1409396) - There is a new DEFAULT_SUBSCRIBE_OR_INVITE setting. Set this to Yes to make the default selection on the admin Mass Subscriptions page Invite rather than Subscribe. (LP: #1404511) - There is a new list attribute in the Bounce processing section. bounce_notify_owner_on_bounce_increment if set to Yes will cause Mailman to notify the list owner on every bounce that increments a list member's score but doesn't result in a probe or disable. There is a new configuration setting setting DEFAULT_BOUNCE_NOTIFY_OWNER_ON_BOUNCE_INCREMENT to set the default for new lists. This in turn defaults to No. (LP: #1382150) Changed behavior - Mailman's log files, request.pck files and heldmsg-* files are no longer created world readable to protect against access by untrusted local users. Note that permissions on existing log files won't be changed so if you are concerned about this and don't rotate logs or have a logrotate process that creates new log files instead of letting Mailman create them, you will need to address that. (LP: #1327404) Other changes - The Python Powered logo image has been replaced in the misc/ directory in the source distribution. Depending on how you've installed these images, you may need to copy PythonPowered.png from the misc/ directory in the source or from the $prefix/icons/ installed directory to another location for your web server. (LP: #1408575) i18n - Mailman's character set for Romanian has been changed from iso-8859-2 to utf-8 and the templates and messages recoded. This change will require running 'bin/arch --wipe' on any existing Romanian language lists in order to recode the list's archives, and will require recoding any edited templates in lists/LISTNAME/ro/*, templates/DOMAIN/ro/* and templates/site/ro/*. It may also require recoding any existing iso-8859-2 text in list attributes. (LP: #1418735) - Mailman's character set for Russian has been changed from koi8-r to utf-8 and the templates and messages recoded. This change will require running 'bin/arch --wipe' on any existing Russian language lists in order to recode the list's archives, and will require recoding any edited templates in lists/LISTNAME/ru/*, templates/DOMAIN/ru/* and templates/site/ru/*. It may also require recoding any existing koi8-r text in list attributes. (LP: #1418448) - The Russian message catalog has been updated by Danil Smirnov. - The Romanian message catalog has been updated. (LP: #1415489) - The Russian templates have been updated by Danil Smirnov. (LP: #1403462) - The Japanese translation has been updated by SATOH Fumiyasu. (LP: #1402989) - A minor change in the French translation of a listinfo subscribe form message has been made. (LP: #1331194) Bug fixes and other patches - Organization: headers are now unconditionally removed from posts to anonymous lists. Regexps in ANONYMOUS_LIST_KEEP_HEADERS weren't kept if the regexp included the trailing ':'. This is fixed too. (LP: #1419132) - The admindb interface has been fixed so the the detail message body display doesn't lose part of a multi-byte character, and characters which are invalid in the message's charset are replaced rather than the whole body not being converted to the display charset. (LP: #1415406) - Fixed a bug in bin/rmlist that would throw an exception or just fail to remove held message files for a list with regexp special characters in its name. (LP:#1414864) - When applying DMARC mitigations, CookHeaders now adds the original From: to Cc: rather than Reply-To: in some cases to make MUA 'reply' and 'reply all' more consistent with the non-DMARC cases. (LP: #1407098) - The Subject: of the list welcome message wasn't always in the user's preferred language. Fixed. (LP: #1400988) - Accept email command in Subject: prefixed with Re: or similar with no intervening space. (LP: #1400200) - Fixed a UnicodeDecodeError that could occur in the web admin interface if 'text' valued attributes have unicode values. (LP: #1397170) - We now catch the NotAMemberError exception thrown if an authenticated unsubscribe is submitted from the user options page for a nonmember. (LP: #1390653) - Fixed an archiving bug that would cause messages with 'Subject: Re:' only to be indexed in the archives without a link to the message. (LP: #1388614) - The vette log entry for a message discarded by a handler now includes the list name and the name of the handler. (LP: #558096) - The options CGI now rejects all but HTTP GET and POST requests. (LP: #1372199) - A list's poster password will now be accepted on an Urgent: header. (LP: #1371678) - Fixed a bug which caused a setting of 2 for REMOVE_DKIM_HEADERS to be ignored. (LP: #1363278) - Renamed messages/sr/readme.sr to README.sr. (LP: #1360616) - Moved the dmarc_moderation_action checks from the Moderate handler to the SpamDetect handler so that the Reject and Discard actions will be done before the message might be held by header_filter_rules, and the Wrap Message and Munge From actions will be done on messages held by header_filter_rules if the message is approved. (LP: #1334450) -