Thanks, Peter for your suggestions.
The problem is not so much the high volume of messages, but with replies being sent to the list, instead of to the original sender or to another address specified by the sender using the reply-to field in
the mail header.
So sizelim is not the answer.
I have also thought about using the “topics” mechanism, but this is good for defining who receives messages, and will not prevent a user to reply to the list (or simply do a reply-all) instead of to the sender.
AM I missing something here – please correct me if I’m wrong…
I am aware that I’m trying to find a technical solution to a human-behavioral issue (assuming the user’s mail program behaves “well”).
Thanks,
/Zvika
From: LISTSERV List Owners' Forum <[log in to unmask]>
On Behalf Of Peter M. Weiss
Sent: Wednesday, October 21, 2020 7:31 PM
To: [log in to unmask]
Subject: Re: FW: Controlling Reply Messages
Maybe some partial remediation?
If any high daily volume by users, have a daily limit (I've forgotten all of the sub-parms).
Also, a SIZELIM= (remembering HTML are larger) may cut down how many cascaded replies
If particular users, maybe SET REVIEW.
Implement TOPICS= and default the reserve OTHER so no one receives those (except DIGEST) but instead has a catch-all for non-categorized as MISC.
Just my 2 agorot
On 10/21/2020 11:04, Bar-deroma Zvi wrote:
Ooops – I forgot to mention – I suggested sender=…,confirm but the idea was rejected.
To unsubscribe from the LSTOWN-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1
This email is from an external mail server, be judicious when opening attachments or links