Re: [Mailman-Users] Some lists no longer archiving new messages

[Beu, Ed (DOA)]

Thank you Mark, just had to change owner from Root to Mailman, deleted the 
shunted messages that I had already imported manually and ran the unshunt 
command on the rest!

Worked like a charm! 

Regards,
~Ed

Ed Beu, System Programmer
Dept. of Administration, ETS
(907)269-6790 ed@alaska.gov

-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska@python.org] 
On Behalf Of Mark Sapiro
Sent: Saturday, September 03, 2016 7:44 AM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] Some lists no longer archiving new messages

On 09/02/2016 03:31 PM, Beu, Ed (DOA) wrote:
> 
> The few lists that I have 'imported' mail from Thunderbird into Mailman 
> archives will not archive new messages.


I suspect a permissions issue on archives/private/LIST.mbox/LIST.mbox,
but there should be errors and tracebacks in mailman's error log and
shunted messages in the shunt queue. If you have the RedHat package,
these are /var/log/mailman/error and /var/spool/mailman/shunt respectively.

If you can't figure out what the problem is from the error log, post the
info here. Once you have fixed the problem you can run unshunt
(/usr/lib/mailman/bin/unshunt) to archive the shunted messages, but
first you may want to examine them with /usr/lib/mailman/bin/show_qfiles
to ensure that all of them should be unshunted and there are none from
older, unrelated errors.

-- 
Mark Sapiro <m...@msapiro.net>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] Some lists no longer archiving new messages

[Beu, Ed (DOA)]

Hi,

The few lists that I have 'imported' mail from Thunderbird into Mailman 
archives will not archive new messages.

I have imported all the messages again, and I have imported one message at a 
time - then I've run the following command:

/bin/arch -wipe listname

I've have also run: bin/arch listname 
/var/lib/mailman/archives/private/listname.mbox/listname.mbox

After doing so, new messages sent to the list are not archived and do not show 
up in the mbox file.


We're running Mailman v2.1.12 on Centos 6.7 and using Postfix 2.6.6..

Thanks in advance for any assistance!

~Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/





--
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] unique Message-IDs

[Beu, Ed (DOA)]

-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska@python.org] 
On Behalf Of Mark Sapiro
Sent: Thursday, August 25, 2016 7:48 AM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] unique Message-IDs

On 08/24/2016 11:20 AM, Beu, Ed (DOA) wrote:
> 
> We've run into a situation whereas our email archiving system is puking on 
> mail sent from large Mailman lists due to the Message-IDs all being the same 
> on each individual message.
> 
> I found the following article and tried it, without any success.
> 
> https://mail.python.org/pipermail/mailman-users/2011-November/072525.html


>>Did you try just deleting the Message-ID or replacing it with a Mailman
>>Generated one?

I tried both methods, both did not work.

>>If you are not VERPing or personalizing deliveries, replacing the
>>Message-ID will not be completely effective because the message with the
>>replaced Message-ID will still be sent to chunks with multiple
>>recipients. Whether deleting the Message-ID will be effective or not
>>will depend on when in its processing the MTA adds its own Message-ID.

With VERP turned on it presented issues with our Spam Filter, so not an option.

> Any other suggestions?


>>Enable verp by putting

>>VERP_DELIVERY_INTERVAL = 1

>>in mm_cfg.py and then replace the Message-ID with a Mailman generated
>>one per
>><https://mail.python.org/pipermail/mailman-users/2011-November/072525.html>


>>or maybe just fix your archiving system.

Plans are in the works for a replacement (O365)! 

>>Note that replacing the Message-ID in this way is a violation of mail
>>RFCs and I don't recommend it.

Understood!

>>What happens if a local user sends a message with multiple To:, Cc:
>>and/or Bcc: recipients. Doesn't that confuse your archiving system too?
>>What do you do about that?

I don't run the archiving system so not sure.  The archiving admin mentioned he 
was manually changing MSG-IDs the other day.

Thanks, Ed

-- 
Mark Sapiro <m...@msapiro.net>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/
--
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] unique Message-IDs

[Beu, Ed (DOA)]

Hello Mark,

We've run into a situation whereas our email archiving system is puking on mail 
sent from large Mailman lists due to the Message-IDs all being the same on each 
individual message.

I found the following article and tried it, without any success.

https://mail.python.org/pipermail/mailman-users/2011-November/072525.html

We're running Mailman v2.1.12 on Centos 6.7 and using Postfix 2.6.6..

Any other suggestions?

Thx, Ed


Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/





--
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] display members moderator flag

[Beu, Ed (DOA)]

Hi Mark,

We've discovered that if the Unsubscribe_Policy is set to Yes (1), the 
moderator can unsubscribe members without the members input! The member simply 
gets a notice that they've been unsubscribed.

~Ed

Ed Beu, System Programmer
Dept. of Administration, ETS
(907)269-6790 ed@alaska.gov


-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: Thursday, August 04, 2016 10:45 AM
To: Beu, Ed (DOA) <ed@alaska.gov>; mailman-users@python.org
Subject: Re: [Mailman-Users] display members moderator flag

On 08/04/2016 09:39 AM, Beu, Ed (DOA) wrote:
> 
> Some of these 'list admins' are used to being able to 'unsubscribe' members 
> without the member having to confirm via the email confirmation. Our old 
> system would unsubscribe the member and send a notice that they were removed 
> from the list. 
> 
> Other than relying on the bounce mechanism or by knowing the members password 
> to remove them, is there any way for a list moderator to accomplish this 
> task? Perhaps access to the 'Membership List' only?


The list moderator password only allows access to the admindb web UI.
Allowing access to selected admin UI functions with that password would
require non-trivial source changes.

If you are willing to create your own web page with it's own
authentication, see <https://wiki.list.org/x/4030648> and the members.c
program linked therefrom for a way to execute Mailman command scripts,
e.g. bin/remove_members, from a web application.

-- 
Mark Sapiro <m...@msapiro.net>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] display members moderator flag

[Beu, Ed (DOA)]

Thank you Mark for all the different options, very useful!

I have another question, which may require a new thread, but here goes.

We have chosen to not give our list managers "Administrative" access to their 
lists. We feel there are too many options that could be changed that could be 
detrimental to a list. Therefore we're only giving them the Moderator password 
so that they can use the 'who' command to obtain membership reports on their 
own.

Some of these 'list admins' are used to being able to 'unsubscribe' members 
without the member having to confirm via the email confirmation. Our old system 
would unsubscribe the member and send a notice that they were removed from the 
list. 

Other than relying on the bounce mechanism or by knowing the members password 
to remove them, is there any way for a list moderator to accomplish this task? 
Perhaps access to the 'Membership List' only?

Thanks in advance for your assistance!

~Ed


Ed Beu, System Programmer
Dept. of Administration, ETS
(907)269-6790 ed@alaska.gov

-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska@python.org] 
On Behalf Of Mark Sapiro
Sent: Wednesday, August 03, 2016 4:24 PM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] display members moderator flag

On 08/03/2016 10:46 AM, Beu, Ed (DOA) wrote:
> 
> Other than browsing through the membership listing in the GUI and looking for 
> unchecked mod settings, to identify who may post unmoderated, is there a 
> script that would display this type of information?


Beginning with Mailman 2.1.21, Mailman's bin/list_members script has
options to list just the moderated or unmoderated members.

There is also a withlist script at
<https://www.msapiro.net/scripts/list_mod.py> (mirrored at
<https://fog.ccsf.edu/~msapiro/scripts/list_mod.py>) that can do this.


> I've searched through archives and did a fair share of google searches, but 
> not finding anything specific to this. Perhaps a feature request to make the 
> membership listing sort capable some day would satisfy my needs.


There is also a script at
<https://www.msapiro.net/scripts/mailman-subscribers.py> (mirror
<https://fog.ccsf.edu/~msapiro/scripts/mailman-subscribers.py>) that can
run on your work station and screen scrape the admin Membership List and
write a CSV which can be imported to a spreadsheet ans searched/sorted
as you like.

-- 
Mark Sapiro <m...@msapiro.net>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] display members moderator flag

[Beu, Ed (DOA)]

Hello,

We're using Mailman v2.1.12 on Centos 6.7, and we just went production with it 
last Sunday, July 31.

Other than browsing through the membership listing in the GUI and looking for 
unchecked mod settings, to identify who may post unmoderated, is there a script 
that would display this type of information?

I've searched through archives and did a fair share of google searches, but not 
finding anything specific to this. Perhaps a feature request to make the 
membership listing sort capable some day would satisfy my needs.

Thanks in advance for any recommendations or suggestions.

~Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
Anchorage, AK 99501-1677

" http://www.doa.alaska.gov/ets/





--
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] migrating current list links to mailman

[Beu, Ed (DOA)]

We've removed the redirect and created the jl.htm files where Apache can see 
them and display the HTML message. This works as planned.

Thx, Ed

-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska@python.org] 
On Behalf Of Beu, Ed (DOA)
Sent: Tuesday, June 14, 2016 9:35 AM
To: Mark Sapiro <m...@msapiro.net>; mailman-users@python.org
Subject: Re: [Mailman-Users] migrating current list links to mailman

Thanks very much for the information. Good to know I was on the right track, 
but even with your verification and better code, the redirect still takes me to 
the new /listinfo/listname (subscribe) page rather than the new jl.htm page.

I have put the new jl.htm at /var/lib/mailman/lists/listname/jl.htm

