Mailman 3 August 2013 - Mailman-Users

Re: [Mailman-Users] About PostLimit.py again ( was :To restrict sending email messages per day)
by e.c. Aug. 10, 2013

Aug. 10, 2013

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 <mark(a)msapiro.net> wrote: > Mark Sapiro wrote: > > > See <http://www.msapiro.net/scripts/PostLimit.py> (mirrored at > > <http://fog.ccsf.cc.ca.us/~msapiro/scripts/PostLimit.py>)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 <http://wiki.list.org/x/V4Hz> with > this information. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

2 1

Help with Reverse-Proxy Integration
by Thomas Murgan Aug. 7, 2013

Aug. 7, 2013

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

2 2

HTML formatting and Header/Footer
by Roger Richmond Aug. 6, 2013

Aug. 6, 2013

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

3 3

scripts and blog about virtual Mailman / Mailmen
by Daniel Pocock Aug. 5, 2013

Aug. 5, 2013

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

1 0

mailman group errors after updating postfix
by LuKreme Aug. 3, 2013

Aug. 3, 2013

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

1 0

creating hidden field to stop bot spam subscription request
by The League CA Cities Aug. 2, 2013

Aug. 2, 2013

Hello some of my list are being spammed with bot subscription request. I am looking for a way to add a hidden field to the subscription page of each list that a bot would see but a human user will not. I would like to have Mailman automatically drop any subscription request that has the hidden field fill out. below is the subscription area for the list and I have added the subject field. the subject field is what i would like to hide and have drop the request. Subscribe-Box> </TD> <TD WIDTH="12%"> </TD></TR> <tr> <td bgcolor="#dddddd" width="55%">Your name & City/Company (required):</td> <td width="33%"><mm-fullname-box></td> <TD WIDTH="12%"> </TD></TR> <TR> <td bgcolor="#dddddd" width="55%">Subject (required):</td> <td width="33%"><mm-fullname-box></td> <TD WIDTH="12%"> </TD></TR> <TR> I am new to HTML and this is as far as i can get at the moment. If anyone has any suggestions I would greatly appreciate it. I am running Mailman on a Linux server. Thank you Doug

5 8

Integrate mailman and postfix
by Tian Zhiying Aug. 1, 2013

Aug. 1, 2013

Hi I want integrate mailman and postfix, postfix can already work properly. Now I have a question: I create a maillist : it(a)domain.com When I send mail from a user(tian(a)domain.com) to it(a)domain.com, received a bounce: it(a)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

1 0