[Mailman-Developers] cgi/mail delivery problem: an idea

[Scott]

First I'd like to say sorry I've kindof dropped off keeping up with
mailman over the last few days.  I will come back, i've just been
really busy with other stuff. 

At any rate, there's a problem with the way certain processes have to
wait for the completion of delivery of a message (or even lotsa
messages) before finishing.

you'll note that mass subscribe, admindb, convert_list, and many other
processes can trigger a mail delivery and that in many of those cases,
waiting for the delivery causes problems (especially the cgi's).

Here's an idea of how to deal with.  i'm just bouncing this off
everyone for now:

add a mechanism that just queue's messages in mailman's mail queue,
and let the run_queue cron job take care of it.

some things to consider about this:  

1) there's been talk of setting up mailman to allow command line
delivery again (i'm all for this).  we'd have to take that into
account in run_queue. 

2) the cgi's would no longer immediately make those deliveries, the
   deliveries would take place on the next cron job.  this may not be
   entirely appropriate in some cases, like receiving a confirmation
   messages upon subscribing from the web.


this is a problem that i believe should be addressed before v1 or
whatever. 

what do y'all think?

scott