[Mailman-Users] Charset chaos

[Johannes Rohr]

Dear all,

I am trying to understand how to fix this issue, sorry if it came up 
before. It must have, still I couldn't find a working solution through 
Google:


The default language of my server is de (German), which has several 
non-ASCII characters (umlauts & ß).


Lately the issue is that in the standard setting 
(DEFAULT_SERVER_LANGUAGE = 'de'), all the system messages are rendered 
properly, (for instance on the list overview page: "Für Administratoren 
der Listen gibt es die Seite Übersichtsseite für Listenadministratoren 
zur Verwaltung der eigenen Liste. ") but the the UTF-8 of the list 
descriptions is rendered as two-character sequences: "Diskussion 
(öffentlich)" instead of "Diskussion (Öffentlich)", the same is true 
for the footers of all messages delivered to subscribers: "Für 
Eintragung, Löschung (...)" instead öf "Für Eintragung, Löschung (...)".


Now, I tried to remedy this by adding "add_language('de', 'Deutsch', 
'utf-8', 'ltr')" to /etc/mailman/mm_cfg.py but after doing so, while the 
UTF-8 code is now rendered correctly as single characters, the 
translated system messages are now being garbled: "Unten finden Sie eine 
Aufstellung aller �ffentlichen Mailinglisten (...)"


How do I ensure that both the system messages? The .po file for de seems 
to be in latin1 (iso-8859-1), not UTF-8. Is this on purpose? The Russian 
one is in proper UTF-8, but the French and Spanish ones are also in 
Latin1. The server is on Ubuntu 20.04, running mailman 2.1.29, which 
seems to be way behind upstream.


I kind of half fixed it locally by

1. recoding the po file from latin1 to utf-8,
2. re-running msgfmt,
3. re-running dpkg-reconfigure -plow mailman and selecting the default
   language
4. adding add_language('de', 'Deutsch', 'utf-8', 'ltr') to
   /etc/mailman/mm_cfg.py
5. restarting mailman

At first glance, everything seems to be in order now, just that the main 
welcome pages both for users and administrators are now stubbornly in 
English, while everything else in German, now with proper Umlauts. Is 
this an issue with the Debian/Ubuntu package? What is the canonical way 
of dealing with it?


Thanks a lot for your advice!

Johannes
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] What does rmlist remove?

[Johannes Rohr]

Dear all,

what files are being removed by rmlist (without -a). I suppose,
/var/lib/mailman/lists/$LISTNAME/config.pck and the entries in
/var/lib/mailman/data/virtual-mailman

When I restore both, have I restored the list? Mailman2 uses no
database, so maybe the answer is yes?

Background: testing migration to mailman3, and I want to start with a
partial migration, affecting only one little used virtualhost. I thought
that deleting the lists this virtualhost from mailman2 will allow me to
play around with them in mailman3 (after making the required changes to
the postfix configuration). But if I find that mailman3 has too many
drawbacks, I would prefer to undo the changes.

Alternatively, instead of calling rmlist I could just manually remove
the lists from virtual-mailman of mailman2, although, virtual-mailman
get automatically rewritten with each list creation or deletion, but
that's rather infrequent over here)

Cheers,

Johannes


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Monthly notifications bounce, are sent without DKIM signature.

[Johannes Rohr]

Am 01.02.2021 um 17:22 schrieb Mark Sapiro:

On 2/1/21 1:58 AM, Johannes Rohr wrote:

I get a batch of bounces once a month from GMail, when mailman sends out
the monthly reminders.

When I look into the headers of those notifications, it looks like they
miss the DKIM signature, which is super weird, because the notification
about the bounce that mailman sends to the listowner has a DKIM
signature. I wonder what is going wrong there. My understanding is that
the signing is done by rspamd and that mailman doesn't have anything to
do with it. Why aren't all messages signed?


As you note, Mailman has nothing to do with DKIM signing of outgoing
mail. Your outgoing MTA does it, probably by invoking some milter. It
could be rspamd or something else. You have to look at the
configuration. If you are using rspamd's DKIM signing module, see
<https://rspamd.com/doc/modules/dkim_signing.html>.


