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 somewh

Re: [Mailman-Users] Prefix in Subject line anomaly??

2015-11-05 Thread Mark Sapiro
On 11/05/2015 01:53 PM, am wrote: > Yes, I am looking at the Welcome to the list message. I see: Only list posts have the subject_prefix added. Welcome and other administrative messages do not. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use

Re: [Mailman-Users] Another anomaly? Header is not showing

2015-11-05 Thread Mark Sapiro
On 11/05/2015 11:36 AM, am via Mailman-Users wrote: > In the mailing list setup (v.2.1.20) there is a section in non-digest to > add Header info: msg_header Option > > I used it in the hopes that I can put something at the top of EVERY > message. > > But nothing appears in the messages - neither

Re: [Mailman-Users] Prefix in Subject line anomaly??

2015-11-05 Thread Mark Sapiro
On 11/05/2015 11:11 AM, am via Mailman-Users wrote: > Prefix for Subject Line not showing in email subject line, but it DOES show > in the archive. Are you looking at a message actually received from the list and not one received by direct To:, Cc: or Bcc:? Examine the complete headers of the me

[Mailman-Users] Prefix in Subject line anomaly??

2015-11-05 Thread am via Mailman-Users
Prefix for Subject Line not showing in email subject line, but it DOES show in the archive. ​ The prefix is [CaucusPlanners] ​Mailman ​ version 2.1.20... ​ help please... C-L -- Mailman-Users mailing list Mailman-Users@python.org https://mail

[Mailman-Users] Another anomaly? Header is not showing

2015-11-05 Thread am via Mailman-Users
In the mailing list setup (v.2.1.20) there is a section in non-digest to add Header info: msg_header Option I used it in the hopes that I can put something at the top of EVERY message. But nothing appears in the messages - neither header nor does the footer show up. Help, please... C-L

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/m

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

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 >

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

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

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 la

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.

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.

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. /us

Re: [Mailman-Users] List Owner Password Reminder

2015-11-05 Thread Mark Sapiro
On 11/04/2015 02:05 PM, Christopher A Puchalski wrote: > > Is there a "self service" password reminder for list owners? No. > I am in the process of trying to deploy mailman within my company to > replace a old majordomo instance. Majordomo access/authentication was > managed by local LDAP cre

[Mailman-Users] List Owner Password Reminder

2015-11-05 Thread Christopher A Puchalski
Is there a "self service" password reminder for list owners? I am in the process of trying to deploy mailman within my company to replace a old majordomo instance. Majordomo access/authentication was managed by local LDAP credentials so users had no real excuse not to know their passwords. This