From cp at ccil.org Fri Aug 2 06:27:18 2013 From: cp at ccil.org (Chuck Peters) Date: Fri, 2 Aug 2013 00:27:18 -0400 Subject: [Mailman-Users] creating hidden field to stop bot spamsubscriptionrequest In-Reply-To: <87mwxfyji6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <50CBDB80.3080009@Damon-Family.org> <87mwxfyji6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On Sat, Dec 15, 2012 at 12:25 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > The asking of a question which requires an "obvious to a human but > > extremely difficult to a machine" answer is probably the best > > defence as long as the questions and answers aren't fixed over many > > Mailman installations. > > That's a great idea, actually! How about a standard (but optional) > feature for the subscription page like this: > > *Please read the following description carefully. You will be* > *tested on the content later. * > > This is the mailman-users list. It is used for communication > about the Mailman mailing list management software, primarily > among users, although developers often participate. > > To subscribe > > Your name: [ ] > Your email: [ ] > *Test question: * > * Do programmers of this package lurk here? (yes/no) [ ]* > > Of course the "test question" would be list-owner configured, a la the > "security question" for password recovery that is commonly > implemented. The portions enclosed in stars would only be generated > if the "test question" were non-blank. > > The answer to the "test question" could be further obfuscated by > placing it on a different page. Has this feature made it into 2.1.16rc2? If not, does someone have a patch? Thanks, Chuck From dikim at cs.indiana.edu Sat Aug 3 05:40:02 2013 From: dikim at cs.indiana.edu (DongInn Kim) Date: Fri, 2 Aug 2013 23:40:02 -0400 Subject: [Mailman-Users] Update virtual-mailman for the migrated lists Message-ID: <3E753388-452A-41FC-8A44-159FAAD03F26@cs.indiana.edu> Hi, Is there a way to generate the virtual-mailman file for the migrated lists which are hosted by some virtual hosts? It seems that there are patterns to follow in virtual-mailman and I may be able to update it manually. The manual work should not be done on this file but I have no idea how to deal with the migrated mailing lists which are hosted by some virtual hosts. If there is a script to do this kind job properly, that would be nice. Regards, -- - DongInn From kremels at kreme.com Sat Aug 3 19:02:03 2013 From: kremels at kreme.com (LuKreme) Date: Sat, 3 Aug 2013 11:02:03 -0600 Subject: [Mailman-Users] mailman group errors after updating postfix Message-ID: <029910B4-34DC-4013-8EEF-4ED24C53F984@kreme.com> In case this is useful to anyone else: === What I was going to post === After updating postfix to 2.10, mailman (which has datestamps on the binaries of Apr 2010) is failing. The log message in maillot is the dreaded: Aug 3 10:38:33 mail Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mailman", but the system's mail server executed the mail script as group "nobody". Try tweaking the mail server to run the script as group "mailman", or re-run configure, providing the command line option `--with-mail-gid=nobody Since Mailman hasn't changed and has worked through 2.6 and 2.8, I suspect there is some configuration that has changed in postfix. Is this something I can fix in recompiling postfix (best), or do I have to recompile mailman (don't want to)? === EOF === I found the solution before posting. I went into the data directory for mailman and changed the owner on the aliases and aliases.db to "mailman" and everything works fine. I could also have simply run bin/check_perms -f (most of the info I found on the error was about recompiling mailman to fix this error, which is why I'm sending this along). This is almost certainly the solution to the problem I had in Jan 2010 in mailman-user, for anyone playing along at home.) -- "640K ought to be enough RAM for anybody." - Bill Gates, 1981 From pmcevoy at silvacapitalmanagement.com Fri Aug 2 21:14:23 2013 From: pmcevoy at silvacapitalmanagement.com (Patrick McEvoy) Date: Fri, 02 Aug 2013 14:14:23 -0500 Subject: [Mailman-Users] Howto change Mailman email To field from list@example.com to members individual email address Message-ID: <51FC050F.9040700@silvacapitalmanagement.com> Hello, I have just set up a Mailman mailing list. When I send an email to the list the email header each member receives has my email address in the >From field and the list email address in the To field instead of the recipient's email address in the To field. How can I change this? Thank you, Patrick From tianzy1225 at thundersoft.com Thu Aug 1 08:34:20 2013 From: tianzy1225 at thundersoft.com (Tian Zhiying) Date: Thu, 1 Aug 2013 14:34:20 +0800 Subject: [Mailman-Users] Integrate mailman and postfix Message-ID: <20130801143420377278167@thundersoft.com> Hi I want integrate mailman and postfix, postfix can already work properly. Now I have a question: I create a maillist : it at domain.com When I send mail from a user(tian at domain.com) to it at domain.com, received a bounce: it at domain.com: user unknown. Command output: Invalid user specified. Following is my postfix configuration and mailman configuration: Postfix configuration: # postconf -n alias_maps = hash:/etc/aliases, hash:/var/www/extsuite/mailman/data/aliases bounce_queue_lifetime = 1d broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = mailman enable_original_recipient = no html_directory = no inet_interfaces = all mail_owner = postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man max_use = 10 maximal_queue_lifetime = 1d message_size_limit = 70960000 mydestination = $myhostname localhost localhost.$mydomain mydomain = domain.com myhostname = mail2.domain.com mynetworks = 127.0.0.0/8 192.168.0.0/16 newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = no receive_override_options = no_address_mappings recipient_delimiter = + sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_banner = $myhostname ESMTP "Version not Available" smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_non_fqdn_hostname, reject_unknown_sender_domain, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_recipient_domain, reject_unauth_pipelining, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, permit smtpd_reject_unlisted_sender = yes smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $mydomain smtpd_sasl_security_options = noanonymous smtpd_sender_login_maps = mysql:/etc/postfix/mysql_virtual_sender_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf smtpd_sender_restrictions = permit_mynetworks, reject_sender_login_mismatch, reject_authenticated_sender_login_mismatch, reject_unauthenticated_sender_login_mismatch unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf,hash:/var/www/extsuite/mailman/data/virtual-mailman virtual_gid_maps = static:1000 virtual_mailbox_base = /var/mailbox virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 70971520 virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_transport = maildrop virtual_uid_maps = static:1000 Mailman configuration: DEFAULT_EMAIL_HOST = 'mail.domain.com' DEFAULT_URL_HOST = 'mail.domain.com' MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.com'] add_virtualhost('mail.domain.com','mail.domain.com') DEFAULT_SERVER_LANGUAGE = 'zh_CN' Any problem? Please help me. Thanks. Tian Zhiying From stephen at xemacs.org Sun Aug 4 09:22:47 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 04 Aug 2013 16:22:47 +0900 Subject: [Mailman-Users] Howto change Mailman email To field from list@example.com to members individual email address In-Reply-To: <51FC050F.9040700@silvacapitalmanagement.com> References: <51FC050F.9040700@silvacapitalmanagement.com> Message-ID: <874nb5ncmw.fsf@uwakimon.sk.tsukuba.ac.jp> Patrick McEvoy writes: > Hello, > > I have just set up a Mailman mailing list. When I send an email to the > list the email header each member receives has my email address in the > >From field and the list email address in the To field instead of the > recipient's email address in the To field. How can I change this? Go to your list administrator's page for that list. Non-digest options -> Personalization Select "Full Personalization". Save the options. Your link names and option names may vary somewhat, I'm translating (my installation's primary language is Japanese). From roger.richcorp at btconnect.com Mon Aug 5 11:32:30 2013 From: roger.richcorp at btconnect.com (Roger Richmond) Date: Mon, 5 Aug 2013 10:32:30 +0100 Subject: [Mailman-Users] HTML formatting and Header/Footer Message-ID: <037501ce91be$b66c2ec0$23448c40$@richcorp@btconnect.com> I am an administrator of a small mailing list running Mailman 2.1.15. I only have access to the web interface, not the server, and even if i did, I'm not confident about writing or changing the code. I know that this problem has been raised before, but wondered whether there had been any progress towards a solution. I want messages to the list to be distributed in HTML format, but I also need to attach a footer. (The footer is a disclaimer to a health support list). Mailman sends the footer as an attachment. I have seen the FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030707 but this doesn't resolve the situation. Is there a solution yet? Roger Richmond From daniel at pocock.com.au Mon Aug 5 14:08:33 2013 From: daniel at pocock.com.au (Daniel Pocock) Date: Mon, 05 Aug 2013 14:08:33 +0200 Subject: [Mailman-Users] scripts and blog about virtual Mailman / Mailmen Message-ID: <51FF95C1.9040409@pocock.com.au> I've published some scripts that I used to get my own virtual Mailman setup running - the whole concept and my experiences with this are in my blog today: http://danielpocock.com/effectively-supporting-virtual-domains-with-mailman Any feedback (or corrections) are welcome of course. Regards, Daniel From Richard at Damon-Family.org Tue Aug 6 03:36:45 2013 From: Richard at Damon-Family.org (Richard Damon) Date: Mon, 05 Aug 2013 21:36:45 -0400 Subject: [Mailman-Users] HTML formatting and Header/Footer In-Reply-To: <037501ce91be$b66c2ec0$23448c40$@richcorp@btconnect.com> References: <037501ce91be$b66c2ec0$23448c40$@richcorp@btconnect.com> Message-ID: <5200532D.70605@Damon-Family.org> On 8/5/13 5:32 AM, Roger Richmond wrote: > I am an administrator of a small mailing list running Mailman 2.1.15. I > only have access to the web interface, not the server, and even if i did, > I'm not confident about writing or changing the code. > > > > I know that this problem has been raised before, but wondered whether there > had been any progress towards a solution. I want messages to the list to be > distributed in HTML format, but I also need to attach a footer. (The footer > is a disclaimer to a health support list). Mailman sends the footer as an > attachment. I have seen the FAQ at > http://wiki.list.org/pages/viewpage.action?pageId=4030707 but this doesn't > resolve the situation. > > > > Is there a solution yet? > > > > Roger Richmond > As the pages states, it is non-trivial to figure out how to add some text as a header or footer to a general HTML page. I suspect it was decided that it was better to place these as separate mime sections, where it is guaranteed that they are visible (at least as an attachment), than the tack them into a message in a way where they might not be visible at all, and may even break the existing formatting of the original message. -- Richard Damon From shop at justbrits.com Tue Aug 6 12:38:10 2013 From: shop at justbrits.com (" Just Brits " Shop) Date: Tue, 06 Aug 2013 05:38:10 -0500 Subject: [Mailman-Users] HTML formatting and Header/Footer In-Reply-To: <5200532D.70605@Damon-Family.org> References: <037501ce91be$b66c2ec0$23448c40$@richcorp@btconnect.com> <5200532D.70605@Damon-Family.org> Message-ID: <5200D212.9070509@justbrits.com> | On 8/5/13 5:32 AM, Roger Richmond wrote: | I am an administrator of a small mailing list running Mailman 2.1.15. I | only have access to the web interface, not the server, and even if i did, | I'm not confident about writing or changing the code. | |I know that this problem has been raised before, but wondered whether there | had been any progress towards a solution. I want messages to the list to be | distributed in HTML format, but I also need to attach a footer. (The footer |is a disclaimer to a health support list). Mailman sends the footer as an | attachment. I have seen the FAQ at | http://wiki.list.org/pages/viewpage.action?pageId=4030707 but this doesn't | resolve the situation. | | Is there a solution yet? | |Roger Richmond | | |And Richard at Damon-Family.org replied: | | As the pages states, it is non-trivial to figure out how to add some | text as a header or footer to a general HTML page. | |I suspect it was decided that it was better to place these as separate |mime sections, where it is guaranteed that they are ||| *"visible (at least as an attachment),"* *Richard II, what do you mean "attachment" ? ? MINE all come out perfectly** **as a footer as does THIS List one (below)** :-)** ** :-)** ? ! ?** * | than the tack them into a message in a way where they | might not be visible at all, and may even break the existing formatting |of the original message. |-- | Richard Damon | | ------------------------------------------------------ | Mailman-Users mailing list Mailman-Users at python.org | http://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: http://mail.python.org/mailman/options/mailman-users/shop%40justbrits.com From Richard at Damon-Family.org Tue Aug 6 13:23:56 2013 From: Richard at Damon-Family.org (Richard Damon) Date: Tue, 06 Aug 2013 07:23:56 -0400 Subject: [Mailman-Users] HTML formatting and Header/Footer In-Reply-To: <5200D212.9070509@justbrits.com> References: <037501ce91be$b66c2ec0$23448c40$@richcorp@btconnect.com> <5200532D.70605@Damon-Family.org> <5200D212.9070509@justbrits.com> Message-ID: <5200DCCC.5070902@Damon-Family.org> On 8/6/13 6:38 AM, " Just Brits " Shop wrote: > > *"visible (at least as an attachment),"* > > *Richard II, what do you mean "attachment" ? ? MINE all come > out perfectly** **as a footer as does THIS List one (below)** :-)** > ** :-)** ? ! ?** * > It depends on your MUA (email program). Some will display the multiple parts all inline, some will display some of them as attachments. I believe the inline is the "proper" way based on the standards, but is not required, and is not universally done, thus the qualification. (and infact, it is a frequent question BECAUSE some major programs display it as an attachment). Note also, the problem ONLY occurs with "HTML formatted" messages, not plain text, as for plain text messages it is safe to just add them, as there is no formatting to get in the way. -- Richard Damon From thomas.murgan at paccert.org Wed Aug 7 03:05:47 2013 From: thomas.murgan at paccert.org (Thomas Murgan) Date: Wed, 07 Aug 2013 13:05:47 +1200 Subject: [Mailman-Users] Help with Reverse-Proxy Integration Message-ID: <52019D6B.8000208@paccert.org> Hello, I am a newbie to Mailman.Googling and I have tried following steps in this link: http://mail.python.org/pipermail/mailman-users/2004-July/038393.html This does not work for me: ProxyPass /mailman http://internal-server/mailman ProxyPassReverse /mailman http://internal-server/mailman This works: ProxyPass / http://internal-server/mailman/ ProxyPassReverse / http://internal-server/mailman/ but this somehow gets the 'mailman' portion in the URL hidden. Example: http://external-server/listinfo >> http://internal-server/mailman/listinfo Issues arising: When I want to access the admin web externally (clicking the 'Let me in' button): http://external-server/mailman/admin/list >> it produces 404 Not found message: "The requested URL /mailman/mailman/admin/list was not found on this server. An extra mailman get included in the URL. Somehow it seems the solution may be simple (solved previously), but can someone please direct me. thanks Thomas From stephen at xemacs.org Thu Aug 8 02:45:39 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 08 Aug 2013 09:45:39 +0900 Subject: [Mailman-Users] Help with Reverse-Proxy Integration In-Reply-To: <52019D6B.8000208@paccert.org> References: <52019D6B.8000208@paccert.org> Message-ID: <87eha5ko24.fsf@uwakimon.sk.tsukuba.ac.jp> Thomas Murgan writes: > This does not work for me: > ProxyPass /mailman http://internal-server/mailman > ProxyPassReverse /mailman http://internal-server/mailman If you want all URLs starting with "http://external-server/mailman" to be forwarded to corresponding URLs at "http://internal-server/mailman", this is the correct syntax. If in fact what you want is something different, be specific. Without seeing the rest of the URL space configuration it's hard to guess what might be wrong. What do you mean by "doesn't work"? What errors are produced in the browser? What is in Apache's log? Check Apache's error log as well. Given that > http://external-server/listinfo >> http://internal-server/mailman/listinfo "works" (I assume you mean that produces the listinfo page from the Mailman installed on internal-server), I would guess that you have some configuration on external-server that interferes with configuring /mailman with ProxyPass. Was Mailman ever installed on external-server, so that there is an Alias or ScriptAlias for the path /Mailman on that Apache? Perhaps you have a Location or Directory element blocking the ProxyPass. From thomas.murgan at paccert.org Thu Aug 8 05:01:57 2013 From: thomas.murgan at paccert.org (Thomas Murgan) Date: Thu, 08 Aug 2013 15:01:57 +1200 Subject: [Mailman-Users] Help with Reverse-Proxy Integration In-Reply-To: <87eha5ko24.fsf@uwakimon.sk.tsukuba.ac.jp> References: <52019D6B.8000208@paccert.org> <87eha5ko24.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <52030A25.9070806@paccert.org> On 8/8/2013 12:45 PM, Stephen J. Turnbull wrote: > Thomas Murgan writes: > > > This does not work for me: > > ProxyPass /mailman http://internal-server/mailman > > ProxyPassReverse /mailman http://internal-server/mailman > > If you want all URLs starting with "http://external-server/mailman" to > be forwarded to corresponding URLs at "http://internal-server/mailman", > this is the correct syntax. If in fact what you want is something > different, be specific. > > Without seeing the rest of the URL space configuration it's hard to > guess what might be wrong. What do you mean by "doesn't work"? What > errors are produced in the browser? What is in Apache's log? Check > Apache's error log as well. > > Given that > > > http://external-server/listinfo >> http://internal-server/mailman/listinfo > > "works" (I assume you mean that produces the listinfo page from the > Mailman installed on internal-server), I would guess that you have > some configuration on external-server that interferes with configuring > /mailman with ProxyPass. Was Mailman ever installed on > external-server, so that there is an Alias or ScriptAlias for the path > /Mailman on that Apache? Perhaps you have a Location or Directory > element blocking the ProxyPass. > I did have mailman installed on the external-server. I have removed it and now my ProxyPass works like a charm. Thanks again > From eminmn at sysmatrix.net Thu Aug 8 17:54:39 2013 From: eminmn at sysmatrix.net (e.c.) Date: Thu, 8 Aug 2013 10:54:39 -0500 Subject: [Mailman-Users] About PostLimit.py again ( was :To restrict sending email messages per day) Message-ID: Thanks for these pythons routines, Mark. Since I don't know much about the language, I need some clarification on the part of the code between triple quote marks (""") and also between the lines that have ----------- cut -----. Are these constructs some kind of ad hoc python syntax extensions for commenting out or do they need to be made invisible with prepended # characters? I would especially like to know whether it's possible to substitute worldtime (gmt) in the places where localtime is referenced. This posting throttling functionality is needed to make a mailman list correspond as closely as possible to the functionality once offered by LISTSERV. Is the part of the code between the cut marks only to be used if the globals M, L, and PERIOD are to be set with list attributes via the extend.py file? Could someone comment the code relating to the global PERIOD and localetime. For my purposes PERIOD could be hardcoded to 24 hours and based on gmt. It looks like the code at http://www.msapiro.net/scripts/PostLimit.py can't be inserted as is into Mailman/Handlers/PostLimit.py Am I right about that? Thanks in advance for any help, Ed On Sun, Jul 21, 2013 at 8:17 PM, Mark Sapiro wrote: > Mark Sapiro wrote: > > > See (mirrored at > > )for a script > > that limits the number of posts from a member to a list either per > > calendar day or a configurable period of hours. > > > > It could be made lots fancier with the limit and time period being list > > attributes or mm_cfg variables instead of hard coded and options to hold > > rather than reject, but it will work. > > > I have enhanced the script at the above locations to support a per > member limit and/or a per list limit. I have also made it take > parameters from list attributes if set there and provided a sample > extend.py to enable it and set parameters for a list. > > Additionally, I have created a FAQ at with > this information. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From Ralf.Hildebrandt at charite.de Thu Aug 8 19:55:26 2013 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Thu, 8 Aug 2013 19:55:26 +0200 Subject: [Mailman-Users] Bug in 2.1.16rc2 regarding new logging to vette? Message-ID: <20130808175526.GC16765@charite.de> - IncomingRunner now logs rejected messages to the vette log. (LP: #1068837) So I had a look today and found: Aug 06 12:12:59 2013 (11069) doctors: Refused posting: ... Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting: Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting: Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting: I *looks* as if there's something missing, like the message-id or some other identifier... Other log entries do have such an identifier: Aug 06 12:28:12 2013 (22645) doctors post from xxxxkan at charite.de held, message-id=<20130806102810.GH14852 at charite.de>: Post by non-member to a members-only list -- 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 waltmayo at gmail.com Thu Aug 8 16:42:18 2013 From: waltmayo at gmail.com (Walt Mayo) Date: Thu, 8 Aug 2013 10:42:18 -0400 Subject: [Mailman-Users] Message bodies empty only on gmail mobile Message-ID: I have many users who, when reading list messages using gmail mobile see only blank/empty body text. Any help with this would be greatly appreciated. Walt From mark at msapiro.net Sat Aug 10 22:46:22 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Aug 2013 13:46:22 -0700 Subject: [Mailman-Users] About PostLimit.py again ( was :To restrict sending email messages per day) In-Reply-To: References: Message-ID: <5206A69E.9060005@msapiro.net> On 08/08/2013 08:54 AM, e.c. wrote: > Thanks for these pythons routines, Mark. Since I don't know much about > the language, I need some clarification on the part of the code between > triple quote marks (""") and also between the lines that have > ----------- cut -----. Are these constructs some kind of ad hoc python > syntax extensions for commenting out or do they need to be made > invisible with prepended # characters? The text contained within the """ marks is a Python docstring. Everything from """Handler to limit a member's posts to a list to M per calendar day or M per through -------------------------- cut ------------ """ is documentation. The lines between -------------------------- cut ------------ lines, i.e., beginning with import copy and ending with mlist.post_period = 0 are what you could put in lists/LISTNAME/extend.py after editing the lines mlist.post_member_limit = 0 mlist.post_list_limit = 0 mlist.post_period = 0 per the comments preceding them. > I would especially like to know whether it's possible to substitute > worldtime (gmt) in the places where localtime is referenced. Yes. Just replace the four occurrences of time.localtime with time.gmtime. Note that this only affects the time zone for determining the current day if the period is the current day rather than a number of hours. > This > posting throttling functionality is needed to make a mailman list > correspond as closely as possible to the functionality once offered by > LISTSERV. Is the part of the code between the cut marks only to be used > if the globals M, L, and PERIOD are to be set with list attributes via > the extend.py file? Could someone comment the code relating to the > global PERIOD and localetime. The extend.py or something equivalent is required in any case tio i8nsert the PostLi8mit handler into the list's pipeline. If period is set to a non-zero value, it is irrelevant whether time is local time or UTC (GMT) because an elapsed number of hours is the same regardless of time zone. > For my purposes PERIOD could be hardcoded > to 24 hours and based on gmt. Just copy the code between the -------------------------- cut ------------ lines to lists/LISTNAME/extend.py and change mlist.post_period = 0 to mlist.post_period = 24 in that file. You will also need to set mlist.post_member_limit = M in that file where M is the maximum number of user posts per 24 hour period, e.g. mlist.post_member_limit = 2 will reject the 3rd post from a member within the last 24 hours, and if you want to limit the total number of list posts, also set mlist.post_list_limit to that limit. > It looks like the code at > http://www.msapiro.net/scripts/PostLimit.py can't be inserted as is into > > Mailman/Handlers/PostLimit.py > > Am I right about that? No, the code at http://www.msapiro.net/scripts/PostLimit.py is intended to be copied as is to Mailman/Handlers/PostLimit.py -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Aug 11 03:17:51 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Aug 2013 18:17:51 -0700 Subject: [Mailman-Users] Update virtual-mailman for the migrated lists In-Reply-To: <3E753388-452A-41FC-8A44-159FAAD03F26@cs.indiana.edu> References: <3E753388-452A-41FC-8A44-159FAAD03F26@cs.indiana.edu> Message-ID: <5206E63F.8070706@msapiro.net> On 08/02/2013 08:40 PM, DongInn Kim wrote: > > Is there a way to generate the virtual-mailman file for the migrated lists which are hosted by some virtual hosts? > It seems that there are patterns to follow in virtual-mailman and I may be able to update it manually. The manual work should not be done on this file but I have no idea how to deal with the migrated mailing lists which are hosted by some virtual hosts. > If there is a script to do this kind job properly, that would be nice. If I understand correctly, Mailman's bin/genaliases is what you want. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Aug 11 03:40:53 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Aug 2013 18:40:53 -0700 Subject: [Mailman-Users] Howto change Mailman email To field from list@example.com to members individual email address In-Reply-To: <874nb5ncmw.fsf@uwakimon.sk.tsukuba.ac.jp> References: <51FC050F.9040700@silvacapitalmanagement.com> <874nb5ncmw.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <5206EBA5.4090003@msapiro.net> On 08/04/2013 12:22 AM, Stephen J. Turnbull wrote: > Patrick McEvoy writes: > > > > I have just set up a Mailman mailing list. When I send an email to the > > list the email header each member receives has my email address in the > > >From field and the list email address in the To field instead of the > > recipient's email address in the To field. How can I change this? > > Go to your list administrator's page for that list. > Non-digest options -> Personalization > Select "Full Personalization". > Save the options. If this option doesn't appear on that page, the installation needs to set OWNERS_CAN_ENABLE_PERSONALIZATION = Yes in mm_cfg.py to enable it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Aug 11 05:54:18 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Aug 2013 20:54:18 -0700 Subject: [Mailman-Users] Message bodies empty only on gmail mobile In-Reply-To: References: Message-ID: <52070AEA.8060901@msapiro.net> On 08/08/2013 07:42 AM, Walt Mayo wrote: > I have many users who, when reading list messages using gmail mobile > see only blank/empty body text. Any help with this would be greatly > appreciated. Does your list have a non-empty, possibly whitespace only, msg_header? Can you post a raw message with all MIME parts and headers as received from your list? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Aug 11 06:43:02 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Aug 2013 21:43:02 -0700 Subject: [Mailman-Users] Bug in 2.1.16rc2 regarding new logging to vette? In-Reply-To: <20130808175526.GC16765@charite.de> References: <20130808175526.GC16765@charite.de> Message-ID: <52071656.3090009@msapiro.net> On 08/08/2013 10:55 AM, Ralf Hildebrandt wrote: > - IncomingRunner now logs rejected messages to the vette log. > (LP: #1068837) > > So I had a look today and found: > > Aug 06 12:12:59 2013 (11069) doctors: Refused posting: > ... > Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting: > Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting: > Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting: > > I *looks* as if there's something missing, like the message-id or some > other identifier... Those are long standing messages that are logged when a post is rejected or discarded via the admindb CGI or discarded by the user via the confirm CGI. They haven't changed in years. They are multi-line as in Aug 03 09:32:29 2013 (23645) LISTNAME: Discarded posting: From: user at example.com Subject: Specialized Stumpjumper for sale Reason: Non-members are not allowed to post messages to this list. The change in 2.1.16 that you reference produces messages like: Aug 02 22:31:55 2013 (26451) Message rejected, msgid: list: LISTNAME, handler: Moderate, reason: ... The reason is provided by the handler. It is nonmember_rejection_notice or a canned message in the case of a non-member reject and a canned message in the case of other auto rejects. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Aug 11 07:42:47 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 10 Aug 2013 22:42:47 -0700 Subject: [Mailman-Users] Mailman Moderation Queue - recovery possible? In-Reply-To: References: Message-ID: <52072457.3030807@msapiro.net> On 07/31/2013 04:34 AM, Drew Tenenholz wrote: > > Is there a way to restore or access the messages once they have been discarded? Assuming you didn't check "Preserve messages for the site administrator", only from some kind of file system backup. If you did check that box it will be in $var-prefix/spam/spam-LISTNAME-dddd.msg. > If I were able to get to a backup snapshot of the system, which file would I be looking to restore? $var-prefix/data/heldmsg-LISTNAME-dddd with a .pck or .txt extension depending on the setting of HOLD_MESSAGES_AS_PICKLES. If you can restore the file, you can see the message with bin/dumpdb if it's a .pck or cat if it's a .txt, but it won't appear in the admindb interface unless you do something like . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Aug 11 22:30:37 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 11 Aug 2013 13:30:37 -0700 Subject: [Mailman-Users] All the mails are not reaching all the members In-Reply-To: References: <51F6883E.3040805@msapiro.net> Message-ID: <5207F46D.7000009@msapiro.net> On 07/30/2013 01:32 AM, Amit Bhatt wrote: > I am the list moderator and can manage my mailing list but not that > much of tech savvy. If you can please let me know where and how to > Check Mailman's logs, particularly 'bounce', 'smtp' and > 'smtp-failure', > and the MTA logs to see if messages are being delivered, bouncing and etc. These logs are on the server that hosts your Mailman. You will have to enlist the help of whoever administers the server and its Mailman installation to see and interpret these logs. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From grshirley at gmail.com Mon Aug 12 19:31:22 2013 From: grshirley at gmail.com (Glenn Shirley) Date: Mon, 12 Aug 2013 13:31:22 -0400 Subject: [Mailman-Users] mailman and web with different hosting companies Message-ID: <52091BEA.4040307@gmail.com> If I have my mailman and web hosted by different companies (don't ask!) I get 404 errors when clicking on "Submit All Data" buttons. This is presumably because there are absolute references i.e. the POST is to my web domain rather than to the local host where mailman is hosted. Apart from changing the code has anyone dealt with this in an easier way? i couldn't find anything in the archives similar. Cheers, Glenn. From mark at msapiro.net Wed Aug 14 02:40:05 2013 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Aug 2013 17:40:05 -0700 Subject: [Mailman-Users] mailman and web with different hosting companies In-Reply-To: <52091BEA.4040307@gmail.com> References: <52091BEA.4040307@gmail.com> Message-ID: <520AD1E5.5070305@msapiro.net> On 08/12/2013 10:31 AM, Glenn Shirley wrote: > If I have my mailman and web hosted by different companies (don't ask!) > I get 404 errors when clicking on "Submit All Data" buttons. This is > presumably because there are absolute references i.e. the POST is to my > web domain rather than to the local host where mailman is hosted. If this is recent Mailman, the Action URL in the FORM tag should be relative. You can check by viewing the page source. In any case, this is probably an issue for the Mailman host to solve. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pmcevoy at silvacapitalmanagement.com Tue Aug 13 22:56:29 2013 From: pmcevoy at silvacapitalmanagement.com (Patrick McEvoy) Date: Tue, 13 Aug 2013 15:56:29 -0500 Subject: [Mailman-Users] Personalized header based on Gender. Message-ID: <520A9D7D.2000903@silvacapitalmanagement.com> Hello, I have turned on Full Personalization so I can have the individual's email address in the To field instead of the list email address. I am adding a personalized header to the list as well and would like to know if there is any way to personalize the header based on gender. For example Dear Mr for males and Dear Mrs females. Thanks for your help, Patrick From mark at msapiro.net Wed Aug 14 03:08:15 2013 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 13 Aug 2013 18:08:15 -0700 Subject: [Mailman-Users] Personalized header based on Gender. In-Reply-To: <520A9D7D.2000903@silvacapitalmanagement.com> References: <520A9D7D.2000903@silvacapitalmanagement.com> Message-ID: <520AD87F.9000504@msapiro.net> On 08/13/2013 01:56 PM, Patrick McEvoy wrote: > > I have turned on Full Personalization so I can have the individual's > email address in the To field instead of the list email address. I am > adding a personalized header to the list as well and would like to know > if there is any way to personalize the header based on gender. For > example Dear Mr for males and Dear Mrs females. Not in current Mailman. This would require modification to add a gender or a salutation attribute for each list member. If this were done, adding a new substitution variable for it is very easy, but adding the mechanism to collect and store the per-user data is more difficult. Why not just use 'Dear %(user_name)s:'. Of course, you'd then find that many users don't provide a display name, which issue would probably apply to providing gender as well. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Wed Aug 14 07:00:33 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 14 Aug 2013 14:00:33 +0900 Subject: [Mailman-Users] Personalized header based on Gender. In-Reply-To: <520A9D7D.2000903@silvacapitalmanagement.com> References: <520A9D7D.2000903@silvacapitalmanagement.com> Message-ID: <87fvuckgsu.fsf@uwakimon.sk.tsukuba.ac.jp> Patrick McEvoy writes: > For example Dear Mr for males and Dear Mrs females. Best avoided, for various reasons as Mark mentions, and also because of the Miss/Mrs/Ms issue for women. From vancleef at lostwells.net Wed Aug 14 18:12:51 2013 From: vancleef at lostwells.net (Hank van Cleef) Date: Wed, 14 Aug 2013 10:12:51 -0600 (MDT) Subject: [Mailman-Users] Personalized header based on Gender. In-Reply-To: <520A9D7D.2000903@silvacapitalmanagement.com> Message-ID: <201308141612.r7EGCp0J007809@joanne.lostwells.net> The esteemed Patrick McEvoy has said: > > Hello, > > I have turned on Full Personalization so I can have the individual's > email address in the To field instead of the list email address. I am > adding a personalized header to the list as well and would like to know > if there is any way to personalize the header based on gender. For > example Dear Mr for males and Dear Mrs females. > > Thanks for your help, > > Patrick > If you try to do this, you're going to get into a nasty thicket of "political correctness" issues. As Mark suggests, you're best off using Dear [name] with no attempt at honorifics. You're looking at sociological issues here, not technological. Hank From pmcevoy at silvacapitalmanagement.com Wed Aug 14 19:21:05 2013 From: pmcevoy at silvacapitalmanagement.com (Patrick McEvoy) Date: Wed, 14 Aug 2013 12:21:05 -0500 Subject: [Mailman-Users] Personalized header based on Gender. In-Reply-To: <201308141612.r7EGCp0J007809@joanne.lostwells.net> References: <201308141612.r7EGCp0J007809@joanne.lostwells.net> Message-ID: <520BBC81.70204@silvacapitalmanagement.com> To clarify, in some languages other than English dear has gender such as Spanish, Estimado for males and Estimada for females. Thanks, Patrick On 08/14/2013 11:12 AM, Hank van Cleef wrote: > The esteemed Patrick McEvoy has said: >> Hello, >> >> I have turned on Full Personalization so I can have the individual's >> email address in the To field instead of the list email address. I am >> adding a personalized header to the list as well and would like to know >> if there is any way to personalize the header based on gender. For >> example Dear Mr for males and Dear Mrs females. >> >> Thanks for your help, >> >> Patrick >> > If you try to do this, you're going to get into a nasty thicket of > "political correctness" issues. As Mark suggests, you're best off > using Dear [name] with no attempt at honorifics. > > You're looking at sociological issues here, not technological. > > Hank -- Patrick McEvoy CTO Silva Capital Management, LLC 625 N. Michigan Ave, Suite 412 Chicago, IL 60611 Office: 312-397-0400, Fax: 312-397-0404 pmcevoy at silvacapitalmanagement.com Silva Capital Management, LLC From stephen at xemacs.org Wed Aug 14 19:47:16 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 15 Aug 2013 02:47:16 +0900 Subject: [Mailman-Users] Personalized header based on Gender. In-Reply-To: <520BBC81.70204@silvacapitalmanagement.com> References: <201308141612.r7EGCp0J007809@joanne.lostwells.net> <520BBC81.70204@silvacapitalmanagement.com> Message-ID: <877gfojhaz.fsf@uwakimon.sk.tsukuba.ac.jp> Patrick McEvoy writes: > To clarify, in some languages other than English dear has gender such as > Spanish, Estimado for males and Estimada for females. Ugh, that is a problem. The best solution I can think of is to put it in the fullname in the email address: To: "Mr. Patrick McEvoy" I'm pretty sure there is already a formatting sequence to insert fullname. Unfortunately, Mailman is not designed to be a customer relationship management system, so whatever you do will be something of a kludge. Steve From vancleef at lostwells.net Wed Aug 14 21:22:07 2013 From: vancleef at lostwells.net (Hank van Cleef) Date: Wed, 14 Aug 2013 13:22:07 -0600 (MDT) Subject: [Mailman-Users] Personalized header based on Gender. In-Reply-To: <520BBC81.70204@silvacapitalmanagement.com> Message-ID: <201308141922.r7EJM7X5007919@joanne.lostwells.net> The esteemed Patrick McEvoy has said: > > This is a multi-part message in MIME format. > --------------020104040702070705060401 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 7bit > > To clarify, in some languages other than English dear has gender such as > Spanish, Estimado for males and Estimada for females. > > Thanks, > > Patrick > Yes, French (which I deal with) has the same issue. And while other-language cultures don't seem to have as much of a political correctness problem as US American, it still exists to the extent that I consider it wise to devise a gender-neutral greeting, even if not the commonly-used one in the culture. Hank From gp at holisticgp.com.au Thu Aug 15 15:06:27 2013 From: gp at holisticgp.com.au (Dr Michael Daly) Date: Thu, 15 Aug 2013 23:06:27 +1000 (EST) Subject: [Mailman-Users] virtual domain and alias_maps Message-ID: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> Hi I am having problems getting mail delivered to list members, on a virtual domain. This did not happen when a conventional ie non virtual, domain. Maybe there is a problem with aliases...I had to manually create the /usr/lib/mailman/data dir and both the 'alias' and 'virtual-mailman' files in that dir (not sure of what contents should be in the described 'alias' and 'virtual-mailman' files) But running genaliases does not create the expected .db files ownership /permissions on those two files are apache:mailman and 664 In postfix I have: alias_maps = hash:/etc/aliases, hash:/usr/lib/mailman/data/aliases virtual_alias_maps = hash:/etc/postfix/virtual, hash:/usr/lib/mailman/data/virtual-mailman and I have created the list and configured mm_cfg.py as specified Thanks Michael From mark at msapiro.net Thu Aug 15 19:53:37 2013 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Aug 2013 10:53:37 -0700 Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> Message-ID: <520D15A1.5020603@msapiro.net> On 08/15/2013 06:06 AM, Dr Michael Daly wrote: > > and I have created the list and configured mm_cfg.py as specified And what is in mm_cfg.py? Specifically do you have MTA = 'Postfix' and POSTFIX_STYLE_VIRTUAL_DOMAINS = ['the.lists.email.hostname'] See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Thu Aug 15 19:55:16 2013 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Thu, 15 Aug 2013 17:55:16 +0000 Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> Message-ID: <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.com> Michael Daly wrote: >Hi >I am having problems getting mail delivered to list members, on a virtual domain. This did not happen when a conventional ie non virtual, domain. >Maybe there is a problem with aliases...I had to manually create the /usr/lib/mailman/data dir and both the 'alias' and 'virtual-mailman' files in that dir >(not sure of what contents should be in the described 'alias' and 'virtual-mailman' files) >But running genaliases does not create the expected .db files What output do you get after running it? >In postfix I have: >alias_maps = hash:/etc/aliases, hash:/usr/lib/mailman/data/aliases Not required. virtual_alias_maps = hash:/etc/postfix/virtual, hash:/usr/lib/mailman/data/virtual-mailman Yes. >and I have created the list and configured mm_cfg.py as specified So you set MTA to Postfix and populated POSTFIX_STYLE_VIRTUAL_DOMAINS to your virtual domains? Thanks. Andrew. From gp at holisticgp.com.au Fri Aug 16 04:02:20 2013 From: gp at holisticgp.com.au (Dr Michael Daly) Date: Fri, 16 Aug 2013 12:02:20 +1000 (EST) Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.c om> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.com> Message-ID: <3973.203.45.56.250.1376618540.squirrel@www.holisticgp.com.au> Hi Running genaliases produces NO output, just a carriage return. Running genaliases -h produces the relevant help information I should say the mailman version is 2.1.9, which was installed via an 'apt-get' command on a centos package. In mm_cfg.py I have: ('cpddomain.org.au' is not the real domain name, but it is a virtual one) At present a subscriber can send a message to the list owner, but no others, and the message does NOT have the expected Subject Line prefix eg [List name] ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in Defaults.py. # add_virtualhost('www.cpddomain.org.au', 'cpddomain.org.au') POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cpddomain.org.au'] MTA = 'Postfix' Thanks Michael Michael Daly wrote: >Hi >I am having problems getting mail delivered to list members, on a virtual > domain. This did not happen when a conventional ie non virtual, domain. >Maybe there is a problem with aliases...I had to manually create the > /usr/lib/mailman/data dir and both the 'alias' and 'virtual-mailman' > files in that dir >(not sure of what contents should be in the described 'alias' and > 'virtual-mailman' files) >But running genaliases does not create the expected .db files What output do you get after running it? >In postfix I have: >alias_maps = hash:/etc/aliases, hash:/usr/lib/mailman/data/aliases Not required. virtual_alias_maps = hash:/etc/postfix/virtual, hash:/usr/lib/mailman/data/virtual-mailman Yes. >and I have created the list and configured mm_cfg.py as specified So you set MTA to Postfix and populated POSTFIX_STYLE_VIRTUAL_DOMAINS to your virtual domains? Thanks. Andrew. Dr Michael Daly MB, BS GradDip(Integrative Medicine), GradCert(Evidence Based Practice), M Bus(Information Innovation), GradDip(Document Management) 03 9521 0352 0413 879 029 From jimpop at gmail.com Fri Aug 16 04:17:34 2013 From: jimpop at gmail.com (Jim Popovitch) Date: Thu, 15 Aug 2013 22:17:34 -0400 Subject: [Mailman-Users] Post-subscription processing Message-ID: What's the sanest way to export a list of current subscribers everytime there is a new subscriber? I want to maintain a table of current list members (for postfix to reject if to:list != from:subscriber) Tia, -Jim P. From mark at msapiro.net Fri Aug 16 04:39:31 2013 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Aug 2013 19:39:31 -0700 Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <3973.203.45.56.250.1376618540.squirrel@www.holisticgp.com.au> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.com> <3973.203.45.56.250.1376618540.squirrel@www.holisticgp.com.au> Message-ID: <520D90E3.2030703@msapiro.net> On 08/15/2013 07:02 PM, Dr Michael Daly wrote: > > I should say the mailman version is 2.1.9, which was installed via an > 'apt-get' command on a centos package. Then I should say see the FAQ at . > In mm_cfg.py I have: > ('cpddomain.org.au' is not the real domain name, but it is a virtual one) > > At present a subscriber can send a message to the list owner, but no > others, and the message does NOT have the expected Subject Line prefix eg > [List name] By addressing the owner's email or LISTNAME-owner at ... ? Either way, the lack of a subject_prefix is normal? > ############################################################## > # Put YOUR site-specific configuration below, in mm_cfg.py . # > # See Defaults.py for explanations of the values. # > > # Note - if you're looking for something that is imported from mm_cfg, but > you > # didn't find it above, it's probably in Defaults.py. > # > add_virtualhost('www.cpddomain.org.au', 'cpddomain.org.au') > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cpddomain.org.au'] > MTA = 'Postfix' Is the host_name attribute on the list's General Options page cpddomain.org.au? With MTA = 'Postfix' genaliases will write Mailman's data/aliases file with 10 aliases for each list as in item 3 of the FAQ at . In addition, it will write data/virtual-mailman with virtual mapping for each list whose host_name is cpddomain.org.au. It will also invoke the commands defined in the Defaults.py settings POSTFIX_ALIAS_CMD = '/usr/sbin/postalias' POSTFIX_MAP_CMD = '/usr/sbin/postmap' to create/update data/aliases.db and data/virtual-mailman.db. If you don't see this, it's because the data directory is not in /usr/lib/mailman/. See the FAQ at -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Aug 16 05:24:15 2013 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 15 Aug 2013 20:24:15 -0700 Subject: [Mailman-Users] Post-subscription processing In-Reply-To: References: Message-ID: <520D9B5F.4010602@msapiro.net> On 08/15/2013 07:17 PM, Jim Popovitch wrote: > What's the sanest way to export a list of current subscribers > everytime there is a new subscriber? I want to maintain a table of > current list members (for postfix to reject if to:list != > from:subscriber) How about unsubscribes? Changes of address? I would suggest that the most reliable way is to put hooks in the Mailman/OldStyleMemberships.py member adaptor routines addNewMember and removeMember. This will get changes of address too because that is done by a remove and add. Another is to create something that would parse the subscribe log and get those list names that have entries with time stamps later than the last run and do bin/list_members for those lists, and run it frequently via cron. This has the advantage of not modifying Mailman, but has the drawback that address changes aren't logged (unless you are running ), and there may be log rotation issues to deal with. If you have lots of excess resources, you could just run bin/list_members for all lists at frequent intervals via cron. e.g. #!/bin/bash for list in `/path/to/bin/list_lists --bare`; do /path/to/bin/list_members $list > /path/to/${list}_member_list done -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jra at baylink.com Fri Aug 16 05:46:35 2013 From: jra at baylink.com (Jay Ashworth) Date: Thu, 15 Aug 2013 23:46:35 -0400 (EDT) Subject: [Mailman-Users] Post-subscription processing In-Reply-To: <520D9B5F.4010602@msapiro.net> Message-ID: <32027875.3716.1376624795792.JavaMail.root@benjamin.baylink.com> ----- Original Message ----- > From: "Mark Sapiro" > On 08/15/2013 07:17 PM, Jim Popovitch wrote: > > What's the sanest way to export a list of current subscribers > > everytime there is a new subscriber? I want to maintain a table of > > current list members (for postfix to reject if to:list != > > from:subscriber) > > How about unsubscribes? Changes of address? I would suggest that the > most reliable way is to put hooks in the > Mailman/OldStyleMemberships.py > member adaptor routines addNewMember and removeMember. This will get > changes of address too because that is done by a remove and add. Perhaps I'm missing something, but doesn't Mailman already have "only allow members to post to the list"? NANOG had to make special provisions, but that was because they wanted to have a read-only status to put people in when they needed a timeout. Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274 From jimpop at gmail.com Fri Aug 16 06:39:41 2013 From: jimpop at gmail.com (Jim Popovitch) Date: Fri, 16 Aug 2013 00:39:41 -0400 Subject: [Mailman-Users] Post-subscription processing In-Reply-To: <32027875.3716.1376624795792.JavaMail.root@benjamin.baylink.com> References: <520D9B5F.4010602@msapiro.net> <32027875.3716.1376624795792.JavaMail.root@benjamin.baylink.com> Message-ID: On Thu, Aug 15, 2013 at 11:46 PM, Jay Ashworth wrote: > ----- Original Message ----- >> From: "Mark Sapiro" > >> On 08/15/2013 07:17 PM, Jim Popovitch wrote: >> > What's the sanest way to export a list of current subscribers >> > everytime there is a new subscriber? I want to maintain a table of >> > current list members (for postfix to reject if to:list != >> > from:subscriber) >> >> How about unsubscribes? Changes of address? I would suggest that the >> most reliable way is to put hooks in the >> Mailman/OldStyleMemberships.py >> member adaptor routines addNewMember and removeMember. This will get >> changes of address too because that is done by a remove and add. > > Perhaps I'm missing something, but doesn't Mailman already have "only > allow members to post to the list"? > > NANOG had to make special provisions, but that was because they wanted > to have a read-only status to put people in when they needed a timeout. The SDLU list is whitelist'ed from spamassassin processing, so a fair amout of spam from non-members gets into the moderator queue. The goal is to reject at the MTA where sender is not in a sender_access restriction table (which will be maintained by this modification to Mailman). Mark, thanks for the ideas and input. I want to avoid the cron solution, in order to prevent racing issues with folks who subscribe and immediately post. -Jim P. From jra at baylink.com Fri Aug 16 06:52:48 2013 From: jra at baylink.com (Jay Ashworth) Date: Fri, 16 Aug 2013 00:52:48 -0400 (EDT) Subject: [Mailman-Users] Post-subscription processing In-Reply-To: Message-ID: <25481315.3736.1376628768624.JavaMail.root@benjamin.baylink.com> ----- Original Message ----- > From: "Jim Popovitch" > The SDLU list is whitelist'ed from spamassassin processing, so a fair amout > of spam from non-members gets into the moderator queue. The goal is to > reject at the MTA where sender is not in a sender_access restriction > table (which will be maintained by this modification to Mailman). Got it. That sounds generally useful; in implementing patches you might want to keep in mind my personal favorite programming maxim: Figure out what general case your problem is a specific case of... and then solve the general case. :-) Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274 From gp at holisticgp.com.au Fri Aug 16 10:17:10 2013 From: gp at holisticgp.com.au (Dr Michael Daly) Date: Fri, 16 Aug 2013 18:17:10 +1000 (EST) Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <520D90E3.2030703@msapiro.net> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.com> <3973.203.45.56.250.1376618540.squirrel@www.holisticgp.com.au> <520D90E3.2030703@msapiro.net> Message-ID: <2575.150.101.154.174.1376641030.squirrel@www.holisticgp.com.au> Thanks for the advice; I found the *data directory* in /etc/mailman/, along with the 'genaliases' produced files that I had been unable to locate So I reconfigured postfix with: alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases (I know someone said above this wasn't needed) AND virtual_alias_maps = hash:/etc/postfix/virtual, hash:/etc/mailman/virtual-mailman So, now, at least email sent to the list server address (discuss at cpddomain.org.au) seems to reach the mailserver, but the maillog shows its rejected as an unknown user: to=, orig_to=, relay=local, delay=0.09, delays=0.08/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "discuss") Where 'discuss at cpddomain' is the list-server email address given in the welcome email, but which seems to be reconfigured as an email addressed to the main (non-virtual) domain on the system I don't have a specific entry in my vmailbox file for discuss at cpddomain.org.au...I didn't think that was needed The other anomaly is that the relevant alias entries appear both in /etc/mailman/aliases: # STANZA START: discuss # CREATED: Fri Aug 16 16:38:08 2013 discuss: "|/usr/lib/mailman/mail/mailman post discuss" discuss-admin: "|/usr/lib/mailman/mail/mailman admin discuss" discuss-bounces: "|/usr/lib/mailman/mail/mailman bounces discuss" discuss-confirm: "|/usr/lib/mailman/mail/mailman confirm discuss" discuss-join: "|/usr/lib/mailman/mail/mailman join discuss" discuss-leave: "|/usr/lib/mailman/mail/mailman leave discuss" discuss-owner: "|/usr/lib/mailman/mail/mailman owner discuss" discuss-request: "|/usr/lib/mailman/mail/mailman request discuss" discuss-subscribe: "|/usr/lib/mailman/mail/mailman subscribe discuss" discuss-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe discuss" # STANZA END: discuss and in /etc/mailman/virtual-mailman: # STANZA START: discuss # CREATED: Fri Aug 16 16:38:08 2013 discuss at cpddomain.org.au discuss discuss-admin at cpddomain.org.au discuss-admin discuss-bounces at cpddomain.org.au discuss-bounces discuss-confirm at cpddomain.org.au discuss-confirm discuss-join at cpddomain.org.au discuss-join discuss-leave at cpddomain.org.au discuss-leave discuss-owner at cpddomain.org.au discuss-owner discuss-request at cpddomain.org.au discuss-request discuss-subscribe at cpddomain.org.au discuss-subscribe discuss-unsubscribe at cpddomain.org.au discuss-unsubscribe # STANZA END: discuss Hopefully a solution is not far away! Michael On 08/15/2013 07:02 PM, Dr Michael Daly wrote: > > I should say the mailman version is 2.1.9, which was installed via an > 'apt-get' command on a centos package. Then I should say see the FAQ at . > In mm_cfg.py I have: > ('cpddomain.org.au' is not the real domain name, but it is a virtual > one) > > At present a subscriber can send a message to the list owner, but no > others, and the message does NOT have the expected Subject Line prefix > eg > [List name] By addressing the owner's email or LISTNAME-owner at ... ? Either way, the lack of a subject_prefix is normal? > ############################################################## > # Put YOUR site-specific configuration below, in mm_cfg.py . # > # See Defaults.py for explanations of the values. # > > # Note - if you're looking for something that is imported from mm_cfg, > but > you > # didn't find it above, it's probably in Defaults.py. > # > add_virtualhost('www.cpddomain.org.au', 'cpddomain.org.au') > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cpddomain.org.au'] > MTA = 'Postfix' Is the host_name attribute on the list's General Options page cpddomain.org.au? With MTA = 'Postfix' genaliases will write Mailman's data/aliases file with 10 aliases for each list as in item 3 of the FAQ at . In addition, it will write data/virtual-mailman with virtual mapping for each list whose host_name is cpddomain.org.au. It will also invoke the commands defined in the Defaults.py settings POSTFIX_ALIAS_CMD = '/usr/sbin/postalias' POSTFIX_MAP_CMD = '/usr/sbin/postmap' to create/update data/aliases.db and data/virtual-mailman.db. If you don't see this, it's because the data directory is not in /usr/lib/mailman/. See the FAQ at -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/gp%40holisticgp.com.au Dr Michael Daly MB, BS GradDip(Integrative Medicine), GradCert(Evidence Based Practice), M Bus(Information Innovation), GradDip(Document Management) 03 9521 0352 0413 879 029 From mark at msapiro.net Fri Aug 16 19:31:30 2013 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 16 Aug 2013 10:31:30 -0700 Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <2575.150.101.154.174.1376641030.squirrel@www.holisticgp.com.au> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.com> <3973.203.45.56.250.1376618540.squirrel@www.holisticgp.com.au> <520D90E3.2030703@msapiro.net> <2575.150.101.154.174.1376641030.squirrel@www.holisticgp.com.au> Message-ID: <520E61F2.6080006@msapiro.net> On 08/16/2013 01:17 AM, Dr Michael Daly wrote: > > So I reconfigured postfix with: > alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases > (I know someone said above this wasn't needed) And that was bad advice. It is needed. See below. > AND > virtual_alias_maps = hash:/etc/postfix/virtual, > hash:/etc/mailman/virtual-mailman > > So, now, at least email sent to the list server address > (discuss at cpddomain.org.au) seems to reach the mailserver, but the maillog > shows its rejected as an unknown user: > to=, orig_to=, > relay=local, delay=0.09, delays=0.08/0.01/0/0.01, dsn=5.1.1, > status=bounced (unknown user: "discuss") > Where 'discuss at cpddomain' is the list-server email address given in the > welcome email, but which seems to be reconfigured as an email addressed to > the main (non-virtual) domain on the system That is as it should be except for the ultimate 'unknown user' which I don't fully understand. > I don't have a specific entry in my vmailbox file for > discuss at cpddomain.org.au...I didn't think that was needed It's not. > The other anomaly is that the relevant alias entries appear both in > /etc/mailman/aliases: This is as it should be. > # STANZA START: discuss > # CREATED: Fri Aug 16 16:38:08 2013 > discuss: "|/usr/lib/mailman/mail/mailman post discuss" > discuss-admin: "|/usr/lib/mailman/mail/mailman admin discuss" > discuss-bounces: "|/usr/lib/mailman/mail/mailman bounces discuss" > discuss-confirm: "|/usr/lib/mailman/mail/mailman confirm discuss" > discuss-join: "|/usr/lib/mailman/mail/mailman join discuss" > discuss-leave: "|/usr/lib/mailman/mail/mailman leave discuss" > discuss-owner: "|/usr/lib/mailman/mail/mailman owner discuss" > discuss-request: "|/usr/lib/mailman/mail/mailman request discuss" > discuss-subscribe: "|/usr/lib/mailman/mail/mailman subscribe discuss" > discuss-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe discuss" > # STANZA END: discuss The above are the aliases that cause mail to the local addresses 'discuss' and 'discuss-*' to be appropriately piped to Mailman. > and in /etc/mailman/virtual-mailman: > # STANZA START: discuss > # CREATED: Fri Aug 16 16:38:08 2013 > discuss at cpddomain.org.au discuss > discuss-admin at cpddomain.org.au discuss-admin > discuss-bounces at cpddomain.org.au discuss-bounces > discuss-confirm at cpddomain.org.au discuss-confirm > discuss-join at cpddomain.org.au discuss-join > discuss-leave at cpddomain.org.au discuss-leave > discuss-owner at cpddomain.org.au discuss-owner > discuss-request at cpddomain.org.au discuss-request > discuss-subscribe at cpddomain.org.au discuss-subscribe > discuss-unsubscribe at cpddomain.org.au discuss-unsubscribe > # STANZA END: discuss These are virtual mappings that map virtual addresses like discuss(-*)@cpddomain.org.au to local addresses discuss(-*). This part is working correctly per the part of the log message that says "to=, orig_to=,", however the part that says "relay=local, ... status=bounced (unknown user: "discuss")" is saying that for some reason, the alias discuss: "|/usr/lib/mailman/mail/mailman post discuss" is not being processed by Postfix even though the message is being handled by the 'local' transport. What are the ownership and permissions on /etc/mailman/aliases.db. Is the time stamp of this as recent as that on /etc/mailman/aliases? Are there any Postfix log entries related to /etc/mailman/aliases? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gp at holisticgp.com.au Sat Aug 17 10:54:40 2013 From: gp at holisticgp.com.au (Dr Michael Daly) Date: Sat, 17 Aug 2013 18:54:40 +1000 (EST) Subject: [Mailman-Users] virtual domain and alias_maps In-Reply-To: <520E61F2.6080006@msapiro.net> References: <50690.120.148.195.2.1376571987.squirrel@www.holisticgp.com.au> <624f711d4fd543a5872ac44aadf768d2@DBXPR04MB047.eurprd04.prod.outlook.com> <3973.203.45.56.250.1376618540.squirrel@www.holisticgp.com.au> <520D90E3.2030703@msapiro.net> <2575.150.101.154.174.1376641030.squirrel@www.holisticgp.com.au> <520E61F2.6080006@msapiro.net> Message-ID: <50164.120.148.195.2.1376729680.squirrel@www.holisticgp.com.au> Hey... reporting success! The problem has resolved after changing permissions for files residing in the /etc/mailman (data) directory to: mailman:mailman The timestamps were ok Well actually, mailman:mailman is what I did for the 'aliases' file but (accidentally) not for 'virtual mailman' (was root:mailman). But it all works! When you have exhausted your own supply of ideas, getting help this way from experts giving their time on an honorary basis is absolutely fantastic! For anyone searching the archives, the location of the data dir is actually specified in /usr/lib/mailman/Mailman/Defaults.py under 'CONFIG_DIR' Thanks again! Michael Mailman 2.1.9 What are the ownership and permissions on /etc/mailman/aliases.db. Is the time stamp of this as recent as that on /etc/mailman/aliases? Are there any Postfix log entries related to /etc/mailman/aliases? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From crile at crile.com Sat Aug 17 21:33:24 2013 From: crile at crile.com (Crile Carvey) Date: Sat, 17 Aug 2013 19:33:24 +0000 Subject: [Mailman-Users] New list sending only to one member Message-ID: <2e27123696294548821d57ad36ed4b20@BL2PR05MB212.namprd05.prod.outlook.com> Hello, I have added a new list to an existing, fully functional mailman installation but messages are not being delivered to all of the list members. This mailman instance has been operational for a number of years servicing two other active lists. Those lists continue to work just fine, so I don't believe it is an installation or mailman problem but rather something I did or did not do when adding the new list. I used the mailman web interface to create the list and add the members. The only thing I did outside of the mailman web interface was to add aliases. I added the aliases by using webmin, which provides a GUI layer on top of postfix. Everything seemed to work fine until I started testing. After posting a test message to the list, I found that the test message was only delivered to one member. It may be of interest that the one member to whom the message was delivered is a member of one of the other lists and is also a mailman administrator. I am a mailman newbie, as well as clumsy with linux, but I have full access to the server and I am comfortable running commands. Thanks for any assistance or hints. Crile From mark at msapiro.net Sun Aug 18 17:46:39 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 18 Aug 2013 08:46:39 -0700 Subject: [Mailman-Users] New list sending only to one member In-Reply-To: <2e27123696294548821d57ad36ed4b20@BL2PR05MB212.namprd05.prod.outlook.com> References: <2e27123696294548821d57ad36ed4b20@BL2PR05MB212.namprd05.prod.outlook.com> Message-ID: <5210EC5F.4000008@msapiro.net> On 08/17/2013 12:33 PM, Crile Carvey wrote: > > The only thing I did outside of the mailman web interface > was to add aliases. And what aliases did you add? A couple of possibilities are that you are mailing to LISTNAME-owner at ... instead of LISTNAME at ... or that the alias for LISTNAME has the 'owner' argument rather than the 'post' argument > I added the aliases by using webmin, which > provides a GUI layer on top of postfix. Why aren't you using Mailman-Postfix integration ? > Everything seemed to work > fine until I started testing. After posting a test message to the > list, I found that the test message was only delivered to one member. What's in Mailman's 'post', 'smtp' and 'smtp-failure' logs? What's in Postfix' logs for the message delivery to Mailman and the message(s) from Mailman? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Ralf.Hildebrandt at charite.de Sun Aug 18 18:09:22 2013 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Sun, 18 Aug 2013 18:09:22 +0200 Subject: [Mailman-Users] Removing somebody from all lists (even pending subscriptions) Message-ID: <20130818160922.GO18912@charite.de> At python.org we recently had massive subscription attempts from addresses to multiple (>10) mailinglists, with an obvious intention of spamming. Naturally, I used: /srv/mailman/bin/remove_members --fromall address at freemailer.example to remove the culprit from all lists. Unfortunately I have not found a way of removing the address from the list of *pending* subscription requests. How can I solve that problem? -- 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 Sun Aug 18 19:24:05 2013 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 18 Aug 2013 10:24:05 -0700 Subject: [Mailman-Users] Removing somebody from all lists (even pending subscriptions) In-Reply-To: <20130818160922.GO18912@charite.de> References: <20130818160922.GO18912@charite.de> Message-ID: <52110335.8050809@msapiro.net> On 08/18/2013 09:09 AM, Ralf Hildebrandt wrote: > > Unfortunately I have not found a way of removing the address from the > list of *pending* subscription requests. How can I solve that problem? The script at may help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From drew.tenenholz at isid.org Tue Aug 20 19:05:41 2013 From: drew.tenenholz at isid.org (Drew Tenenholz) Date: Tue, 20 Aug 2013 13:05:41 -0400 Subject: [Mailman-Users] Moving a List from 2.1.11 (Mac) --> 2.1.9 (RHEL linux) Message-ID: All -- Anything to be particularly aware of when moving a list from 2.1.11 on a Mac server (where I ignored the Apple pre-installed version of Mailman and set up a new installation from the Mailman source so at least the components are where they are supposed to be, OS X 10.5.8 [!] ) to a Linux server running RHEL 5.x and Mailman 2.1.9. I wouldn't prefer to downgrade, but consolidation of mailman to a single machine is going to be helpful in the long run. Unfortunately for me, I'm going from the Mac server where I have full control to a Linux server operated by a partner organization where I have somewhat less control in that I can't upgrade Mailman from the RHEL release version. I've read through the FAQ 3.4 at which seems to indicate that it will generally be OK, but I'm looking for any changes that make my 2.1.11 list (which is in Cyrillic, by the way) not work well on the 2.1.9 installation (which does mostly English, and some Spanish & Portuguese, but nothing from a non-Roman alphabet right now). Thanks, Drew Tenenholz From eminmn at sysmatrix.net Thu Aug 22 18:53:32 2013 From: eminmn at sysmatrix.net (e.c.) Date: Thu, 22 Aug 2013 11:53:32 -0500 Subject: [Mailman-Users] Polling or voting on list Message-ID: Our list would benefit from an ability on the part of listmembers to vote on proposals made by listowners. In this type of discussion list a non-secret ballot would be appropriate, and both a tally of pro and con vote totals along with table (text file?) showing the vote associated with each subscribed email address. The results could be sent to each listmember or posted somehow on the list webmail site. (Does mailman have an area like Sympa's _Shared Documents_ area in the web interface?) Also, a way of setting a deadline for voting would have to be an option. (In our case a voting period of between 10 and 30 days would be appropriate.) Thanks for any info about mailman's current capabilities along these lines or suggestions for implementing this functionality. Ed From seun.ojedeji at gmail.com Thu Aug 22 20:05:12 2013 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Thu, 22 Aug 2013 19:05:12 +0100 Subject: [Mailman-Users] Polling or voting on list In-Reply-To: References: Message-ID: Within the contest of a mailing list would be voting or rating posts? Either way, I don't think mailman currently have such feature. Cheers! sent from Google nexus 4 On 22 Aug 2013 17:54, "e.c." wrote: > Our list would benefit from an ability on the part of listmembers to vote > on proposals made by listowners. In this type of discussion list a > non-secret ballot would be appropriate, and both a tally of pro and con > vote totals along with table (text file?) showing the vote associated with > each subscribed email address. The results could be sent to each listmember > or posted somehow on the list webmail site. (Does mailman have an area like > Sympa's _Shared Documents_ area in the web interface?) Also, a way of > setting a deadline for voting would have to be an option. (In our case a > voting period of between 10 and 30 days would be appropriate.) > > Thanks for any info about mailman's current capabilities along these lines > or suggestions for implementing this functionality. > > Ed > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://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: > http://mail.python.org/mailman/options/mailman-users/seun.ojedeji%40gmail.com > From barry at list.org Fri Aug 23 15:56:58 2013 From: barry at list.org (Barry Warsaw) Date: Fri, 23 Aug 2013 09:56:58 -0400 Subject: [Mailman-Users] ANN: wiki.list.org migrations Message-ID: <20130823095658.64e3ae70@anarchist> Hello everyone, I want to mention a few things related to wiki.list.org. First and most immediately, our currently wiki hosting provider Contegix, is in the process of a major infrastructure update which will cause some downtime for wiki.list.org. Contegix has been hosting our wiki gratis for several years, for which we are very grateful. Their support over the years has been superb. Unfortunately, the infrastructure our wiki is hosted on is quite legacy, and in fact, we are the last organization to be hosted on it. The time has come to for them to retire it, but they have again graciously offered to continue hosting our wiki gratis on their new infrastructure. The migration process is tricky, since we have to coordinate with Contegix's timing and our DNS changes with John Viega (Mailman's original author and owner of the list.org domain). Please be aware that the wiki may experience some downtime as both DNS and the instance get shuffled around. As some of you know, Paul Boddie has been working diligently on migrating our current Atlassian Confluence wiki to Moin. While Confluence has served us well over the years, we recognize that it is inappropriate for a GNU project such as Mailman to utilize a non-free wiki. Moin is our current choice for a free software wiki hosting platform, and Paul has done an amazing job on the migration, as anyone who reads mailman-developers can see. That work is close, but not quite ready for production. Stay tuned for more announcements on that front, or join mailman-developers for more information, or if you'd like to pitch in to help. We will send another announcement when the Contegix transfer is complete. In the meantime, if you see outages for wiki.list.org, please be patient. I hope there won't be too much of a disruption of service. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From eminmn at sysmatrix.net Fri Aug 23 16:41:10 2013 From: eminmn at sysmatrix.net (e.c.) Date: Fri, 23 Aug 2013 09:41:10 -0500 Subject: [Mailman-Users] Polling or voting on list In-Reply-To: References: Message-ID: Thanks, Seun. I suspected as much. The purpose of the prospective voting is to offload all moderator functions onto the general membership in those cases where the mailman program itself is not able mediate those functions (e.g. having owners set maximum daily posting limits per member and for the whole list). The list in questions is of planetary scope (with members from all continents except Antarctica and including members having 20 or 30 different native languages and the widest imaginable spectrum of opinions on political, cultural, and religious matters and with all these areas and many others considered on topic) so it's not typical of dedicated discussion groups. The prime directive here is to protect freedom of speech (writing, actually) while also providing for the fair-minded restraint of the occasional loose canon. From this short description of the problem it might seem that the group should have succumbed to anarchy long ago but it has been in continued existence since 1996. Ed On Thu, Aug 22, 2013 at 1:05 PM, Seun Ojedeji wrote: > Within the contest of a mailing list would be voting or rating posts? > > Either way, I don't think mailman currently have such feature. > > Cheers! > > sent from Google nexus 4 > On 22 Aug 2013 17:54, "e.c." wrote: > >> Our list would benefit from an ability on the part of listmembers to vote >> on proposals made by listowners. In this type of discussion list a >> non-secret ballot would be appropriate, and both a tally of pro and con >> vote totals along with table (text file?) showing the vote associated with >> each subscribed email address. The results could be sent to each >> listmember >> or posted somehow on the list webmail site. (Does mailman have an area >> like >> Sympa's _Shared Documents_ area in the web interface?) Also, a way of >> setting a deadline for voting would have to be an option. (In our case a >> voting period of between 10 and 30 days would be appropriate.) >> >> Thanks for any info about mailman's current capabilities along these lines >> or suggestions for implementing this functionality. >> >> Ed >> ------------------------------------------------------ >> Mailman-Users mailing list Mailman-Users at python.org >> http://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: >> http://mail.python.org/mailman/options/mailman-users/seun.ojedeji%40gmail.com >> > From mail at simonszu.de Thu Aug 22 18:54:53 2013 From: mail at simonszu.de (Simon Szustkowski) Date: Thu, 22 Aug 2013 18:54:53 +0200 Subject: [Mailman-Users] Moderation commands not working Message-ID: <6959E62F-6DAE-4075-A621-C24EA3818208@simonszu.de> Hi, i have a problem with a pending moderation request. Whenever i chose one of the four options for the pending email and submit the form, the page reloads and is still showing this email as pending. I did not find anything valuable in the log files, but i executed a check_perms to see if mailman can't moderate this email because of a filesystem permission problem. I don't know where to search for the bug, so i hope, anyone around here could help me. Thank you very much in advance. Simon -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From Nicholas.Waller at unbc.ca Fri Aug 23 00:46:50 2013 From: Nicholas.Waller at unbc.ca (Nicholas Waller) Date: Thu, 22 Aug 2013 22:46:50 +0000 Subject: [Mailman-Users] Messages disappear after moderator approval Message-ID: <1038B5FDE919B5499BEF8BB67C0DD428A7FF66@PG-ADR-EXCH-12.adr.unbc.ca> We are seeing messages get dropped after passing through moderation on every one of our mailing lists. == Moderation fails when performed on a *separate* webserver == Our Mailman environment is split across two servers, front-end and back-end. The back-end server handles Postfix and the Mailman qrunners, while the front-end server hosts Apache and the Mailman CGI scripts for moderating lists. The two servers share an NFS mount between them that includes all the shared Mailman data. All normal mail flow is working correctly, but when a list moderator logs into the web frontend and approves a message, it disappears without a trace. 1. Postfix smtpd receives the incoming message over SMTP, then 2. Postfix smtpd delivers the message to /usr/lib/mailman/mail/mailman. 3. Mailman marks writes to vette logfile (backend server) that message is held for approval. 4. List moderator uses CGI web interface to mark the message as approved. 5. Mailman writes an entry to vette logfile (on frontend server) saying held message approved. 6. At this point, the .pck file related to the held message disappears, but nothing is delivered, and no further log entries are created. == Moderation succeeds with web interface on the main Mailman server == Although we don't normally run the Mailman web interface on the back-end server (to reduce attack surface), I got it running for testing purposes. When we use the Mailman web interface on the backend server, the message gets delivered normally and we see these log entries as expected. 1. smtp logfile updated with number of recipients and time for completion 2. post logfile updated with list name, message ID, and "success". == Background == The problem started after migrating the Mailman environment to new servers. It didn't crop up on it's own, it's most likely a result of some configuration error that we haven't caught yet. We're using: - Scientific Linux 6.3 on both servers - Python 2.6.6 on both servers - Mailman 2.1.12 installed from OS packages on both servers - selinux in Permissive mode on backend server - selinux in Enforcing mode on frontend (web) server, but no log entries with type=AVC are being recorded. Furthermore, using setenforce 0 doesn't fix the problem. I'm not sure where to look next. Is it supported to run the Mailman frontend on a different server? What are the common points of failure when running a Mailman setup this way? -- Nic Waller System Administrator Phone 250-960-5919 Office ADM 3-2078B Information Technology Services University of Northern British Columbia From stephen at xemacs.org Sun Aug 25 02:40:50 2013 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 25 Aug 2013 09:40:50 +0900 Subject: [Mailman-Users] Polling or voting on list In-Reply-To: References: Message-ID: <87vc2ueh65.fsf@uwakimon.sk.tsukuba.ac.jp> e.c. writes: > Thanks, Seun. I suspected as much. The purpose of the prospective voting is > to offload all moderator functions onto the general membership in those > cases where the mailman program itself is not able mediate those functions > (e.g. having owners set maximum daily posting limits per member and for the > whole list). This may not give you the results you hope for in the context of a mailing list. It's commonly seen on web forums, in the form of +/- buttons on comments so that spammy or off-topic ones can be moderated out of sight. However for this to reflect general opinion of the subscribers on a mailing list, you would need to quarantine the message, then wait for a quorum to vote. This is disruptive of message flow, at the very least, and would likely introduce (new) biases in the posts, due to the fact that lurkers are different from (volunteer) moderators are more or less different from posters. If you want to experiment, it would be an interesting experiment. But if you want to preserve the spirit of the list while lessening the burden on administrators (specifically moderators), I would suggest converting to a web forum. There is a third possibility, which is to wait for Mailman 3 and see what comes up. Mailman 3 itself is going to be basically the same as Mailman 2 in terms of post distribution and moderation. However, instead of bundling Pipermail, which by today's standards isn't even a bare-bones archive manager (no search function), the recommended archive manager is HyperKitty. HyperKitty is very much "in progress," but already has some social networking/web forum-like features. Good luck with your experiment! Steve From her at adm.ku.dk Tue Aug 27 11:00:48 2013 From: her at adm.ku.dk (Henrik Rasmussen) Date: Tue, 27 Aug 2013 09:00:48 +0000 Subject: [Mailman-Users] Changing "Send questions and comments" mail-address without changing MAILMAN_OWNER Message-ID: <6DCC3E5DA06FE346B4DE4876C4F2713D7FDA5B96@P2KITMBX08WC04.unicph.domain> I am running a Mailman version 2.1.5 installation. I need to change the e-mail address that users are requested to send questions and comments to (messages/uk/LC_MESSAGES/mailman.po: msgid "

