Albert:

I remember there was some small trick to this when I did it a year or so ago. If I remember right there was a change to the MxGuard INI file that wasn't obvious. I'll take a look in a bit and see if I can get back to you with something.

Eric

----- Original Message ----- From: "Alberto Santoni" <[EMAIL PROTECTED]>
To: "Message Sniffer Community" <sniffer@sortmonster.com>
Sent: Thursday, June 28, 2007 11:42 AM
Subject: [sniffer] Re: After Updating MXGUARD


Pete,

after a day the SNF doesn't work yet ... what else can I try?
I have checked all that possible

With my best regards
Alberto Santoni
---------------------------------------------------
ASPita Sprl
Grande rue au Bois, 196 - 1030 - Brussels
+32(0)2 217 85 28 office
+32(0)2 735 78 65 fax
+32(0)476 53 88 34 mobile
Skype: Aspita.be
---------------------------------------------------


-----Original Message-----
From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On
Behalf
Of Pete McNeil
Sent: 27 June 2007 23:44
To: Message Sniffer Community
Subject: [sniffer] Re: After Updating MXGUARD

Hello Alberto,

Wednesday, June 27, 2007, 5:15:58 PM, you wrote:

> Hello

> After an update of MxGuard 1.7 -> 3.1 the Sniffer doesn't work any
more
> ....
> I have the Sniffer in persistent mode and loaded with Srvany
> I found many files I never seen in the Sniffer dir .SRV .FIN .XXX

> Which tests can I do to understand the problem ?

It turns out that those files have always been there - but most of
them (not the SRV) went away very quickly.

Most likely during your transition your SNF workspace got clogged with
a lot of these and that is causing some problems.

First thing to do is to shut down SMTP & SNF (your persistent
instance) and clear out all of those job files. Each file represents a
sing scan job - the extension represents the status. With everything
shut down there should be none of these files so it's safe to delete
them.

Once that is done you can start things up again and everything should
work normally.

If not then the normal testing procedures should help you discover the
problem quickly.

Hope this helps,

_M


--
Pete McNeil
Chief Scientist,
Arm Research Labs, LLC.


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <sniffer@sortmonster.com>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to
<[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>



#############################################################
This message is sent to you because you are subscribed to
 the mailing list <sniffer@sortmonster.com>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>




#############################################################
This message is sent to you because you are subscribed to
 the mailing list <sniffer@sortmonster.com>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to