RT-Bounce

We had a bounced email show up in our RT queue this morning, and it caused
an unending loop. I don’t see any mention of problems in the documentation,
but I was wondering if it is common? Is there a way to prevent it?

Thanks!

Sincerely,
Joe Johnson
Fox Valley Internet
jajohnson@fvi.net

It’s not command RT should detect such things and cope. Can you get us
an exact copy of the message with all headers intact?On Thu, May 27, 2004 at 10:56:06AM -0500, Joe Johnson wrote:

We had a bounced email show up in our RT queue this morning, and it caused
an unending loop. I don’t see any mention of problems in the documentation,
but I was wondering if it is common? Is there a way to prevent it?

Thanks!

Sincerely,
Joe Johnson
Fox Valley Internet
jajohnson@fvi.net


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

RT Developer and Administrator training is coming to LA, DC and Frankfurt this spring and summer.
http://bestpractical.com/services/training.html

Sign up early, as class space is limited.

I removed the config to stop it for happening again, but I’ll try to see if
I can get it to repeat. It may be a while.

JoeFrom: “Jesse Vincent” jesse@bestpractical.com
To: “Joe Johnson” jajohnson@fvi.net
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, May 27, 2004 11:24 AM
Subject: Re: [rt-users] RT-Bounce

It’s not command RT should detect such things and cope. Can you get us
an exact copy of the message with all headers intact?

We had a bounced email show up in our RT queue this morning, and it
caused

an unending loop. I don’t see any mention of problems in the
documentation,

but I was wondering if it is common? Is there a way to prevent it?

Thanks!

Sincerely,
Joe Johnson
Fox Valley Internet
jajohnson@fvi.net


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

RT Developer and Administrator training is coming to LA, DC and
Frankfurt this spring and summer.

http://bestpractical.com/services/training.html

Sign up early, as class space is limited.

Hi,
we had a similar problem with a AdminCC bouncing and the return
message did not get filtered correctly – creating another ticket with
the AdminCC added by way of Queue-AdminCC. Nice, 800 tickets in 20 minutes.

We believe (running 3.0.10) there is no check in RT::Ticket->Create 

that will filter out this. Although there is a module
RT::EmailParser->CheckForSuspiciousSender() that will actually do just
what we needed here.

We decided to add the following test in RT::Ticket->Create(). It's 

not quite nice enough as really there should be a check not only for
certain requestors that often bounce, but also Mail::RFC822::Address
checked; I just check for length. I would much rather see this kind of
check configurable through the RT_SiteConfig.pm though.

# quick fix, just before calling RT::User->new() in 

RT::Ticket->Create().
if ( $args{Requestor} =~ /(mailer-daemon|postmaster)/i ||
length($args{Requestor})<4 ) {
return (0, 0, “’$1’ is not a valid requestor” );
}

BTW: The Mail::RFC822::Address check, we decided to put into
User->Create so that we can rely on the email address to be at least
once checked when creating a new User (automatically or manually).

Hope this helps you too.

Ralf.

Joe Johnson wrote: