On Thu, 19 May 2005, Matthew Newton wrote:
You could also use my patch (number 1164457 on sf.net):
http://sourceforge.net/tracker/index.php?func=detailaid=1164457group_id=103atid=300103
This lets you write something like:
SITE_HIDE_LIST_OPTIONS = ['owner']
in mm_cfg.py, and will then
At 8:59 PM -0400 2005-05-20, Charles Sprickman wrote:
That leads to the next question... Where are the defaults initially set
from? A few of the things I've hid are things I'd still like to flip a
value on. I know I could do this with config_list, but I'm wondering if
there is
On Sat, 21 May 2005, Brad Knowles wrote:
At 8:59 PM -0400 2005-05-20, Charles Sprickman wrote:
That leads to the next question... Where are the defaults initially set
from? A few of the things I've hid are things I'd still like to flip a
value on. I know I could do this with
On Wed, May 18, 2005 at 01:43:12PM -0700, Mark Sapiro wrote:
George Booth wrote:
That would explain why I couldn't find it. So, it's a binary code, not conf
files or anything I can directly edit. Not very convenient, eh? Anyway,
thanks for the info. :)
snip
- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
To: George Booth [EMAIL PROTECTED]; mailman-users@python.org
Sent: Wednesday, May 18, 2005 5:21 PM
Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be
changed?
George Booth wrote:
- Original Message
I'm the admin of a Mailman server that is quickly running out of disk space.
One of the solutions our fearless leader wants to implement is a sitewide
limit on message size. I know I can set a default limit in mm_cfg.py, but
the list owners can always change that. Is there a way to lock certain
- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
To: Mike Alberghini [EMAIL PROTECTED]; mailman-users@python.org
Sent: Wednesday, May 18, 2005 2:27 PM
Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be
changed?
You can modify the GUI to remove the option from
At 3:03 PM -0400 2005-05-18, Mike Alberghini wrote:
I'm the admin of a Mailman server that is quickly running out of disk space.
One of the solutions our fearless leader wants to implement is a sitewide
limit on message size. I know I can set a default limit in mm_cfg.py, but
the list
At 2:52 PM -0500 2005-05-18, George Booth wrote:
Where is the GUI file kept? I have a need to remove the option from the GUI
allowing users to activate their archives (we don't allow them because of
performance degradation with email when Mailman archives), but have no idea
where the GUI
- Original Message -
From: Brad Knowles [EMAIL PROTECTED]
To: George Booth [EMAIL PROTECTED]
Cc: mailman-users@python.org
Sent: Wednesday, May 18, 2005 3:04 PM
Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be
changed?
At 2:52 PM -0500 2005-05-18, George Booth wrote
George Booth wrote:
- Original Message -
From: Brad Knowles [EMAIL PROTECTED]
snip
It's not a GUI file. It is the GUI as created by the Python programs
that generate the required HTML. So, you're talking about hacking Python
code.
That would explain why I couldn't find it. So,
At 3:21 PM -0500 2005-05-18, George Booth wrote:
That would explain why I couldn't find it. So, it's a binary code, not conf
files or anything I can directly edit. Not very convenient, eh? Anyway,
thanks for the info. :)
No, it's not binary code. Mailman is written in Python.
Mark Sapiro wrote:
Alternatively, I *think* (Warning! I don't know what I'm talking about)
you can just remove the Mailman/Gui/Archive.py* files alltogether AND
put
ARCHIVE_CATEGORIES.remove('archive')
DEFAULT_ARCHIVE = Off
in mm_cfg.py to remove the Archiving Options completely and default
At 2:09 PM -0700 2005-05-18, Mark Sapiro wrote:
ADMIN_CATEGORIES.remove('archive')
Why not instead have the following in mm_cfg.py:
ADMIN_CATEGORIES = [
# First column
'general', 'passwords', 'language', 'members', 'nondigest', 'digest',
# Second column
# Old
On 5/18/05 2:09 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
Mark Sapiro wrote:
Alternatively, I *think* (Warning! I don't know what I'm talking about)
you can just remove the Mailman/Gui/Archive.py* files alltogether AND
put
ARCHIVE_CATEGORIES.remove('archive')
DEFAULT_ARCHIVE = Off
in
- Original Message -
From: Brad Knowles [EMAIL PROTECTED]
To: Mark Sapiro [EMAIL PROTECTED]
Cc: Mark Sapiro [EMAIL PROTECTED]; George Booth [EMAIL PROTECTED];
mailman-users@python.org
Sent: Wednesday, May 18, 2005 4:23 PM
Subject: Re: [Mailman-Users] Setting sitewide defaults that can't
On Wed, 18 May 2005, Brad Knowles wrote:
At 2:09 PM -0700 2005-05-18, Mark Sapiro wrote:
ADMIN_CATEGORIES.remove('archive')
Why not instead have the following in mm_cfg.py:
ADMIN_CATEGORIES = [
# First column
'general', 'passwords', 'language', 'members', 'nondigest',
At 5:38 PM -0400 2005-05-18, Charles Sprickman wrote:
I'm handy with PHP and perl, but I've never dug into Python at all. What
can you folks recommend as far as a crash-course in Python?
One way I've found that really focuses your mind really, really
well is to hack on your
John W. Baxter wrote:
I really thought the Original Poster enquired about maximum message size,
not archiving. Perhaps I missed a transition.
Yup. The OP did ask about maximum message size, but George Booth
brought up Archiving.
Then I got carried away because if you remove the archive Yes|No
Brad Knowles wrote:
At 5:38 PM -0400 2005-05-18, Charles Sprickman wrote:
I'm handy with PHP and perl, but I've never dug into Python at all. What
can you folks recommend as far as a crash-course in Python?
One way I've found that really focuses your mind really, really
well is to
George Booth wrote:
- Original Message -
From: Brad Knowles [EMAIL PROTECTED]
Why not instead have the following in mm_cfg.py:
ADMIN_CATEGORIES = [
# First column
'general', 'passwords', 'language', 'members', 'nondigest', 'digest',
# Second column
# Old version
21 matches
Mail list logo