Actually I investigated and it turned out to be a mailman issue after 
all, at least partially: Namely that the monthly notification is send 
out by the DEFAULT_EMAIL_HOST regardless of the urlhost of the 
respective list. Is this because internally these are mails to the site 
wide mailman mailing list?


There was no DKIM key for the DEFAULT_EMAIL_HOST (which I have changed 
now) but the only time this had an effect for me was once a month, when 
mailman sends out the reminders.


Thanks for your continued great support!

Johannes

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Daily "pending moderator requests" despite empty moderation queue

[Johannes Rohr]

Sorry, found the answer, it is in the FAQ:

https://wiki.list.org/DOC/I%20receive%20a%20daily%20%22n%20LISTNAME%20moderator%20request%28s%29%20waiting%22%20email%2C%20but%20there%20are%20no%20requests.%20Unsubscribed%20users%20get%20pas

I indeed had cloned this mailman instance for testing purpuses and 
presumably the cloned instance sent out the messages.


Johannes


Am 18.02.2021 um 09:28 schrieb Johannes Rohr:

Dear all,

for some lists, the listowners in the last few days keep getting "pending
moderator requests" emails every day, even though there are no pending
requests.

What mechanism generates these requests and how can I get rid of those
redundant mails? (short of migrating to mailman 3 which I plan on doing)

Cheers, thanks a lot in advance,

Johannes



--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Daily "pending moderator requests" despite empty moderation queue

[Johannes Rohr]

Dear all,

for some lists, the listowners in the last few days keep getting "pending 
moderator requests" emails every day, even though there are no pending 
requests. 

What mechanism generates these requests and how can I get rid of those 
redundant mails? (short of migrating to mailman 3 which I plan on doing)

Cheers, thanks a lot in advance,

Johannes

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Non-member regexps

[Johannes Rohr]

Does the @[NAME] expression, that accepts posts to mailing list X by
subscribers of mailing list Y still work in mailman3? Strictly speaking,
it is not a regexp, but I rely on it heavily.

I am testing out mailman3 and I have to say, migration works much better
than I expected! Kudos!!

However, regexps from "accept_these_nonmembers" have not been migrated,
so I wonder if they are still recognized.

Cheers,

Johannes

