Re: [Mailman-Users] 64 bit encoding

2015-11-10 Thread Mark Sapiro 
On 11/9/15 7:18 PM, Ruben Safir wrote:
> On 11/09/2015 08:30 PM, Mark Sapiro wrote:
>>
>> So the messages were delivered.  What's the problem?
>>
>>
> 
> 
> that is 2 of 108 :)


So are the other 106 eligible to receive non-digest messages; i.e.
regular, not digest members with delivery enabled?  If so, what does
postfix say in the mail log about those 106 recipients?

Please note that I am in an airport after traveling for 10 hours and
still have over 7 hours to my final destination, so don't expect quick
replies from me. I will have little time to reply for some while. It
will help if you can actually find some log messages that indicate a
problem.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-09 Thread Ruben Safir 
On 11/09/2015 08:30 PM, Mark Sapiro wrote:
> 
> 
> On November 9, 2015 8:15:49 PM EST, Ruben  wrote:
> 
>> 2015-11-08T08:56:54.786350-05:00 www postfix/smtp[21541]: 0AF2B161158: 
>> to=, relay=mx1.hotmail.com[134.170.2.199]:25,
>> delay=2.8, 
>> delays=1.7/0.6/0.16/0.27, dsn=2.0.0, status=sent (250 
>> <563f4bdf.8010...@panix.com> Queued mail for delivery)
>> 2015-11-08T08:56:56.824374-05:00 www postfix/smtp[21527]: 0AF2B161158: 
>> to=, 
>> relay=jordanloyd-com.mail.protection.outlook.com[216.32.181.170]:25, 
>> delay=4.8, delays=1.7/0.08/0.82/2.2, dsn=2.6.0, status=sent (250 2.6.0 
>> 563f4bdf.8010...@panix.com> [InternalId=28059021348382, 
>> Hostname=BY1PR02MB1274.namprd02.prod.outlook.com] Queued mail for
>> delivery)
> 
> 
> So the messages were delivered.  What's the problem?
> 
> 


that is 2 of 108 :)
--
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] 64 bit encoding

2015-11-09 Thread Mark Sapiro 


On November 9, 2015 8:15:49 PM EST, Ruben  wrote:

>2015-11-08T08:56:54.786350-05:00 www postfix/smtp[21541]: 0AF2B161158: 
>to=, relay=mx1.hotmail.com[134.170.2.199]:25,
>delay=2.8, 
>delays=1.7/0.6/0.16/0.27, dsn=2.0.0, status=sent (250 
><563f4bdf.8010...@panix.com> Queued mail for delivery)
>2015-11-08T08:56:56.824374-05:00 www postfix/smtp[21527]: 0AF2B161158: 
>to=, 
>relay=jordanloyd-com.mail.protection.outlook.com[216.32.181.170]:25, 
>delay=4.8, delays=1.7/0.08/0.82/2.2, dsn=2.6.0, status=sent (250 2.6.0 
>563f4bdf.8010...@panix.com> [InternalId=28059021348382, 
>Hostname=BY1PR02MB1274.namprd02.prod.outlook.com] Queued mail for
>delivery)


So the messages were delivered.  What's the problem?


-- 
Mark Sapiro 
Sent from my Not_an_iThing with standards compliant, open source software.
--
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] 64 bit encoding

2015-11-09 Thread Ruben 



On 11/09/2015 07:12 PM, Mark Sapiro wrote:



On November 9, 2015 6:56:56 PM EST, Mark Sapiro  wrote:



On November 9, 2015 6:49:53 PM EST, Ruben  wrote:






I made this change and I think I'm getting no throughput through the
list altogether :(

I have the mail logs being tailed and all the mailman/logs but I'm not



spotting the problem


==> /var/lib/mailman/logs/post <==
Nov 09 18:34:12 2015 (28269) post to hangout from mrbrk...@panix.com,
size=6608, message-id=<563ae93a.2000...@panix.com>, 11 failures



What's in Mailman's smtp-failure log for these?

Anything in Mailman's error log?

What's in the mail log for these?




FWIW, I greps one of the message ids for a submited message

www:~ # grep 563f4bdf.8010...@panix.com  /var/log/mail
2015-11-08T08:19:52.449351-05:00 www postfix/cleanup[21142]: 
48B12161158: message-id=<563f4bdf.8010...@panix.com>
2015-11-08T08:55:41.806591-05:00 www postfix/cleanup[21512]: 
B7863161158: message-id=<563f4bdf.8010...@panix.com>
2015-11-08T08:56:51.592725-05:00 www postfix/cleanup[21512]: 
EE83216249E: message-id=<563f4bdf.8010...@panix.com>
2015-11-08T08:56:53.680355-05:00 www postfix/cleanup[21512]: 
0AF2B161158: message-id=<563f4bdf.8010...@panix.com>
2015-11-08T08:56:54.786350-05:00 www postfix/smtp[21541]: 0AF2B161158: 
to=, relay=mx1.hotmail.com[134.170.2.199]:25, delay=2.8, 
delays=1.7/0.6/0.16/0.27, dsn=2.0.0, status=sent (250 
<563f4bdf.8010...@panix.com> Queued mail for delivery)
2015-11-08T08:56:56.824374-05:00 www postfix/smtp[21527]: 0AF2B161158: 
to=, 
relay=jordanloyd-com.mail.protection.outlook.com[216.32.181.170]:25, 
delay=4.8, delays=1.7/0.08/0.82/2.2, dsn=2.6.0, status=sent (250 2.6.0 
563f4bdf.8010...@panix.com> [InternalId=28059021348382, 
Hostname=BY1PR02MB1274.namprd02.prod.outlook.com] Queued mail for delivery)

--
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] 64 bit encoding

