Re: [sniffer] Spam Submissions - same spam

2005-03-24 Thread Pete McNeil 
On Thursday, March 24, 2005, 11:00:56 AM, Scott wrote:

SF A question:
SF  
SF If I have the same spam sent to multiple  recipients, should
SF I be submitting more than one copy to [EMAIL PROTECTED]

If you mean there are multiple recipients in the SMTP envelope then we
only need one copy.

If there are separate envelopes then chances are there will be subtle
changes that we can use - so please send each one.

Thanks,

_M




This E-Mail came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

Re: [sniffer] Spam submissions

2004-07-28 Thread Pete McNeil 
On Wednesday, July 28, 2004, 5:34:43 AM, Landry wrote:

LW Pete, I put together a little script that modifies the Q*.SMD
LW file for identified spam messages that were held in my spam
LW directory, but were not tagged by Sniffer, and can forward a copy
LW of these messages to your spam@ address.  However, the messages
LW will look like they came from the original sender and will also
LW show the original recipient on the To line.  For example,
LW queue-file Qff1e0159007addb3.SMD could originally look like (all
LW sender and recipient domains masked):

snip/

LW This script is not automated so it is not going to be sending
LW you unconfirmed spam.  We will only forward messages that have
LW been confirmed by one of our staff to be spam and that Sniffer did
LW not tag.  This way I can forward specific messages that end up in
LW my spam directory to you from a remote command line on the server,
LW and you will receive the message in its original intended format,
LW including sender and recipient information.  I will not start
LW forwarding spam to your spam@ address until I hear that this
LW process would be okay with you.

This sounds great!

Thanks!
_M

PS: It is possible to create virtual spam traps on systems that use a
sufficient number of additional tests. Essentially, if the message
would normally be held or dropped based on the other tests and it
still failed Sniffer then it would be reasonable to automatically
forward that to spam@ in the way you describe. In many cases this
content is clean enough to be processed with the same rules we use for
normal spamtraps. We have been considering the creation of a new class
of processing for this kind of virtual spamtrap.




This E-Mail came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: [sniffer] Spam submissions

2004-07-28 Thread Landry William 

-Original Message-
From: Pete McNeil [mailto:[EMAIL PROTECTED]

LW Pete, I put together a little script that modifies the Q*.SMD file
LW for identified spam messages that were held in my spam directory,
LW but were not tagged by Sniffer, and can forward a copy of these
LW messages to your spam@ address.  However, the messages will look
LW like they came from the original sender and will also show the
LW original recipient on the To line.  For example, queue-file
LW Qff1e0159007addb3.SMD could originally look like (all sender and
LW recipient domains masked):

snip/

LW This script is not automated so it is not going to be sending you
LW unconfirmed spam.  We will only forward messages that have been
LW confirmed by one of our staff to be spam and that Sniffer did not
LW tag.  This way I can forward specific messages that end up in my
LW spam directory to you from a remote command line on the server, and
LW you will receive the message in its original intended format,
LW including sender and recipient information.  I will not start
LW forwarding spam to your spam@ address until I hear that this process
LW would be okay with you.

This sounds great!

Thanks!
_M

PS: It is possible to create virtual spam traps on systems that use a
sufficient number of additional tests. Essentially, if the message would
normally be held or dropped based on the other tests and it still failed
Sniffer then it would be reasonable to automatically forward that to spam@
in the way you describe. In many cases this content is clean enough to be
processed with the same rules we use for normal spamtraps. We have been
considering the creation of a new class of processing for this kind of
virtual spamtrap.

=

Let me look into it a bit to see how I might be able to accomplish this.
I'll report back soon...

Bill

---
This message and any included attachments are from Siemens Medical Solutions
USA, Inc. and are intended only for the addressee(s). 
The information contained herein may include trade secrets or privileged or
otherwise confidential information.  Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful.  If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to [EMAIL PROTECTED]

Thank you

This E-Mail came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html