Am 29.09.20 um 17:26 schrieb Mark Sapiro:
> On 9/29/20 5:38 AM, Daniel Krause via Mailman-Users wrote:
>> Good Day
>>
>> We are using mailman 3, and would like to whitelist a domain for acceptance
>> of messages as non-members.
>> It seems possible from my online searches, I have also tried with an online
>> python regex tester(https://www.regextester.com/94044), but I have not
>> managed to be successful.
>>
>> Below are 2 examples I have tried
>>
>> ^.+@noldor\.co\.za$
> This looks good.
>
>
>> ^[a-zA-Z0-9_.+-]+@(?:(?:[a-zA-Z0-9-]+\.)?[a-zA-Z]+\.)?noldor\.co\.za$
> This is unduly complex. These regexps are matched case insensitively so
> it isn't necessary to include both a-z and A-Z. Also, I don't thing you
> need to be concerned about invalid addresses, so
>
>   ^.+@(?:.+\.)?noldor\.co\.za$
>
> would do, or even simpler
>
>   ^.*[@.]noldor\.co\.za$
>
>
>> ^.+@gmail.com$
> This would allow user@gmailxcom, but probably not an issue.
>
>
>> ^.*gmail\.com$
> This is good.
>
> How are you unsuccessful? If you have say
>
>   ^.+@noldor\.co\.za$
>
> in accept_these_nonmembers, what happens when an address from that
> domain posts to the list?
>
> Note that while determination of whether a message is from a list member
> checks addresses in several things (default From:, envelope sender,
> Reply-To:, Sender), *_these_nonmembers checks only the first address
> found in From:, Sender:, envelope sender in that order by default, but
> if USE_ENVELOPE_SENDER is set True in mm_cfg.py, the order is Sender:,
> From:, envelope sender.
>
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Monthly notifications bounce, are sent without DKIM signature.

[Johannes Rohr]

Dear all,

I get a batch of bounces once a month from GMail, when mailman sends out
the monthly reminders.

When I look into the headers of those notifications, it looks like they
miss the DKIM signature, which is super weird, because the notification
about the bounce that mailman sends to the listowner has a DKIM
signature. I wonder what is going wrong there. My understanding is that
the signing is done by rspamd and that mailman doesn't have anything to
do with it. Why aren't all messages signed?

Cheers,

Johannes





Am 27.01.21 um 20:11 schrieb Mark Sapiro:
> On 1/26/21 5:57 PM, steve lund wrote:
>> We seem to be having all too frequent occurrences of multiple bounces that
>> seem to be related only to the domain of the address recipient.
>
> As pointed out in another reply, this is likely a DMARC issue and MM
> 2.1.34 has settings to mitigate this.
>
>
>> The interesting thing about this occurrence other than losing the name
>> associated with the email address (since the members were unsubscribed not
>> just disabled) is that I NEVER received ANY bounce notifications other than
>> the unsubscribe notification. I find this quite odd and unsettling
>> considering that the list shows that it IS configured to send earlier
>> bounce notifications and I have received them in the past... just not
>> leading up to this latest incident. The typical error message is:
>>
>> jonxx_daj...@yahoo.com  has been removed from
>> MSing-ride. (disabled address)
>
> That occurred after the users delivery was disabled by bounce and the
> notices to the user were exhausted. When the delivery was first
> disabled, (three weeks earlier with default bounce settings) there was a
> notice sent to the list admins about the disable if the list's admin
> Bounce processing -> bounce_notify_owner_on_disable setting is Yes.
>
> Also, you can set Bounce processing ->
> bounce_notify_owner_on_bounce_increment to Yes to be sent a notice when
> a bounce is received that increments the score.
>
> If one or both of these settings is Yes and you aren't receiving the
> notices, that's between Mailman's MTA and you.
>
>
>> So I guess that my question is whether or not these types of problems are
>> now endemic to all email lists or ifOur ISP is technically "challenged"
>> and
>>
>> 1. Doesn't know how to properly configure Mailman to send out the requested
>> notifications.
>
> Since you got the unsub notice, I'd expect that all requested notices
> have been sent.
>
>
>> 2. Continues to get blacklisted for sending SPAM even though they don't.
>
> What are your settings under Privacy options... -> Sender filters for
> dmarc_moderation_action and dmarc_quarantine_moderation_action? at a
> minimum, they should be Munge From and Yes respectively.
>
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Virtualhosts in mailman 3 / postorius

[Johannes Rohr]

Am 25.09.20 um 13:41 schrieb Brian Carpenter:
> On 9/25/20 6:49 AM, Johannes Rohr wrote:
>> I am now playing around with Mailman 3,  considering to migrate
>> eventually. Reading the documentation, I haven't understood whether
>> there is still a possibility to configure virtual hosts within mailman.
>>
>> My goal is to ensure that visitors ofhttps://lists.domain1.org  only see
>> the lists @lists.domain1.org and not the others, just as the setting
>> VIRTUAL_HOST_OVERVIEW = 1 in /etc/mailman/mm_cfg.py does. I would assume
>> that one can have a similar behaviour in mailman3, can't one?
>
> It is possible with the following setting set via settings_local.py:
>
> filter_vhost = true
>
Great, and apart from that, is the virtualhost configuration obsolete in
mailman3? I noticed that when you create a new list, you already have to
append the domain, so this looks to me as if this is now implicit.

Cheers,

Johannes
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Virtualhosts in mailman 3 / postorius

[Johannes Rohr]

Dear all,

I am now playing around with Mailman 3,  considering to migrate
eventually. Reading the documentation, I haven't understood whether
there is still a possibility to configure virtual hosts within mailman.

My goal is to ensure that visitors of https://lists.domain1.org only see
the lists @lists.domain1.org and not the others, just as the setting
VIRTUAL_HOST_OVERVIEW = 1 in /etc/mailman/mm_cfg.py does. I would assume
that one can have a similar behaviour in mailman3, can't one?

Thanks a lot in advance!

Johannes

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: How get UTF-8 in web interface

[Johannes Rohr]

Am 09.08.20 um 00:38 schrieb Mark Sapiro:

> whereas the msgstr ends in
>
> "\n"
>
> That is: It misses the last line which only consists of blanks.
> I don't understand why this needed to be "fixed". The line of blanks is
> just whitespace and is not rendered in the HTML anyway and msgfmt (at
> least my "(GNU gettext-tools) 0.19.8.1" version) doesn't complain.
>
Without adding the empty line, my copy of msgformat refused to compile it. 
0.19.8.1-10build1, apparently the same version as yours, but still. 

>
> I'm not sure what the problem is with Russian. It hasn't been utf-8 all
> along. Before 2.1.19, it was koi8-r. See
> .ho

Indeed. The additional problem with Russian/Cyrillic is that you have
those various competing encodings, koi8, ISO-8859-5 and I think a third
one, and so recoding is always trial and error.

The strange thing though, is that /etc/mailman/ru isn't automatically
re-generated after the encoding has changed. I also deleted the
directory and expected it to be regenerated by dpkg-reconfigure mailman
but that didn't happen either. Last, I inspected the
/var/lib/dpkg/info/mailman.postinst to understand what it does, but I
was kind overwhelmed by it, so what I ended up with was installing
mailman on a virtual machine and copying the generated /etc/mailman/ru
from there.

I wonder, if in the long run the only sustainable solution is upgrading
to mailman 3, also having noticed that Debian bullseye seems to have
removed mailman2 altogether. But the upgrade still isn't
straightforward, is it?


Cheers,

Johannes


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: How get UTF-8 in web interface

[Johannes Rohr]

Am 08.08.20 um 21:44 schrieb Mark Sapiro:
> On 8/8/20 6:47 AM, Johannes Rohr wrote:
>> Dear all,
>>
>> As a quick fix I have now recoded the mailman.po for de to from latin1
>> to utf8 and re-compiled it with msgfmt. This seems to fix things. BTW, I
>> stumbled across a problem with the mo file, that I had to fix first.
> What was the problem with the .mo? Is something wrong in the distribution?

Line 7111, the msgid ends in

"   "

whereas the msgstr ends in

"\n"

That is: It misses the last line which only consists of blanks.

>
> Note that Debian's (and Ubuntu's) Mailman 2.1 package at one time[1]
> recoded templates and message catalogs to UTF-8

