Mail loop

I inherited an RT 0.9.14 system and know very little about it.

Is there a simple way to specify a list of addresses that RT should never
reply to? E.g. we have a user name which is the same as an RT queue name, so
mail from that user can generate a mail loop.

Thanks,

–Bruce bhami@sun.com

Bruce Hamilton, Senior System Administrator

Sun Microsystems, ULAX01, Los Angeles CA, USA

First up, you really. really. desperately want to upgrade to 1.0.5.

If you’re a little bit handy with perl, you can
modify $RTROOT/lib/rt/ui/mail/manipulate. Look for "postmaster"
and add another regexp. If you need help, I can cons up an
example.On Thu, Nov 30, 2000 at 02:03:47PM -0800, Bruce A. Hamilton wrote:

I inherited an RT 0.9.14 system and know very little about it.

Is there a simple way to specify a list of addresses that RT should never
reply to? E.g. we have a user name which is the same as an RT queue name, so
mail from that user can generate a mail loop.

Thanks,

–Bruce bhami@sun.com

Bruce Hamilton, Senior System Administrator

Sun Microsystems, ULAX01, Los Angeles CA, USA


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

Pelcgb-serrqbz abj!

First up, you really. really. desperately want to upgrade to 1.0.5.

If you’re a little bit handy with perl, you can
modify $RTROOT/lib/rt/ui/mail/manipulate. Look for "postmaster"
and add another regexp. If you need help, I can cons up an
example.

Note that this is the bit of code where, in earlier versions,
RT would drop anything from postmaster or daemon into /dev/null
without even a log entry.  This is without any possible doubt
the STUPIDEST thing to ever be programmed into any ticketing
system, and is yet another good excuse to upgrade ASAP.

(And yes, I know why it was there and who put it there, and 
we're all glad it won't happen again.)

J.D. Falk "Laughter is the sound
Product Manager that knowledge makes when it’s born."
Mail Abuse Prevention System LLC – The Cluetrain Manifesto

Hello All,

We once again falled on a rt loop battle. I have a cron job backing up the
db every hours, but this time, i did not need to use it. My disk filled up
before the db was broke with an oversized table and we backup emails on an
imap account in case of rt crash.

Now, i need to know if there is any way, to stop autoresponding for a
auto-responder war. For example, can we stop RT recording correspondence for
a ticket after 50 attachments ?

Any hints, suggestions?

Best regards,
Steve Poirier
Directeur d�veloppement / Project Manager
Inet-Technologies inc.

Has anyone on this list run into a mail loop with another autoresponder.

Is there someway to setup RT or Sendmail to detect the loop and stop sending
mail to the autoresponder.

TIA

Daniel Fairchild - Chief Security Engineer | danielf@supportteam.net

“DFCSE” == Daniel F Chief Security Engineer <-" danielf@supportteam.net> writes:

DFCSE> Has anyone on this list run into a mail loop with another
DFCSE> autoresponder. Is there someway to setup RT or Sendmail to
DFCSE> detect the loop and stop sending mail to the autoresponder.

What version of RT?

I actually had some Klez variang hit my support queue with the return
address as the other address to which it listens, resulting in about
45,000+ attachments to one particular ticket, and a very full mail
queue and mailboxes for the admins. Not a pretty sight.

It turned out to be a bug in the 2.0.14 loop detector (or somewhere
along the chain of code that comprizes it.)

Now, if this autoresponder discards the entire original mail and
creates a new one with its contents, then you’re hosed. There’s no
way to detect that it was in response to something you sent…

Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

Vivek Khera wrote:

Now, if this autoresponder discards the entire original mail and
creates a new one with its contents, then you’re hosed. There’s no
way to detect that it was in response to something you sent…

… but you’re still not completely hosed. See

http://www.fsck.com/pub/rt/contrib/2.0/UpdateSquelch/

and

http://www.fsck.com/pub/rt/contrib/2.0/AutoReplySquelch.tgz
Phil Homewood, Systems Janitor, www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

Why 2.0.14 would be my version :slight_smile:

does one of these fix it.
http://www.fsck.com/pub/rt/contrib/2.0/UpdateSquelch/
http://www.fsck.com/pub/rt/contrib/2.0/AutoReplySquelch.tgz

Thanks for all the help.On Monday 30 December 2002 15:05, Vivek Khera wrote:

“DFCSE” == Daniel F Chief Security Engineer <-"
danielf@supportteam.net> writes:

DFCSE> Has anyone on this list run into a mail loop with another
DFCSE> autoresponder. Is there someway to setup RT or Sendmail to
DFCSE> detect the loop and stop sending mail to the autoresponder.

What version of RT?

I actually had some Klez variang hit my support queue with the return
address as the other address to which it listens, resulting in about
45,000+ attachments to one particular ticket, and a very full mail
queue and mailboxes for the admins. Not a pretty sight.

It turned out to be a bug in the 2.0.14 loop detector (or somewhere
along the chain of code that comprizes it.)

Now, if this autoresponder discards the entire original mail and
creates a new one with its contents, then you’re hosed. There’s no
way to detect that it was in response to something you sent…

Daniel Fairchild - Chief Security Engineer | danielf@supportteam.net
The distance between nothing and infinity is always the same no matter how
close you get to nothing.

“DFCSE” == Daniel F Chief Security Engineer <-" danielf@supportteam.net> writes:

DFCSE> Why 2.0.14 would be my version :slight_smile:
DFCSE> does one of these fix it.
DFCSE> http://www.fsck.com/pub/rt/contrib/2.0/UpdateSquelch/
DFCSE> http://www.fsck.com/pub/rt/contrib/2.0/AutoReplySquelch.tgz

DFCSE> Thanks for all the help.

Those will probably help with autoresponders. The RT self-loop needs
patches to notice when it sends mail to itself:

rt-2.0.14-Interface::Email.patch (383 Bytes)

SendEmail.patch (802 Bytes)

Content-Description: message body text

“DFCSE” == Daniel F Chief Security Engineer <-" danielf@supportteam.net> writes:

Those will probably help with autoresponders. The RT self-loop needs
patches to notice when it sends mail to itself:

While these patches can help, you should also upgrade to the latest
MailTools to fix the underlying bug these patches deal with.

-j

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.