2015-11-09 Thread Ruben 



On 11/09/2015 07:12 PM, Mark Sapiro wrote:



On November 9, 2015 6:56:56 PM EST, Mark Sapiro  wrote:



On November 9, 2015 6:49:53 PM EST, Ruben  wrote:






I made this change and I think I'm getting no throughput through the
list altogether :(

I have the mail logs being tailed and all the mailman/logs but I'm not



spotting the problem


==> /var/lib/mailman/logs/post <==
Nov 09 18:34:12 2015 (28269) post to hangout from mrbrk...@panix.com,
size=6608, message-id=<563ae93a.2000...@panix.com>, 11 failures



What's in Mailman's smtp-failure log for these?


what would I be looking for here?  there is nothing but failed domain 
lookups, none of then from working email lists, that I see




Anything in Mailman's error log?



nothing since Oct 25

www:~ # tail -f /var/lib/mailman/logs/error
[Errno 2] No such file or directory: 
'/var/lib/mailman/qfiles/out/1445396648.951926+5b9ff5008329d53f6f74502963da062941598f03.bak'

Oct 25 01:32:55 2015 mailmanctl(4827): No child with pid: 30374
Oct 25 01:32:55 2015 mailmanctl(4827): [Errno 3] No such process
Oct 25 01:32:55 2015 mailmanctl(4827): Stale pid file removed.
Oct 25 01:32:58 2015 mailmanctl(4830): PID unreadable in: 
/var/lib/mailman/data/master-qrunner.pid
Oct 25 01:32:58 2015 mailmanctl(4830): [Errno 2] No such file or 
directory: '/var/lib/mailman/data/master-qrunner.pid'

Oct 25 01:32:58 2015 mailmanctl(4830): Is qrunner even running?
Oct 25 01:33:01 2015 mailmanctl(4833): PID unreadable in: 
/var/lib/mailman/data/master-qrunner.pid
Oct 25 01:33:01 2015 mailmanctl(4833): [Errno 2] No such file or 
directory: '/var/lib/mailman/data/master-qrunner.pid'

Oct 25 01:33:01 2015 mailmanctl(4833): Is qrunner even running?



What's in the mail log for these?





2015-11-09T19:58:56.574951-05:00 www postfix/smtpd[28205]: NOQUEUE: 
reject: RCPT from www.mrbrklyn.com[96.57.23.82]: 450 4.1.2 
: Recipient address rejected: Domain not found; 
from= to= proto=ESMTP 
helo=
2015-11-09T19:58:56.582345-05:00 www postfix/smtpd[28205]: NOQUEUE: 
reject: RCPT from www.mrbrklyn.com[96.57.23.82]: 450 4.1.2 
: Recipient address rejected: Domain not found; 
from= to= proto=ESMTP 
helo=
2015-11-09T19:58:56.590302-05:00 www postfix/smtpd[28205]: NOQUEUE: 
reject: RCPT from www.mrbrklyn.com[96.57.23.82]: 450 4.1.2 
: Recipient address rejected: Domain not found; 
from= to= proto=ESMTP 
helo=
2015-11-09T19:58:56.598704-05:00 www postfix/smtpd[28205]: NOQUEUE: 
reject: RCPT from www.mrbrklyn.com[96.57.23.82]: 450 4.1.2 
: Recipient address rejected: Domain not found; 
from= to= proto=ESMTP 
helo=
2015-11-09T19:58:56.606356-05:00 www postfix/smtpd[28205]: NOQUEUE: 
reject: RCPT from www.mrbrklyn.com[96.57.23.82]: 450 4.1.2 
: Recipient address rejected: Domain not found; 
from= to= proto=ESMTP 
helo=
2015-11-09T19:58:56.615825-05:00 www postfix/smtpd[28205]: disconnect 
from www.mrbrklyn.com[96.57.23.82]
2015-11-09T19:58:56.747491-05:00 www postfix/smtpd[28737]: connect from 
www.mrbrklyn.com[96.57.23.82]
2015-11-09T19:58:56.757163-05:00 www postfix/smtpd[28737]: NOQUEUE: 
reject: RCPT from www.mrbrklyn.com[96.57.23.82]: 450 4.1.2 
: Recipient address rejected: Domain not found; 
from= to= proto=ESMTP 
helo=

--
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] 64 bit encoding

2015-11-09 Thread Mark Sapiro 


