Mailman 3 July 2015 - Mailman-Users

Disabling the digest feature
by MLA 20 Jul '15

20 Jul '15

I have a low volume mailing list and would like to remove the digest option, so what I've done is (via the Mailman administrative interface): - in "Membership management"-"Membership list": disabled "Digest" from those members who had this enabled - in "Digest option": set Edit_digest to NO to disable the digest feature entirely - posted a message to the list to tell about the change and that current digest-receiving members have had their subscriptions changed to non-digest. This is all I have to do, right? But for testing purposes I subscribed to the list with a new address and noticed that in my user's administration page ("options" section) there's a choice for "set digest mode" for on/off. How can I remove this and any other trace of the digest option which I might have missed? Thanks. M.

2 3

newsgroup->mailman moderation
by Danil Smirnov 20 Jul '15

20 Jul '15

Hi Mark! I've found your posting advising how to set all posts from Usenet group to moderation: https://mail.python.org/pipermail/mailman-users/2013-June/075346.html When look into Moderate.py I've found another code than mentioned in the post: --- # Okay, so the sender wasn't specified explicitly by any of the non-member # moderation configuration variables. Handle by way of generic non-member # action. assert 0 <= mlist.generic_nonmember_action <= 4 if mlist.generic_nonmember_action == 0 or msgdata.get('fromusenet'): # Accept return elif mlist.generic_nonmember_action == 1: Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost) elif mlist.generic_nonmember_action == 2: do_reject(mlist) elif mlist.generic_nonmember_action == 3: do_discard(mlist, msg) --- Is it correct to change the code in this way? --- # Okay, so the sender wasn't specified explicitly by any of the non-member # moderation configuration variables. Handle by way of generic non-member # action. assert 0 <= mlist.generic_nonmember_action <= 4 if mlist.generic_nonmember_action == 0: # Accept return elif mlist.generic_nonmember_action == 1 or msgdata.get('fromusenet'): Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost) elif mlist.generic_nonmember_action == 2: do_reject(mlist) elif mlist.generic_nonmember_action == 3: do_discard(mlist, msg) --- TIA, Danil

2 12

MM doesn't really forward me the full message
by Skip Montanaro 18 Jul '15

18 Jul '15

Sometimes when I see a bit of held spam, I ask Mailman to forward it to me with the intention of pumping it into SpamBayes for training purposes. (This is on mail.python.org, where we are running 2.1.something.) Unfortunately, it doesn't properly forward the entire message to me. It's one of those crappy forwards like you get from Gmail, where the message body and three or four user-visible headers are embedded in the message: Am I missing something? Is MM the culprit here or Gmail? Is there some way to get MM to forward me the complete message (including all headers) as an attachment? Thx, Skip Montanaro

2 1

Expiring mailing lists
by Gretchen R Beck 17 Jul '15

17 Jul '15

I noticed that a couple of sites lists include expiration dates for their mailman lists. I'm interested in using such a feature on my site; is there a particular version where this is available, or is it customized site-by-site? Any pointers to information on implementation? [Also, if this is the wrong list to ask this question, please point me to the right one] Thanks! Gretchen Beck Carnegie Mellon

2 1

Editing already created list web address
by Robert Susmilch 17 Jul '15