Right now, some are, some are not.

>  and changed the
> definition of add_language in Defaults.py to hard-code utf-8 as the
> charset for every language.

Again, that is mixed now.

>
> This was OK as far as it went, but they didn't consider the issue of
> strings in list attributes

What's that? Excuse my ignorance.

>  being encoded in the old charset. This caused
> serious issues for some sites. See
> <https://mail.python.org/archives/list/mailman-users@python.org/thread/JDLVQY3EUEN2W4VIC4XVMO2HOT53NMZ5/#NTXJUVDV7SUWSLAPJ7AQTZTXGJGJW6DR>
> for one thread on this.
Thanks for the pointer!
>
> [1] They appear to have removed
> <https://sources.debian.org/patches/mailman/1:2.1.18-2/91_utf8.patch/>
> from the latest packages. It was in their 1:2.1.23-1 package, but is not
> in the 1:2.1.29-1 package.
>
Ah, interesting. However, what is the canonical approach then? Is the
mailman web interface supposed to recode everything to UTF on the fly?
Because, firefox thinks, that the pages are in UTF-8, presumably because
that's what the server says.

Strangely, after I recompiled de in UTF-8, German umlauts would display
correctly, but Russian, which has been in UTF-8 all along is suddenly
messed up. And here, it is not the message strings that are messed up
but it is the contents of listinfo.html that is in some 8 bit Russian
charset. How does that happen? Apparently I can't just delete a
subdirectory in /etc/mailman, because even after running
dpkg-reconfigure mailman and selecting the languages that I want, the
directory is created, but it is empty. How can I manually regenerate the
languages?

Cheers, and thanks for your support!

Johannes

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: How get UTF-8 in web interface

[Johannes Rohr]

Dear all,

As a quick fix I have now recoded the mailman.po for de to from latin1
to utf8 and re-compiled it with msgfmt. This seems to fix things. BTW, I
stumbled across a problem with the mo file, that I had to fix first.

Now it looks ok.

Cheers,

Johannes