On November 9, 2015 6:56:56 PM EST, Mark Sapiro  wrote:
>
>
>On November 9, 2015 6:49:53 PM EST, Ruben  wrote:
>>
>>
>
>>I made this change and I think I'm getting no throughput through the 
>>list altogether :(
>>
>>I have the mail logs being tailed and all the mailman/logs but I'm not
>
>>spotting the problem
>>
>>
>>==> /var/lib/mailman/logs/post <==
>>Nov 09 18:34:12 2015 (28269) post to hangout from mrbrk...@panix.com, 
>>size=6608, message-id=<563ae93a.2000...@panix.com>, 11 failures
>
>
>What's in Mailman's smtp-failure log for these?
>
>Anything in Mailman's error log?
>
>What's in the mail log for these?


-- 
Mark Sapiro 
Sent from my Not_an_iThing with standards compliant, open source software.
--
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] 64 bit encoding

2015-11-09 Thread Ruben 



On 11/04/2015 12:10 PM, Mark Sapiro wrote:

On 11/03/2015 06:42 PM, Ruben Safir wrote:

I'm converting my mailing lists from majordomo to mailman using postfix.
  A lot of little issues have cropped up but the biggest problem I have
currently is that it seems that mailman is converting files to 64 bit
which is screwing up my home cooked archives but good.



Actually, Mailman is sending messages in UTF-8 character set as base64
encoded. Actually, many MUAs will also base64 encode UTF-8 message bodies.

This is actually a python email library thing. You can change the
encoding for UTF-8 message bodies with the following patch to
Mailman/Message.py, but if your messages are not predominately ascii
text, you won't like the result any better.

diff -u 2.1/Mailman/Message.py 21/Mailman/Message.py
--- 2.1/Mailman/Message.py  2014-05-17 18:34:20.240159000 -0700
+++ 21/Mailman/Message.py   2015-11-04 08:50:31.772899979 -0800
@@ -36,6 +36,10 @@
  from Mailman import mm_cfg
  from Mailman import Utils

+email.Charset.add_charset('utf-8',
+  email.Charset.SHORTEST,
+  email.Charset.QP,
+  'utf-8')
  COMMASPACE = ', '

  mo = re.match(r'([\d.]+)', email.__version__)



I made this change and I think I'm getting no throughput through the 
list altogether :(


I have the mail logs being tailed and all the mailman/logs but I'm not 
spotting the problem



==> /var/lib/mailman/logs/post <==
Nov 09 18:34:12 2015 (28269) post to hangout from mrbrk...@panix.com, 
size=6608, message-id=<563ae93a.2000...@panix.com>, 11 failures



/usr/lib/mailman/Mailman/Message.py
~~
import email.Message
import email.Utils
from email.Charset import Charset
from email.Header import Header

from types import ListType, StringType

from Mailman import mm_cfg
from Mailman import Utils
email.Charset.add_charset('utf-8',
  email.Charset.SHORTEST,
  email.Charset.QP,
  'utf-8')

COMMASPACE = ', '

mo = re.match(r'([\d.]+)', email.__version__)
VERSION = tuple([int(s) for s in mo.group().split('.')])

--
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] 64 bit encoding

2015-11-06 Thread Mark Sapiro 
On 11/5/15 9:05 PM, Ruben Safir wrote:
> On 11/05/2015 03:50 PM, Mark Sapiro wrote:
>> And you've basically arranged that by making the archive public as far
>> as mailman is concerned and telling apache
>>
>> Alias /pipermail/ /usr/local/apache/htdocs/mailman/archives/public/
>>
>> so at least the default public archive URLs point somewhere where the
>> archives presumably aren't.
> 
> 
> Yeah - I should take it out.  I didn't know what it was when I installed
> it so I just followed directions and inserted it.  I really don't need
> though, do I, since it is about the archives and archives and I'm not
> using mailman's archives.


There are links to the archive on the list's listinfo pages (if you
haven't edited them).

If you don't override PUBLIC_ARCHIVE_URL as I suggested in the post at
,
these links will 404 in any case.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-05 Thread Ruben Safir 
On 11/05/2015 03:50 PM, Mark Sapiro wrote:
> And you've basically arranged that by making the archive public as far
> as mailman is concerned and telling apache
> 
> Alias /pipermail/ /usr/local/apache/htdocs/mailman/archives/public/
> 
> so at least the default public archive URLs point somewhere where the
> archives presumably aren't.


Yeah - I should take it out.  I didn't know what it was when I installed
it so I just followed directions and inserted it.  I really don't need
though, do I, since it is about the archives and archives and I'm not
using mailman's archives.


--
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] 64 bit encoding

2015-11-05 Thread Mark Sapiro 
On 11/05/2015 10:33 AM, Ruben Safir wrote:
> On 11/05/2015 01:05 PM, Mark Sapiro wrote:
>  
>> How do you start Mailman? Where is the bin/mailmanctl that starts it?
> 
> /etc/rc.d/mailman which unfortunately is piped through systemd.
> 
...
> MM_CT=/usr/lib/mailman/cron/crontab
> MM_CTRL=/usr/lib/mailman/bin/mailmanctl
> MM_PID=/var/lib/mailman/data/master-qrunner.pid


So starting Mailman runs the Mailman in /usr/lib/mailman/


>> what is in paths.py in the same bin/ directory? 
> 
> Excellent question...
> 
> import os
> import sys
> 
> # some scripts expect this attribute to be in this module
> prefix = '/usr/lib/mailman'


And paths.py is consistent with this.


