I'm relatively new to Mailman but I've managed
to build it from source and set up a few lists,
with generous help from this list.
While working through issues relating to
creating a standard list configuration, I started
to feel that there was a fundamental flaw in the
way Mailman lists are
On 12/6/06, Jon Forrest [EMAIL PROTECTED] wrote:
I'm relatively new to Mailman but I've managed
to build it from source and set up a few lists,
with generous help from this list.
While working through issues relating to
creating a standard list configuration, I started
to feel that there
Patrick Bogen sent the message below at 08:39 12/6/2006:
On 12/6/06, Jon Forrest [EMAIL PROTECTED] wrote:
I'm relatively new to Mailman but I've managed
to build it from source and set up a few lists,
with generous help from this list.
While working through issues relating to
creating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 6, 2006, at 11:59 AM, Dragon wrote:
As far as I can discern from my limited perusing of source code, it
would be a huge change in architecture.
This is true. While a more detailed discussion of this topic belongs
on the developers list,
At 10:39 AM -0600 12/6/06, Patrick Bogen wrote:
The command-line config_list and/or with_list tools have a slightly
higher up-front cost (in terms of work required), but trivialize the
cost-per-list for config updates, for the purpose of applying a single
value across multiple lists.
At 8:26 AM -0800 12/6/06, Jon Forrest wrote:
Given that Mailman is written in Python, my naive impression
would be that this should be relatively easy to implement.
(As my old boss Mike Stonebraker used to say, it's just
a simple matter of software).
Unfortunately, there are people on
At 8:59 AM -0800 12/6/06, Dragon wrote:
Your old boss obviously has no realistic grasp of the subject.
Don't jump to conclusions too quickly. See my other message first.
--
Brad Knowles, [EMAIL PROTECTED]
Trend Micro has announced that they will cancel the stop.mail-abuse.org
mail
