Hi Jeff,
I seem to get a number of emails that stop spamx in its track with the above error message. I have to manually remove them from my spam folder and then after refreshing I can carry on. Here is a copy of the log for one such message.



X-Account-Key: account3
X-UIDL: 8408f67cdae81c985f33dc80b75bb2f3
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000
X-Apparently-To: **************** via 206.190.39.208; Sat, 16 Oct 2004 23:39:58 +0000
X-YahooFilteredBulk: 200.223.170.34
X-Originating-IP: [200.223.170.34]
Return-Path: <ldsyfpwvsdxst@yahoo.com>
Received: from 200.223.170.34 (HELO 195.50.106.7) (200.223.170.34)
by mta120.mail.ukl.yahoo.com with SMTP; Sat, 16 Oct 2004 23:39:58 +0000
Received: from 32.80.165.235 by 200.223.170.34; Sat, 16 Oct 2004 18:32:53 -0600
Message-ID: <TVIUPAPDVQQHVLULYUYEGPQ@yahoo.com>
From: "Jodie Steele" <ldsyfpwvsdxst@yahoo.com>
Reply-To: "Jodie Steele" <ldsyfpwvsdxst@yahoo.com>
To: rockatlantic@yahoo.co.uk
Cc: rockbabe89@yahoo.co.uk, rockchick56ew@yahoo.co.uk, *********************
Subject: [Bulk] did you see my picture?
Date: Sat, 16 Oct 2004 19:39:53 -0500
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="--446259623872953"
X-Priority: 3
X-MSMail-Priority: Normal found 200.223.170.34 by originating IP
lookup 200.223.170.34
sending lookup 200.223.170.34
receiving 1194 bytes from North America
disconnecting
lookup 200.223.170.34
lookup done
sending lookup 200.223.170.34
receiving 1598 bytes from Latin America
disconnecting
lookup 200.223.170.34
lookup done
sending lookup 200.223.170.34
receiving 698 bytes from Brazil
disconnecting
lookup abuse
lookup done
sending lookup
receiving 2 bytes from abuse
disconnecting
nothing to do reportspammer
abuse done

Although I cannot offer a solution to this problem, you may wish to note that you are not alone. I too encounter the same problem from time to time and employ the same solution.

Like you I hope that someone can provide a solution.

Regards,

Stan Kay

I'm on it...

I'll have something for this in the next code release...

2.2.4 seems to have fixed this, but I am now getting messages that stop the application with "status - looking in North America" and one or two others (this is the one sitting on my screen for the last hour).

After several minutes (I have let it run overnight just to be sure), I manually move the offending message and start again.

Sounds like a few additional timers and rule for routing to notprocessed on timeouts could be useful.

Thanks for this feedback.

I'm working on it!

Until I get this timing code modification done, you can click 'Process Selected' and SpamX should pick right up and process the bunch...

I'll let you know when it's done.

Yowza - that was fast

We're here to serve...