>> Are there any lists with
>> public archives and if so, are there symlinks in
>> /usr/local/apache/htdocs/mailman/archives/public/ and where do they point?
> 
> I have done the archives using the same software I wrote in 1996 but the mbox 
> et al seems to be in 
> 
> www:/etc/postfix # ls -al  
> /var/lib/mailman/archives/private/hangout.mbox/hangout.mbox 
> -rw-rw-r-- 1 mailman mailman 486238 Nov  5 11:32 
> /var/lib/mailman/archives/private/hangout.mbox/hangout.mbox
> 
> www:/etc/postfix # ls -al  /var/lib/mailman/archives/public/
> total 8
> drwxrwsr-x 2 root   mailman 4096 Oct 20 23:43 .
> drwxrwsr-x 4 root   mailman 4096 Oct  8  2014 ..
> lrwxrwxrwx 1 daemon mailman   41 Oct 20 23:43 hangout -> 
> /var/lib/mailman/archives/private/hangout
> lrwxrwxrwx 1 daemon mailman   39 Oct 20 16:08 learn -> 
> /var/lib/mailman/archives/private/learn
> lrwxrwxrwx 1 root   mailman   41 Oct 20 11:14 mailman -> 
> /var/lib/mailman/archives/private/mailman


This is all consistent with an instalation with prefix =
/usr/lib/mailman and var_prefix = /var/lib/mailman


>>
>> Do the web server and the qrunners actually reference the same archives,
> 
> I would prefer the webserver not to reach the archives that mailman archives 
> at all, 
> since my real archive is sitting on a remote postgres server.


And you've basically arranged that by making the archive public as far
as mailman is concerned and telling apache

Alias /pipermail/ /usr/local/apache/htdocs/mailman/archives/public/

so at least the default public archive URLs point somewhere where the
archives presumably aren't.

You might consider setting PUBLIC_ARCHIVE_URL in mm_cfg.py to something like

PUBLIC_ARCHIVE_URL = 'http://remote.server/whatever/%(listname)s'

You might also avoid this whole patching issue by teaching your archiver
to decode base64 and quoted-printable encoded message bodies.

I still wonder about

ScriptAlias /mailman/ /usr/local/apache/htdocs/mailman/cgi-bin/

If you do for example

strings /usr/local/apache/htdocs/mailman/cgi-bin/admin | grep mailman

do you see paths like /usr/lib/mailman and /usr/lib/mailman/scripts?

If so, you are probably OK. If they point at some /usr/local/apache
directory, you may have issues with the web UI manipulating totally
different list objects than the real ones.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-05 Thread Mark Sapiro 
On 11/05/2015 10:38 AM, Ruben Safir wrote:
> 
> # STANZA START: mailman
> # CREATED: Tue Oct 20 11:14:22 2015
> mailman: "|/usr/lib/mailman/mail/mailman post mailman"
...


So list related email goes to the mailman in /usr/lib/mailman/, so
/usr/lib/mailman/Mailman/Message.py is the file to patch.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-05 Thread Ruben Safir 
On 11/05/2015 01:18 PM, Mark Sapiro wrote:
> On 11/05/2015 09:55 AM, Ruben Safir wrote:
> 
>> www:/etc/postfix # grep  mailman ./*
>> ./main.cf:#alias_maps = "hash:/etc/aliases, 
>> hash:/var/lib/mailman/data/aliases"
>> ./main.cf:alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
>> ./master.cf:#mailman   unix  -   n   n   -   -   pipe
>> ./master.cf:#  flags=FR user=list 
>> argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>> ./master.cf.rpmnew:#mailman   unix  -   n   n   -   -   
>> pipe
>> ./master.cf.rpmnew:#  flags=FR user=list 
>> argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>>
>>
>> evidently it is under /usr/lib/mailman/bin/ ?
> 
> 
> All I see there is a pointer to /var/lib/mailman/data/aliases. What's in
> that file?
> 

# This file is generated by Mailman, and is kept in sync with the
# binary hash file aliases.db.  YOU SHOULD NOT MANUALLY EDIT THIS FILE
# unless you know what you're doing, and can keep the two files properly
# in sync.  If you screw it up, you're on your own.

# The ultimate loop stopper address
mailman-loop: /var/lib/mailman/data/owner-bounces.mbox

# STANZA START: mailman
# CREATED: Tue Oct 20 11:14:22 2015
mailman: "|/usr/lib/mailman/mail/mailman post mailman"
mailman-admin:   "|/usr/lib/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman"
mailman-join:"|/usr/lib/mailman/mail/mailman join mailman"
mailman-leave:   "|/usr/lib/mailman/mail/mailman leave mailman"
mailman-owner:   "|/usr/lib/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/lib/mailman/mail/mailman request mailman"
mailman-subscribe:   "|/usr/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
# STANZA END: mailman

# STANZA START: hangout
# CREATED: Tue Oct 20 11:23:34 2015
hangout: "|/usr/lib/mailman/mail/mailman post hangout"
hangout-admin:   "|/usr/lib/mailman/mail/mailman admin hangout"
hangout-bounces: "|/usr/lib/mailman/mail/mailman bounces hangout"
hangout-confirm: "|/usr/lib/mailman/mail/mailman confirm hangout"
hangout-join:"|/usr/lib/mailman/mail/mailman join hangout"
hangout-leave:   "|/usr/lib/mailman/mail/mailman leave hangout"
hangout-owner:   "|/usr/lib/mailman/mail/mailman owner hangout"
hangout-request: "|/usr/lib/mailman/mail/mailman request hangout"
hangout-subscribe:   "|/usr/lib/mailman/mail/mailman subscribe hangout"
hangout-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe hangout"
# STANZA END: hangout


> I'm glad to see the postfix-to-mailman.py trensport is commented out.
> See the FAQ at .
> 

--
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] 64 bit encoding

2015-11-05 Thread Ruben Safir 
On 11/05/2015 01:05 PM, Mark Sapiro wrote:
> On 11/05/2015 09:48 AM, Ruben Safir wrote:
> 
 /usr/local/apache/conf/mailman/Mailman/Message.py
 /usr/local/apache/conf/mailman/Mailman/Message.pyc
>>>
>>
>> ohh.
>>
>> Maybe I did that because I didn't want my cgi-bin directory outside of
>> my apache trunk.  It is odd habit I picked up in the last 30 years is
>> that I want my webservers restricted to the apache directory tree which
>> is /usr/local/apache/
>>
>> It didn't occur to be that mailing system binary and script libraries
>> would also end up in the apache trunk.
> 
> 
> They don't have to, but the real question now is do you have one Mailman
> installation in /usr/local/apache/conf/mailman, or do you have a split
> installation with some things there and some things in /usr/lib/mailman.
> 

The idea is to have it split, and let the mail stuff do its thing in /usr/lib/ 
or /var/lib,
and to integrate the admin interface to my existing apache tree minus the 
mailman archive 
which I don't currently have use for.

> 
>> 
>> ServerAdmin ru...@mrbrklyn.com
>> DocumentRoot "/usr/local/apache/htdocs/nylxs"
>> ScriptAlias /mailman/
>> /usr/local/apache/htdocs/mailman/cgi-bin/
>> Alias   /mailmanicons/  /usr/local/apache/htdocs/mailman/icons/
>> Alias   /pipermail/
>> /usr/local/apache/htdocs/mailman/archives/public/
> ...
>> 
>> ServerName   lists.mrbrklyn.com
>> DocumentRoot "/usr/local/apache/htdocs/mailman/"
>> ScriptAlias /mailman/
>> /usr/local/apache/htdocs/mailman/cgi-bin/
>> Alias   /mailmanicons/
>> /usr/local/apache/htdocs/mailman/icons/
>> Alias   /pipermail/
>> /usr/local/apache/htdocs/mailman/archives/public/
> 
> 
> Now it seems that apache is pointed at Mailman stuff in yes a third
> place, /usr/local/apache/htdocs/mailman.
>

well, that is just the public side of the webserver so anything that is 
displayed to the world is under /usr/local/apache/htdocs/ and for mailman

/usr/local/apache/htdocs/mailman
the configuration files for the web sever should be nicely tucked into 
/usr/local/apache/conf and /usr/local/apache/conf/mailman/

normal I would put cgi-bins under /usr/local/apache/cgi-bin/ but for mailman I 
was going tuck them under the mailman config section for the webserver under 
/usr/local/apache/conf/mailman


 
> How do you start Mailman? Where is the bin/mailmanctl that starts it?

/etc/rc.d/mailman which unfortunately is piped through systemd.

#! /bin/sh
# Copyright (c) 2000-2001 SuSE GmbH Nuernberg, Germany.
# Copyright (c) 2002 SuSE Linux AG
#
# Author: Heiko Rommel 
#
# /etc/init.d/mailman
#
### BEGIN INIT INFO
# Provides: mailman
# Required-Start: $remote_fs $syslog cron sendmail $named
# Required-Stop:  $remote_fs $syslog
# Default-Start:  3 5
# Default-Stop:   0 1 2 6
# Description:Starts the mailinglist manager Mailman
### END INIT INFO

# Check for missing binaries (stale symlinks should not happen)
ETC_CT=/etc/cron.d/mailman
MM_CT=/usr/lib/mailman/cron/crontab
MM_CTRL=/usr/lib/mailman/bin/mailmanctl
MM_PID=/var/lib/mailman/data/master-qrunner.pid
test -f $MM_CT || exit 5
test -x $MM_CTRL || exit 5


> what is in  in the same bin/ directory? 

Excellent question...

import os
import sys

# some scripts expect this attribute to be in this module
prefix = '/usr/lib/mailman'
exec_prefix = '${prefix}'

# work around a bogus autoconf 2.12 bug
if exec_prefix == '${prefix}':
exec_prefix = prefix


> Are there any lists with
> public archives and if so, are there symlinks in
> /usr/local/apache/htdocs/mailman/archives/public/ and where do they point?

I have done the archives using the same software I wrote in 1996 but the mbox 
et al seems to be in 

www:/etc/postfix # ls -al  
/var/lib/mailman/archives/private/hangout.mbox/hangout.mbox 
-rw-rw-r-- 1 mailman mailman 486238 Nov  5 11:32 
/var/lib/mailman/archives/private/hangout.mbox/hangout.mbox

