Have you updated simscan since you made the changes?
 
/var/qmail/bin/simscanmk
/var/qmail/bin/simscanmk -g
 
Anytime I make updates to the mailserver settings I also using qmail-inject to send a message through (great for showing what is failing):
echo "mail test message" > /tmp/mailtest.txt
env QMAILQUEUE=/var/qmail/bin/simscan SIMSCAN_DEBUG=2 /var/qmail/bin/qmail-inject [EMAIL PROTECTED] < /tmp/mailtest.txt
 
George.
 
----- Original Message -----
Sent: Tuesday, June 06, 2006 6:53 AM
Subject: RE: [qmailtoaster] SpamAssasssin and alternate SMTP port

Jake,

 

I rebooted the server and sent a new email but to no avail – there still aren’t lines in the header like below:

 

X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on 
        ns1.vickersconsulting.net
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,
        JV_Junk3r,SARE_SUB_OBFU_Q1 autolearn=no version=3.1.0

 

Any other ideas?  Not sure what could be the causing the problem to be honest.

 

Thanks for your help.

 

Jon

 


From: Jake Vickers [mailto:[EMAIL PROTECTED]
Sent: Monday, June 05, 2006 7:26 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] SpamAssasssin and alternate SMTP port

 

Jon M. Ernster wrote:

I’m just having problem sending out.  Since my ISP blocks port 25 I have to use their SMTP server, or setup an alternate port on my mail server which I know my ISP has open (8889).

 

BTW, even though the status of spamd is now up, I sent an email from an external address to my mail server and the header didn’t indicate any checking by spamassassin – is the spamassassin pretty much bare bones and I have to add a bunch of rules to learn from now?  (Forgive me, this is the first time I’ve set up a production web/mail server on Linux – I’m use to having cpanel which made things pretty easy)

 

I checked out your site and installed the qmail-spam script – was reading your spam sucks section too, that’s why I’m asking…I’ll have to read all of it when I’m not at work. J

 

You can set it up to send through their mail server, which should accept port 25 to it.
If you haven't done so, reboot the machine. Send a message again, and check the /var/qmail/spamd/current log, as well as the /var/log/qmail/smtp log and see if the logs coincide.
In the header of your messages, you should see something like this:

From - Mon Jun 05 22:22:20 2006
X-Account-Key: account10
X-UIDL: 1149560404.M29408P21575V0000000000000308I005B831F.ns1.vickersconsulting.net,S=12982
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
Content-Filter: maildrop-toaster
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 21558 invoked by uid 89); 6 Jun 2006 02:20:03 -0000
Received: by simscan 1.1.0 ppid: 21543, pid: 21554, t: 1.2130s
         scanners: clamav: 0.87.1/m:34/d:1162 spam: 3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on 
        ns1.vickersconsulting.net
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,
        JV_Junk3r,SARE_SUB_OBFU_Q1 autolearn=no version=3.1.0
Received: from unknown (HELO ns1.qmailtoaster.com) (38.99.66.144)
  by ns1.vickersconsulting.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 6 Jun 2006 02:20:02 -0000
Received-SPF: pass (ns1.vickersconsulting.net: SPF record at qmailtoaster.com designates 38.99.66.144 as permitted sender)
Received: (qmail 1549 invoked by uid 89); 6 Jun 2006 02:13:32 -0000
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
List-Post: <mailto:qmailtoaster-list@qmailtoaster.com>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <mailto:[EMAIL PROTECTED]>
Reply-To: qmailtoaster-list@qmailtoaster.com
Delivered-To: mailing list qmailtoaster-list@qmailtoaster.com
Received: (qmail 1543 invoked by uid 89); 6 Jun 2006 02:13:32 -0000
Received-SPF: none (ns1.qmailtoaster.com: domain at dumbfounded.net does not designate permitted sender hosts)

 

Reply via email to