Am 08.08.20 um 15:27 schrieb Johannes Rohr:
>
> Dear all,
>
> I am looking for a way to ensure that everything is in proper UTF-8 in
> the web interface Specifically, my problem is that messages from
> gettext for German are inserted in ISO-8859-1 while for other
> languages I have tested, including Norwegian and Russian, mailman
> seems to generate proper UTF-8, even without explicitly enabling UTF-8
> in mm_cfg.py.
>
> As an example, take
> https://lists.uferwerk.org/cgi-bin/mailman/listinfo/huehner
>
> "Um frühere Nachrichten an diese Liste zu sehen, besuchen Sie bitte
> das Archiv der Liste Huehner
> <https://lists.uferwerk.org/cgi-bin/mailman/private/huehner/>. (/Das
> aktuelle Archiv ist nur f�r die Abonnenten der Liste zug�nglich./)"
>
> When I inspect the source code of the German page, I see that part of
> the umlauts are properly encoded as html entities such as ,
>  and others are not, they are plain ISO-8819-1 and thusly get
> screwed up, when the browser interprets the page as UTF-8. They seem
> to be inserted on-the-fly by the python interpreter, from
> /var/lib/mailman/messages/de/LC_MESSAGES/mailman.po  and I notice that
> /var/lib/mailman/messages/de/LC_MESSAGES/mailman.po is in ISO-8859-1,
> not in UTF-8.
>
> In mm_cfg.py I have done what the manual recommends
> <https://wiki.list.org/DOC/4.90%20My%20list%27s%20moderator%20interface%20and%20plain%20format%20digests%20have%20garbled%20non-ascii.%20Change%20English%20charset%20to%20utf-8.>.
> Without it, the message strings get rendered correctly, while the list
> descriptions from the configuration, which are apparently in UTF-8 get
> rendered as two letter strings: "*Huehner -- Liste für alle
> Hühner-Eltern im Uferwerk".*
>
> Can someone maybe tell me what I can do to reconcile this apparent
> mismatch?
>
> Thanks so much in advance,
>
> Johannes
>
> *
> *
>
>

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] How get UTF-8 in web interface

[Johannes Rohr]

Dear all,

I am looking for a way to ensure that everything is in proper UTF-8 in
the web interface Specifically, my problem is that messages from gettext
for German are inserted in ISO-8859-1 while for other languages I have
tested, including Norwegian and Russian, mailman seems to generate
proper UTF-8, even without explicitly enabling UTF-8 in mm_cfg.py.

As an example, take
https://lists.uferwerk.org/cgi-bin/mailman/listinfo/huehner

"Um frühere Nachrichten an diese Liste zu sehen, besuchen Sie bitte das
Archiv der Liste Huehner
. (/Das
aktuelle Archiv ist nur f�r die Abonnenten der Liste zug�nglich./)"

When I inspect the source code of the German page, I see that part of
the umlauts are properly encoded as html entities such as , 
and others are not, they are plain ISO-8819-1 and thusly get screwed up,
when the browser interprets the page as UTF-8. They seem to be inserted
on-the-fly by the python interpreter, from
/var/lib/mailman/messages/de/LC_MESSAGES/mailman.po  and I notice that
/var/lib/mailman/messages/de/LC_MESSAGES/mailman.po is in ISO-8859-1,
not in UTF-8.

In mm_cfg.py I have done what the manual recommends
.
Without it, the message strings get rendered correctly, while the list
descriptions from the configuration, which are apparently in UTF-8 get
rendered as two letter strings: "*Huehner -- Liste für alle
Hühner-Eltern im Uferwerk".*

Can someone maybe tell me what I can do to reconcile this apparent mismatch?

Thanks so much in advance,

Johannes

*
*


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: "Message discarded" "spamdetect", why?

[Johannes Rohr]

Am 21.06.20 um 18:15 schrieb Mark Sapiro:

> The list it happens on has its Privacy options... -> Sender filters ->
> dmarc_moderation_action set to Discard.

It isn't. It is set o "0".

>
> If that is not the case and "SpamDetect" processing is discarding some
> but not all messages for the same list, then perhaps it is not DMARC but
> header_filter_rules responsible for the discard.

It is also empty:

header_filter_rules = []

Cheers,

Johannes
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: "Message discarded" "spamdetect", why?

[Johannes Rohr]

Am 20.06.20 um 19:37 schrieb Mark Sapiro:
> On 6/20/20 5:52 AM, Johannes Rohr wrote:
>> Hi,
>>
>> yesterday, I member tried multiple times to send a to a list, from a
>> roundcube webmailer which is running on the same host as mailman itself.
>> The message is in plain text without any attachments, no HTML either.
>> Yet it was silently discarded by mailman. In /var/log/mailman/vette I
>> find the message
>>
>> Jun 19 21:02:42 2020 (14835) Message discarded, msgid: <@***>'
>>     list: **,
>>     handler: SpamDetect
>
> There are 3 reasons why SpamDetect can discard a message.
>
> 1) (not likely) The message contains a header with value matching a
> header/regexp combination in mm_cfg.KNOWN_SPAMMERS which is empty by
> default.
>
> 2) The message is from a sender in a domain publishing a DMARC policy of
> reject or possibly quarantine and the list's Privacy options... ->
> Sender filters -> dmarc_moderation_action is Discard.

Thanks, Marc, a lot for the explanation!!! Very helpful!! Now, for the
messages that got rejected, none of the three reasons apply. However, in
/var/log/mailman/error, I see the message I wrote about " DNSException:
Unable to query DMARC policy for *** (_dmarc.***.org). The DNS operation
timed out." with both the time and sender address matching the rejected
message. So could it be that mailman treats a failed DMARC DNS query as
if the domain in question had set its DMARC policy to "reject" or
"quarantine"?

And in our case, I feel that disabling this kind of checks altogether
would make sense, given that all mail is parsed by rspamd before it is
handed over to mailman. rspamd does an outstanding job, therefore, I
don't think that there is a need for mailman to parse messages for spam.

Cheers,

Johannes


>
> 3) The message matched a Spam Filter Rule in Privacy options... -> Spam
> filters -> header_filter_rules with a Discard Action.
>
> Check these things in your list configuration.
>

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: DNSException: Unable to query DMARC policy

[Johannes Rohr]

Am 20.06.20 um 19:10 schrieb Mark Sapiro:
[...]
> You can increase these by setting them in mm_cfg.py. On mail.python.org,
> they are set as
>
> DMARC_RESOLVER_TIMEOUT = seconds(8)
> DMARC_RESOLVER_LIFETIME = seconds(10)

Thanks so much Marc, great advice there!!!

Johannes


>
> for Mailman 2.1.
>
>
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] "Message discarded" "spamdetect", why?

[Johannes Rohr]

Hi,

yesterday, I member tried multiple times to send a to a list, from a
roundcube webmailer which is running on the same host as mailman itself.
The message is in plain text without any attachments, no HTML either.
Yet it was silently discarded by mailman. In /var/log/mailman/vette I
find the message

Jun 19 21:02:42 2020 (14835) Message discarded, msgid: <@***>'
    list: **,
    handler: SpamDetect


The filter configuration for the list is:

filter_mime_types = ''

pass_mime_types = """multipart/mixed
multipart/alternative
text/plain"""
filter_filename_extensions = """exe
bat
cmd
com
pif
scr
vbs
cpl"""

pass_filename_extensions = ''

Can anyone say why mailman considered it to be spam? BTW, all messages
are scanned by rspamd anyway, which does an outstanding job at spam
detection, so mailman's rudimentary spam detection mechanism seems
rather superfluous to me. Can't one just turn it off altogether?

Cheers,

Johannes



--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] DNSException: Unable to query DMARC policy

[Johannes Rohr]

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

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

Re: [Mailman-Users] Toggle plain text setting for new users

[Johannes Rohr]

Am Mittwoch, 22. April 2020, 17:59:53 CEST schrieb Mark Sapiro:
> On 4/22/20 7:36 AM, Johannes Rohr wrote:
> > What I am asking about is the per-user setting:
> > 
> > When you go to /members  you will see that in the members table, the
> > second column from the right is called "plain" and if the box is ticket,
> > messages are delivered as plain text. And the preset is that the box /is/
> > ticked.
> > 
> > I would like to find out how I can toggle the preset.
> 
> First of all, that setting is only applicable for digest subscriber and
> controls whether they are sent the plain text or the HTML version of the
> digest.