17 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear List, Is there a place to edit an already created list's web address. I have finally gotten the web server working, however I have created a virtualhost at lists.susmilch.com instead of www.susmilch.com. When I created an active list I used the www, and have since changed the mm_cfg.py to reflect that. New lists refer me internally to the correct addresses, but old lists keep refering to www every time I click a link. - -- Respectfully, Robert Susmilch =============== The "gobbledygook" in this email is due to this email having been "signed" with PGP (or the free GPG). If both parties (sender and receiver) had PGP key's the entire email could be encrypted (rendered secure and unreadable except by the key holders) for confidentiality and security. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIbBAEBCAAGBQJVqTh6AAoJEJvhIiLnDQ8q8oUP9iEtqmfEVZL5MjG1mbI6t7QY 4aR+sbE2OUyNpFGIU4DQl7uQkIhC3C16deokJ2QFUzlsyq2y/ybJO79IYHjejnGt qVEIfYMLMHjv5Pb9J/j83ztMbCl2zdaBiDoeclZTtyWH4seVICi6+sq4Obc+Xe4n dqjTVdHEt8N2iC0AW/WOh7DsDLw2MkIrizuYk+S0all4kZ4vGHEagNj7/h/Tyuwy Ox7smmZuzy6t276uCxzqOv0xetL6fN9YF/RTkgg5XWRyS7LSUE3wtlnVMm/N2lPZ sGYUkbyb8PpGoX7Ac5VQt2znEXDHV/QW8BvS88oSXBCfyfxkdOFLzlQPEAMgKk+1 iWnd9hid0uAq15c0nS6/CAQ+Z/ucp3BxR4CQZe45WyQFCvYdsywokX6XhV52aCPa Jne/MJDb/5mg3e/ll+6T+evwqiypzupS51FRiMehsfoOUY9Tfey5pg8tSRur3FCj Hr3aEqNb5zrNjzEiTgOsBrdzlj7D8ntKHU91gZ2CoCgBI8p8uc1pFNtsNBjYB2me uqUzWCpTDKBNbumKFROaA8IMBVJIgvLtGR6NoNKC3DJSruS4BNtgMeJltNZoPAAV krbsetdA+uYGjtLuAh/jrmtI72D1zzI//0/2TfJKz32Lb9yBsbXv1iM6Jw8bsePk ArsQLgr1quqgS3NGP7I= =rOy0 -----END PGP SIGNATURE-----

2 1

How to stop mail-bombers from abusing web subscribe page
by Daniel Miller 16 Jul '15

16 Jul '15

Hi all, We have discovered "mail bomber" programs like "boom mail" abusing the web "subscribe" feature of Mailman 2.1.15 to send hundreds of subscription confirmation messages to addresses that then complain to us and report us as spammers. Is there a canonical way to deal with this? The ones we see look like this in our web logs: 104.154.46.32 nmap.org - [29/Jun/2015:15:03:03 +0000] "GET /mailman/subscribe/announce?email=ALLCAPS.EMAIL@EXAMPLE.COM&fullname=&pw=123456789&pw-conf=123456789&language=en&digest=0&email-button=Subscribe HTTP/1.1" 504 323 "http://ugbox.club/boommail_bachdev/" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" We ended up using this config in Apache: <Location /mailman/subscribe> # Stop spammers from sending tons of GET requests to mail-bomb victims with subscription confirmations <LimitExcept POST> Deny from All </LimitExcept> # Those spammers never set referer correctly, either RewriteEngine On RewriteCond %{HTTP_HOST}@@%{HTTP_REFERER} !^([^@]*)@@https?://\1/.* RewriteRule .* [NC,F] </Location> We'd love to hear if there's a better way to do this. Dan

2 2

Mailman list mail for server loops back to myself
by Robert Susmilch 16 Jul '15

