this one myself.
I'd like to use verp and I really want to use this script (it makes making
lists incredibly simple)
-Jeff
On Mon, Dec 06, 2004 at 05:01:31PM -0500 or thereabouts, Jeff Garvas wrote:
> I'm running Version 2.1.5 in a qmail environment. I recently had to deal
> with
I'm running Version 2.1.5 in a qmail environment. I recently had to deal
with a spam issue (another device on the same segment as me was running
an open proxy and that machine was permitted to relay through me)
Once I solved that one of my larger mailing lists started generating
complaints of use
laced python it wasn't impacting
the already running state of qrunner.
Problem solved. :)
-jeff
On Thu, Aug 05, 2004 at 08:14:45PM -0700 or thereabouts, John W. Baxter wrote:
> On 8/5/2004 12:24, "Jeff Garvas" <[EMAIL PROTECTED]> wrote:
>
> Looks right to me (T
On Thu, Aug 05, 2004 at 09:51:03AM -0700 or thereabouts, John W. Baxter wrote:
> Run python from the command line.
>
> At the prompt, type
> print True
>
> But what matters is what happens on the machine on which True is claimed by
> Mailman to be undefined.
John,
Great idea. So how do I fix
On Thu, Aug 05, 2004 at 02:57:14PM +0900 or thereabouts, Stephen J. Turnbull wrote:
> IIRC the lack of definition of Boolean constants is a problem specific
> to 2.3.2, and all you have to do is define True and False to 1 and 0
> respectively somewhere in the startup. I'm not sure if the mm_cfg i
Here is the latest story in my saga.
I'm running Mailman 2.1.5 with Python 2.3.4
If I create a list and make a user moderated they can't post to the list.
the logs/errors file fills up with a bunch of lines, but this is at the bottom:
File "/usr/local/mailman/Mailman/ListAdmin.py", line 113, in
Hi folks,
I've determined that the problems I'm having with Mailman now are related
to the fact that I have Python 2.3.2 running in Debian (woody). Moderated
messages keep erroring into logs/error about True not being defined.
Does anyone here know of any reliable Python 2.3.3 or 2.3.4 backport
I apologize if this is already documented somewhere. While I can find
lots of information about this error with other applications (and a
different line number) I can't seem to find any information about
this with respect to mailman. If I've missed a FAQ I'm just blind :)
I have mailman+qmail
David,
I run an "announce only" list.
http://www.OhioCCW.org/mailman/listinfo/ccw-alert
Its really easy. You tell people its announcements only, no posts, and
you put it into moderated mode. I even approve the announcement posts
instead of telling mailman to "let them through" to prevent some
I asked about this last week and never saw a response, so I'm going to try
and ask with a little more detail. If anyone has any suggestions, please
let me know. I have not poked around the code to see why this occurs this
way.
When you run a list that is non-moderated, but you limit posts to
I've found either a configuration error (on my part) or a possible flaw in
the way mailman checks posts to lists. Others may not consider this a
flaw, and I appologize if I've managed to miss this in any previous
discussions.
I created a list for testing and told it to limit posts to those
in
I've been testing some sample mailing lists and trying to "break the
rules" for my environment.
For example, I created a list and configured it to be moderated. Then, I
posted a message to the list from a non-member account.
One would expect (or atleast I would) that the administration interf
12 matches
Mail list logo