www:/etc/postfix # ls -al  /var/lib/mailman/archives/public/
total 8
drwxrwsr-x 2 root   mailman 4096 Oct 20 23:43 .
drwxrwsr-x 4 root   mailman 4096 Oct  8  2014 ..
lrwxrwxrwx 1 daemon mailman   41 Oct 20 23:43 hangout -> 
/var/lib/mailman/archives/private/hangout
lrwxrwxrwx 1 daemon mailman   39 Oct 20 16:08 learn -> 
/var/lib/mailman/archives/private/learn
lrwxrwxrwx 1 root   mailman   41 Oct 20 11:14 mailman -> 
/var/lib/mailman/archives/private/mailman



> 
> Do the web server and the qrunners actually reference the same archives,

I would prefer the webserver not to reach the archives that mailman archives at 
all, 
since my real archive is sitting on a remote postgres server.


> data, lists, locks, logs, qfiles and spam directories? Of these, some
> are only used by one or the other, but it's absolutely critical that
> they reference the same archives, data, lists and locks directories.
> 

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.pyt

Re: [Mailman-Users] 64 bit encoding

2015-11-05 Thread Mark Sapiro 
On 11/05/2015 09:55 AM, Ruben Safir wrote:

> www:/etc/postfix # grep  mailman ./*
> ./main.cf:#alias_maps = "hash:/etc/aliases, 
> hash:/var/lib/mailman/data/aliases"
> ./main.cf:alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
> ./master.cf:#mailman   unix  -   n   n   -   -   pipe
> ./master.cf:#  flags=FR user=list 
> argv=/usr/lib/mailman/bin/postfix-to-mailman.py
> ./master.cf.rpmnew:#mailman   unix  -   n   n   -   -   
> pipe
> ./master.cf.rpmnew:#  flags=FR user=list 
> argv=/usr/lib/mailman/bin/postfix-to-mailman.py
> 
> 
> evidently it is under /usr/lib/mailman/bin/ ?


All I see there is a pointer to /var/lib/mailman/data/aliases. What's in
that file?

I'm glad to see the postfix-to-mailman.py trensport is commented out.
See the FAQ at .

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-05 Thread Mark Sapiro 
On 11/05/2015 09:48 AM, Ruben Safir wrote:

>>> /usr/local/apache/conf/mailman/Mailman/Message.py
>>> /usr/local/apache/conf/mailman/Mailman/Message.pyc
>>
> 
> ohh.
> 
> Maybe I did that because I didn't want my cgi-bin directory outside of
> my apache trunk.  It is odd habit I picked up in the last 30 years is
> that I want my webservers restricted to the apache directory tree which
> is /usr/local/apache/
> 
> It didn't occur to be that mailing system binary and script libraries
> would also end up in the apache trunk.


They don't have to, but the real question now is do you have one Mailman
installation in /usr/local/apache/conf/mailman, or do you have a split
installation with some things there and some things in /usr/lib/mailman.


> 
> ServerAdmin ru...@mrbrklyn.com
> DocumentRoot "/usr/local/apache/htdocs/nylxs"
> ScriptAlias /mailman/
> /usr/local/apache/htdocs/mailman/cgi-bin/
> Alias   /mailmanicons/  /usr/local/apache/htdocs/mailman/icons/
> Alias   /pipermail/
> /usr/local/apache/htdocs/mailman/archives/public/
...
> 
> ServerName   lists.mrbrklyn.com
> DocumentRoot "/usr/local/apache/htdocs/mailman/"
> ScriptAlias /mailman/
> /usr/local/apache/htdocs/mailman/cgi-bin/
> Alias   /mailmanicons/
> /usr/local/apache/htdocs/mailman/icons/
> Alias   /pipermail/
> /usr/local/apache/htdocs/mailman/archives/public/


Now it seems that apache is pointed at Mailman stuff in yes a third
place, /usr/local/apache/htdocs/mailman.

How do you start Mailman? Where is the bin/mailmanctl that starts it?
what is in paths.py in the same bin/ directory? Are there any lists with
public archives and if so, are there symlinks in
/usr/local/apache/htdocs/mailman/archives/public/ and where do they point?

Do the web server and the qrunners actually reference the same archives,
data, lists, locks, logs, qfiles and spam directories? Of these, some
are only used by one or the other, but it's absolutely critical that
they reference the same archives, data, lists and locks directories.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-05 Thread Ruben Safir 
On 11/05/2015 12:24 PM, Mark Sapiro wrote:
> On 11/05/2015 08:41 AM, Ruben Safir wrote:
>>
>> Which file am I patching?  Is this a normal setup?  I pulled it from
>> opensuse.
>>
>>
>> ruben@www:~> locate Mailman/Message.py
>> /usr/lib/mailman/Mailman/Message.py
>> /usr/lib/mailman/Mailman/Message.pyc
> 
> The above two are probably what you want.
> /usr/lib/mailman/Mailman/Message.py is the source to patch. After you
> apply the patch and restart Mailman, Python will automatically detect
> that the .py is newer and recompile it into the .pyc.
> 
> 
>> /usr/local/apache/conf/mailman/Mailman/Message.py
>> /usr/local/apache/conf/mailman/Mailman/Message.pyc
> 

ohh.

Maybe I did that because I didn't want my cgi-bin directory outside of
my apache trunk.  It is odd habit I picked up in the last 30 years is
that I want my webservers restricted to the apache directory tree which
is /usr/local/apache/

