So far its doing good.
In the last 3.5 hours the ‘MS SMTP 200/2003 Provider’ has processed 6231 emails.
The ‘Exchange 2000/2003 Provider’ has precessed 1021821 while it has been scanning the Exchange mail store.
No errors in the event log. We will let it run until something happens.
Everyone here is curious about what the change in the file is.
Thanks
dan
Glad to hear that… Fingers xed. 
As about the change, actually, the modification consisted only in exactly 6 characters in the source code ;D But the strange thing is, a lot of MSDN samples actually use this code (the original version), so if this proves to be the culprit I guess MS will have to update quite a few of its pages…
Cheers
Vlk
Any news on the current status? 
Here are some new stats from our server:
In the last 23 hours the ‘MS SMTP 200/2003 Provider’ has processed 28500 emails.
The ‘Exchange 2000/2003 Provider’ has precessed 2872451 emails.
Through the night the server ran with out any problems. There are no errors in the event viewer. So far it seems to be working. - Knock on wood! ;D
We will wait until Monday before we put Avast back on our Front-end OWA Server and the other cluster node. We don’t want any issues over the weekend.
dan
Great, thanks for that.
Let’s wait till Monday.
Good news. Thanks Scrimpyd for testing
Just got back home from Redmond.
Any news on this issue (from Idaho)?
Thanks
Vlk
Vlk, hope you had a good trip.
Well so far the stats are:
In the last 3 days 11 hours the ‘MS SMTP 200/2003 Provider’ has processed 101419 emails.
The ‘Exchange 2000/2003 Provider’ has precessed 3009627 emails.
No errors in the event logs from exchange or the cluster services.
dan
Very good, thanks for keeping us updated.
Hopefully, it will work flawlessly on the cluster as well…
You said that before applying the patch, it usually crashed after a couple of hours, right?
Thanks
Vlk
Still everything OK? knock, knock…
So far things are looking good.
In the last 4 days 20 hours the ‘MS SMTP 200/2003 Provider’ has processed 1386683 emails.
The ‘Exchange 2000/2003 Provider’ has precessed 3075252 emails.
I did move the Exchange Virtual Servers over to Server1 this morning so I could reboot Server2. Server2 still gives me a DCOM error in the event log when the server boots up. Not sure what is causing it yet. I moved the cluster back to Server2 and it is running again. I am not sure if I should be concerned about the DCOM error or not. I dont see that error on Server1, the only differences in the two is Server1 does not have Avast installed on it, Server2 does. Once Server2 is up everything works as I would expect. So I am still trying to figure out what is causing the error. I will keep looking. I have looked in the DCOM Config and I dont see any process with that ID to give it the permissions that might need.
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 11/20/2006
Time: 7:31:01 AM
User: NT AUTHORITY\SYSTEM
Computer: SERVER2
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{9DA0E106-86CE-11D1-8699-00C04FB98036}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool.
Howdy All-
I solved the DCOM error. Not sure what changed but the CLSID 9DA0E106-86CE-11D1-8699-00C04FB98036 finally showed up in the DCOM config in the Component Services MMC. ??? I checked the Security tab and it was set to ‘Customize’ But when I clicked on the ‘Edit’ button there were no users or groups in the ‘Launch Permissions’ window. I added SYSTEM, INTERACTIVE and Administrators and gave them the correct rights to launch and activate. Rebooted the server and now NO DCOM error.
I just wish I knew what triggered that CLSID to show up in the DCOM config finally. ???
So far so good?
Server2 ran great over the weekend. I am going to install 4.7 and the fixed dll file on our Exchange Front-End and OWA server, Server3 today. I will let you know how that goes.
dan
I thought I would post an update.
I have Avast 4.7 with the .dll file Vlk posted on two servers.
The product is working great. There are no errors in the event logs on either system.
What should I do about the AvSmtp2K.dll.sum file in the program directory?
Will the patched .dll be included in future versions of Avast?
Should I still be doing program updates along with the virus database updates?
Thanks Vlk for all the help.
dan
Hey, thanks a lot for the update!
Yes, the fix will be included in the next program update (scheduled just before Xmas). You don’t need to worry about anything – the patched AvSmtp2K.dll file will get replaced by the official (fixed) version when you perform the update (so: yes, I’d recommend to install all program updates in any case as there will be some other fixes/enhancements as well).
Thanks
Vlk
Do I need to delete the AvSmtp2K.dll.sum file from the directory? I thought that you had said the this file would prevent the update from overwriting the AvSmtp2K.dll file in the programs directory.
Just want to be clear about this files purpose.
Thanks
dan
You don’t need to delete it.
If you look inside the AvSmtp2K.dll.sum file, you’ll notice the Build= line. That is, the .sum file (which tells the updater to ignore the patched version) is bound to a specific version of avast.
Once the version number increases, the .dll file will get replaced by the new, official version, and the .sum file will be deleted automatically (as it won’t be needed anymore).
Hope this explains it.
Cheers
Vlk
Vlk,
We are also having positive results with the patch. Thanks for your quick response
Hi,
Where I can download this patch, I always have this trouble at the restart of my SBS. 
Thank’s in advance.
GG.