We are using the latest version of RT and now we have the problem that
sometimes overnight 4000 to 10000 requests are created by
autoresponders, mainly by GMX. That means that f.e. a GMX user sends
an email at 10 pm to our queue and the RT replies with the standard
answer and the ticket ID. The autoresponder of the user answers with
the standard text and RT replies with the standard answer and a new
ticket ID …
This is a very serious problem because approximatly all 20 to 30 hours
I have to stop the request tracker, remove all the dummy entries form
the database and restart the request tracker.
Are there any known ways to handle such a everyday problem?
That’s just no good. Do these autoresponder messages have any
notation that they’re from autroresponders? (Such as a precedence: bulk)
header? Also, what version of RT are you running, exactly? ‘latest’
can be interpreted many different ways by many different folks.
-jOn Sun, Mar 04, 2001 at 04:06:26PM +0100, Hansjoerg Posch wrote:
Hello!
We are using the latest version of RT and now we have the problem that
sometimes overnight 4000 to 10000 requests are created by
autoresponders, mainly by GMX. That means that f.e. a GMX user sends
an email at 10 pm to our queue and the RT replies with the standard
answer and the ticket ID. The autoresponder of the user answers with
the standard text and RT replies with the standard answer and a new
ticket ID …
This is a very serious problem because approximatly all 20 to 30 hours
I have to stop the request tracker, remove all the dummy entries form
the database and restart the request tracker.
Are there any known ways to handle such a everyday problem?
Ugh. sadly, that’s not at all standard…not that there is an official
standard, but most folks who write autoresponders have the common courtesy
of setting the Precedence header to ‘bulk’.
Basically, what you want to do is add some code to lib/rt/ui/mail/manipulate
just after this:
That’s just no good. Do these autoresponder messages have any
notation that they’re from autroresponders? (Such as a precedence:
bulk)
header? Also, what version of RT are you running, exactly?
‘latest’
can be interpreted many different ways by many different folks.
-j
On Sun, Mar 04, 2001 at 04:06:26PM +0100, Hansjoerg Posch wrote:
Hello!
We are using the latest version of RT and now we have the problem
that
sometimes overnight 4000 to 10000 requests are created by
autoresponders, mainly by GMX. That means that f.e. a GMX user
sends
an email at 10 pm to our queue and the RT replies with the
standard
answer and the ticket ID. The autoresponder of the user answers
with
the standard text and RT replies with the standard answer and a
new
ticket ID …
This is a very serious problem because approximatly all 20 to 30
hours
I have to stop the request tracker, remove all the dummy entries
form
the database and restart the request tracker.
Are there any known ways to handle such a everyday problem?