And, the redirection code at /etc/httpd/conf.d/mailman.conf
# Uncomment the following line, to redirect queries to /mailman to the 
listinfo page (recommended).
RedirectMatch ^/soalists/(.*)/jl.htm /mailman/listinfo/$1
RedirectMatch ^/mailman[/]*$ /mailman/listinfo
RedirectMatch ^[/]*$ /mailman/listinfo

I suspected the last two lines of RedirectMatch were causing the issue, but I 
get the same result if I remark them out.

Thanks again!
~Ed


-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska@python.org] 
On Behalf Of Mark Sapiro
Sent: Tuesday, June 14, 2016 9:05 AM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] migrating current list links to mailman

On 06/13/2016 11:23 AM, Beu, Ed (DOA) wrote:
> 
> Example:http:/list.domain/lists/listname/jl.htm   
> 
>  http:/list.domain/mailman/listinfo/listname  
>  <Mailman's link>
> 
> We would like some type of redirect in place on the new mailman server that 
> would simply display the new link (so that it can be copied) when someone 
> uses an old bookmark or hyperlink on a different website.


There are various ways to do this depending on what you want the user to
see.

If I understand the URL scheme above something in Apache like

RedirectMatch ^/lists/(.*)/jl.htm  /mailman/listinfo/$1

would serve to redirect http:/list.domain/lists/listname/jl.htm to
http:/list.domain/mailman/listinfo/listname for any 'listname', but if
you actually want to display something to the user, you could create a
replacement lists/listname/jl.htm containing something like

--




List listname - page has moved




Page Moved

The page for the listname list has moved.
The new location is

http:/list.domain/mailman/listinfo/listname.
You will go there automatically in 5 seconds.




--

This will display the page and go to the new page after 5 seconds. You
would need one of these per list. If you want to change the delay,
change '5' to whatever you want in the

 content="5;

line and the

You will go there automatically in 5 seconds.

line. If you want the user to have to click, remove the



lines and the "You will go there automatically" line.


--
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] migrating current list links to mailman

[Beu, Ed (DOA)]

Hello,

This may not be the correct forum for this question, but in hopes that it is, I 
have an HTML type question.

We are planning to replace our current listserv software with Mailman 2.x. Our 
root URL will not be changing, but each lists subscription pages will be 
different.

Example:http:/list.domain/lists/listname/jl.htm   

 http:/list.domain/mailman/listinfo/listname   


We would like some type of redirect in place on the new mailman server that 
would simply display the new link (so that it can be copied) when someone uses 
an old bookmark or hyperlink on a different website.

Our Mailman version is 2.1.20 from Yum, on CentOS 6.7, running Apache & Postfix 
& Mimedefang.

Note: I'm an HTML greenie, so any assistance is greatly appreciated.

Thx, Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/



--
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] Mm_cfg.py not setting attribute

[Beu, Ed (DOA)]

FWIW... the Defaults.py files for Mailman 2.1.20 and 2.1.12 are not identical.



The following statements, including the one I was troubleshooting, do not exist 
in version 2.1.12.


DEFAULT_BOUNCE_NOTIFY_OWNER_ON_BOUNCE_INCREMENT = No

DEFAULT_DMARC_WRAPPED_MESSAGE_TEXT = ''

DEFAULT_EQUIVALENT_DOMAINS = ''

DEFAULT_REGULAR_EXCLUDE_IGNORE = True

DEFAULT_RESPOND_TO_POST_REQUESTS = Yes

DEFAULT_SUBSCRIBE_AUTO_APPROVAL = []

DEFAULT_SUBSCRIBE_OR_INVITE = No




~Ed



-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska@python.org] 
On Behalf Of Mark Sapiro
Sent: Monday, May 23, 2016 6:20 PM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] Mm_cfg.py not setting attribute



On 05/23/2016 05:24 PM, Beu, Ed (DOA) wrote:

>

> We currently have two instances of Mailman running for test purposes. The 
> newlist command along with a customized mm_cfg.py file is producing different 
> results on the two systems.

>

> Configurations are as follows on these two test systems.

>

> T1

> Solaris 10

> Mailman 2.1.20 (csw package)

>

> T2

> CentOS 6.7 (Final)

> Mailman 2.1.12 (yum package)

>

> On the T1 system I am adding the following statement to the mm_cfg.py file:

> DEFAULT_RESPOND_TO_POST_REQUESTS = No

>

> Then, when I run "./newlist -q listname 
> my.em...@domain.com<mailto:my.em...@domain.com<mailto:my.em...@domain.com%3cmailto:my.em...@domain.com>>
>  12345678" the list setting is as desired (respond_to_post_request = No).

>

> On the T2 system using the same scenario above, the "respond_to_post_request" 
> attribute does not change from the Defaults.py setting of Yes.





It should if you spelled it correctly.





