I have the following Criterion Script below. Basically I have all of these e-mails which have the following line in the header that I am trying to match. X-ME-Spam: High (460) I have verified (by changing the order) that this "Spam" filter is running after [System Spam Filter]. I had Debug Status en...

Ping!

I have ME 3.66 instaled because of IMAP problems since 3.64 version. IMAP service is running I can access it via Telnet. The outlook express is reporting IMAP service did not respond in 60 sec. Does anybody have same problems? Thanks! If you restart all MailEnable services manually does Outlook rep...

My experience with the built in Mail Enable Bayesian is that it is virtually untrainable (in auto mode) (Years of Auto training has resulted in an epic .02% detection). Even After rigorous manual training it seems like it never gets it (At one point i had got it to a very short lived 40%. Within few...

I have tried to use the Microsoft fixes but did not work. I get an error on both of them telling me that this solutions are not for my system. Trying to do this manual update on a life server give me the crips. Almost everytime I had to do some twisted update I got in trouble. Anyway. I think that ...

For your Impossible to load the type you might want to refer to this link. See Ian's response. http://forum.mailenable.com/viewtopic.php?f=2&t=24084 Once you get back to the Access Deneied you probably should use a program from Microsoft/Systernals called Process Monitor and filter it to monitor fil...

You'll probably need to see if you can manually update your browser files for .NET Framework 2.0.

Re-read the post I pointed out which highlights the section(s) of interest if you have to do a manual update.

cemag wrote:Thank you! I seems indeed that the application pool of the webmail site was running on .net 2.0. I have changed that and now it seems to work.

Cool, glad to be of help and that you got it working.

Sorry but I am looking for a solution not for a joke. Do you think I am stupid? i know that on compatibility modus works. That is not the point. How can I tel a few honder people that they have to do that and why should I even start such discussion? Most of them don't even understand what a compati...

See the answers in here http://forum.mailenable.com/viewtopic.php?f=3&t=25303

Apparently you are probably affected by the problem that shortened the executable paths in the service entries.

Not an official answer, but I would hazard a guess that the answer should be "yes" since the COM component should wrap the respective engine and the security restrictions should be built into the engine.

I recently upgraded ME Pro from 6 to 7 this weekend and spent the time getting SpamAssassin installed and working. Aside from being a CPU hog, everything seems to be working great aside from one minor problem. I noticed that SpamAssassin is scanning out-bound e-mail. This is going to be very bad com...

Not to perform necroscopy but. The SA Scans/Detections count is still broken in the release edition. However to answer OP's question regarding "how do i know it's working" I created a filter that was based upopn the single criteria of "Failing SpamAssassin" For the action I appended the Subject Pref...

I believe since the time this thread was last active - to now, I've done two migrations. At least one should have been a 32-64 bit migration. Both times I never exported the registry. In fact I simply: installed fresh. Stopped all MailEnable services and Copied over the Config folder and the PostOff...

You might aslo compare your existing registry with the new one. (might have to search for duplicates since you have already imported the registry once) Windows has a tendency of putting certain apps registry down a WOW64 node - so you might have to modify the existing import to match where the new M...