Mailman-Users July 2020

mailman-users@python.org

23 participants
19 discussions

identify why a message from a particular user is being discarded

by Bryan Teague

Hello, I’m running an older version of the Mailman software (2.1.15), currently. This morning, a mailing list owner reported that they had a user that could not send an email to the mailing list. When I looked in the logs, I saw the email come in, and then be discarded according to vette log. This user has been able to post to the mailing list in the past. I have reviewed the settings for the mailing list and can not determine why the message is being discarded. Is there anything I can do to get additional insight into this discard issue? Thanks, Bryan Bryan Teague Senior Web Administrator, Library and Web Services Information Technology Services Maher Hall 196 5998 Alcalá Park San Diego, CA 92110-2492 Work: 619.260.7842 Cell: 619.321.7288 bryant(a)sandiego.edu <mailto:bryant@sandiego.edu>

8 months, 3 weeks

experimental mailman3 gpg wkd support for service mails

by Ludwig Reiter

Hello! I'm working on gpg/wkd support for mailman 3. The repository is: https://gitlab.com/reiterl/mailman3-gpg-wkd.git The code sign and encrypt service mails and is experimental. I tested it with mailman 3, python 3.7 and gpgme 1.12.0. Published it here, because someone with interest in signed and encrypted mails with gpgme and wkd can look at it. Kind Regards, Ludwig -- Intevation GmbH, Osnabrück Firmensitz: Neuer Graben 17, 49074 Osnabrück Registereintrag: Amtsgericht Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

8 months, 3 weeks

Compiling mailaman-2.1.x against python3.x

by Odhiambo Washington

Hi, I am trying to manually compile mailman-2.1.34 against python3.x on FreeBSD-12.1 because python2.7 is being EoLed on the platform. I am getting these errors which I need help with: root@gw:/home/wash/Tools/Mailman/2.1.29/mailman-2.1.34 # ln -fs /usr/local/bin/python3.6 /usr/local/bin/python root@gw:/home/wash/Tools/Mailman/2.1.29/mailman-2.1.34 # ./configure --with-cgi-gid=80 --with-mail-gid=26 checking for --with-python... no checking for python... /usr/local/bin/python checking Python interpreter... /usr/local/bin/python checking Python version... 3.6.11 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... /usr/bin/true checking for --without-gcc... no checking for gcc... no checking for cc... cc 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 cc accepts -g... yes checking for cc 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 ^[^#] :-)

8 months, 3 weeks

problem with locale settings and command line interface

by mailman＠werner.by

Hi, I've mailing lists with some members using non ASCII characters in there names, like "Franz Müller <fmueller(a)example.com>". Mailman 2.1.29 is installed. When I run "list_members -f mylist" I get question marks in the output. My locale settings: LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= What can I do to get the names in UTF-8? Thanks Torsten

9 months

experimental mailman 2.1 gpg/wkd support

by Ludwig Reiter

Hello! I'm working on gpg/wkd support for mailman 2.1. The repository is: https://gitlab.com/reiterl/mailman2-gpg-wkd.git The code sign and encrypt service mails and is experimental. I tested it with mailman 2.1.32, python 2.7 and gpgme 1.12.0. I published it here, because someone with interest in signed and encrypted mails with gpgme and wkd can have a look at it. Kind Regards, Ludwig -- Intevation GmbH, Osnabrück Firmensitz: Neuer Graben 17, 49074 Osnabrück Registereintrag: Amtsgericht Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

9 months

Mailman2 - separator lines for headers and footers

by vince＠vheuser.com

I added a header temporarily, then deleted it. Now I have lines separating the sections for header and footer but nothing in those areas. Search the manual. Not finding it. Is there any way to turn off the lines between the body of the message and header/footer? Thanks! ~Vince

9 months

(core) features in MM2.1 not available in MM3

by Brett Delmage

Is there a reliable and comprehensive list of features (some which I consider fundamental and core) implemented in MM2.1 which are not yet, or never will be implemented in MM3? I've see messages here which give me concern about fundamental operations which would unexpectedly break in MM3. I'v considered migrating to MM3 but it feels like there are a lot of hidden gotchas. Thanks. Brett

9 months

Mailman 2.1.34 released

by Mark Sapiro

I am pleased to announce the release of Mailman 2.1.34. This is a minor bug fix release and has updates to the Spanish i18n. See the attached README.txt for details. As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1 branch from the GNU Mailman project. There has been some discussion as to what this means. It means there will be no more releases from the GNU Mailman project containing any new features. There may be future patch releases to address the following: i18n updates. security issues. bugs affecting operation for which no satisfactory workaround exists. Mailman 2.1.34 is the fourth such patch release. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.34 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

One list subscribed to another fails to deliver email

by Philip Colmer

We have a number of "source" lists, e.g. listA, listB and listC. Each of them has listZ as a member, with the intention that all posts to A, B and C get replicated to Z. This all works until it gets to the point where posts to Z get emailed out to the members of Z. This is currently failing because the gateway mail system we are using is reporting "Duplicate header 'Delivered-To'". Is there a setting or mechanism I can set in Mailman 2.1 that strips the duplicate header or does anyone have any other suggestions on how to resolve this? Thanks. Philip

9 months, 1 week