It didn't occur to be that mailing system binary and script libraries
would also end up in the apache trunk.



ServerAdmin ru...@mrbrklyn.com
DocumentRoot "/usr/local/apache/htdocs/nylxs"
ScriptAlias /mailman/
/usr/local/apache/htdocs/mailman/cgi-bin/
Alias   /mailmanicons/  /usr/local/apache/htdocs/mailman/icons/
Alias   /pipermail/
/usr/local/apache/htdocs/mailman/archives/public/
ServerName www.nylxs.com
DirectoryIndex index.html
PerlModule Embperl
Embperl_UseEnvon
ErrorLog logs/nylxs_error_log
CustomLog logs/nylxs_access_log common

   Options Indexes ExecCGI
   DirectoryIndex index.html
   
   SetHandler perl-script
#  PerlResponseHandler URL_BLOCK
   PerlHandler Embperl
   
   AllowOverride None
   Order allow,deny
   Allow from all




ServerName   lists.mrbrklyn.com
DocumentRoot "/usr/local/apache/htdocs/mailman/"
ScriptAlias /mailman/
/usr/local/apache/htdocs/mailman/cgi-bin/
Alias   /mailmanicons/
/usr/local/apache/htdocs/mailman/icons/
Alias   /pipermail/
/usr/local/apache/htdocs/mailman/archives/public/


"
ErrorLog logs/mailman_error_log
TransferLog  logs/mailman_access_log

 order allow,deny
 allow from all



order allow,deny
allow from all



Options +FollowSymLinks
order allow,deny
allow from all





> This is very strange. I've never seen anything like it. My best guess is
> that for some  reason, the openSUSE package installs a separate Mailman/
> directory for use by the web server. If that is the case, this one
> doesn't need to be patched because the patch doesn't affect anything in
> the web UI.
> 
> To be sure, I'd need to see the apache configuration, the MTA
> configuration and the contents of the directories.
> 
> I did quickly look at
> ,
> ,
> etc. and they all refer to /usr/lib/mailman so I have no idea what
> /usr/local/apache/conf/mailman/ is about.
> 
> The bottom line is the Message.py you need to patch is the one that's
> imported by the qrunners, IncomingRunner and OutgoingRunner in
> particular.  Is there even a
> /usr/local/apache/conf/mailman/Mailman/Queue/ directory at all?
> 
> If the two Message.py files are the same, it wouldn't hurt to patch both.
> 

--
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] 64 bit encoding

2015-11-05 Thread Ruben Safir 
On 11/05/2015 12:31 PM, Mark Sapiro wrote:
> On 11/05/2015 08:41 AM, Ruben Safir wrote:
>>
>> Which file am I patching?  Is this a normal setup?  I pulled it from
>> opensuse.
>>
>>
>> ruben@www:~> locate Mailman/Message.py
>> /usr/lib/mailman/Mailman/Message.py
>> /usr/lib/mailman/Mailman/Message.pyc
> 
> The above two are probably what you want.
> /usr/lib/mailman/Mailman/Message.py is the source to patch. After you
> apply the patch and restart Mailman, Python will automatically detect
> that the .py is newer and recompile it into the .pyc.
> 
> 
>> /usr/local/apache/conf/mailman/Mailman/Message.py
>> /usr/local/apache/conf/mailman/Mailman/Message.pyc
> 
> This is very strange. I've never seen anything like it. My best guess is
> that for some  reason, the openSUSE package installs a separate Mailman/
> directory for use by the web server. If that is the case, this one
> doesn't need to be patched because the patch doesn't affect anything in
> the web UI.
> 
> To be sure, I'd need to see the apache configuration, the MTA
> configuration and the contents of the directories.
> 
> I did quickly look at
> ,
> ,
> etc. and they all refer to /usr/lib/mailman so I have no idea what
> /usr/local/apache/conf/mailman/ is about.
> 
> The bottom line is the Message.py you need to patch is the one that's
> imported by the qrunners, IncomingRunner and OutgoingRunner in
> particular.  Is there even a
> /usr/local/apache/conf/mailman/Mailman/Queue/ directory at all?
> 
> If the two Message.py files are the same, it wouldn't hurt to patch both.
> 
www:/etc/postfix # grep mailman main.cf
#alias_maps = "hash:/etc/aliases, hash:/var/lib/mailman/data/aliases"
alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases

www:/etc/postfix # grep  mailman ./*
./main.cf:#alias_maps = "hash:/etc/aliases, hash:/var/lib/mailman/data/aliases"
./main.cf:alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
./master.cf:#mailman   unix  -   n   n   -   -   pipe
./master.cf:#  flags=FR user=list 
argv=/usr/lib/mailman/bin/postfix-to-mailman.py
./master.cf.rpmnew:#mailman   unix  -   n   n   -   -   pipe
./master.cf.rpmnew:#  flags=FR user=list 
argv=/usr/lib/mailman/bin/postfix-to-mailman.py


evidently it is under /usr/lib/mailman/bin/ ?

--
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] 64 bit encoding

2015-11-05 Thread Mark Sapiro 
On 11/05/2015 08:41 AM, Ruben Safir wrote:
> 
> Which file am I patching?  Is this a normal setup?  I pulled it from
> opensuse.
> 
> 
> ruben@www:~> locate Mailman/Message.py
> /usr/lib/mailman/Mailman/Message.py
> /usr/lib/mailman/Mailman/Message.pyc

