[Mailman-Users] can you temporarily disable individual lists?
Hello, Is it possible to temporarily disable an individual mailing list? I'm not referring to 'emergency moderation' - this doesn't work when the current moderator may be prone to errors, etc. Regards, Alan Rubin Unix Systems Administrator Midrange Server Group, Data Centre Services Department of Business and Employment Northern Territory Government Phone: +61 (08) 8999 5111 Fax: +61 (08) 8999 7493 e-Mail: alan.ru...@nt.gov.au -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] can you temporarily disable individual lists?
Mark, I can get access to the web interface and the underlying OS. What happens when you move/rename the directory? I guess if we disabled the list, we don't want mail to the list to start bouncing, we just want mail to not be sent even with moderation - until the list was re-enabled. I guess a 'disabling' of the list would be like cutting out any mistakes until investigations are completed on errors or training is allowed for. Regards, Alan Rubin Unix Systems Administrator Midrange Server Group, Data Centre Services Department of Business and Employment Northern Territory Government Phone: +61 (08) 8999 5111 Fax: +61 (08) 8999 7493 e-Mail: alan.ru...@nt.gov.au -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Thursday, 5 August 2010 10:24 AM To: Alan Rubin; mailman-users@python.org Subject: Re: [Mailman-Users] can you temporarily disable individual lists? Alan Rubin wrote: Is it possible to temporarily disable an individual mailing list? I'm not referring to 'emergency moderation' - this doesn't work when the current moderator may be prone to errors, etc. It depends on what access you have and what you want to happen when mail is sent to the list. If your MTA uses aliases, you could remove or redirect the list's aliases. You could move the lists/LISTNAME directory somewhere else. If you are the list owner without access to the underlying installation, then No, I don't think it's possible. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] SOP for notifying list owners
Hello, Just curious if the community has a Standard Operating Procedure for list administrators to notify list owners when there are changes to the Mailman installation. Maybe like a list of list owners? Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 5111 Fax: +61 (08) 8999 7493 e-Mail: alan.ru...@nt.gov.au -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] subscribing by email
Mark,
Nope, I didn't realise that a restart was required. I just restarted it
and it seems to work fine now. Thanks for the help, once again.
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 5111
Fax: +61 (08) 8999 7493
e-Mail: alan.ru...@nt.gov.au
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Wednesday, 18 February 2009 1:28 AM
To: Alan Rubin; Mailman User List
Subject: RE: [Mailman-Users] subscribing by email
Alan Rubin wrote:
I applied the patch, used the request address, and my message still
gets
shunted.
Did you restart Mailman after applying the patch?
Feb 17 14:59:32 2009 (1046) Uncaught runner exception: 'NoneType'
object
has no attribute 'lower'
Feb 17 14:59:32 2009 (1046) Traceback (most recent call last):
File /export/home/mailman/Mailman/Queue/Runner.py, line 114, in
_oneloop
self._onefile(msg, msgdata)
File /export/home/mailman/Mailman/Queue/Runner.py, line 185, in
_onefile
keepqueued =3D self._dispose(mlist, msg, msgdata)
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 239,
in _dispose
res.process()
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 112,
in process
stop =3D self.do_command(cmd, args)
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 139,
in do_command
return handler.process(self, args)
File /export/home/mailman/Mailman/Commands/cmd_subscribe.py, line
74, in process
if (digest is None
AttributeError: 'NoneType' object has no attribute 'lower'
Feb 17 14:59:32 2009 (1046) SHUNTING:
1234848571.543715+462ea839ccdd63f659aab843129562980c886d3c
Diff on the cmd_subscribe.py new and old:
# diff Mailman/Commands/cmd_subscribe.py Mailman/Commands/cmd_sub
74,75c74
if (digest is None
and password and password.lower() in ('digest',
'nodigest')):
---
if digest is None and password.lower() in ('digest', 'nodigest'):
I think the only possible explanation for the above is you didn't
restart Mailman.
Also, even without the patch, if you sent a
subscribe nodigest address=...@example.com
command to the list-request address, it shouldn't trigger that error
unless you also had, e.g., a bare 'subscribe' in the subject. In mails
to -request, both Subject: and body are scanned for commands so if you
mail to -request with Subject: subscribe and body
subscribe nodigest address=...@example.com
that's two subscribe commands and the plain subscribe will trigger
the bug.
The web form that you pointed me at should work regardless of this
error
with the cmd_subscribe.py utility?
That's correct.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] subscribing by email
Hello,
We are running mailman 2.1.10 on Solaris 9 with postfix.
We have a customer who would like to use a form on a website to
subscribe people to a mailing list. In theory, the form would email the
details the list-join address of the list. I have tried following the
instructions from the members' manual:
subscribe [PASSWORD] [digest-nodigest] [address=ADDRESS]
Subscribe to this mailing list. Your password must be given to
unsubscribe or change your options, but
if you omit the password, one will be generated for you. You may be
periodically reminded of your
password.
The next argument may be either: 'nodigest' or 'digest' (no quotes!). If
you wish to subscribe an address
other than the address you sent this request from, you may specify
'address=ADDRESS' (no brackets
around the email address, and no quotes!)
I am testing this process with a test list using the following email:
-Original Message-
From: Alan Rubin
Sent: Tuesday, 17 February 2009 1:46 PM
To: 'test-j...@lists.nt.gov.au'
Subject:
subscribe nodigest address=adam.sm...@nt.gov.au
but my attempts keep getting shunted (tried twice, first without a
digest option):
Feb 17 13:46:20 2009 (1046) Traceback (most recent call last):
File /export/home/mailman/Mailman/Queue/Runner.py, line 114, in
_oneloop
self._onefile(msg, msgdata)
File /export/home/mailman/Mailman/Queue/Runner.py, line 185, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 241,
in _dispose
res.do_command('join')
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 139,
in do_command
return handler.process(self, args)
File /export/home/mailman/Mailman/Commands/cmd_subscribe.py, line
74, in process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
Feb 17 13:46:20 2009 (1046) SHUNTING:
1234844179.158844+4d54d8a83f98a957ccff205953e10afbc0a9eecd
Any help? Am I missing a step? This is somewhat urgent, if anyone is
still awake in the West.
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 5111
Fax: +61 (08) 8999 7493
e-Mail: alan.ru...@nt.gov.au
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] subscribing by email
Mark,
I applied the patch, used the request address, and my message still gets
shunted.
Feb 17 14:59:32 2009 (1046) Uncaught runner exception: 'NoneType' object
has no attribute 'lower'
Feb 17 14:59:32 2009 (1046) Traceback (most recent call last):
File /export/home/mailman/Mailman/Queue/Runner.py, line 114, in
_oneloop
self._onefile(msg, msgdata)
File /export/home/mailman/Mailman/Queue/Runner.py, line 185, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 239,
in _dispose
res.process()
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 112,
in process
stop = self.do_command(cmd, args)
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 139,
in do_command
return handler.process(self, args)
File /export/home/mailman/Mailman/Commands/cmd_subscribe.py, line
74, in process
if (digest is None
AttributeError: 'NoneType' object has no attribute 'lower'
Feb 17 14:59:32 2009 (1046) SHUNTING:
1234848571.543715+462ea839ccdd63f659aab843129562980c886d3c
Diff on the cmd_subscribe.py new and old:
# diff Mailman/Commands/cmd_subscribe.py Mailman/Commands/cmd_sub
74,75c74
if (digest is None
and password and password.lower() in ('digest',
'nodigest')):
---
if digest is None and password.lower() in ('digest', 'nodigest'):
The web form that you pointed me at should work regardless of this error
with the cmd_subscribe.py utility?
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 5111
Fax: +61 (08) 8999 7493
e-Mail: alan.ru...@nt.gov.au
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Tuesday, 17 February 2009 2:22 PM
To: Alan Rubin; Mailman User List
Subject: Re: [Mailman-Users] subscribing by email
Alan Rubin wrote:
We have a customer who would like to use a form on a website to
subscribe people to a mailing list. In theory, the form would email
the
details the list-join address of the list.
Unduly complicated. See the FAQ at http://wiki.list.org/x/hIA9.
But, since you ask, read on...
I have tried following the
instructions from the members' manual:
subscribe [PASSWORD] [digest-nodigest] [address=ADDRESS]
Subscribe to this mailing list. Your password must be given to
unsubscribe or change your options, but
if you omit the password, one will be generated for you. You may be
periodically reminded of your
password.
The next argument may be either: 'nodigest' or 'digest' (no quotes!).
If
you wish to subscribe an address
other than the address you sent this request from, you may specify
'address=ADDRESS' (no brackets
around the email address, and no quotes!)
I am testing this process with a test list using the following email:
-Original Message-
From: Alan Rubin
Sent: Tuesday, 17 February 2009 1:46 PM
To: 'test-j...@lists.nt.gov.au'
Subject:
subscribe nodigest address=adam.sm...@nt.gov.au
You can't send a generic subscribe command to to the -join or
-subscribe address. The subject/body of mail to those addresses are
ignored and they just request subscription of the From: address with
generated password and default digest/nodigest.
If you want to send a subscribe command as above in the subject or body
of the mail, you have to send it to the -request address.
But that isn't the reason for the following.
but my attempts keep getting shunted (tried twice, first without a
digest option):
Feb 17 13:46:20 2009 (1046) Traceback (most recent call last):
File /export/home/mailman/Mailman/Queue/Runner.py, line 114, in
_oneloop
self._onefile(msg, msgdata)
File /export/home/mailman/Mailman/Queue/Runner.py, line 185, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 241,
in _dispose
res.do_command('join')
File /export/home/mailman/Mailman/Queue/CommandRunner.py, line 139,
in do_command
return handler.process(self, args)
File /export/home/mailman/Mailman/Commands/cmd_subscribe.py, line
74, in process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
Feb 17 13:46:20 2009 (1046) SHUNTING:
1234844179.158844+4d54d8a83f98a957ccff205953e10afbc0a9eecd
Any help? Am I missing a step? This is somewhat urgent, if anyone is
still awake in the West.
This was a bug in the 2.1.10 release. See
http://mail.python.org/pipermail/mailman-announce/2008-April/000111.htm
l
for a patch, but the irony here is if you had sent the mail to
test-requ...@lists.nt.gov.au, it would have worked and not triggered
the bug.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http
Re: [Mailman-Users] pending request problem
Mark, I don't see how that is likely. I'd be very surprised if there was another mailman server in this environment. corporate_reporting [EMAIL PROTECTED] sts.nt.gov.au To Sent by:[EMAIL PROTECTED] [EMAIL PROTECTED] s.nt.gov.au ts.nt.gov.aucc Subject 09/10/2008 08:00 AM 1 Corporate_Reporting_Finance moderator request(s) waiting I'm not sure if the above will paste properly into this email, but the simple headers indicate the sender as being @ lists.nt.gov.au. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] Sent by:To mailman-users-bounc [EMAIL PROTECTED], es+alan.rubin=nt.go mailman-users@python.org [EMAIL PROTECTED] cc Subject 10/10/2008 01:11 AM Re: [Mailman-Users] pending request problem [EMAIL PROTECTED] wrote: Cron runs checkdbs every morning at 8AM, but I am an owner of a few of these lists and I don't get moderator pending notices every day if there is nothing to do. Is this an option to set in the individual list configuration? # At 8AM every day, mail reminders to admins as to pending requests. # They are less likely to ignore these reminders if they're mailed # early in the morning, but of course, this is local time... ;) 0 8 * * * /opt/csw/bin/python -S /export/home/mailman/cron/checkdbs I am suggesting that these notices are coming from a different cron/checkdbs, possibly even on a different machine being run by a different crontab. (There is no list config setting.) Here's the notice they are receiving. It says 1 request waiting but nothing is listed when they go to the web page. The [EMAIL PROTECTED] mailing list has 1 request(s) waiting for your consideration at: http://lists.nt.gov.au/mailman/admindb/corporate_reporting_finance Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. Look at the chain of Received: headers in this message to find what machine it originates from. Then find the mailman installation on that machine that it's coming from. E.g. find / -name corporate_reporting_finance I am sure that you will find this notice is not being sent from /export/home/mailman/cron/checkdbs on the 'lists.nt.gov.au'(150.191.80.112) box. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http
[Mailman-Users] pending request problem
Hello,
Mailman 2.1.10.
We have a list that is sending the moderator daily a message about pending
requests. When the moderator clicks on the admin link, Mailman shows no pending
requests. However, there is a pending.pck file in the directory of the list on
the Mailman server. Here are the contents:
[- start pickle file -]
- start object 1 -
{ '15540c1c834bfb99ef20a9621a0437c182b4d5ef': ('H', 31),
'1e79ecd565fa5e2349bdeec5f41506560f8a7104': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'37ec39382577ef6007a990a63c9eadd48c8b2fb5': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'46dd36aa9b2098c04413916363b9f70153420587': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'4e4faa7381d3b9dd50943813c8b39f2c15a0f888': ('H', 26),
'6f13dd1779f3ba010efdeb561f203dd59e1015ed': ('H', 25),
'720da6f23ef531826a3ded71d7f074e3af5aedb3': ('H', 21),
'b7801bf76362de4aa4ac6d2db9f1cfab6e8c8b51': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'ca468272da6d506f17983c18576835a1117d8354': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'eff52942711894f6c3210e00d62357d0eb42a1d8': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'evictions': { '15540c1c834bfb99ef20a9621a0437c182b4d5ef':
1223691481.6416359,
'1e79ecd565fa5e2349bdeec5f41506560f8a7104':
1223606953.9437859,
'37ec39382577ef6007a990a63c9eadd48c8b2fb5':
1223606953.5659289,
'46dd36aa9b2098c04413916363b9f70153420587':
1223606954.17202,
'4e4faa7381d3b9dd50943813c8b39f2c15a0f888':
1223680324.9617939,
'6f13dd1779f3ba010efdeb561f203dd59e1015ed':
1223677576.544651,
'720da6f23ef531826a3ded71d7f074e3af5aedb3':
1223606023.4145031,
'b7801bf76362de4aa4ac6d2db9f1cfab6e8c8b51':
1223606050.2751639,
'ca468272da6d506f17983c18576835a1117d8354':
1223606952.789958,
'eff52942711894f6c3210e00d62357d0eb42a1d8':
1223606953.7517281},
'version': 2}
[- end pickle file -]
The date on the file is October 8. Why is there nothing showing on the web
interface? How can this be cleaned up/fixed?
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 6814
Fax: +61 (08) 8999 7493
e-Mail: [EMAIL PROTECTED]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] pending request problem
Mark,
Cron runs checkdbs every morning at 8AM, but I am an owner of a few of these
lists and I don't get moderator pending notices every day if there is nothing to
do. Is this an option to set in the individual list configuration?
# At 8AM every day, mail reminders to admins as to pending requests.
# They are less likely to ignore these reminders if they're mailed
# early in the morning, but of course, this is local time... ;)
0 8 * * * /opt/csw/bin/python -S /export/home/mailman/cron/checkdbs
Here's the notice they are receiving. It says 1 request waiting but nothing is
listed when they go to the web page.
The [EMAIL PROTECTED] mailing list has 1
request(s) waiting for your consideration at:
http://lists.nt.gov.au/mailman/admindb/corporate_reporting_finance
Please attend to this at your earliest convenience. This notice of
pending requests, if any, will be sent out daily.
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 6814
Fax: +61 (08) 8999 7493
e-Mail: [EMAIL PROTECTED]
Mark Sapiro
[EMAIL PROTECTED]
Sent by:To
mailman-users-bounc [EMAIL PROTECTED],
es+alan.rubin=nt.go mailman-users@python.org
[EMAIL PROTECTED]
cc
Subject
09/10/2008 10:15 AM Re: [Mailman-Users] pending request
problem
[EMAIL PROTECTED] wrote:
Mailman 2.1.10.
We have a list that is sending the moderator daily a message about pending
requests. When the moderator clicks on the admin link, Mailman shows no
pending
requests. However, there is a pending.pck file in the directory of the list on
the Mailman server. Here are the contents:
[- start pickle file -]
- start object 1 -
{ '15540c1c834bfb99ef20a9621a0437c182b4d5ef': ('H', 31),
'1e79ecd565fa5e2349bdeec5f41506560f8a7104': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'37ec39382577ef6007a990a63c9eadd48c8b2fb5': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'46dd36aa9b2098c04413916363b9f70153420587': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'4e4faa7381d3b9dd50943813c8b39f2c15a0f888': ('H', 26),
'6f13dd1779f3ba010efdeb561f203dd59e1015ed': ('H', 25),
'720da6f23ef531826a3ded71d7f074e3af5aedb3': ('H', 21),
'b7801bf76362de4aa4ac6d2db9f1cfab6e8c8b51': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'ca468272da6d506f17983c18576835a1117d8354': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'eff52942711894f6c3210e00d62357d0eb42a1d8': ( 'E',
'corporate_reporting_finance',
'[EMAIL PROTECTED]'),
'evictions': { '15540c1c834bfb99ef20a9621a0437c182b4d5ef':
1223691481.6416359,
'1e79ecd565fa5e2349bdeec5f41506560f8a7104':
1223606953.9437859,
'37ec39382577ef6007a990a63c9eadd48c8b2fb5':
1223606953.5659289,
'46dd36aa9b2098c04413916363b9f70153420587':
1223606954.17202,
'4e4faa7381d3b9dd50943813c8b39f2c15a0f888':
1223680324.9617939,
'6f13dd1779f3ba010efdeb561f203dd59e1015ed':
1223677576.544651,
'720da6f23ef531826a3ded71d7f074e3af5aedb3':
1223606023.4145031,
'b7801bf76362de4aa4ac6d2db9f1cfab6e8c8b51':
1223606050.2751639,
'ca468272da6d506f17983c18576835a1117d8354':
1223606952.789958,
'eff52942711894f6c3210e00d62357d0eb42a1d8':
1223606953.7517281},
'version': 2}
[- end pickle file -]
The date on the file is October 8. Why is there nothing showing on the web
interface? How can this be cleaned up/fixed?
The pending.pck has nothing to do with the n moderator requests email
or the requests in the admindb interface. The file that contains those
is request.pck.
pending.pck is used by 'confirm' to process confirmations. The 'H'
entries in that file are held
[Mailman-Users] subscription approval
Hello, We have a client with a moderated (one-way) list where subscription requires approval of the owner. When the owner uses the web interface to approve this subscription request the original subscription email is also sent to the whole list (so, you get a blank email from the new subscriber with the signature etc in it). How can we use the web interface to accept the email without having the original message also approved for posting to the list? We are using Mailman v2.1.10. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] subscription approval... apologies
Hello again, I jumped the gun when communicating with my client. The client is not highly skilled in IT and appears to have mixed up a normal post attempt with a subscription request. Looking through the logs and testing the behavior with a test list confirms that approving subscription requests does not in actuality appear to forward to the list. I am sorry for any confusion. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED] u Sent by:To mailman-users-bounc mailman-users@python.org es+alan.rubin=nt.go cc [EMAIL PROTECTED] Subject [Mailman-Users] subscription approval 25/09/2008 10:26 AM Hello, We have a client with a moderated (one-way) list where subscription requires approval of the owner. When the owner uses the web interface to approve this subscription request the original subscription email is also sent to the whole list (so, you get a blank email from the new subscriber with the signature etc in it). How can we use the web interface to accept the email without having the original message also approved for posting to the list? We are using Mailman v2.1.10. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/alan.rubin%40nt.gov.au Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] digest message modification
Hello, Is there any way to strip out certain headers/lines from a message being shown in a digest format? My clients are trying to present their information as directly as possible and they would like to remove certain bits. Today's Topics: 1. Test message (Mainframe Services Change Notification Mailing List) -- Message: 1 Date: Wed, 10 Sep 2008 08:59:09 +0930 From: Mainframe Services Change Notification Mailing List [EMAIL PROTECTED] Subject: [Change_Notification] Test message To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII ... I think they would like to see lines like Content-type and Message-ID removed as it may confuse their audience. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] digest message modification
Mark, Is there a way to do this on a per-list basis? From the web interface or from the command line? Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] Sent by:To mailman-users-bounc [EMAIL PROTECTED], es+alan.rubin=nt.go mailman-users@python.org [EMAIL PROTECTED] cc Subject 10/09/2008 10:02 AM Re: [Mailman-Users] digest message modification [EMAIL PROTECTED] wrote: Is there any way to strip out certain headers/lines from a message being shown in a digest format? See the settings MIME_DIGEST_KEEP_HEADERS and PLAIN_DIGEST_KEEP_HEADERS in defaults.py. You can copy PLAIN_DIGEST_KEEP_HEADERS omitting Message-ID and Content-Type and put the rest in mm_cfg.py. E.g. PLAIN_DIGEST_KEEP_HEADERS = [ 'Message', 'Date', 'From', 'Subject', 'To', 'Cc', 'Keywords', ] Do not remove Content-Type from MIME_DIGEST_KEEP_HEADERS as that will destroy the MIME format of the digest. People should only be selecting the MIME format digest if their MUAs understand MIME (these days almost all do) in which case they won't be seeing the actual Content-Type header anyway. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/alan.rubin%40nt.gov.au Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] monthly password reminders
Hello, Is there any way, besides editing the options.html template file, to completely disable regular/monthly password reminders? According to the list options page, whether or not a list sends out reminders individual subscribers can still change this setting. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] monthly password reminders
Mark, Is that a singular reminder that is requested and not a periodic one (if monthly reminders are set off)? Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] Sent by:To mailman-users-bounc [EMAIL PROTECTED], es+alan.rubin=nt.go mailman-users@python.org [EMAIL PROTECTED] cc Subject 02/09/2008 08:45 AM Re: [Mailman-Users] monthly password reminders [EMAIL PROTECTED] wrote: Is there any way, besides editing the options.html template file, to completely disable regular/monthly password reminders? According to the list options page, whether or not a list sends out reminders individual subscribers can still change this setting. Granted, it could be more clear, but if you read the description of Get password reminder email for this list? on the options page, it says the user can turn off reminders by selecting No. It does not say the the user can get reminders if the list setting is off. In fact, if the list is set to not send reminders, the list is not included in reminders regardless of any list member's setting. Also, A site can disable monthly reminders all together by removing the cron/mailpasswds entry from Mailman's crontab. However, none of this prevents a user from requesting a reminder from the options login page. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/alan.rubin%40nt.gov.au Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] monthly password reminders
Mark/list, on a different but related tact, what could I alter in the cron script to send out a 'reminder' that the user belongs to the list, but not actually send the password? IT Security is a little antsy about having these passwords floating around through the email system (don't ask). Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] Sent by:To mailman-users-bounc [EMAIL PROTECTED], es+alan.rubin=nt.go mailman-users@python.org [EMAIL PROTECTED] cc Subject 02/09/2008 09:05 AM Re: [Mailman-Users] monthly password reminders [EMAIL PROTECTED] wrote: Is that a singular reminder that is requested and not a periodic one (if monthly reminders are set off)? If the list's send_reminders is set to No, no periodic reminders are sent for that list regardless of the user's setting on the user options page. If the user clicks the Remind button on the options login page (after providing her email address), she will get a one-time reminder regardless of any other settings. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/alan.rubin%40nt.gov.au Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] digest reply-to
Hello, Where can you set an explicit digest reply-to email address? I have tried the General Options and the reply-to is always to the list no matter what I change (even if I set an explicit reply-to address). If I have a one-way list that only sends in digest, I don't want people/autoresponders to pick up the list as the reply-to and fill up the next digest (in the case when an allowed poster is on holidays and fails to set their out-of-office policy correctly, for example). Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] changing Digest formatting
Hello, Is there any way to remove/re-arrange the header that is printed with every digest? Send Change_Notification mailing list submissions to [EMAIL PROTECTED] To subscribe or unsubscribe via the World Wide Web, visit http://list.example.com/mailman/listinfo/list or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of List digest... ... We're using digests for announcements and we'd rather not send all that information to the recipients, at least at the beginning of the message. We wouldn't want them to miss the meat of the message. We'd like to get the message started with Today's Topics. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Redirecting Mailman URL
Hello, We have an internal Mailman server. The service is up and running for our internal clients, but now we need to have it accessible to the world. We have a reverse-proxy that will allow us to redirect to port 80 for our internal Mailman server, but our Security group seems to have a fondness for external hosts with hostnames that only begin with www. Internally, and in the Mailman configuration, the hostname is just lists. If I add a ServerAlias of www.lists... to my Apache configuration, listinfo interprets www.lists in a different manner and claims there are no lists published for www.lists... Is there a way I can have www.lists get the same results as lists either through mm_cfg.py or the Apache configuration? Perhaps with add_virtualhost? Any help would be appreciated. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Digest options - list configuration
Mark/All, So, if digest_send_periodic is No (so that digests are not sent every day as indicated by the default senddigests cron entry), senddigests will not force the list to send a new digest even with the -l option? If you host many lists and one list/customer wants messages sent only on a specific schedule, and you don't want to degrade the ability for the entire list server, then the only real option is to cook up some recipe which keeps mail intended for the list in a separate queue and only gets added to the list at the time that you want a digest created and sent? To be more specific about my scenario, we are attempting to migrate from Majordomo to Mailman. We have a list that sends out change control notifications on a twice weekly basis. In the majordomo configuration, individual messages are collected in a work folder and when a Perl script called 'digests', written for majordomo, is run from cron, the messages in the work folder are gathered into a single digest message and sent to the list subscribers. Perhaps I am taking the wrong approach with Mailman? Is there another way to deliver a similar service without cooking up my own scheme, or has someone already contributed such a tool/scheme? Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] To 07/08/2008 12:18 AM [EMAIL PROTECTED], mailman-users@python.org cc Subject Re: [Mailman-Users] Digest options - list configuration [EMAIL PROTECTED] wrote: If these lines occur in mailman's crontab - # Noon, mail digests for lists that do periodic as well as threshhold delivery. 0 12 * * * /opt/csw/bin/python -S /export/home/mailman/cron/senddigests how will lists with digests enabled be affected? If the list has a high threshold, will it still have the contents of its digest sent? If digest_send_periodic is Yes, and the list has had at least one post since the last digest, a digest will be sent when cron/senddigests runs. Do options in the configuration take precedence over the script? The only configuration option that affects cron/senddigests is digest_send_periodic which controls whether or not cron/senddigests will send a digest for this list. If the intention is to schedule sending of digests from cron for a particular list on specific days only, will the script send the digest regardless of the threshold? Yes And, if you disable the cronjob above, how will that affect any other lists on the mail server where users arbitrarily choose to receive digests and list owners allow this? If you disable cron/senddigests, no periodic digests will be sent for any list. If you change the schedule, it will affect all lists. You can run cron/senddigests for specific lists with a -l listname option (run 'cron/senddigests -h' for info) so you could set up your crontab to run 'cron/senddigests -l list1' on one schedule and 'cron/senddigests -l list2' on another, but the problem is there's no all lists except ... option, so it becomes cumbersome. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Digest options - list configuration
Mark, I chose option two, but it didn't seem to work. I am not a python programmer. Is there a general switch to turn on simple debugging (a la -x in sh scripting). I ran this: su mailman -c /opt/csw/bin/python -S /export/home/mailman/cron/senddigests_mod -l change_notification and I got no errors or log messages that I can find, but the digest.mbox is still full and I never received a digest in my mailbox. Here is the edit to the copy, senddigests_mod: for listname in listnames: mlist = MailList.MailList(listname, lock=0) #if mlist.digest_send_periodic: if True: mlist.Lock() try: try: mlist.send_digest_now() mlist.Save() # We are unable to predict what exception may occur in digest # processing and we don't want to lose the other digests, so # we catch everything. except Exception, errmsg: print sys.stderr, \ 'List: %s: problem processing %s:\n%s' % \ (listname, os.path.join(mlist.fullpath(), 'digest.mbox'), errmsg) finally: mlist.Unlock() The executable bit is set and the permission is the same as the original. It is owned by root with the executable bit set for all and in the group mailman. Perhaps it needs to be owned by root as well? The original cronjob was set in mailman's crontab. The list is also set correctly: ~mailman/bin/config_list -o - change_notification snip # Should a digest be dispatched daily when the size threshold isn't # reached? # # legal values are: #0 = No #1 = Yes digest_send_periodic = 0 snip Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] To 07/08/2008 09:13 AM [EMAIL PROTECTED], mailman-users@python.org cc Subject Re: [Mailman-Users] Digest options - list configuration [EMAIL PROTECTED] wrote: So, if digest_send_periodic is No (so that digests are not sent every day as indicated by the default senddigests cron entry), senddigests will not force the list to send a new digest even with the -l option? Correct. If you host many lists and one list/customer wants messages sent only on a specific schedule, and you don't want to degrade the ability for the entire list server, then the only real option is to cook up some recipe which keeps mail intended for the list in a separate queue and only gets added to the list at the time that you want a digest created and sent? There are other ways to address this. See below. To be more specific about my scenario, we are attempting to migrate from Majordomo to Mailman. We have a list that sends out change control notifications on a twice weekly basis. In the majordomo configuration, individual messages are collected in a work folder and when a Perl script called 'digests', written for majordomo, is run from cron, the messages in the work folder are gathered into a single digest message and sent to the list subscribers. Perhaps I am taking the wrong approach with Mailman? Is there another way to deliver a similar service without cooking up my own scheme, or has someone already contributed such a tool/scheme? Here are a couple of possible approaches. First the kludgy approach. Set the crontab to run a script instead of cron/senddigests. The script would be something like (warning! may have syntax errors) #!/bin/sh prefix=/path/to/mailman special=the_special_listname for list in `$prefix/bin/list_lists --bare`; do if [[ $list != $special ]] ; then $prefix/cron/senddigests -l $list
Re: [Mailman-Users] Digest options - list configuration
Mark, I put in the print line and there was no output when I ran the script. And no success either. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] Sent by:To mailman-users-bounc [EMAIL PROTECTED], es+alan.rubin=nt.go mailman-users@python.org [EMAIL PROTECTED] cc Subject 07/08/2008 12:19 PM Re: [Mailman-Users] Digest options - list configuration [EMAIL PROTECTED] wrote: I chose option two, but it didn't seem to work. I am not a python programmer. Is there a general switch to turn on simple debugging (a la -x in sh scripting). No. I ran this: su mailman -c /opt/csw/bin/python -S /export/home/mailman/cron/senddigests_mod -l change_notification and I got no errors or log messages that I can find, but the digest.mbox is still full and I never received a digest in my mailbox. Had it actually worked, lists/change_notification/digest.mbox would have been removed. I can't begin to guess what was wrong. You seem to have done everything right. If there were some problem, there should have been something written to your terminal/console. Here is the edit to the copy, senddigests_mod: for listname in listnames: mlist = MailList.MailList(listname, lock=0) #if mlist.digest_send_periodic: if True: mlist.Lock() try: try: mlist.send_digest_now() mlist.Save() # We are unable to predict what exception may occur in digest # processing and we don't want to lose the other digests, so # we catch everything. except Exception, errmsg: print sys.stderr, \ 'List: %s: problem processing %s:\n%s' % \ (listname, os.path.join(mlist.fullpath(), 'digest.mbox'), errmsg) finally: mlist.Unlock() The executable bit is set and the permission is the same as the original. It is owned by root with the executable bit set for all and in the group mailman. Perhaps it needs to be owned by root as well? The original cronjob was set in mailman's crontab. It needs to actually run as group mailman, and if you run it as you did, the execute bit is not needed. Everything looks fine for running it as you did, and if the permissions weren't adequate, you would have gotten an error. The list is also set correctly: ~mailman/bin/config_list -o - change_notification snip # Should a digest be dispatched daily when the size threshold isn't # reached? # # legal values are: #0 = No #1 = Yes digest_send_periodic = 0 This shouldn't matter for senddigests_mod at all. It only affects whether the normal senddigests will send a digest for this list, which it won't with the above setting. You could try adding a print so if True: mlist.Lock() try: becomes if True: print 'Processing' + listname mlist.Lock() try: just to be sure it's getting there. It should print Processing change_notification when you run it. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/alan.rubin%40nt.gov.au Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Digest options
Hello, We are using Mailman 2.1.10. For digests, how would I set which day of the week, month, year, etc. that a digest is sent out? For example, if I choose Weekly digest, how do I set it to send with the week starting on Wednesday? Or if monthly, how do I choose the 15th? The options listed in the GUI aren't very specific. What are the defaults? Is there a way to setup a digest list that does not send out ANY digests automatically but can be generated/started/kicked-off through a cron job? Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Digest options - list configuration
Mark, Thanks for your answer. It is very enlightening. This is a bit of a tangent, but also has to do with 'interpretation' of Mailman's configuration. If you read/work with the list configuration from the command line, using ~mailman/bin/config_list, you will see many descriptions that say something such as: # legal values are: #0 = No #1 = Yes But then the current/default value will be listed as True or False, literally. Which is it? Are both 0/False and 1/True acceptable? Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] To 06/08/2008 11:15 AM [EMAIL PROTECTED], mailman-users@python.org cc Subject Re: [Mailman-Users] Digest options [EMAIL PROTECTED] wrote: We are using Mailman 2.1.10. For digests, how would I set which day of the week, month, year, etc. that a digest is sent out? For example, if I choose Weekly digest, how do I set it to send with the week starting on Wednesday? Or if monthly, how do I choose the 15th? The options listed in the GUI aren't very specific. What are the defaults? You misunderstand what those settings are for. They have nothing to do with when digests are sent. Wach digest has a volume number and an issue number. The issue number increments with each digest. The digest_volume_frequency setting controls how often the issue number resets to 1 and the volume number increments instead. The things that control when digests are sent are first of all, digest_size_threshhold. When the size of the mailbox file holding the messages accummulated for the digest reaches that size, a digest will be produced immediately regardless of when that is. The digest itself may be a little smaller (or bigger if the triggering post was large) due to removal of some headers and scrubbing of attachments. In addition, if digest_send_periodic is set to Yes, the periodic cron/senddigests will send a digest when it runs if there are any messages for the digest at that time. Mailman's default crontab runs cron/senddigests daily at noon local time. Is there a way to setup a digest list that does not send out ANY digests automatically but can be generated/started/kicked-off through a cron job? That is effectively what happens if you set digest_size_threshhold large enough so that you never trigger a digest on size before cron/senddigests runs. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Digest options - list configuration
Mark, Back to Digests... If these lines occur in mailman's crontab - # Noon, mail digests for lists that do periodic as well as threshhold delivery. 0 12 * * * /opt/csw/bin/python -S /export/home/mailman/cron/senddigests how will lists with digests enabled be affected? If the list has a high threshold, will it still have the contents of its digest sent? Do options in the configuration take precedence over the script? If the intention is to schedule sending of digests from cron for a particular list on specific days only, will the script send the digest regardless of the threshold? And, if you disable the cronjob above, how will that affect any other lists on the mail server where users arbitrarily choose to receive digests and list owners allow this? Thanks for your help, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: [EMAIL PROTECTED] Mark Sapiro [EMAIL PROTECTED] To 06/08/2008 12:28 PM [EMAIL PROTECTED], mailman-users@python.org cc Subject Re: [Mailman-Users] Digest options - list configuration [EMAIL PROTECTED] wrote: Thanks for your answer. It is very enlightening. This is a bit of a tangent, but also has to do with 'interpretation' of Mailman's configuration. If you read/work with the list configuration from the command line, using ~mailman/bin/config_list, you will see many descriptions that say something such as: # legal values are: #0 = No #1 = Yes But then the current/default value will be listed as True or False, literally. Which is it? Are both 0/False and 1/True acceptable? Yes they are. At least assuming your Python is 2.3 or later, and assuming the attribute is one with only Yes or No possibilities. Prior to 2.3 there were no built-in constants True and False. Since Mailman through 2.1.8 was compatible with Python back to 2.1, we used 0 and 1 instead of False and True as values or we used a kludge like try: True, False except NameError: True = 1 False = 0 to define True and False if they weren't built in. Eventually, Mailman will move to using True and False everywhere to represent truth value constants, but even then, some old lists will still have 1 or 0 as the value of some list attributes just because they were set that way at one time and never changed. However, all the above has to do with the actual attribute value shown by config_list -o or set by config_list -i. In the actual text # legal values are: #0 = No #1 = Yes the 0 and 1 are the index of the radio button in the GUI for that attribute in the same way as, e.g. # legal values are: #0 = Accept #1 = Hold #2 = Reject #3 = Discard are the possible settings for generic_nonmember_action and # legal values are: #0 = No #1 = Yes #2 = Full Personalization are the possible settings for personalize. The bottom line is if you see a setting reported as True or False, it's OK to set it to False or True with config_list, but if the setting is reported as 0 or 1, you can't be sure that the code doesn't somewhere treat it as a number, so it is best to set it to a number. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
