I don't think we can blame LP for this one, I believe it's because of the CPanel upgrade.

Most servers that I personally deal with (I use one, and have several clients I do freelance programming for spread across other servers) all show me the exact same behavior you describe. Our subject rewrites no longer work, they all have "***SPAM***" as a prefix now, regardless of our user_prefs, but this was already explained as something we could not control with the upgrade.

The other one, of course, is the SpamAssassin explanation as to why something was flagged as spam, and using the X-Spam-Status and X-Spam-Report message headers, and the back-end mail filtering seems to ignore the "spam box". Again, I believe this is a change instituted by the whole CPanel/SpamAssassin setup in Cpanel v11. Personally, I'm getting tired of rewriting my code and documentation to all of these changes ;o) It's getting much, much harder to automate the process of taking care of spam.

Personally, I'm just tired of this issue dragging on for so long -- it's been, what, two months now (mid-August!!) -- SpamAssassin *still* stops running every couple of days on my server, and I'll get dozens of spam in my Inbox per day. One of my client ends up with hundreds of spam messages per day when this happens. I've been tempted to watch incoming Emails and send an automated message to support whenever I see that spam scoring is turned off, and requesting it get restarted... but that'd probably get really annoying and LP wouldn't be very happy with me, heh.

I've looked at other third-party filtering but that's just a pain. Unfortunately I have no good answer for you other than to manually move spam messages back into your spam folder manually or set up a mail filter in your own Email client (Outlook, Thunderbird, etc).

I don't think Mitch's response yesterday was accurate -- CPanel 11 has most definitely changed the behavior of SpamAssassin.

Yeah, usually consider recent being the last few days and not the last few months.   If you want to double check, support should be able to look in on your specific account and give you a little more information than I can over the forum here though. 

Hey all, sorry my silence lately. Anyone running the newest version with the flag turned on to check for new versions, I apologize for a script error on my side; I recently moved my iandouglas.com site to a new hosting provider.

I get the following error:

Software error:
Could not connect to iandouglas.com to check for a new version of this software.<br />

I hadn't ran the script in awhile.  It use to work but now I get this error.  How do I fix this.

Thanks

Thanks.  Just so everyone is clear line 505 should be

print '<p><a href="/cgi-bin/'.$0.'">re-scan mailboxes</a><br />' ;

Notice the added " prior to the >

Thanks

I've added a poll message here in the Email forum about a feature for the next release of the SpamAssassin trainer script. Please check it out and let me know how you'd like to handle Email notification when scanning is completed. I've left the poll open for 30 days, so that should coincide pretty well with an April release of the new script, which will be the same Perl/CGI web-friendly output as it is right now, plus a PHP version for those who hate Perl, plus a Perl version more suitable to automating as a cron job.

Hi Fantasma,

Yes, you need to configure the script both for a 'ham' folder as well as a 'spam' folder. Ideally, if you call them something like 'scan-ham' and 'scan-spam', the folders will be right next to each other.

When you say the trainer is reporting 0 tokens for ham, do you mean that it learned from 0 messages, or that the reported number at the bottom of the output says 0 ham messages?

It sounds like there might be a configuration problem.

Ian

1. My script is in use on many LunarPages servers as well as other hosting providers who use CPanel, so yes it should work just fine.

2. Flagging CPanel to create the 'spam' folder only allows it to create the folder once a piece of spam has been received. It will not create it for a given account until spam is received at that account.

3. There's an option in the script for add-on domains, but since I don't use add-on domains myself here at LP I haven't thoroughly tested it. If you're willing to help me test it, I'll be happy to help you get up and running. My contact information is at www.iandouglas.com or you can send me a private message here.