Re: [Mailman-Users] Migration Problem

2015-01-08 Thread Dennis Putnam 
On 1/8/2015 7:06 PM, Mark Sapiro wrote:
> On 01/08/2015 03:23 PM, Dennis Putnam wrote:
>
>> However,
>> the only step I did not do yet is the URL change (I am testing a
>> kickstart file) so my last problem may be due to that but I am thinking
>> not. When I access the listinfo, no lists are published but I can see
>> them in /var/lib/mailman/lists.
>
> It probably is the URL used to visit the page. See the FAQ at
> 
>
>
>> Also the admin pages are not password
>> projected. So either I did not copy something from the old server
>> (CentOS 6 (32 bit)) or whatever I did copy from 2.1.12 (32 bit) is not
>> compatible with 2.1.15 (64 bit).
>
> A much more likely explanation is you have an authentication cookie in
> your browser. There is no configuration or data (other than the cookie)
> that would cause authentication for the admin pages to be bypassed.
>
>
>> There is probably a 'withlist' command
>> that fixes all this but that command cannot be run in the kickstart file
>> so I'd rather copy the appropriate files from the old server if
>> possible. Is there something other than /var/lib/mailman that I should
>> have copied? Perhaps something in /usr/lib/mailman.
>
> Probably not.
>
>
>> P.S. I still have to figure out how to migrate my custom changes which
>> are in /usr/lib/mailman.
>
> The moral here is whenever you make a change to any Mailman module, you
> should keep a diff that can be reapplied as a patch when you upgrade.
>
> At this point, if you don't have that, you could download the 2.1.12
> source tarball from  or
> , unpack it and diff it against your
> 2.1.12 /usr/lib/mailman to see what you changed. You may have to sift a
> bit to separate your changes from any RedHat package changes, but you
> should be able to work it out.
>
>
Thanks again for the reply. I doubt it is a cookie cache issue since I
tried the access from the newly installed user and browser but I'll play
with it some more. I'll see if I can run the change URL script in the
kickstart file. I am hoping that mailman does not need to be running to
do that. I do have the patch files, but I question if they are directly
compatible with this version so I haven't tried that yet.



signature.asc
Description: OpenPGP digital signature
--
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] Migration Problem

2015-01-08 Thread Mark Sapiro 
On 01/08/2015 03:23 PM, Dennis Putnam wrote:

> However,
> the only step I did not do yet is the URL change (I am testing a
> kickstart file) so my last problem may be due to that but I am thinking
> not. When I access the listinfo, no lists are published but I can see
> them in /var/lib/mailman/lists.


It probably is the URL used to visit the page. See the FAQ at



> Also the admin pages are not password
> projected. So either I did not copy something from the old server
> (CentOS 6 (32 bit)) or whatever I did copy from 2.1.12 (32 bit) is not
> compatible with 2.1.15 (64 bit).


A much more likely explanation is you have an authentication cookie in
your browser. There is no configuration or data (other than the cookie)
that would cause authentication for the admin pages to be bypassed.


> There is probably a 'withlist' command
> that fixes all this but that command cannot be run in the kickstart file
> so I'd rather copy the appropriate files from the old server if
> possible. Is there something other than /var/lib/mailman that I should
> have copied? Perhaps something in /usr/lib/mailman.


Probably not.


> P.S. I still have to figure out how to migrate my custom changes which
> are in /usr/lib/mailman.


The moral here is whenever you make a change to any Mailman module, you
should keep a diff that can be reapplied as a patch when you upgrade.

At this point, if you don't have that, you could download the 2.1.12
source tarball from  or
, unpack it and diff it against your
2.1.12 /usr/lib/mailman to see what you changed. You may have to sift a
bit to separate your changes from any RedHat package changes, but you
should be able to work it out.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
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] Migration Problem

