Mailman-Users June 2020

mailman-users@python.org

31 participants
31 discussions

DNSException: Unable to query DMARC policy
by Johannes Rohr 21 Jun '20

21 Jun '20

Dear all, lately my mailman instance has applied the DMARC workarounds an increasing number of mails. Looking into /var/log/mailman/error, I see a large number of messages containing the string "DNSException: Unable to query DMARC policy for [address]: connection timed out". We are running Ubuntu 18.04 LTS, the current mailman version is from 2018. Except from installing the occasional security updates, I don't see what has changed, that might be responsible for these timeouts. What command does mailman use to query for the DMARC status of an address? Cheers, thanks a lot for any hint... Johannes

3 3

Re: searchable private mailing lists in Mailman 2.1.20
by Carl Zwanzig 20 Jun '20

20 Jun '20

Please keep this on-list On 6/18/2020 12:23 PM, Anatoly Oreshkin wrote: > My private list archives are local files and directories. Mnogosearch can > search my list archives but > how to integrate Mailman and Mnogosearch ? > I need a mnogosearch search string to be on Mailman archive TOC page I think those pages are generated by code in ./mailman/Mailman/Archiver, but you'll have to look for where the archive index.html page is generated and add the HTML code for the search. I can not help with that. > I choose Mnogosearch because of its ability to support russian character > encoding OK, any decent search engine should support UTF, which will pretty much include all encodings. z!

5 6

Setting a moderator password
by Bernie Cosell 20 Jun '20

20 Jun '20

