On 03/30/2017 04:32 PM, Jon Ribbens wrote:
> 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 m
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 d
On 03/30/2017 08:58 AM, Jon Ribbens wrote:
> On Thu, Mar 30, 2017 at 08:35:54AM -0700, Mark Sapiro wrote:
>
>> 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 resta
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
On 03/30/2017 02:02 AM, Jon Ribbens wrote:
> 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 an
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