2015-01-08 Thread Dennis Putnam 
On 1/7/2015 10:18 PM, Mark Sapiro wrote:
> On 01/07/2015 06:44 PM, Dennis Putnam wrote:
>> I am trying to migrate mailman from CentOS 6 (32 bit) to CentOS 7 (64
>> bit) and have run into a problem. I am having problems with the web
>> pages. They all get a permissions denied error and the log shows:
>>
>> [Wed Jan 07 21:37:50.331181 2015] [authz_core:error] [pid 5012] [client
>> ::1:60272] AH01630: client denied by server configuration:
>> /usr/lib/mailman/cgi-bin/listinfo
>
> And CentOS 7 has Apache 2.4?
Yes. 2.4.6-17 to be precise.
>
>
>> Here is my mailman.conf file:
>> ---
>> # Directives for the mailman web interface
>>
>> Alias /pipermail/ "/var/lib/mailman/archives/public/"
>> ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin/"
>>
>> # For the archives
>>
>> 
>> Options +FollowSymLinks
>> Require all granted
>> 
>
> You probably also need
>
> 
> Options ExecCGI
> Require all granted
> 
>
>
> See .
>
>
Thanks for the reply. Yep, that was it. Odd that the install package
included the directive for the archives but not the scripts. However,
the only step I did not do yet is the URL change (I am testing a
kickstart file) so my last problem may be due to that but I am thinking
not. When I access the listinfo, no lists are published but I can see
them in /var/lib/mailman/lists. Also the admin pages are not password
projected. So either I did not copy something from the old server
(CentOS 6 (32 bit)) or whatever I did copy from 2.1.12 (32 bit) is not
compatible with 2.1.15 (64 bit). There is probably a 'withlist' command
that fixes all this but that command cannot be run in the kickstart file
so I'd rather copy the appropriate files from the old server if
possible. Is there something other than /var/lib/mailman that I should
have copied? Perhaps something in /usr/lib/mailman.

P.S. I still have to figure out how to migrate my custom changes which
are in /usr/lib/mailman.




signature.asc
Description: OpenPGP digital signature
--
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] All my lists quit working!

2015-01-08 Thread Larry Stone 

On Jan 8, 2015, at 7:49 AM, Jan Steinman  wrote:

> First, the bad news: Mac OS X 10.6.8. Yea, I've read Mark's dire warning. 
> Please don't shoot me. I'm hoping this is a generic sort of problem.
> 

OS X Server? or OS X (client)?

> When I send a message to ANY of the dozen or so lists I host, my MTA 
> immediately says it doesn't know the addressee.

Log entries please.

> /etc/postfix/main.cf contains the following lines:
>   virtual_alias_maps = 
> hash:/etc/postfix/virtual,hash:/var/mailman/data/virtual-mailman,hash:/etc/postfix/virtual_users
>   alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
> 
Please provide your postconf -n . That will show how postfix is actually 
configured, not how you think it is configured by providing just a few lines 
out of main.cf. 

> The file "/var/mailman/data/virtual-mailman" is empty.
> 
> The file "/var/mailman/data/aliases" has all my lists in it.
> 
> The corresponding ".db" files for those two have the same timestamp as their 
> corresponding text files.
> 
> Here is an example of what is in the "aliases" file:
> 
>   # STANZA START: beaders
>   # CREATED: Wed Jan  7 13:06:39 2015
>   beaders: "|/usr/share/mailman/mail/mailman post beaders"
>   beaders-admin:   "|/usr/share/mailman/mail/mailman admin beaders"
>   beaders-bounces: "|/usr/share/mailman/mail/mailman bounces beaders"
>   beaders-confirm: "|/usr/share/mailman/mail/mailman confirm beaders"
>   beaders-join:"|/usr/share/mailman/mail/mailman join beaders"
>   beaders-leave:   "|/usr/share/mailman/mail/mailman leave beaders"
>   beaders-owner:   "|/usr/share/mailman/mail/mailman owner beaders"
>   beaders-request: "|/usr/share/mailman/mail/mailman request beaders"
>   beaders-subscribe:   "|/usr/share/mailman/mail/mailman subscribe 
> beaders"
>   beaders-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe 
> beaders"
>   # STANZA END: beaders
> 
> I run "dumpdb aliases.db" and get:
> 
>   [- start marshal file -] Traceback (most recent call last): 
> File "/usr/share/mailman/bin/dumpdb", line 156, in  msg = main()
> File "/usr/share/mailman/bin/dumpdb", line 136, in main obj = load(fp) 
> ValueError: bad marshal data 

Mailman’s dumpdb is for Python databases. aliases.db is not a Python database.

> Does this mean that "dumpdb" is bad, or does it mean that "aliases.db" is 
> bad, or neither

It means dumpdb is the wrong tool for dumping aliases.db.

> Any help (despite my using an unsupported version) appreciated!

Show log entries and postconf -n as requested above as it looks correct at 
first glance. Also, check your master.cf to see if there are any overrides (-o) 
on your smtpd entry.

-- 
Larry Stone
lston...@stonejongleux.com
http://www.stonejongleux.com/



--
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] All my lists quit working!

