Hello!
I see that there are some mailling list managers (e.g. sympa)
which use the tag “list” in the precedence field. So I suggest the
following modification:
regards!
sven
— lib/RT/Interface/Email.pm 2006-10-20 18:37:05.000000000 +0200
+++ local/lib/RT/Interface/Email.pm 2007-03-08 17:24:46.000000000
+0100
@@ -158,7 +158,7 @@
my $head = shift;
my $Precedence = $head->get("Precedence") || "";
- if ( $Precedence =~ /^(bulk|junk)/i ) {
- if ( $Precedence =~ /^(bulk|junk|list)/i ) {
return (1);
}
Hello!
I see that there are some mailling list managers (e.g. sympa)
which use the tag “list” in the precedence field. So I suggest the
following modification:
The goal of the precedence check is to avoid mail looping. Usually
“bulk” or “junk” indicates an autoresponder that’s going to get into a
looping argument with RT. Is that an issue you’re running into with
sympa?
The goal of the precedence check is to avoid mail looping. Usually
“bulk” or “junk” indicates an autoresponder that’s going to get into a
looping argument with RT. Is that an issue you’re running into with
sympa?
It should also check for Auto-generated headers and not respond to
auto-generated or auto-responded email. 
But really, RT needs a throttle on how many responses it sends to a
given address per some time unit. There are so many b0rked
autoresponders out there that you can’t account for all of them.
smime.p7s (2.47 KB)
Hello!
looping argument with RT. Is that an issue you’re running into with
sympa?
Yes, we had a lot of problems with the sympa mailing list manager at
our site but also with other mailing list manager from the outside.
- people try to subscribe queues to mailing list
- queue receive posts from ml and we send auto replies
- people cc mailing lists in ticket correspondence
It should also check for Auto-generated headers and not respond to
auto-generated or auto-responded email.
yes we hope to archive this with Set($RedistributeAutoGeneratedMessages,
‘privileged’);
We also have extra rules for procmail but of course they only work
for the mailing list we know about.
But really, RT needs a throttle on how many responses it sends to a
given address per some time unit. There are so many b0rked
autoresponders out there that you can’t account for all of them.
sounds good, but difficult to implement in a generic way.
best regards and i hope that my mini patch will be included!
sven