Switch to full style
Forum for support for the PureSight for WinGate content filtering plugin
Post a reply

Unable to release quarantined Outlook .msg-Files

Jul 23 04 9:28 pm

Hello from Germany,

we are using Wingate 5.2.3 with PureSight. On Wingate-Server we're running a POP3-Proxy Service which ist mapped to port 109, transfering E-Mails to a local Outlook-Client on our LAN.

Sometimes PureSight defines a prohibited content in E-Mails. It happens that PureSight is scanning the content of Mails not correctly, finding sexual content in an absolutley clean file, don't know what's the matter for this. Our "Allowed level sliders" for sexual & gambling content are at 85%.
However, the .msg-files are saved to the Quarantinefolder on our Wingate-Server. I have to release the quarantined E-Mailitems on Wingate and want to open them with Outlook 2000 but this doesn't work. Following message is displayed after i doubleklick the file "Unable to open the specified file, possibly it doesn't exist, it is currently in use or check you have to check your rights to open the file".

Any ideas? Thanks for replys!

Jul 26 04 2:50 pm

If you browse to the physical file location, can you then actually copy the files out to another location to try and view them ? What happens if you attempt to open them with a text editor, such as notepad ?

Jul 27 04 1:31 am

Copying the file to another Outlookclient works, opening the .msg file with WordPad works also. I'm able to view the the e-mail textparts (senderadress etc.) - But what is with the attachements embedded in the .msg file? With the Editor i can only see the names of the atteched files.

Thanks!

Jul 27 04 2:29 am

If you have Outlook Express you could rename the .msg to .eml and view that way.

Larry

Jul 27 04 7:40 pm

Renaming the .msg files to .eml solves the problem! Outlook-Express starts and opens the mail. Still had to set a key in the registry which redefines the allowed file extensions (the problem with automatic blocked attachements from Office 2000 SR1a - MS KowledgeBase No. KB318515).

Now it works fine. Thanks!
Post a reply