2015-01-08 Thread Jan Steinman 
First, the bad news: Mac OS X 10.6.8. Yea, I've read Mark's dire warning. 
Please don't shoot me. I'm hoping this is a generic sort of problem.

When I send a message to ANY of the dozen or so lists I host, my MTA 
immediately says it doesn't know the addressee.

/etc/postfix/main.cf contains the following lines:
virtual_alias_maps = 
hash:/etc/postfix/virtual,hash:/var/mailman/data/virtual-mailman,hash:/etc/postfix/virtual_users
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases

The file "/var/mailman/data/virtual-mailman" is empty.

The file "/var/mailman/data/aliases" has all my lists in it.

The corresponding ".db" files for those two have the same timestamp as their 
corresponding text files.

Here is an example of what is in the "aliases" file:

# STANZA START: beaders
# CREATED: Wed Jan  7 13:06:39 2015
beaders: "|/usr/share/mailman/mail/mailman post beaders"
beaders-admin:   "|/usr/share/mailman/mail/mailman admin beaders"
beaders-bounces: "|/usr/share/mailman/mail/mailman bounces beaders"
beaders-confirm: "|/usr/share/mailman/mail/mailman confirm beaders"
beaders-join:"|/usr/share/mailman/mail/mailman join beaders"
beaders-leave:   "|/usr/share/mailman/mail/mailman leave beaders"
beaders-owner:   "|/usr/share/mailman/mail/mailman owner beaders"
beaders-request: "|/usr/share/mailman/mail/mailman request beaders"
beaders-subscribe:   "|/usr/share/mailman/mail/mailman subscribe 
beaders"
beaders-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe 
beaders"
# STANZA END: beaders

I run "dumpdb aliases.db" and get:

[- start marshal file -] Traceback (most recent call last): 
File "/usr/share/mailman/bin/dumpdb", line 156, in  msg = main()
File "/usr/share/mailman/bin/dumpdb", line 136, in main obj = load(fp) 
ValueError: bad marshal data 

Does this mean that "dumpdb" is bad, or does it mean that "aliases.db" is bad, 
or neither?

Any help (despite my using an unsupported version) appreciated!

I promise to jump on the 3.0 bandwagon as soon as I can. I hate what Apple did 
to this.

 ...the exploitation of animals for milk was already an established 
practice at the time farming arrived in Britain in the late fifth millennium 
B.C. -- M.S. Copley
 Jan Steinman, EcoReality Co-op 

--
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] custon mm page

2015-01-08 Thread Mark Sapiro 
On 01/07/2015 12:50 PM, JB wrote:
> what file name do I use and where do I upload a custom member options login 
> page?


The options login page is built on the fly by the loginpage() function
in the $prefix/Mailman/Cgi/options.py module. There is no template
involved for the login page. You have to modify it in the source code
and the mods apply to all lists unless you test for something to trigger
different behavior.

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

2015-01-08 Thread Mark Sapiro 
On 01/07/2015 10:50 AM, JB wrote:
> 
> I have finished setting up the list and then I went into the TOPICS section 
> and set up three topics (fishing, books, trains).  I do not see anywhere that 
> allows users to subscribe to specific topics nor do I know how to send out an 
> email and indicate which topic(s) it is pertaining to.


Users subscribe to topics on their respective user options pages.

When you set up the topics you provided a regexp to match against to
determine if a message is in that topic. This regexp is matched against
the Subject: header of the message, the Keywords: header if any.

Also in the Topics setup is a setting for topics_bodylines_limit.
Mailman will also look at up to this many of the initial body lines of
the message looking for pseudo Subject: and Keywords: headers. This body
lines search stops when the limit is reached or a non-header like line
is encountered.

Say the regexp for the 'books' topic is 'books?'. A message will match
the books topic if for example the Subject: contains the word 'book' or
'books' or the first body line is for example 'Keywords: books'.


> I would like to have a subscribe page (or link) that allows the user to sign 
> up for the list and indicate which topics he wants to receive all in one 
> place.  I really want to use custom skinned pages to do this.  I know how to 
> write the pages for a simple subscribe/unsubscribe page but this whole mess 
> with topics is throwing me.


Making Mailman support a single CGI transaction to both subscribe a user
and specify topics for that subscription would require creating a new
CGI and making significant source changes. The major hurdles are the
fact that subscribing is a request that normally requires confirmation,
approval or both, and topic subscription can only be done for an
existing user.

The current process has a mechanism for carrying things like the user's
real name and preferred language with the subscription request, but that
would have to be extended to carry topics as well.

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