Answered Switching from SpamCure to Cloudmark

  • 7. prosince 2009 11:36
     
     
    Hi there,
    as recommended I did the update with the new service-pack before december, 1st. Also I disabled all retiring engines. So I thought... But there seem to be some options where I didn't make the changes. Fool ;-)

    Now I was reviewing some of my configuration and did notice, that there are some more entries to do the switch.

    My problem is, that I can't make any changes at "Settings - AntiSpam - Realtime Scan Job", "Settings - AntiSpam - Manual Scan Job" and "Settings - AntiSpam - MTA Scan Job".
    There "SpamCure" is still set and the two comboboxes are greyed out.

    What do I have to do to make the changes there and switch to Cloudmark?

Všechny reakce

  • 8. prosince 2009 9:20
    Moderátor
     
     Odpovědět

    Hi,

     

    Thank you for the post.

     

    As far as I know, the SpamCure setting will be gray out if any scan job other than SMTP is highlighted.  This is because SpamCure only works on an SMTP level. 

     

    Regards,


    Nick Gu - MSFT
  • 16. prosince 2009 12:52
     
     
    How do you remove the spamcure engine from being listed on the Scanner Updates?

    I have managed to remove the old AV engines by deselecting them from each of the jobs (smtp MTA and 2x storage groups) and from the manual quick scan.

    Because these options are greyed out for the Spam Engine It wont remove from antigen.
  • 4. ledna 2010 10:54
     
     
    I think the problem is the same as mine. I've disabled all the retired anti-virus engines, and consequently the notification emails regarding them have ceased. However, I am still receiving email notifications regarding the Spamcure engine. I have changed the Antigen settings to enable Cloudmark instead, and have disabled the Spamcure update.

    It looks as if the greyed out ticked box for spamcure on the realtime and manual scan jobs is causing Antigen to think Spamcure is still in use and therefore sends me the 'spamcure obsolete' notification email every day.

    I wish to remove the spamcure engine from Antigen and I would like the 'spamcure obsolete' notification emails to cease. Does anyone have any advice on how to achieve this?
  • 14. ledna 2010 19:06
     
     
    I am having the same experience.  Updated to Antigen 9.0 SP2 yesterday and the spam is still getting through, the Quarantine folder is not listing any detections from Cloudmark, I've confirmed all of the appropriate engine settings (even with a Microsoft tech on the line to fix a related install issue), and only the SMTP scan job options are editable, where the Storage Group and MTA scan settings are greyed out with Spamcure selected.

    Why is my Cloudmark engine not operating?  Is there a way to test this?
  • 20. ledna 2010 13:19
     
     
    Try renaming the Cloudmark folder in C:\Program Files\Microsoft Antigen for Exchange\Engines\x86 and then try updating the cloudmark engine

    Im still trying to find out how to remove the SpamCure engine from antigen - its disabled but I want to remove it completely
  • 21. ledna 2010 8:09
     
     

    You also need to delete the retired engines from your scheduled tasks. After the update, the schedules are not automatically deleted. This is the cause that you contiue to get warnings in your event viewer and engine faillures.

    Kind Regards,

    Igor

  • 25. ledna 2010 9:32
     
     
    Hi Igor,

    I deleted updates for the obsolete engines from my scheduled tasks back in December but having restarted our mail server I have noticed that I have started getting them again? 

    If I delete all Antigen-related Scheduled Tasks will Antigen recreate the relevant ones automatically (based on Scanner Updates settings)?

    Let us know, thanks in advance,
    Skielve
  • 25. ledna 2010 10:25
     
     

    Hello Skielve,

    The StarEngineService.exe controls the spamcure service. You have to verify that this service is stopped or deleted.
    If this service is not in a stopped state, you have to to do the following:

    1. Make sure you have all new service packs and patches.
    2. Disable spam cure updates in the administration tools. 
    3. Disable and stop the Star engine.
    4. Stop all Antigen services
    5. Go to your Antigen engine folder and rename the spamcure folder (or just delete the folder)
    6. Delete scheduled tasks



    Regards,

    Igor

  • 10. února 2010 10:16
     
     
    Hello,

    I have the same problem as grummelrocker does...

    - Eventlog notification: SpamCure is obsolete.... blabla
    - SpamCure is greyed out for Realtime Scan Job, Manual Scan Job and MTA Scan Job under "Anti-Spam" in the Antigen console
    - SpamCure Updates have been disabled under "Scanner Updates" in the Antigen console
    - StarEngine has been stopped and siabled
    - Scheduled Tasks have been disabled and afterwards deleted, because the notification returned
    - The SpamCure Engine folder has been renamed and afterwards deleted, because the notification returned
    - The Server has been rebooted several times

    - There arent any other notifications/errors/warning in the eventlog

    There is a hotfix but the description doesnt describe the problem I have.
    (=> http://support.microsoft.com/kb/975355)

    Doesn anyone have an idea how to go on?

    Thanks!
  • 15. února 2010 19:28
     
     
    I have the same situation as you.  Have you had any luck getting Cloudmark to start detecting spam?  Also have the grayed-out issue, and I know that my Cloudmark engine is up-to-date and so are the signature defs. 
  • 17. února 2010 9:51
     
     
    No, I couldnt solve the issue until now... :/
  • 10. ledna 2012 16:51
     
     

    I'm still having this same issue.  My users are being spammed and I am unable to change the scanner in use by First Storage Group.  


    On another note, since my SMTP Scan Job IS using Cloudmark, would it just be redundant to have it on on the FSG Real-time scan as well or does it perform different functions?  Lastly, my Cloudmark hasn't found a new update since 7/11/11 (about 6 full months).  That seems like way too long to me. 

     

    Can anyone please provide some input on this?