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

[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 was setup long ago and predates my joining the
company by 15+ years. In the case of mailman it looks like passwords for
list owners are tied to the software. We have many lists (1000+) so was
hoping I could avoid getting into the business of password resets if
possible. My goal would be to add a "I forgot my password" button to the
admin login page that would kind of force that monthly password reminder
right then.  I know list members have several options but from what I have
seen owners do not.

Is that even possible?


Chris 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/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] 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 credentials so users had no real excuse not to know
> their passwords. This was setup long ago and predates my joining the
> company by 15+ years. In the case of mailman it looks like passwords for
> list owners are tied to the software. We have many lists (1000+) so was
> hoping I could avoid getting into the business of password resets if
> possible. My goal would be to add a "I forgot my password" button to the
> admin login page that would kind of force that monthly password reminder
> right then.  I know list members have several options but from what I have
> seen owners do not.
> 
> Is that even possible?


In MM 2.1.x list owner/moderator passwords, as opposed to the list
member password for the owner if the owner is a list member (not
required), are kept in encrypted form and are not retrievable as plain
text, thus a reminder is not possible. A 'reset' function with a dialog
with the owner/moderator email address(es) is possible, but such a thing
has not been implemented.

See the FAQs at  and
, and Mailman's 'bin/change_pw --help'.

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

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 message.

Does it have headers like

X-BeenThere: l...@example.com
X-Mailman-Version: 2.1.20

If not, it didn't come from Mailman.

-- 
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] 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 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: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

[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
--
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] 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.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] 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 header nor does the footer
> show up.


There are two possibilities.

1) You are looking at a message that didn't come from the list. See my
reply in another thread at
.

2) The msg_header and msg_footer are there as separate MIME parts
because the post after any content filtering was not a simple text/plain
message and your MUA is not showing them to you. 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 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