> > [EMAIL PROTECTED]: general discussions about Nessus.
> > * To unsubscribe, send a mail to [EMAIL PROTECTED] with
> > "unsubscribe nessus" in the body.
> > * To subscribe again, send a mail to [EMAIL PROTECTED] with
> > "subscribe nessus" in the body
another option:
can you pre-parse the subject line?
In fact, that recent rash of removes made me create this rule in procmail
:0
* ^Subject:.(remove|unsubscribe)
{ EXITCODE = 67 }
:0 a
/dev/null
I suspect that more than human's responsible, its someones new idea to
automatically get 'removed' from 'spam' lists, something in the new
headers triggers someones anti-spam measures (and they did not read RFC's
that tell them how stupid it is to respond directly to a spammer) or some
spammer subscribed his list to the nessus list
(like that idiot who spamms the list once per month telling us how
valuable their 'top hits' web keywords service is)
--
Michael Scheidell
SECNAP Network Security, LLC
Sales: 866-SECNAPNET / (1-866-732-6276)
Main: 561-368-9561 / www.secnap.net
Looking for a career in Internet security?
http://www.secnap.net/employment/
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
* To subscribe again, send a mail to [EMAIL PROTECTED] with
"subscribe nessus" in the body
