>>>>> "S" == SRE <eckert@climber.org> writes:
S> Point me to the right part of the code and I'll take a stab at it.
Make Mj::Deliver::deliver keep count (although what you want to keep count
of is questionable, since it delivers digests and normal messages at the
same time in parallel). Return the count. Make Mj::Mailout::deliver
return this count as well, perhaps in a or hashref so you could keep track
of digest subscribers and other classes separately). Take those results
and send them back to the user where appropriate.
S> It's useful for the person sending the post in two ways.
You haven't convinced me to spend any time on it at all. It's "gee whiz
factor", chrome, whatever. IMHO useless. Not that I won't take a patch,
if it's well done. That's always the case.
S> And since we all want Mj2 to be a real competitor, I'll mention the
S> ListServ software which has this as its default behavior.
I've said it before and I can't say it any more strongly: I don't care one
whit what Listserv does. Next you're going to want to keep track of CPU
usage as well, so we can report back another bit of entirely useless data?
S> See, it's a nice package. How many people it was sent to (not whether it
S> was delivered, which you correctly point out would be difficult to
S> know), what the subject was, which list it went to, and the "set"
S> command can be used to turn the messages on or off on a per-list
S> basis.
Wow. So I have no idea of all of those users are on the digest and won't
get it until next week. I'm in no better a state than I was before.
- J<
References:
|
|