I'm trying to set a moderator password for my list and I seem to be doing something wrong: I went into "Passwords" entered the moderator password both times and 'submitted' it and I get "Authorization failed" when I tried to use it. What did I forget to do? Do moderators log in on a different login screen than the normal one or something? Note that I don't need a "moderator" email address [we're preparing for moderators in emergency moderation] but I added one anyway and it didn't help /Bernie\ Bernie Cosell bernie(a)fantasyfarm.com -- Too many people; too few sheep --

4 3

error installing Mailman 2.1.12
by Anatoly Oreshkin 19 Jun '20

19 Jun '20

I'm trying to install Mailman 2.1.12 on Centos 7.7. I've done the following steps 1. tar zxvf mailman-2.1.12.tgz 2. applied patches cd mailman-2.1.12 patch -p1 < ../indexing-2.1.12-0.1.patch patch -p1 < ../htdig-2.1.12-0.1.patch patch -p1 < ../exitstatus-2.1.12-0.1.patch patch -p1 < ../modinc-2.1.12-0.1.patch patch -p1 < ../mhonarc-2.1.12-0.1.patch 3. ./configure --prefix=/usr/local/mailman --with-var-prefix=/var/mailman \ --with-mail-gid=mail --with-cgi-gid=apache make make install On this step, make install, I've received a lot of warnings like these: src/_koco_ksc5601.h:3337:3: warning: (near initialization for ‘ksc5601_encode_page3[11104]’) [-Wpointer-sign] src/_koco_ksc5601.h:3337:3: warning: pointer targets in initialization differ in signedness [-Wpointer-sign] src/_koco_ksc5601.h:3337:3: warning: (near initialization for ‘ksc5601_encode_page3[11109]’) [-Wpointer-sign] src/_koco_ksc5601.h:3338:3: warning: pointer targets in initialization differ in signedness [-Wpointer-sign] "\xf8\xf9", 0, 0, 0, 0, "\xf0\xae", 0, 0, ^ src/_koco_ksc5601.h:3338:3: warning: (near initialization for ‘ksc5601_encode_page3[11112]’) [-Wpointer-sign] src/_koco_ksc5601.h:3338:3: warning: pointer targets in initialization differ in signedness [-Wpointer-sign] src/_koco_ksc5601.h:3338:3: warning: (near initialization for ‘ksc5601_encode_page3[11117]’) [-Wpointer-sign] src/_koco_ksc5601.h:3340:3: warning: pointer targets in initialization differ in signedness [-Wpointer-sign] 0, 0, "\xd1\xb8", 0, 0, 0, 0, "\xd6\xdf", ^ ......... Listing /usr/local/mailman/Mailman/Queue ... Compiling /usr/local/mailman/Mailman/Queue/ArchRunner.py ... Compiling /usr/local/mailman/Mailman/Queue/BounceRunner.py ... Compiling /usr/local/mailman/Mailman/Queue/CommandRunner.py ... Compiling /usr/local/mailman/Mailman/Queue/IncomingRunner.py ... .... Compiling /usr/local/mailman/Mailman/versions.py ... Downgrade detected, from version 0x20114f0 to version 0x2010cf0 This is probably not safe. Exiting. make: *** [update] Error 1 What is the cause of these errors ? How to solve this problem ? Thanks.

3 2

searchable private mailing lists in Mailman 2.1.20
by Anatoly Oreshkin 18 Jun '20

18 Jun '20

Hello, I've installed Mailman 2.1.20 on my server. I would like to have the possibility to search private mailing lists. As mailing lists contain russian letters so I need as a search tool Mnogosearch search engine. How to include Mnogosearch in Mailman 2.1.20 ? Has anybody done this task ? Or has the information how to do this task ? Thanks.

3 2

Scrubber: filename too long
by tlhackque 18 Jun '20

18 Jun '20

From /usr/lib/mailman/cron/senddigests, I'm seeing this - which is the result of an annoying webbug URL in some (actually important) inbound messages. I guess one approach would be for the filename name to be simply the sha-xxx of the generated name...not being a Python person, what's the best way to solve this? Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 94, in ? main() File "/usr/lib/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 301, in process url = save_attachment(mlist, part, dir) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 506, in save_attachment fp = open(path, 'w') IOError: [Errno 36] File name too long: '/var/lib/mailman/archives/private/sb-notices/attachments/20200617/7bfd746c/openupnuTyAIB5RnlGqcUYpxASzOCjK0U2XEEfdN09lb80k8EAccOT3iskue1a45bqJenPWT4XeDAj9c-2FnJ-2F1UfxwtikwjXfVn4FKSvPvMQ4-2F-2BnoeZraMSMf1dLwio-2FiUT1wYNZx4eF1A5j8DF1-2FMAhxu72-2BX1pzdJx1CWDywpoyPVWKwluqE4AyFhrreaxc8kYpHZaUFUlP3MPFmNEDQ5Tr-2Bg-2BJRAhSYLdif3kj8rKn-2FDEhbw-3D.gif'

2 1

One mailing list is unable to receive mail from user.
by Masaharu Kawada 18 Jun '20

18 Jun '20

Dear list, One mailman mailing list can not receive mail from user and /var/log/mailman/vette shows "Message discarded," as follows. ---/var/log/mailman/vette: Jun 04 14:17:37 2020 (1238) Message discarded, msgid: < TY2PR01MB4779856244XXXXXXXXXXXXXXX(a)TY2PR01MB4779.xxx.xxx.com> The failed mail shows an 'x-beenthere' header in it like below. errors-to: xxxx(a)yyyylist.co.jp list-id: <xxxx.yyyylist.co.jp> x-beenthere: xxxx(a)yyyylist.co.jp <---This is the mailing list where mail from user can not be sent. The 'x-beenthere' header looks to be the reason why the problematic mailing list fails to receive mail from user, but I have no idea in what kind of situation we get 'x-beenthere' header in mail. Does anyone in the list have any idea to describe why the mailing list is unavailable to receive mail and what makes us get an 'x-beenthere' header? Thanks, Masaharu

2 2

Mailman 2.1.12 and issues with TLS 1.2 and DMARC
by Jonathan Ashby 16 Jun '20

16 Jun '20

Hello I wonder if you can help. My organisation represents and supports GPs across most of London. We have elected representatives and we use Mailman mailing lists to provide listservers to elected representatives. We currently use version 2.1.12 (http://lists.lmc.org.uk/mailman/admin) but I am aware of changes with TLS and DMARC are starting to effect our messages to listserver members. An example is doctors.org email addresses do not accept our listserver messages because the DMARC settings in their systems sees the ‘sender’ is sending mail out purporting to be from the email address of the person posting the entry on the listserver, which they regard as spoofing. We send emails to NHS mail addresses which currently reach their destination but I am aware that NHS mail is going to move to Exchange Online next month. I am looking at ways to future proof our listservers as they are such an important part of our communication strategy. Are you able to assist in providing me with guidance on the steps I should be taking? Many thanks in advance. Best wishes. Jonathan Jonathan Ashby Head of Communications and ICT Londonwide LMCs and Londonwide Enterprise Ltd Direct dial: 020 3818 6228 Mobile: 07768 109601 Fax: 020 7383 7442 Email: jonathan.ashby(a)lmc.org.uk<mailto:jonathan.ashby@lmc.org.uk> Web: www.lmc.org.uk<http://www.lmc.org.uk/> Twitter: @LondonwideLMCs<http://www.twitter.com/LondonwideLMCs> ---------------------------- Visit www.lmc.org.uk/coronavirus-covid-19<http://www.lmc.org.uk/coronavirus-covid-19> for the latest official resources and guidance on covid-19. Remember that you can use WhatsApp and FaceTime for online consultations as well as the usual online tools. Think of the environment - do you really need to print this email? This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please accept our apologies and notify the sender. The registered and office address for Londonwide Local Medical Committees Limited is: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No: 6391298. Londonwide Enterprise Limited is a wholly owned subsidiary of Londonwide Local Medical Committees Limited. Londonwide Enterprise Limited is registered at: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No. 6990874. Londonwide Enterprise Limited is registered as a Company Limited by Shares. VAT no: 130 1454 66. Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited do not provide legal or financial advice and thereby excludes all liability howsoever arising in circumstances where any individual, person or entity has suffered any loss or damage arising from the use of information provided by Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited in circumstances where professional legal or financial advice ought reasonably to have been obtained. Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited provide guidance and support to GPs and practice teams in the Londonwide area. Additionally Londonwide Local Medical Committees Limited provides representation to GPs and practice teams in the Londonwide area. Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited strongly advises individuals or practices to obtain independent legal or financial advice. ---------------------------- ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________

2 1

Mailman3 installation for large organization
by Waqas Ahmed Khan 16 Jun '20

16 Jun '20

Hi, I have been given the task to install Mailman3 for a large organization, where the list will send emails to 80-100K users. I have the following questions: 1. How to do the hardware sizing and what should be hardware/VM configuration? 2. Should we install an email server ( Postfix) on the same server? 3. Can we use an external SMTP server like GMAIL/Office365 to route emails, is there any guide to configuring this? 4. How to avoid blacklisting of mailing list IPs? Regards, *Waqas Ahmed Khan* p: +923212608044 Skype: waqas-ahmed00 <waqas.ahmed0(a)gmail.com> waqas.ahmed0(a)gmail.com [image: LinkedIn] <http://pk.linkedin.com/pub/waqas-ahmed-khan/15/96a/39a/> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

Can I make mailman archive the bounce messages it has processed?
by Florian.Roemer＠gmx.de 15 Jun '20

15 Jun '20

Dear mailman Community, I am really new to mailman so maybe I am just missing something obvious. However, as far as I understood, when a message sent from a list triggers a bounce at some user, mailman will try to automatically parse the bounce, assign appropriate bounce scores and then discard the message. However, I would like to see the bounce message. The reason is that one of my subscribers complains that she does not get the messages from the list and I see her bounce score increasing, but she has no idea why the messages are bouncing. As she is not that tech savvy, I would really like to help her but for this I would need to see the bounce message to extract the reason why it is bouncing. However, I could not find any archive of the bounce messages on my server. There is a .mbox file for the list but that only contains emails sent to the list, not to the -bounce alias. Is there a way I can access the bounces messages or configure mailman to archive them? Thanks in advance!

5 7