(Send questions and comments to " I still need other mails like non-handled bounces to be sent to the original MAILMAN_OWNER site admin address mailman at my-server.example.com Is there a better way to achieve this than to change the line 280 in the Mailman/Cgi/admin.py file? * Line 280: Link('mailto:%s' % mailman_owner, mailman_owner) Henrik Rasmussen From kremels at kreme.com Wed Aug 28 07:15:35 2013 From: kremels at kreme.com (LuKreme) Date: Tue, 27 Aug 2013 23:15:35 -0600 Subject: [Mailman-Users] Syntax Error on setup.py install (30.b3) Message-ID: <984ADF6A-1854-41CE-9F58-020991CC8AD8@kreme.com> $ python -V Python 2.7.5 $ python bootstrap.py Downloading http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11-py2.7.egg Traceback (most recent call last): File "bootstrap.py", line 254, in ws.require(requirement) File "/tmp/tmpZegqnz/setuptools-0.6c11-py2.7.egg/pkg_resources.py", line 666, in require File "/tmp/tmpZegqnz/setuptools-0.6c11-py2.7.egg/pkg_resources.py", line 565, in resolve pkg_resources.DistributionNotFound: zc.buildout==2.2.0 So I tried: $ python setup.py build $ python setup.py install .... Installed /usr/local/lib/python2.7/site-packages/decorator-3.4.0-py2.7.egg Searching for lazr.delegates Reading http://pypi.python.org/simple/lazr.delegates/ Reading https://launchpad.net/lazr.delegates Reading https://launchpad.net/lazr.delegates/+download Best match: lazr.delegates 2.0 Downloading https://pypi.python.org/packages/source/l/lazr.delegates/lazr.delegates-2.0.tar.gz#md5=eb696d20b284cc41e45b0d8cb8d21f0f Processing lazr.delegates-2.0.tar.gz Writing /tmp/easy_install-ogw7Xe/lazr.delegates-2.0/setup.cfg Running lazr.delegates-2.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-ogw7Xe/lazr.delegates-2.0/egg-dist-tmp-ssyQhM File "build/bdist.freebsd-9.1-RELEASE-i386/egg/lazr/delegates/_python3.py", line 27 def delegate_to(*interfaces, context='context'): ^ SyntaxError: invalid syntax File "/usr/local/lib/python2.7/site-packages/lazr.delegates-2.0-py2.7.egg/lazr/delegates/_python3.py", line 27 def delegate_to(*interfaces, context='context'): ^ SyntaxError: invalid syntax Adding lazr.delegates 2.0 to easy-install.pth file Installed /usr/local/lib/python2.7/site-packages/lazr.delegates-2.0-py2.7.egg Finished processing dependencies for mailman==3.0.0b3 Should I be worried? Is there an Install document somewhere I missed? -- Live long enough to become a problem to your kids.