> On the T2 system I have tried changing the attribute from  
> DEFAULT_RESPOND_TO_POST_REQUESTS to just RESPOND_TO_POST_REQUESTS, changed No 
> to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A number of 
> combinations, and none work on the CentOS machine.





No, no, 0 and False are all essentially equivalent in mm_cfg.py.



Changing the name is the same as commenting it or leaving it out. Every

setting that Mailman references is defined in Defaults.py. Anything you

set in mm_cfg.py that is not a setting mentioned in Defaults.py is ignored.





> Do you have any suggestions or recommendations? Our goal is to use the CentOS 
> system for production, so getting this worked out will be very helpful.





Exactly what mm_cfg.py file are you editing on CentOS. I *think* the

CentOS package has an mm_cfg.py in /etc/mailman and there is a symlink

from /usr/lib/mailman/Mailman/mm_cfg.py to /etc/mailman/mm_cfg.py, but I

may be mistaken about that which is why you should see the FAQ article

at <https://wiki.list.org/x/12812344>.



--

Mark Sapiro <m...@msapiro.net<mailto:m...@msapiro.net>>The highway is 
for gamblers,

San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--

Mailman-Users mailing list 
Mailman-Users@python.org<mailto: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/ed.beu%40alaska.gov
--
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] Mm_cfg.py not setting attribute

[Beu, Ed (DOA)]

Hi,

We currently have two instances of Mailman running for test purposes. The 
newlist command along with a customized mm_cfg.py file is producing different 
results on the two systems.

Configurations are as follows on these two test systems.

T1
Solaris 10
Mailman 2.1.20 (csw package)

T2
CentOS 6.7 (Final)
Mailman 2.1.12 (yum package)

On the T1 system I am adding the following statement to the mm_cfg.py file:
DEFAULT_RESPOND_TO_POST_REQUESTS = No

Then, when I run "./newlist -q listname 
my.em...@domain.com 12345678" the list setting is 
as desired (respond_to_post_request = No).

On the T2 system using the same scenario above, the "respond_to_post_request" 
attribute does not change from the Defaults.py setting of Yes.

On the T2 system I have tried changing the attribute from  
DEFAULT_RESPOND_TO_POST_REQUESTS to just RESPOND_TO_POST_REQUESTS, changed No 
to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A number of 
combinations, and none work on the CentOS machine.

Do you have any suggestions or recommendations? Our goal is to use the CentOS 
system for production, so getting this worked out will be very helpful.

Thx, Ed



Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/



--
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] Order of operation - config files

[Beu, Ed (DOA)]

Hi, I got it working... 

From: Beu, Ed (DOA)
Sent: Wednesday, May 04, 2016 8:49 AM
To: 'mailman-users@python.org' <mailman-users@python.org>
Subject: Order of operation - config files

Hello,

We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10. 
Production version will be running on CentOS.

Since most of our lists are 'Announcement' type lists, I have put the following 
in the mm_cfg.py file:

DEFAULT_DEFAULT_MEMBER_MODERATION = Yes
>>> The double DEFAULT_DEFAULT on this variable appears to be the only doubled 
>>> default in the Defaults.py file. And, using it in the same manner in the 
>>> MM_CFG.py file appears to be the only way to get it to work when creating a 
>>> new list.

For the occasional 'discussion' list I have created a config file 
(discuss.config) to import into the new list to change 'Member Moderation' to 
No, but it does not take effect.

For example, I'm using this command: .../bin> ./newlist -q testdiscuss 
ed@alaska.gov<mailto:ed@alaska.gov> 12345678;./config_list -i 
discuss.config testdiscuss
>>> I change the entry in the MM_CFG.py file to:
DEFAULT_DEFAULT_MEMBER_MODERATION = 1(1 rather than Yes)

>>> used the following statement in my discuss.config file - and it's working 
>>> now
default_member_moderation = 0

Is it not possible to override the mm_cfg.py file entries with a config_list -i 
command?
>>> apparently the config_list -i does run after mm_cfg.py!!

Thanks in advance for any assistance!

~Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov<mailto:ed@alaska.gov>
" http://www.doa.alaska.gov/ets/



--
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] Order of operation - config files

[Beu, Ed (DOA)]

Hello,

We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10. 
Production version will be running on CentOS.

Since most of our lists are 'Announcement' type lists, I have put the following 
in the mm_cfg.py file:

DEFAULT_DEFAULT_MEMBER_MODERATION = Yes

For the occasional 'discussion' list I have created a config file 
(discuss.config) to import into the new list to change 'Member Moderation' to 
No, but it does not take effect.

For example, I'm using this command: .../bin> ./newlist -q testdiscuss 
ed@alaska.gov 12345678;./config_list -i discuss.config testdiscuss

Is it not possible to override the mm_cfg.py file entries with a config_list -i 
command?

Thanks in advance for any assistance!

~Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/



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