Hello,

I posted to the list recently about upgrading to perl 5.8.2 from 5.8.0 which did
away with suidperl so I was have trouble reinstalling qmail-scanner 1.16. I read the
contrib docs and installed qmail-scanner-queue as the setuid file which makes the
call to qmail-scanner-queue.pl. Well, this apparently is causing the output of SA
2.61 not to be right. What I mean is SA 2.61 is tagging the messages and rewriting
the subject as per my configuration(works great when you just run spamassassin). But
when run through qmail scanner, it's still tagged as spam but its not rewrting the
subject or attaching the original message like its suppose to do via the local.cf
file. I've already posted to the SA list and as below shows, it definitly a
qmail-scanner issue.

This works correctly using spamassassin -t < sample-spam.txt > spam.out.

<Example>
Received: from localhost [127.0.0.1] by redhat.vipersystems.biz
        with SpamAssassin (2.61 1.212.2.1-2003-12-09-exp);
        Wed, 17 Dec 2003 09:54:05 -0500
From: Sender <[EMAIL PROTECTED]>
To: Recipient <[EMAIL PROTECTED]>
Subject: *****SPAM***** Test spam mail (GTUBE)
Date: Wed, 23 Jul 2003 23:30:00 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on
        redhat.vipersystems.biz
X-Spam-Level: **************************************************
X-Spam-Status: Yes, hits=1000.0 required=7.5 tests=GTUBE autolearn=no
        version=2.61
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_3FE06E0D.7002443A"

This is a multi-part message in MIME format.

------------=_3FE06E0D.7002443A
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Spam detection software, running on the system "redhat.vipersystems.biz", has
identified this incoming email as possible spam.  The original message has been
attached to this so you can view it (if it isn't spam) or block similar future
email.  If you have any questions, see
[EMAIL PROTECTED] for details.
<Example>

So, what would cause qmail-scanner not to do the same as above?


-- 
Jason




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general

Reply via email to