16 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello Everyone, I apologize in advance for anything I've overlooked, I'm not a postfix expert. Additionally, my wife and I are returning to school after 10 years out of the system and now have much more grabbing at our time with a little one. I am attempting to create a mailing list for a group project of my wife, and now it's a personal battle. I spent several hours last night Googling, and have tried to implement several different "solutions." I have "successfully" created a list with mailman, on CentOS 7 running on a VPS. The server was setup with ISPConfig 3. Additionally postfix is setup to run multiple virtual domains for myself and friends. I have updated the binary file locations of postmap and postalias, however genalias does not create virtual-mailman.db, though it does populate the virtual-mailman table. Postfix complains it does not find the users until I manually run postmap on that file to create the database. Additionally I cannot get the web admin pages to work, as I get a 500 error. However I've read many comments that I need to disable suexec and other options. I am running Wordpress as well as many other odds and ends and would prefer to not screw those up. My main concern is just to get the list working, webpage admin would just be icing. Here is the maillog for a "loop" Jul 10 10:55:00 server1 postfix/postfix-script[4275]: refreshing the Postfix mail system Jul 10 10:55:00 server1 postfix/master[1637]: reload -- version 2.10.1, configuration /etc/postfix Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max connection rate 3/60s for (submission:96.2.151.202) at Jul 10 10:54:39 Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max connection count 1 for (submission:96.2.151.202) at Jul 10 10:53:42 Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max message rate 3/60s for (submission:96.2.151.202) at Jul 10 10:54:40 Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max recipient rate 3/60s for (submission:96.2.151.202) at Jul 10 10:54:40 Jul 10 10:55:00 server1 postfix/anvil[3400]: statistics: max cache size 1 at Jul 10 10:53:42 Jul 10 10:55:01 server1 dovecot: imap-login: Disconnected (disconnected before auth was ready, waited 0 secs): user=<>, rip=::1, lip=::1, secured Jul 10 10:55:01 server1 postfix/postscreen[4319]: CONNECT from [127.0.0.1]:37965 to [127.0.0.1]:25 Jul 10 10:55:01 server1 postfix/postscreen[4319]: WHITELISTED [127.0.0.1]:37965 Jul 10 10:55:01 server1 dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured Jul 10 10:55:01 server1 postfix/smtpd[4324]: connect from localhost[127.0.0.1] Jul 10 10:55:01 server1 postfix/smtpd[4324]: lost connection after CONNECT from localhost[127.0.0.1] Jul 10 10:55:01 server1 postfix/smtpd[4324]: disconnect from localhost[127.0.0.1] Jul 10 10:55:15 server1 postfix/submission/smtpd[3399]: disconnect from unknown[96.2.151.202] Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: warning: hostname host-202-151-2-96-static.midco.net does not resolve to address 96.2.151.202: Name or service not known Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: connect from unknown[96.2.151.202] Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: Anonymous TLS connection established from unknown[96.2.151.202]: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: NOQUEUE: filter: RCPT from unknown[96.2.151.202]: <robert(a)rootunlimited.com>: Sender address triggers FILTER amavis:[127.0.0.1]:10026; from=<robert(a)rootunlimited.com> to=<test1(a)susmilch.com> proto=ESMTP helo=<archer.susmilch.com> Jul 10 10:55:16 server1 postfix/submission/smtpd[4534]: CE95B10269ED: client=unknown[96.2.151.202], sasl_method=PLAIN, sasl_username=robert(a)rootunlimited.com Jul 10 10:55:17 server1 postfix/cleanup[4553]: CE95B10269ED: message-id=<559FEAEF.8000202(a)rootunlimited.com> Jul 10 10:55:17 server1 postfix/qmgr[4279]: CE95B10269ED: from=<robert(a)rootunlimited.com>, sizef7, nrcpt=1 (queue active) Jul 10 10:55:17 server1 postfix/smtpd[4557]: connect from unknown[127.0.0.1] Jul 10 10:55:17 server1 postfix/smtpd[4557]: 246D610269EF: client=unknown[127.0.0.1] Jul 10 10:55:17 server1 postfix/cleanup[4553]: 246D610269EF: message-id=<559FEAEF.8000202(a)rootunlimited.com> Jul 10 10:55:17 server1 postfix/smtpd[4557]: disconnect from unknown[127.0.0.1] Jul 10 10:55:17 server1 postfix/qmgr[4279]: 246D610269EF: from=<robert(a)rootunlimited.com>, size90, nrcpt=1 (queue active) Jul 10 10:55:17 server1 amavis[23237]: (23237-16) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [96.2.151.202]:46678 [96.2.151.202] <robert(a)rootunlimited.com> -> <test1(a)server1.susmilch.com>, Queue-ID: CE95B10269ED, Message-ID: <559FEAEF.8000202(a)rootunlimited.com>, mail_id: biCr3Qlg5n88, Hits: -, size: 667, queued_as: 246D610269EF, dkim_new=mail:rootunlimited.com, 105 ms Jul 10 10:55:17 server1 postfix/smtp[4556]: CE95B10269ED: to=<test1(a)server1.susmilch.com>, orig_to=<test1(a)susmilch.com>, relay7.0.0.1[127.0.0.1]:10026, delay=0.43, delays=0.31/0.01/0/0.11, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 246D610269EF) Jul 10 10:55:17 server1 postfix/qmgr[4279]: CE95B10269ED: removed Jul 10 10:55:17 server1 postfix/smtp[4558]: 246D610269EF: to=<test1(a)server1.susmilch.com>, relay=none, delay=0.03, delays=0.01/0.02/0/0, dsn=5.4.6, status=bounced (mail for server1.susmilch.com loops back to myself) Jul 10 10:55:17 server1 postfix/cleanup[4553]: 2E25010269ED: message-id=<20150710155517.2E25010269ED(a)server1.susmilch.com> Jul 10 10:55:17 server1 postfix/bounce[4559]: 246D610269EF: sender non-delivery notification: 2E25010269ED Jul 10 10:55:17 server1 postfix/qmgr[4279]: 2E25010269ED: from=<>, size773, nrcpt=1 (queue active) Jul 10 10:55:17 server1 postfix/qmgr[4279]: 246D610269EF: removed Jul 10 10:55:17 server1 postfix/submission/smtpd[4534]: disconnect from unknown[96.2.151.202] Jul 10 10:55:17 server1 dovecot: lda(robert(a)rootunlimited.com): sieve: msgid=<20150710155517.2E25010269ED(a)server1.susmilch.com>: MAILER-DAEMON(a)server1.susmilch.com stored mail into mailbox 'INBOX' Jul 10 10:55:17 server1 postfix/pipe[4560]: 2E25010269ED: to=<robert(a)rootunlimited.com>, relay=dovecot, delay=0.11, delays=0.01/0.01/0/0.09, dsn=2.0.0, status=sent (delivered via dovecot service) Jul 10 10:55:17 server1 postfix/qmgr[4279]: 2E25010269ED: removed mm_cfg.py MAILMAN_SITE_LIST = 'mailman' DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/' DEFAULT_EMAIL_HOST = 'server1.rootunlimited.com' DEFAULT_URL_HOST = 'server1.rootunlimited.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_SERVER_LANGUAGE = 'en' DEFAULT_SEND_REMINDERS = 0 MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['susmilch.com'] POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport.sh' Output of postconf -d 2bounce_notice_recipient = postmaster access_map_defer_code = 450 access_map_reject_code = 554 address_verify_cache_cleanup_interval = 12h address_verify_default_transport = $default_transport address_verify_local_transport = $local_transport address_verify_map = btree:$data_directory/verify_cache address_verify_negative_cache = yes address_verify_negative_expire_time = 3d address_verify_negative_refresh_time = 3h address_verify_poll_count = ${stress?1}${stress:3} address_verify_poll_delay = 3s address_verify_positive_expire_time = 31d address_verify_positive_refresh_time = 7d address_verify_relay_transport = $relay_transport address_verify_relayhost = $relayhost address_verify_sender = $double_bounce_sender address_verify_sender_dependent_default_transport_maps $sender_dependent_default_transport_maps address_verify_sender_dependent_relayhost_maps $sender_dependent_relayhost_maps address_verify_sender_ttl = 0s address_verify_service_name = verify address_verify_transport_maps = $transport_maps address_verify_virtual_transport = $virtual_transport alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, nis:mail.aliases allow_mail_to_commands = alias, forward allow_mail_to_files = alias, forward allow_min_user = no allow_percent_hack = yes allow_untrusted_routing = no alternate_config_directories always_add_missing_headers = no always_bcc amavis_delivery_slot_cost = $default_delivery_slot_cost amavis_delivery_slot_discount = $default_delivery_slot_discount amavis_delivery_slot_loan = $default_delivery_slot_loan amavis_destination_concurrency_failed_cohort_limit $default_destination_concurrency_failed_cohort_limit amavis_destination_concurrency_limit $default_destination_concurrency_limit amavis_destination_concurrency_negative_feedback $default_destination_concurrency_negative_feedback amavis_destination_concurrency_positive_feedback $default_destination_concurrency_positive_feedback amavis_destination_rate_delay = $default_destination_rate_delay amavis_destination_recipient_limit = $default_destination_recipient_limi t amavis_extra_recipient_limit = $default_extra_recipient_limit amavis_initial_destination_concurrency = $initial_destination_concurrenc y amavis_minimum_delivery_slots = $default_minimum_delivery_slots amavis_recipient_limit = $default_recipient_limit amavis_recipient_refill_delay = $default_recipient_refill_delay amavis_recipient_refill_limit = $default_recipient_refill_limit anvil_rate_time_unit = 60s anvil_status_update_time = 600s append_at_myorigin = yes append_dot_mydomain = yes application_event_drain_time = 100s authorized_flush_users = static:anyone authorized_mailq_users = static:anyone authorized_submit_users = static:anyone tlsproxy_tls_key_file = $smtpd_tls_key_file tlsproxy_tls_loglevel = $smtpd_tls_loglevel tlsproxy_tls_mandatory_ciphers = $smtpd_tls_mandatory_ciphers tlsproxy_tls_mandatory_exclude_ciphers $smtpd_tls_mandatory_exclude_ciphers tlsproxy_tls_mandatory_protocols = $smtpd_tls_mandatory_protocols tlsproxy_tls_protocols = $smtpd_tls_protocols tlsproxy_tls_req_ccert = $smtpd_tls_req_ccert tlsproxy_tls_security_level = $smtpd_tls_security_level tlsproxy_tls_session_cache_timeout = $smtpd_tls_session_cache_timeout tlsproxy_use_tls = $smtpd_use_tls tlsproxy_watchdog_timeout = 10s trace_service_name = trace transport_maps transport_retry_time = 60s trigger_timeout = 10s undisclosed_recipients_header unknown_address_reject_code = 450 unknown_address_tempfail_action = $reject_tempfail_action unknown_client_reject_code = 450 unknown_helo_hostname_tempfail_action = $reject_tempfail_action unknown_hostname_reject_code = 450 unknown_local_recipient_reject_code = 550 unknown_relay_recipient_reject_code = 550 unknown_virtual_alias_reject_code = 550 unknown_virtual_mailbox_reject_code = 550 unverified_recipient_defer_code = 450 unverified_recipient_reject_code = 450 unverified_recipient_reject_reason unverified_recipient_tempfail_action = $reject_tempfail_action unverified_sender_defer_code = 450 unverified_sender_reject_code = 450 unverified_sender_reject_reason unverified_sender_tempfail_action = $reject_tempfail_action verp_delimiter_filter = -=+ virtual_alias_domains = $virtual_alias_maps virtual_alias_expansion_limit = 1000 virtual_alias_maps = $virtual_maps virtual_alias_recursion_limit = 1000 virtual_delivery_slot_cost = $default_delivery_slot_cost virtual_delivery_slot_discount = $default_delivery_slot_discount virtual_delivery_slot_loan = $default_delivery_slot_loan virtual_destination_concurrency_failed_cohort_limit $default_destination_concurrency_failed_cohort_limit virtual_destination_concurrency_limit $default_destination_concurrency_limit virtual_destination_concurrency_negative_feedback $default_destination_concurrency_negative_feedback virtual_destination_concurrency_positive_feedback $default_destination_concurrency_positive_feedback virtual_destination_rate_delay = $default_destination_rate_delay virtual_destination_recipient_limit = $default_destination_recipient_lim it virtual_extra_recipient_limit = $default_extra_recipient_limit virtual_gid_maps virtual_initial_destination_concurrency = $initial_destination_concurren cy virtual_mailbox_base virtual_mailbox_domains = $virtual_mailbox_maps virtual_mailbox_limit = 51200000 virtual_mailbox_lock = fcntl, dotlock virtual_mailbox_maps virtual_minimum_delivery_slots = $default_minimum_delivery_slots virtual_minimum_uid = 100 virtual_recipient_limit = $default_recipient_limit virtual_recipient_refill_delay = $default_recipient_refill_delay virtual_recipient_refill_limit = $default_recipient_refill_limit virtual_transport = virtual virtual_uid_maps - -- Respectfully, Robert Susmilch =======The "gobbledygook" in this email is due to this email having been "signed" with PGP (or the free GPG). If both parties (sender and receiver) had PGP key's the entire email could be encrypted (rendered secure and unreadable except by the key holders) for confidentiality and security. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVn+7gAAoJEJvhIiLnDQ8qONwP/RhgtCnxJ4TVi1tTLFZmPtBk X0KEH55jcnp5c2sFLWRh/gC3gEQS6npL0e2X2WQIRZa4dtadLu8bwYhoWrvzC3QY M2D6zO/0TN5TKHarXDCTYFks5ZcVcWkDyj3lW/MowPqDcHMCzJ2InXK95BSFef8n 8VrFMfiuv5rA7CmFkhC8VWwrKSMzJsDu3Cq+Rh0oj7enQ9l3UFn7x6sgfKlul5dp hIwa9Lhkw4JwNy9N8Np7vM25UL0Kh6Zn6kaEVUuMeDNDeKcbyD0NZswYzBi8GqWG VMJE7mTRuH93yA34IZJd2obv1PvNuq9nuR2RE3Xb0Wb/MsmdCG0Dq8DljNjGk9Wg YhKLrOk5dVRKhfc8pEkTS7FlPElcu25JTqAF04e3NP95oiFiYaBp81SM01Ebm9KX ja2oC99IBFBLEDhsx9q3fEtJ5Tu6bnAugJMBQhfkpDCoxdsPYW135RtZ3M3ClcLz DbbVACmP0cYOzxXopNmepT4NZnuz/NxM/neXSH6z2SrEd8jGpNNrsLFUvAEynYPP XMatbwPye6n4jtPRMtyB+GeW1PI+8gedWTF05FBDhU/wXuaBxBqGPFz8ujZ7fozM Wa3sAV68SU6tvnTaOwcbSgEoUktjNZbL9CEvOC9sx4rVaC/9n/BBLec/+Iftl16K WngV6F82NEBnC1DQnM6t =4SpA -----END PGP SIGNATURE-----

3 6

implicit destination error.
by Adam Morris 15 Jul '15

15 Jul '15

Hi all, is there a way to set up mailman so if people send messages to one of my lists and put the address in the cc field it is accepted instead of me as owner having to approve the message? -- Adam Morris email: adam(a)damorris.com

2 1

private and public archive directory permissions
by Noah 13 Jul '15

13 Jul '15

Hi there, I migrated to a new server and I am back again with permission issues. I am running apache2 on an ubuntu 14.04 server. is there a good tutorial out there that explains the best practices for ownership for the different directories and sub-directories I run check_perms -f as root and some of the same directories still need correcting even after running 'check_perms -f' as root many times. I have a list user and a mailman user and group that I moved over from my old server. Apache2 is running as www-data . I am using mbox is that matters. here is some config: /var/lib/mailman/archives $ ls -l total 8.0K drwxrws--x 110 mailman 4.0K Jul 4 22:44 private/ drwxrwsr-x 2 mailman 4.0K Jun 2 2012 public/ /etc/apache2/conf-enabled $ ls -l mailman.conf lrwxrwxrwx 1 root 30 Jul 13 00:52 mailman.conf -> ../conf-available/mailman.conf /etc/apache2/conf-enabled $ cat ../conf-available/mailman.conf Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/ ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ <Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Order allow,deny Allow from all </Directory> <Directory /var/lib/mailman/archives/public/> Options Indexes FollowSymlinks AllowOverride None Order allow,deny Allow from all </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Order allow,deny Allow from all </Directory> Cheers, Noah

3 9

Re: [Mailman-Users] [Mailman-Developers] Mailman 3 status
by Barry Warsaw 13 Jul '15

13 Jul '15

[resend w/proper address] On Jul 13, 2015, at 10:47 AM, Stephen J. Turnbull wrote: >- Performance measurements. There are theoretical reasons to believe > that under certain circumstances a "large" Mailman 3 under "heavy" > use *might* suffer bottlenecks, but we just don't know yet. Note that the message delivery subsystem, while modernized and ported to Python 3, is largely inherited from Mailman 2, which means that reliability and performance *of message delivery* should be about the same. Over in mailman-developers we've had some discussion about performance of the REST server, which by default gets vended by Python 3's stdlib wsgiref module and probably would be improved by a better wsgi application server such as gunicorn. Follow ups to -developers on that topic please. >The information provided above is accurate to the best of my ability, >but it has not been checked by the responsible developers. It is >provided in hope of may be of use to those considering installation of >Mailman 3. If you're still on the fence after reading this post, >please do get more accurate information from the responsible >developers on the Mailman Developers list. You did good, Steve! :) Cheers, -Barry

2 1