Puremessage for Exchange

[TheCrust]

Our exchange 2007 box was running Sophos puremessage v3.0.0 and had been perfectly happily for over a year up until lunchtime today when it progressively stopped processing mail.

 

Mail was building up in the submission queue, but going nowhere, and the application log was recording lots of MSExchange Extensibility ID:1050 errors quoting: "The execution time of agent 'PmE12Transport' exceeded 300000 (milliseconds) while handling event 'OnRoutedMessage'."

 

In the end, the only way we could see to get mail flowing again was to remove puremessage completely. We tried disabling it seperately but it didn't work - yet once the uninstall routine was kicked off mail started to flow again.

 

I left it a while, downloaded the latest version of puremessage I could find on Sophos' website (v3.0.2 IIRC) and tried a re-install only to be told by the installer that "it did not support the version of exchange I was using"

 

I'm using Exchange 2007 SP1 on a Windows 2003 R2 server. In what way isn't this supported?

 

Anyone got any suggestions or had similar experiences?

 

Thanks in advance

 

 

 

Jim

[Sophos-Support-5]

I'm using Exchange 2007 SP1 on a Windows 2003 R2 server. In what way isn't this supported?

 

Full requirements at:

Sophos PureMessage for Microsoft Exchange - system requirements

 

If you need any further help please feel free to submit a support query:

 

Sophos - Contact technical support

[TheCrust]

Full requirements at:

Sophos PureMessage for Microsoft Exchange - system requirements

 

 

Yep - read all that yesterday. When I looked into it a bit further overnight, I noticed that while Add/remove programs reports SP1 installed and the rollup 6 pack, the version numbers reported in the registry don't reflect this....

 

I suspect I have some easter-break work coming up - like the replacement of the exchange box. It's a critical system for us (as it is for many!) and not having it protected or filtered is one thing but having it mis-reporting the software it has on it is someting else.....

 

Thanks anyway!

[Gotink]

Is the 1050 event resolved?

How?

 

We have this problem too in Exchange 2010