Ah, ok, thanks Ben!! In that case it doesn't really matter because very few 
people receive the digests.

[...]

> The default for the 'plain' setting is Digest options ->
> mime_is_default_digest. The global default for new lists is the
> mm_cfg.py setting DEFAULT_MIME_IS_DEFAULT_DIGEST.

Great, thanks!!

Johannes


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Toggle plain text setting for new users

[Johannes Rohr]

Am Mittwoch, 22. April 2020, 16:09:49 CEST schrieb Mailman-admin:
> Hello
> 
> Per default mailman is distributing whatever it gets.
> Check your settings in admin page topic "Content filtering".

Thanks, but I am not asking about global filtering rules (which are disabled 
anyway (The 
preset is that filter_content is set to "no").

What I am asking about is the per-user setting: 

When you go to /members  you will see that in the members table, the second 
column 
from the right is called "plain" and if the box is ticket, messages are 
delivered as plain text. 
And the preset is that the box /is/ ticked. 

I would like to find out how I can toggle the preset.

Cheers,

Johannes


> 
> 
> Kind regards,
> Christian Mack
> 
> Am 22.04.20 um 15:11 schrieb Johannes Rohr:
> > Dear all,
> > 
> > I would like to toggle a default setting for new users, name the
> > HTML/plain text switch. In our use case, having everything converted to
> > plain text by default is not very practical.
> > 
> > I am not sure how I achieve this, this question isn't mentioned in the
> > FAQ either. I am looking for a global switch to be put in mm_cfg.py or a
> > local config option for each of the lists. So far I haven't found either.
> > 
> > Would greatly appreciate any hint!!!
> > 
> > Johannes
> 
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/jorohr%40gmail.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Toggle plain text setting for new users

[Johannes Rohr]

Dear all,

I would like to toggle a default setting for new users, name the
HTML/plain text switch. In our use case, having everything converted to
plain text by default is not very practical.

I am not sure how I achieve this, this question isn't mentioned in the
FAQ either. I am looking for a global switch to be put in mm_cfg.py or a
local config option for each of the lists. So far I haven't found either.

Would greatly appreciate any hint!!!

Johannes

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Johannes Rohr]

Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users <
mailman-users@python.org>:

> On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote:
> > Is there a timeline for that?  Mailman 2.x requires python 2.x, which is
> > EOL in about 40 days.
>
> I keep saying this a lot... the EOL you are referring to is Python's
> declared date that the Python team will no longer maintain Python2.
> HOWEVER, Redhat, Debian, etc., *will* still be maintaining Python2
> throughout the lifecycles of their releases that contain Python2.   So,
> for Debian 10 (Buster) that is well past 2022 (which is the LTS end-data
> for Debian 9).
>

Python2 is being removed from Debian's next release, Bullseye, though. This
already has caused turmoil for the Calibre package and I suppose that they
will have to remove mailman 2 also so that it is not going to be in the
bullseye release.


>
> Stop being scared by the Python team's misleading messaging.
>
> -Jim P.
>
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> https://mail.python.org/mailman/options/mailman-users/jorohr%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 3 Ready?

[Johannes Rohr]

Am 25.11.19 um 07:15 schrieb Stephen J. Turnbull:


[...]

> The obvious "turn-key" installation is to use the Docker containers,
> which Abhilash keeps fairly up-to-date.  But see comment below about
> universal working solutions.


[...]

Great suggestion. Is it easy to integrate it with the system's MTA or
does it come with its own MTA?

The obvious big showstopper is that there is no supported upgrade path
from Mailman 2.* yet, according to 
http://www.mailman3.org/en/latest/pre-installation-guide.html#how-can-i-upgrade-from-mailman-2-1-x
and so you certainly don't want to try to upgrade production instances
of mailman  without it.

Cheers,

Johannes

 

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] What to do about SPF rejection?

[Johannes Rohr]

Dear all,

I today saw three bounces where the receiving mail server had said:

host mail.gfbv.de[185.199.217.16] said: 550 external MTA
sending our header From:    (in reply to
end of DATA command)

