RT could do that, but that wouldn't catch any email addresses that forward stuff to an RT email address, or if using fetchmail, that forward stuff to an email address RT pulls from.
On Tue, Jul 27, 2010 at 5:02 PM, Joseph Spenner <[email protected]>wrote: > If life gives you lemons, keep them-- because hey.. free lemons. > > > --- On *Tue, 7/27/10, Mike Johnson <[email protected]>* wrote: > > > From: Mike Johnson <[email protected]> > Subject: Re: [rt-users] RTAddressRegexp - not clear to me > To: "Joseph Spenner" <[email protected]> > Cc: [email protected] > Date: Tuesday, July 27, 2010, 2:35 PM > > > It's really a safeguard, because not everyone that uses your RT instance > is "smart" enough to prevent loops from happening. > > And my example showed 2 queues... but you only need email address and a > "goofy" user for a loop to happen that will cripple the system. > > I've had end-users reply to an email coming from <Mike Johnson via > RT>(which the Reply-To: on those emails is > [email protected]<http://mc/[email protected]>) and > cc [email protected] <http://mc/[email protected]>. > > If you use the ParseNewMessageForTicketCcs, the above can become quite > troublesome without RTAddressRegexp, as it would append > [email protected]<http://mc/[email protected]>as a Cc email address, > which would then email out to > [email protected] <http://mc/[email protected]> whenever you do > correspondence that a Cc would see... > > Hope that helps! > Mike. > > Why couldn't the application simply query the database to figure out what > the queue email addresses are, and don't permit them to be a recipient? > > > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > -- Mike Johnson Datatel Programmer/Analyst Northern Ontario School of Medicine 955 Oliver Road Thunder Bay, ON P7B 5E1 Phone: (807) 766-7331 Email: [email protected]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
