Mailman 3 January 2019 - Mailman-Users

Install mailman-2.1.z with python3.6
by Odhiambo Washington Jan. 7, 2019

Jan. 7, 2019

I need to install Mailman2.1 using python3.x, but I have had some problem. On my Ubuntu-18.04 server, I have both python2.7 and python3.6. Now, everything is all fine with python2.7, but when I use python3.6, it bombs out: root@lists:/home/wash/Mailman/2.1.29/mailman-2.1.29# ./configure --with-cgi-gid=33 --with-mail-gid=117 --with-python=/usr/bin/python3.6 checking for --with-python... /usr/bin/python3.6 checking Python interpreter... /usr/bin/python3.6 checking Python version... 3.6.7 checking dnspython... ok checking Python's email package... Traceback (most recent call last): File "conftest.py", line 8, in <module> version = tuple(int(v) for v in email.__version__.split('.')) AttributeError: module 'email' has no attribute '__version__' cat: conftest.out: No such file or directory checking Japanese codecs... Traceback (most recent call last): File "conftest.py", line 2, in <module> unicode('OK', 'iso-2022-jp') NameError: name 'unicode' is not defined cat: conftest.out: No such file or directory checking Korean codecs... Traceback (most recent call last): File "conftest.py", line 2, in <module> unicode('OK', 'euc-kr') NameError: name 'unicode' is not defined cat: conftest.out: No such file or directory checking that Python has a working distutils... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether make sets $(MAKE)... yes checking for true... /bin/true checking for --without-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether #! works in shell scripts... yes checking for --with-var-prefix... no checking for --with-permcheck... yes checking for --with-username... mailman checking for user name "mailman"... okay checking for --with-groupname... mailman checking for group name "mailman"... okay checking permissions on /usr/local/mailman... File "conftest.py", line 17 if mailmangid <> gid: ^ SyntaxError: invalid syntax cat: conftest.out: No such file or directory configure: error: ***** Installation directory /usr/local/mailman is not configured properly! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

3 3

mm-handler same as postfix-to-mailman.py
by Jim Ziobro Jan. 7, 2019

Jan. 7, 2019

Mm-handler works well when mail-lists are in a separate domain. I ran across postfix-to-mailman.py while researching mailman to postfix connections. I realized it performs the same function as mm-handler. I changed mm-handler to be a drop in as a replacement for postfix-to-mailman.py <https://github.com/fauria/docker-mailman/blob/master/centos7/postfix-to-mai…>. It is under: http://sw.ziobro.info/mm-handler/ I did a test install of mailman with Postfix to test it. It worked. I also setup a Mailman to Postfix connection using the aliases method as described in the documentation. That worked fine also. I don't use Postfix but using the postfix-to-mailman.py seemed a little more obvious than setting up through the aliases method. The Postfix package on CentOS 7 even had comments where the mailman transport entry would go. Configuring is especially tough if you are not familiar with Python. :-) Setting up mailing lists in a separate domain has a nice administrative appeal. I did a little more research to see how popular that method might be. I got a list of 1922 US universities and 457 have a host "lists...." and 191 have a host "list..." in their DNS. I surveyed a few and ran across: Mailman, Lyris, Sympa, Listserv, Majordomo, and Google groups. Many universities outsource their Email to Outlook which has it own Group capability. Running mail list software is clearly popular. Both mm-handler and postfix-to-mailman.py are contributed code. The folks who package the various tools add glue to make them easy to use. It looks like both Sympa <https://sympa-community.github.io/manual/>and Mailman have very similar requirements. Maybe time to work together? I can hook up any mail system. Just give me the list of mail-lists and tell me how to inject messages. Glue will be more specific to a Mailer and OS than either Mailman or Sympa. I think we get a benefit if we make a clean interface between Mailman and its feeding MTA. We can then eliminate some of the hacks like mm-handler. I have some ideas for Mailman2. I'll follow up. Ciao, //Z\\ Jim Ziobro

4 4

admindb pages redirect to localhost
by David Newman Jan. 5, 2019

Jan. 5, 2019

FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1, nginx-1.14.2_3,2 Greetings. Could use help understanding two issues after migrating from Apache to nginx: 1. All Mailman web pages load as expect except links from the admindb page (for pending moderator request), which redirect to localhost. For example, for the admindb page for the list networktest-announce on the host lists.networktest.com, the link for "Click here to reload this page" goes here: https://localhost/mailman/admindb/networktest-announce Similar localhost links appear in admin emails about pending moderator requests. I've pasted below snippets from mm_cfg.py and the Nginx config -- please let me know if you need other info. I suspect the issue may be a lack of an Nginx location for admindb, but I'm not sure how to address that. 2. Also on the admindb page, clicking the submit button to tend to pending requests triggers a warning in Firefox that the info is about to be submitted insecurely, even though the admindb URL begins with https:// - how to fix this? Thanks in advance for troubleshooting clues on both points. dn mm_cfg.py mods: ################################################## # Put YOUR site-specific settings below this line. MTA = 'Postfix' DEFAULT_URL_PATTERN = 'https://%s/mailman/' PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' PRIVATE_ARCHIVE_URL = '/mailman/private' # Clear the Defaults.py VIRTUAL_HOSTS entry # VIRTUAL_HOSTS.clear() # other vhosts omitted from following line POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'lists.networktest.com' ] # other vhosts omitted after following line add_virtualhost('lists.networktest.com','lists.networktest.com') DEB_LISTMASTER = 'postmaster(a)networktest.com' ALLOW_FROM_IS_LIST = Yes ----- lists.networktest.com.conf in Nginx: root@mail8:/usr/local/etc/nginx/vhosts # cat lists.networktest.com.conf server { listen 80; server_name lists.networktest.com; # Lets encrypt location ^~ /.well-known/acme-challenge/ { alias /usr/local/www/.well-known/acme-challenge/; } # Redirect other HTTP connections to HTTPS location / { return 301 https://$server_name$request_uri; } access_log /var/log/lists.networktest.com.access.log; error_log /var/log/lists.networktest.com.error.log; } server { listen 443; server_name lists.networktest.com; access_log /var/log/lists.networktest.com.access.log; error_log /var/log/lists.networktest.com.error.log; ssl on; ssl_certificate /etc/ssl/certs/lists.networktest.com.pem; ssl_certificate_key /etc/ssl/priv/lists.networktest.com.key; ssl_session_timeout 5m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on; root /usr/local/mailman/cgi-bin; location = / { rewrite ^ /mailman/listinfo permanent; } location / { rewrite ^ /mailman$uri; } location ~ ^/mailman(/[^/]*)(/.*)?$ { fastcgi_split_path_info (^/mailman/[^/]*)(.*)$; include fastcgi_params; fastcgi_param GATEWAY_INTERFACE CGI/1.1; fastcgi_param SCRIPT_FILENAME $document_root$1; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_param PATH_TRANSLATED $document_root$2; fastcgi_pass unix:/var/run/fcgiwrap/fcgiwrap.sock; } location /images/mailman { alias /usr/local/mailman/icons; } location /icons { alias /usr/local/mailman/icons; } location /pipermail { alias /usr/local/mailman/archives/public; autoindex on; } }

2 5

question on bounce processing
by Ricardo Kleemann Jan. 4, 2019

Jan. 4, 2019

Hi, Where should I look at for trying to figure out why particular members are being dropped off? I have members receiving the excessive bounce messages but I'm not finding much in the mail log relative to excessive bounces for the email address (I'm probably not looking for the correct bounce lines in the log) I'm running Mailman 2.1.26 on Ubuntu 18.04 and postfix thanks Ricardo

2 3

Changing the mailman access url
by Odhiambo Washington Jan. 3, 2019

Jan. 3, 2019

I have manually installed mailman and moved the files. This is on the same server. Now my problem is the urls: I have http://FQDN/cgi-bin/mailman/admin/LISTNAME which I would like to change to http://FQDN/mailman/admin/skunkworks - ideally, just eliminating the /cgi-bin/ bit. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

3 2

'Warm up' an IP when moving a mailing list server to a new host?
by David Gibbs Jan. 2, 2019

Jan. 2, 2019

Folks: This isn't specific to Mailman ... but is related to mailing list servers in general. I've had my mailing lists on an in-house server for a long time (more than 15 years). I'm currently able to deliver mail to Yahoo without any problems. I've been trying to move the mailing list server to an Amazon VPS ... and, of course, this means that the IP that I'm sending from is changing. Unfortunately, Yahoo has started deferring mail delivery because the new IP doesn't have a reputation (although it's not on any black lists that I'm aware of). The Yahoo postmaster support people are telling me that I should 'warm up' the IP by sending some mail to Yahoo from the new IP and continue to send from the old IP. Any suggestions on how that might be accomplished? The only thing I can think of is to move a few of my lists over to the new, do some apache contortion to proxy requests for the moved lists to the new host, and other rsync stuff to keep my archives in sync. Yahoo is a major PITA. david -- IBM i on Power Systems: For when you can't afford to be out of business! I'm riding 615 miles (Yes, you read that right) in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax-deductible donation to my ride by visiting https://gmane.diabetessucks.net. You can see where my donations come from by visiting my interactive donation map ... https://gmane.diabetessucks.net/map (it's a geeky thing). I may have diabetes, but diabetes doesn't have me!

1 0