The SPF record for gfbv.de is

gfbv.de.86400   IN  TXT "v=spf1 mx 
a:epicmail1.newsaktuell.net ~all"

I am not sure, whether mailman 2 has any workaround for this like for
the DMARC issue

Can anyone spot, whether there is something wrong with the SPF record?
Whose fault is it?

My mailman instance has its own spf record:

lists.ilo169.de.    9531    IN    TXT    "v=spf1 mx a ip4:5.9.62.175 ~all"

I am not familiar with the spf syntax, so I can't tell whether it is our
fault or theirs.

At first glace, it would look to me as if the solution would be similar
to the DMARC workaround, that is to swap the original From: address with
the list address. But again, mailman offers this option only for DMARC
issues.

Does anyone have advice for me?

Thanks so much in advance,

Johannes






--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] change links in mail footer to https

[Johannes Rohr]

Am 09.12.2017 um 20:06 schrieb Mark Sapiro:
> On 12/09/2017 10:40 AM, Chip Davis wrote:
>> That's all well and good Mark, but surely you know that any fix that
>> involves issuing a shell command is useless for those of us responsible
>> for lists on a shared server running cPanel (or equivalent).
>
> The OP indicated that he had changed DEFAULT_URL_PATTERN. If he can do
> that, he can run fix_url.

I have found the reason. There was an error with the config file and
there were two entries for DEFAULT_URL_PATTERN, the first starting with
https and the second which I had not noticed with http. I deleted the
second and now running fix_url dig the trick.

Thanks,

Johannes




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] change links in mail footer to https

[Johannes Rohr]

Hi, all the links in mails generated by mailman start with http, even
though DEFAULT_URL_PATTERN starts with https. How can I change this?

Thanks a lot in advance for any advice,

Johannes



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman uses wrong encoding, /etc/mailman/[language] not generated

[Johannes Rohr]

Am 25.04.2017 um 18:59 schrieb Mark Sapiro:
>  
> You need to look at the messages/de/LC_MESSAGES/mailman.po file you
> have. Near the beginning will be a line like
>
> "Content-Type: text/plain; charset=xxx\n"
>
> where xxx is either ISO-8859-1 or UTF-8. If it is UTF-8 and the 'msgstr'
> values are utf-8 encoded, you can rebuild the .mo with
>
> cd messages/de/LC_MESSAGES/
> msgfmt -o mailman.mo mailman.po
>
> but I suspect that is not the case. I suspect that somehow in your
> migration process you replaced the Debian utf-8 encoded files with older
> iso-8859-1 files.
That might be the case. I didn't do the migration myself, but it is true
that the mailman.po for some reason was encoded in latin-1, not utf-8.
And the files which ship with the deb have the correct UTF-8 encoding.
So those with the wrong encoding must have been carried over. It is a
bit stupid, that those files are in /var so that dpkg doesn't replace them.

But again, thanks for your help! You got me on the right track. In
hindsight, the solution was trivial, but I just wasn't aware of the
existence of message catalogues outside of /usr/share/locale ...

Cheers,

Johannes
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman uses wrong encoding, /etc/mailman/[language] not generated

[Johannes Rohr]

Dear all,

we have recently migrated from a server with Ubuntu 14.4 to one using
Ubuntu's current LTS.

The default language for most mailing lists is German. Since the migration,
mailman serves all pages and mail notifications in latin-1 instead of
utf-8, which the header still decleares the content to be UTF-8, which
leads to broken display, see eg
https://lists.uferwerk.org/cgi-bin/mailman/listinfo/

I noticed that the subdirectory for the English templates /etc/mailman/en
exists, but there is no /etc/mailman/de

On Debian/Ubuntu, /var/lib/mailman/Templates  is a symlink to /etc/mailman,
which by default is owned by root:root. I changed that to root:list and
restarted mailman, in the hope that /etc/mailman/de would eventually be
generated, but it wasn't.

What is the mechanism, by which the templates directory for the respective
language is generated? Could this be a permission issue, and could the
mismatch between the charset declared in the header of the message or
website and the actual charset in the content be somehow related to that?

Thanks in advance for any suggestion,

Johannes
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org