[Mailman-Users] Re: GNU Mailman condemns reinstatement of RMS
On Tue, Apr 13, 2021 at 09:01:37PM -0400, Ruben Safir wrote: > In fact, without Richard, it is not far to think there would be no women > in the movement, and certainly no gays or transexuals. -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] Re: GNU Mailman condemns reinstatement of RMS
On Mon, Apr 12, 2021 at 10:26:05PM -0700, Abhilash Raj wrote: > The GNU Mailman Steering Committee condemns the reinstatement of > Richard M. Stallman (RMS) to the Board of the Free Software Foundation > (FSF), and has taken the following actions: +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/
Re: [Mailman-Users] Mailman 3 confusion
On Mon, Jun 19, 2017 at 06:53:37PM -0700, Mark Sapiro wrote: > It means Postorius (postorius), HyperKitty (mailman-hyperkitty) and > therefore the supporting project modules they import, mailmanclient and > django-mailman3 all require Python 2.7. Not 'at least' Python 2.7, but > some 2.7.x. > > Python 2.7 and Python 3 are significantly different. Programs can be > bilingual, but not all of Postorius, HyperKitty and their dependencies > are fully Python 3 compatible yet. > > This means you need Python 3.4 or later for Mailman core and Python > 2.7.x for Postorius and HyperKitty. These are quite capable of > coexisting on the same box and that is probably what you want, but it is > possible to run Postorius and HyperKitty on a separate box, but there > are potential security issues involved in exposing the core's REST > interface beyond 'localhost'. This is all true, but personally I can't see any likelihood of any noticeable uptake of Mailman 3 until it will all run on one version of Python. Having said that, if there's any specific help needed to achieve that then I'm potentially willing to put some work in. -- 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 brokenly base64-encoding all messages
On Thu, Mar 30, 2017 at 10:22:08AM -0700, Mark Sapiro wrote:
> Sorry, I forgot. Debian's package ignores any charset argument you put
> in add_language.
>
> You need to put
>
> LC_DESCRIPTIONS['en'] = ('English (USA)', 'us-ascii', 'ltr')
>
> in mm_cfg.py. I think that will work.
Awesome, that does indeed appear to work perfectly. Thank you.
Shouldn't this be a FAQ? I looked there first but couldn't find
anything relevant.
--
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 brokenly base64-encoding all messages
On Thu, Mar 30, 2017 at 08:35:54AM -0700, Mark Sapiro wrote:
> I believe that RFC 2045 s6.8 refers back to canonical form as discussed
> in sections 6.5 and 6.6 and RFC 2049 sec 4. While it is arguable that
> this requires all plain text to use CRLF line delimiters regardless of
> encoding, I think common practice is to use CRLF only "on the wire" and
> not in base64 or quoted-printable encodings.
RFC 2045 s6.8 explicitly says that text line breaks "must" be
converted to CRLF before base64 encoding, and that this is regardless
of whether it's canonical form or not.
> If it is a bug, it is in the Python email library, not Mailman.
OK I'll look into reporting it on the Python bug tracker.
> To change the former, you can put
>
> add_language('en', 'English (USA)', 'us-ascii')
>
> in mm_cfg.py.
I've done this (in /etc/mailman/mm_cfg.py) and then done
systemctl restart mailman and it's made no difference.
Is there anything else I need to do also?
(I'm testing it by getting it to reply to a 'help' request.)
--
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 The Definitive Mailman Suite - Download error
On Thu, Mar 30, 2017 at 11:29:01AM +, Henrik Rasmussen wrote: > Both in the Mailman Suite Setup Guide section "Set up and run > Mailman Core" > http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-mailman-core > , and the Mailman Core doc at > http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/WebUIin5.html#gnu-mailman-3 > the code is supposed to be downloaded using the command "git clone > g...@gitlab.com:mailman/mailman.git", but I get a Permission Denied Try this instead: git clone https://gitlab.com/mailman/mailman.git -- 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 brokenly base64-encoding all messages
I'm using Mailman 2.1.22 packaged by Ubuntu 16.10. It appears that on one (but I think not all) of my mailing lists, Mailman is base64-encoding every single message. Yes, including ones that 100% definitely contain only ASCII characters. Does anyone know why Mailman would be doing this? You might say that base64-encoding all messages shouldn't be a problem, and you'd be partly right. However there is also another problem: Mailman is getting the line break encoding wrong in its base64-encoded messages - by which I mean the encoded representation of line breaks inside the base64 data. As per RFC 2045 s6.8: "line breaks must be converted into CRLF sequences prior to base64 encoding" but Mailman is outputting just LF. The latter problem definitely appears to be a bug in Mailman, or perhaps the Python 'email' package. The former seems likely to be a configuration issue, but it's not obvious to me where. -- 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
