I would be very interested in hearing of various mechanisms for trimming over-quoting, including a hold on replies that match some kind of regexp. I know about M. Sapiro's posting at http://mail.python.org/pipermail/mailman-users/2008-April/061227.html which refers me (in the bottom link) to the FAQ _in toto_, but if there's a more pointed location or recent thread, I'd like to know.
Before I started running Mailman a decade or two ago, I used SmartList, for which I wrote and contributed a quote-aware filter. I would be interested in contributing this work to Mailman if it hasn't already been done, or superseded by other concerns.
thank you in advance. Rob
-- Rob Lingelbach rob@colorist.org
Rob Lingelbach wrote:
I would be very interested in hearing of various mechanisms for trimming over-quoting, including a hold on replies that match some kind of regexp. I know about M. Sapiro's posting at http://mail.python.org/pipermail/mailman-users/2008-April/061227.html which refers me (in the bottom link) to the FAQ _in toto_, but if there's a more pointed location or recent thread, I'd like to know.
Actually, that FAQ link used to go to the specific article which is now at <http://wiki.list.org/x/l4A9> before the FAQ was moved.
That FAQ discusses how to install custom handlers to do these kinds of things.
Before I started running Mailman a decade or two ago, I used SmartList, for which I wrote and contributed a quote-aware filter. I would be interested in contributing this work to Mailman if it hasn't already been done, or superseded by other concerns.
I too would be interested if this is done using Python or if it can be refactored for Python.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Jul 4, 2010,
Actually, that FAQ link used to go to the specific article which is now at <http://wiki.list.org/x/l4A9> before the FAQ was moved.
That FAQ discusses how to install custom handlers to do these kinds of things.
Thank you, I'll see if I can work up an understanding of it.
procmail recipes for enabling rejection :
http://www.animalgenome.org/SmartList/contrib/reject_garbage.txt
the specific recipe for rejecting a message with overquoting was this one below. The weighting of quoted versus non-quoted lines, represented by the numbers 20 and -10, was arrived at by trial and error, and as I recall, was fairly lenient toward quoting so as not to make too many subscribers complain. Looks like I was pedantic enough in text of the rejection message. Also, today the quoting is done with some form of rich text at times, is it not?
-----cut here----
# mine (rob <a> colorist.org , 1998) :0 hBHw
20^1 ^>
-10^1 ^[^>] { :0c | formail -i "Subject: ***quote REJECT engaged"| $SENDMAIL -oi $maintainer
:0 | quotereject -attach}
case $function in
-attach)
($formail -i"From: $listreq" -rtA"X-Loop: $listaddr" < $tmprequest ;
$echo "Your mail to the mailinglist has been intercepted and"
$echo "is being returned to you because it it appears to the list server"
$echo "to contain an excessive amount of quoted material."
$echo "Brief quoting is fine, but please quote only for context."
$echo "Do not quote other messages in their entirety, or quote"
$echo "message headers or signature files. "
$echo " "
$echo "...excessive quoting is a waste of resources."
$echo "If you feel that you've edited your message adequately but"
$echo "it was still returned to you, you can appeal to the administator,"
$echo "rob <a> colorist.org"
$echo " "
$echo "[message follows]"
$echo " "; cat $tmprequest)
| $SENDMAIL $sendmailOPT $sender
shift ;;
esac
-----cut here-----
Rob
Rob Lingelbach rob@colorist.org
Rob Lingelbach wrote:
the specific recipe for rejecting a message with overquoting was this one below. The weighting of quoted versus non-quoted lines, represented by the numbers 20 and -10, was arrived at by trial and error, and as I recall, was fairly lenient toward quoting so as not to make too many subscribers complain. Looks like I was pedantic enough in text of the rejection message. Also, today the quoting is done with some form of rich text at times, is it not?
-----cut here----
# mine (rob <a> colorist.org , 1998) :0 hBHw
- 20^1 ^>
- -10^1 ^[^>]
The attached Quoting.py is a handler which could be installed per the FAQ at <http://wiki.list.org/x/l4A9> to do essentially what it says in its docstring.
If I understand your procmail conditions , they would correspond roughly to RATIO = 0.5 in the attached, i.e. quoted lines >= 0.5 * unquoted lines, but not exactly because yours includes the message headers which presumably would all be unquoted.
Also, the attached handler holds the message rather than rejects it, although it could easily be changed to reject.
A proper implementation would make this hold/reject/discard decision a list setting as well as making the ratio and the regexp for a quoted line list settings too.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Jul 5, 2010, at 11:50 AM, Mark Sapiro wrote:
This time, it's really attached (renamed Quoting.py.txt to get through content filtering)
This will be a lot of fun to look at and implement. Holding the message is a much better option than a rejection. And now I know how to sneak suitable attachments through Mailman.
-- Rob Lingelbach rob@colorist.org
participants (2)
-
Mark Sapiro -
Rob Lingelbach