xmon license expire

[strict]

When my xmon trial license expired xmon stopped functioning and began to hold mail in the Exchange Messages Pending Submission queue in the retry state. The event log is filled with Event ID 348: "A message could not be virus scanned – this operation will be retried later"

Now I can understand that if something was wrong and a message was unable to be scanned then queue it until the problem can be resolved. However, if the problem is an expired license then mail should definitely not be held. People forget to renew their license all the time. In my case I have been waiting a WEEK since I initially ordered my license.

In this particular deployment it was no big deal because this particular client is 50 inbound emails per day. If i had deployed this on one of my larger clients, say 4000 emails a day, this would be a nightmare.

My question is, is this a bug or is this a feature? If this is a feature is there a way to disable the problem? If not can this be submitted as a feature request for a future release?

[Blackspear]

Hi strict, welcome to Wilders.

This is indeed a feature, it is designed with safety in mind; should a license expire the user remains protected until a a new license is entered, then all emails are checked and released.

Cheers ;D

[strict]

I agree this is a feature, and should be. After all NOD32 is there to protect users against virii.

With that said I can think of MANY reasons why an administrator would want to disable this feature at will.

1. Shit happens, now my domain is not receiving mail, i would rather have a virus slip through than get fired from my job, give me an option to disable this please

2. Shit happens, my license renewal is taking WAY longer than I expected, let me disable it just in case it takes longer than the expire date

I feel many would agree business class products must be administered by the product users, not the product developers.

Scanner exclusions would be another example:

http://www.wilderssecurity.com/showthread.php?t=114324&highlight=exclusions

How am I supposed to deploy NOD32 onto single server client domain using M$ SB server when i cant exclude the Exchange or SQL directories, or any others that M$ tells you not to scan. Reference:

http://support.microsoft.com/kb/823166/en-us
http://support.microsoft.com/kb/822158/en-us
http://support.microsoft.com/kb/817442/en-us
http://support.microssoft.com/kb/309422/en-us
http://kbase.gfi.com/showarticle.asp?id=KBID001824
http://kbase.gfi.com/showarticle.asp?id=KBID001522

I am trying to convince my IT company to use NOD32 as our standard client anti-malware solution. My IT company has been a Trend shop for years. One of the reasons we are dissatisfied with Trend is their lack of configuration.

Arguably NOD32's biggest selling point is the vast control of configuration. I would suggest ESET not to loose site of this.

At the end of the day my clients pay me to protect them, not ESET. They also pay me to make sure they get their mail.

I really appreciate your response to my post Sir... thank you

[Blackspear]

All you would have to do is remove the license from the license key tab in NOD32 System Setup and emails would then be scanned on the client side.

You should have the server set up to e-mail you with errors.

If his license is taking longer than a few hours, it can be escalated; a few hours is normal, a day is not.

Cheers ;D