The above two are probably what you want.
/usr/lib/mailman/Mailman/Message.py is the source to patch. After you
apply the patch and restart Mailman, Python will automatically detect
that the .py is newer and recompile it into the .pyc.


> /usr/local/apache/conf/mailman/Mailman/Message.py
> /usr/local/apache/conf/mailman/Mailman/Message.pyc

This is very strange. I've never seen anything like it. My best guess is
that for some  reason, the openSUSE package installs a separate Mailman/
directory for use by the web server. If that is the case, this one
doesn't need to be patched because the patch doesn't affect anything in
the web UI.

To be sure, I'd need to see the apache configuration, the MTA
configuration and the contents of the directories.

I did quickly look at
,
,
etc. and they all refer to /usr/lib/mailman so I have no idea what
/usr/local/apache/conf/mailman/ is about.

The bottom line is the Message.py you need to patch is the one that's
imported by the qrunners, IncomingRunner and OutgoingRunner in
particular.  Is there even a
/usr/local/apache/conf/mailman/Mailman/Queue/ directory at all?

If the two Message.py files are the same, it wouldn't hurt to patch both.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-04 Thread Mark Sapiro 
On 11/04/2015 04:27 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
> 
>  > +email.Charset.add_charset('utf-8',
>  > +  email.Charset.SHORTEST,
>  > +  email.Charset.QP,
>  > +  'utf-8')
> 
> I don't know if this actually is available, let alone whether it would
> work (might affect headers, too, and of course elderly recipient
> systems might throw a tantrum), but how about Content-Transfer-Encoding
> of 8bit?


I did test it and it does work. I didn't think of it at the time, but
replacing the body encoding (email.Charset.QP in the above patch) with
None, i.e.

email.Charset.add_charset('utf-8',
  email.Charset.SHORTEST,
  None,
  'utf-8')

also works and produces a message with

Content-Transfer-Encoding: 8bit

It doesn't affect headers. The arguments are character set, header
encoding, body encoding, output codec. The only thing the add_charset in
the patch changes from the default is the body encoding argument.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-04 Thread Stephen J. Turnbull 
Mark Sapiro writes:

 > +email.Charset.add_charset('utf-8',
 > +  email.Charset.SHORTEST,
 > +  email.Charset.QP,
 > +  'utf-8')

I don't know if this actually is available, let alone whether it would
work (might affect headers, too, and of course elderly recipient
systems might throw a tantrum), but how about Content-Transfer-Encoding
of 8bit?

--
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] 64 bit encoding

2015-11-04 Thread Mark Sapiro 
On 11/04/2015 09:16 AM, Ruben Safir wrote:
> 
> Oh thank you!  Because I was reading that it is triggered by header
> msg_header or msg_footer, but nobody really know what that was exactly.
>  It didn't match any settings in the interface.  I greatly appreciate this


To be more specific, if a list specifies a msg_header and/or a
msg_footer (in the list admin Non-digest options), Mailman will decode
the message body of a text/plain message in order to prepend the
msg_header and/or append the msg_footer. Then the message body is
re-encoded by the email library when Mailman sets the new body.

Thus, if msg_header and msg_footer are both empty, the recoding won't
happen, but when it does, it is controlled by the
email.Charset.add_charset() settings for the character set of the body,
and the patch I gave you changes the body encoding from base64 to
quoted-printable.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] 64 bit encoding

2015-11-04 Thread Ruben Safir 
On 11/04/2015 12:10 PM, Mark Sapiro wrote:
>  You can change the
> encoding for UTF-8 message bodies with the following patch to
> Mailman/Message.py, but if your messages are not predominate


Oh thank you!  Because I was reading that it is triggered by header
msg_header or msg_footer, but nobody really know what that was exactly.
 It didn't match any settings in the interface.  I greatly appreciate this

Ruben
--
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] 64 bit encoding

2015-11-04 Thread Mark Sapiro 
On 11/03/2015 06:42 PM, Ruben Safir wrote:
> I'm converting my mailing lists from majordomo to mailman using postfix.
>  A lot of little issues have cropped up but the biggest problem I have
> currently is that it seems that mailman is converting files to 64 bit
> which is screwing up my home cooked archives but good.


Actually, Mailman is sending messages in UTF-8 character set as base64
encoded. Actually, many MUAs will also base64 encode UTF-8 message bodies.

This is actually a python email library thing. You can change the
encoding for UTF-8 message bodies with the following patch to
Mailman/Message.py, but if your messages are not predominately ascii
text, you won't like the result any better.

diff -u 2.1/Mailman/Message.py 21/Mailman/Message.py
--- 2.1/Mailman/Message.py  2014-05-17 18:34:20.240159000 -0700
+++ 21/Mailman/Message.py   2015-11-04 08:50:31.772899979 -0800
@@ -36,6 +36,10 @@
 from Mailman import mm_cfg
 from Mailman import Utils

+email.Charset.add_charset('utf-8',
+  email.Charset.SHORTEST,
+  email.Charset.QP,
+  'utf-8')
 COMMASPACE = ', '

 mo = re.match(r'([\d.]+)', email.__version__)

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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