You won't need to start or stop anything to get Message Sniffer running
as a service with FireDaemon.  In fact, once you do, you can start it or
stop it anytime without loss of scanning; it's strictly a performance
benefit.

My guess is that the only configuration you're missing is the startup
folder.  I'm attaching two GIF images that are my own obfuscated
configuration, which works fine.  You'll have to substitute your own
filename and key.

Andrew 8)

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Greg Wanner
> Sent: Sunday, July 31, 2005 4:06 PM
> To: [email protected]
> Subject: Re: [sniffer] FireDaemon
> 
> Pete:
> 
> Yes it works from the command line with no problem.  Do I 
> need to stop the SMTP and declude config file before starting 
> this as a service?
> 
> 
> [EMAIL PROTECTED]
> 
> ----- Original Message -----
> From: "Pete McNeil" <[EMAIL PROTECTED]>
> To: "Greg Wanner" <[email protected]>
> Sent: Sunday, July 31, 2005 7:01 PM
> Subject: Re: [sniffer] FireDaemon
> 
> 
> > On Sunday, July 31, 2005, 6:43:36 PM, Greg wrote:
> >
> > GW> Can anybody help me with a problem getting the  persistent
> > GW> mode to work with FireDaemon. I loaded the latest version,  1.7.
> > GW> I believe I have everything setup correctly, the right 
> .exe name,
> > GW> authenicationxx and persistent in parameters. It starts to fire
> > GW> up, then  stops. Any hints?
> >
> > Did SNF generate a log file?
> >
> > Were there any errors or warnings in the log file?
> >
> > If you execute the same command from the command line does it work?
> >
> > --- These are just basic things. I'm not very familiar with 
> FireDaemon
> > but it still pays to start with the basics ;-)
> >
> > You may also consider temporarily turning on the debug menu 
> in the SNF
> > .cfg file. If SNF is starting at all that may tell you why it stops.
> > If you are not getting a log file from SNF (any log files) then
> > chances are it has been called incorrectly so your command line
> > settings are incorrect. That is, in general, SNF will almost always
> > produce a log file - even if there are errors. If not then SNF
> > probably did not run, or it rejected it's command line and exited
> > right away.
> >
> > hope this helps,
> >
> > _M
> >
> >
> >
> >
> > This E-Mail came from the Message Sniffer mailing list. For 
> information
> and (un)subscription instructions go to
> http://www.sortmonster.com/MessageSniffer/Help/Help.html
> > ---
> > [This E-mail scanned for viruses by EWOL using Declude Virus]
> >
> >
> 
> ---
> [This E-mail scanned for viruses by EWOL using Declude Virus]
> 
> 
> This E-Mail came from the Message Sniffer mailing list. For 
> information and (un)subscription instructions go to 
> http://www.sortmonster.com/MessageSniffer/Help/Help.html
> 

Attachment: sniffer2.GIF
Description: sniffer2.GIF

Attachment: sniffer1.GIF
Description: sniffer1.GIF

Reply via email to