Pete, I think you are on the wrong side of the message trail on  this one. I
think Stan is referring to a Poster that has set Delivery receipt and/or
Read receipt (possibly as a default) to messages that he sends.  Setting
such a person to DIGEST would not have the desired effect since it is the
recipients (the whole list) of the message that are actually generating the
receipt messages (if their mail system supports the return receipt
function).  Possibly setting the culprit to REVIEW or NOPOST and sending him
a message to turn off the setting(s) would solve the problem.

It may be that the recipients email system is not supporting the return
receipt function properly and is sending the receipt to the wrong address
(ala OOO responses)?  Or maybe it has something to do with the
Reply-To= List|Sender|Both|None|net-address,[Respect|Ignore]
list header keyword [Respect|Ignore] parameters?

Maybe an Internet Standards RFC needs to be written to clarify the handling
of some of these extras that email systems are putting on dealing with
automatic responses (OOO, Return Receipts, Reply and Reply All buttons,
etc).  Would a group in mailing list systems (like LISTSERV and (shudder ;)
MajorDomo, etc) be interested in writing one?

Pete wrote
 >> set the subscriber to DIGEST
 >
 >I am talking about filtering out messages of people who REQUEST
 >notifications. Setting someone's email to digest would not achieve
 >that, it only limits the notification response to once per day.

True, but to whom?  Certainly not the posters nor the subscribers ... and
that's a very good thing.

/pete