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

[Mike Friedman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 30 Mar 2006 at 05:41 (-0500), Michael Erana wrote:

> 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,

The problem is not how to do the initial filtering.  It's that only a 
human being (not a program or script) can tell the difference between 
forwarded spam that's part of a legitimate spam *report* and original 
spam, both of which are likely to be flagged by spam detectors.  (After 
all, the format of a mail message containing forwarded spam could be 
almost anything).

So, one possibility is to divert all apparent spam (before it reaches RT) 
into a mailbox that a person would have to look at.  This person would 
bounce the legitimate reports on to RT, throwing away the rest (i.e., the 
actual spam).  Unfortunately, this promises to be such a waste of 
someone's time, because the legitimate reports are only a tiny percentage 
of all mail that's flagged as spam.

Mike

=============================================================================
> |=> 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.
> |=>
> |=> 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/AwUBRC1oJ60bf1iNr4mCEQJo9wCaAz2RY0IP4fG6S7d6ui7sEHkClQsAn2ti
4lmeBIY028Y+ncysDkdyBKmW
=HYPR
-----END PGP SIGNATURE-----