> "Rodolfo" == Rodolfo Pilas <[EMAIL PROTECTED]> writes:
Rodolfo> I have the problem again:
Rodolfo> load average: 1.08, 1.02, 1.01
Rodolfo> # tail logs/qrunner Oct 16 21:11:00 2001 (738) Master
Rodolfo> qrunner detected subprocess exit (pid: 743, sig: 15, sts:
Rodolfo>
> "David" == David Champion <[EMAIL PROTECTED]> writes:
David> Please, no. If a message goes to a list, I want to receive
David> it from the list. That's critical to local archiving, and
David> it has some effect on how a recipient perceives the message
David> itself. I'd rath
I have the problem again:
# uptime
8:43pm up 5:44, 1 user, load average: 1.08, 1.02, 1.01
# ps ax
738 ?S 0:00 python bin/mailmanctl -n start
739 ?S 0:00 python bin/mailmanctl -n start
740 ?S 0:20 python bin/mailmanctl -n start
741 ?S
On Tue, Oct 16, 2001 at 11:37:46AM -0500, David Champion wrote:
> On 2001.10.16, in <[EMAIL PROTECTED]>,
> "Marc MERLIN" <[EMAIL PROTECTED]> wrote:
> > > Ben's attacks the problem by ensuring that an individual only
> > > gets delivered one copy of an email (based on the message ID)
> > > (i
On 2001.10.16, in <[EMAIL PROTECTED]>,
"Marc MERLIN" <[EMAIL PROTECTED]> wrote:
> > Ben's attacks the problem by ensuring that an individual only
> > gets delivered one copy of an email (based on the message ID)
> > (ie at the delivery stage)
>
> This is indeed what I need.
> (it apparent
On Tue, Oct 16, 2001 at 08:33:44AM -0700, Marc MERLIN wrote:
> > What problem are you trying to tackle?
>
> People who are trying to set reply-to munging because they don't want
> receipients to receive two copies of the posts. While the solution is bad,
> the initial need is real.
> (we
On Tue, Oct 16, 2001 at 11:40:31AM +0800, Mark Tearle wrote:
> Mine attacks the problem by enabling lists to be set up which
> can pull there membership in from other lists.
> (ie at the who is on the list stage of the pipeline)
I looked at your patch closer and you're right. Sorry for the
misun
> "RJ" == Ron Jarrell <[EMAIL PROTECTED]> writes:
RJ> Really, I think we need to redesign large chunks of the admin
RJ> page, and set up multiple access classes.
RJ> Perhaps more generically, we need to make a list of all the
RJ> things people are allowed to do, and set up a
