[rt-users] Endless auto-reply loop

[Sean Quinlan]

We just set up an instance of RT on the webhost (jail shelled) account for
the small non-profit my wife works for. Although the email address used for
support / information requests does get some spam that makes it through
spamassassin, it has never been much and we figured we would just delete
those occasional tickets.

However, within 48 hours we had the misfortune of being emailed by a small
company that apparently uses a mailing list for sending promotions, and that
list is configured to deny incoming emails, and send an email to the sender.
Not a reply, but an email saying the sender has no permission.

See what's coming? We use fetchmail to check the email server every 5
minutes. Every 5 minutes there is an email from this list saying we don't
have permission to post. RT opens a new ticket in response to this email and
auto-reply's. This has been happening every 5 minutes for days now.


Having very limited access to the system, I have been looking for a way to
exclude email addresses from auto-reply. In all my searching I have not
found a concrete answer, or if I did I didn't understand how it applied to
my situation. I did find the following email in the archives:
http://www.mail-archive.com/rt-users@lists.bestpractical.com/msg12292.html

Where Jesse replies:
"And you can always set up individual addresses to not get mail."

But with no further clarification on how to do that. I have looked at the
RTAddressRegexp option, but that does not seem to be intended for the
purpose of blocking outside addresses, and I worry adding the domain of the
problem emailed may have unintended consequences.

Is there a way to configure RT to ignore, or at least not auto-reply, to
certain addresses? Would it be safe to overload RTAddressRegexp for this
purpose or is there a better solution?

Many thanks,
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110118/9bb28b3a/attachment.htm>