[rt-users] Who gets to be a Requestor?

[Michael Erana]

How about funnelling the SPAM reports through a known host so that the SPAM filter can whitelist that host and those messages will get through unscathed... Or create a separate alias for the spam e-mails that is whitelisted (and different from the e-mail address of the RT box).

Michael Eraña, CISSP
CTO
PC Network, Inc.          
eranam at lanusa.com   

 

|=> -----Original Message-----
|=> From: rt-users-bounces at lists.bestpractical.com 
|=> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf 
|=> Of Mike Friedman
|=> Sent: Thursday, March 30, 2006 12:41 AM
|=> To: Jesse Vincent
|=> Cc: rt-users at lists.bestpractical.com
|=> Subject: Re: [rt-users] Who gets to be a Requestor?
|=> 
|=> -----BEGIN PGP SIGNED MESSAGE-----
|=> Hash: SHA1
|=> 
|=> On Wed, 29 Mar 2006 at 22:07 (-0500), Jesse Vincent wrote:
|=> 
|=> >> I've been under the impression that RT will add to the 
|=> Requestor list 
|=> >> for a ticket the origin email address of anyone who 
|=> corresponds on a 
|=> >> ticket, either to create it or for an existing ticket.
|=> >
|=> > That's not the case. If it were, I could add myself as a 
|=> requestor on 
|=> > all your tickets by spamming you. That could be kinda dangerous ;)
|=> 
|=> Jesse,
|=> 
|=> That makes sense.  I guess I was confused because we have a 
|=> perl script that sends notices to people and also updates 
|=> RT, including setting the Requestors to the recipients of 
|=> our notices.
|=> 
|=> Also, since we already get so much spam, we have many 
|=> tickets whose Requestors are spam addresses (i.e., the 
|=> creators of tickets).  We are planning to put up a spam 
|=> interceptor, but we need to decide on the best way to 
|=> design this, because some incoming mail parcels that look 
|=> like spam actually are legitimate *reports* of spam (where 
|=> the actual spam is being forwarded by the complainant) that 
|=> we are obligated to handle and track in RT as well.
|=> 
|=> Anyway, thanks for helping me clear my mind.
|=> 
|=> Mike
|=> 
|=> ____________________________________________________________
|=> _________
|=> Mike Friedman                   System and Network Security
|=> mikef at ack.Berkeley.EDU          2484 Shattuck Avenue
|=> 1-510-642-1410                  University of California at Berkeley
|=> http://ack.Berkeley.EDU/~mikef  
|=> http://security.berkeley.edu 
|=> ____________________________________________________________
|=> _________
|=> 
|=> -----BEGIN PGP SIGNATURE-----
|=> Version: PGP 6.5.8
|=> 
|=> iQA/AwUBRCtvja0bf1iNr4mCEQLn+wCggQL1RjY5kPTLTeCb72gIsTIsA28An2Sm
|=> IALsatZ9SZK7v05jMiZyZHNB
|=> =wh/s
|=> -----END PGP SIGNATURE-----
|=> _______________________________________________
|=> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
|=> 
|=> Community help: http://wiki.bestpractical.com Commercial 
|=> support: sales at bestpractical.com
|=> 
|=> 
|=> Discover RT's hidden secrets with RT Essentials from 
|=> O'Reilly Media. 
|=> Buy a copy at http://rtbook.bestpractical.com
|=> 
|=> 
|=> We're hiring! Come hack Perl for Best Practical: 
|=> http://bestpractical.com/about/jobs.html
|=>