Oh I see that now, I guess at some point (can't remember that far back)
I got help customizing 1.20 with some reporting changes here's a sample
of the 1.20 reports I get for quarantine spam:
Attention: [EMAIL PROTECTED]
A 12.3 problem: was found in an Email message you sent.
This Email scanner intercepted it and stopped the entire message
reaching its destination.
The 12.3 problem: was reported to be:
SPAM exceeds "quarantine" threshold - hits=12.3
Please contact your IT support personnel with any queries regarding this
policy.
Your message was sent with the following envelope:
MAIL FROM: [EMAIL PROTECTED]
RCPT TO: [EMAIL PROTECTED]
... and with the following headers:
---
MAILFROM: [EMAIL PROTECTED]
Received: from bzq-88-155-205-123.red.bezeqint.net (88.155.205.123)
by mail2.adventureaquarium.com with SMTP; 8 Jun 2006 17:31:54 -0000
Received: from gix ([88.155.194.102])
by bzq-88-155-205-123.red.bezeqint.net (8.13.2/8.13.2) with SMTP
id k58IXNCc051963;
Thu, 8 Jun 2006 20:33:23 +0200
Message-ID: <[EMAIL PROTECTED]>
From: "Joanna Tanner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: dupe dinghy
Date: Thu, 8 Jun 2006 20:23:19 +0200
MIME-Version: 1.0
Content-Type: multipart/related;
type="multipart/alternative";
boundary="----=_NextPart_000_000B_01C68B3A.906A7E60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1158
---
The original message is kept in:
mail2.adventureaquarium.com:/var/spool/qmailscan/quarantine
where the System Anti-Virus Administrator can further diagnose it.
If your Message is clean it will be sent on to the intended recipients.
The Email scanner reported the following when it scanned that message:
---
---spamassassin results ---
12.3 problem: 'SPAM exceeds "quarantine" threshold - hits=12.3'
found in message
/var/spool/qmailscan/tmp/mail2.adventureaquarium.com11497879155118740
---
The warning doesn't actually get sent to the sender. I think are nice to
get. They let me know if I might have so FP's long before I actually try
digging through the quarantine dir (gets kinda crowded in there). I get
a similar report for the sa_delete spams and virus/file blocks too.
Jason
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 08, 2006 1:15 PM
To: Jason Staudenmayer; qmail-scanner-general@lists.sourceforge.net
Subject: RE: [Qmail-scanner-general] Add spam report to quarantine
notice
> I was able to update my q-s to 2.01 and finally got the patch to go
in
> right. I set my options plus the ones below but q-s is not marking
> anything for quarantine. I'm using a test tcp.smtp rule so I'm only
> running q-s-2.01 for one IP. I'm pumping good spam (scores 15.7) but
> it's marked as clean.
HI Jason
It is marked as clear because no virus was found but it is marked as
spam, you can see it
> Received: from 207.106.0.242 by ns2.adventureaquarium.com (envelope-
from
> <[EMAIL PROTECTED]>, uid 503) with qmail-scanner-2.01st
> (clamdscan: 0.88.2/1521. spamassassin: 3.1.1. perlscan: 2.01st.
> Clear:RC:0(207.106.0.242):SA:1(15.7/7.5):.
> Processed in 0.821819 secs); 08 Jun 2006 15:47:59 -0000
> X-Spam-Status: Yes, hits=15.7 required=7.5
> X-Spam-Level: +++++++++++++++
X-Spam-Status: Yes
> X-Qmail-Scanner: 2.01st (Clear:RC:0(207.106.0.242):SA:1(15.7/7.5):.
> Processed in 0.821819 secs Process 5408)
And also SA:1(15.7/7.5)
Well this is the way it works...
ST
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
