subject:"\[sniffer\] version"

On Wednesday, October 20, 2004, 12:19:12 PM, Jorge wrote:


  I am particularly interested to hear from MDaemon users who should
  realize a multi-fold improvement in processing speed by using this
  new version of persistent server. This is one of the critical goals
  of these modifications and preliminary responses support that we
  have achieved this goal.
  

JA I run Mdaemon and I proces about 10K message a day. What things should I
JA look for? How can I know the performance has actually improved?

That's a good question. 10K/day is not very large so you may not see
an improvement easily. What you are looking for is higher throughput,
or more precisely, that your system is able to process more messages
in a given period of time.

Systems with heavier loads _should_ see a reduction in their backlog.

Systems that have periods of heavy activity should see the these peaks
handled more quickly.

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

RE: Re[2]: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Frank Osako

Hello _M

_ Systems with heavier loads _should_ see a reduction in their backlog

See a reduction of what in their backlog? Can you give an example of how
to see this type of measurement?

Thanks 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Pete McNeil
Sent: Wednesday, October 20, 2004 11:44 AM
To: Jorge Asch
Subject: Re[2]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 12:19:12 PM, Jorge wrote:


  I am particularly interested to hear from MDaemon users who should  
 realize a multi-fold improvement in processing speed by using this  
 new version of persistent server. This is one of the critical goals  
 of these modifications and preliminary responses support that we  
 have achieved this goal.
  

JA I run Mdaemon and I proces about 10K message a day. What things 
JA should I look for? How can I know the performance has actually improved?

That's a good question. 10K/day is not very large so you may not see an
improvement easily. What you are looking for is higher throughput, or more
precisely, that your system is able to process more messages in a given
period of time.

Systems with heavier loads _should_ see a reduction in their backlog.

Systems that have periods of heavy activity should see the these peaks
handled more quickly.

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 Declude Virus]



---
[This E-mail scanned for viruses by 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

RE: Re[2]: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Colbeck, Andrew

If I might butt in ...

If you fire up Task Manager on a windows machine (or your favourite ps tool
elsewhere), and set the View, Update Speed to High, then sort by the name in
reverse, you will see multiple sniffer.exe and one with a PID that doesn't
change.  That's your persistent instance.

What you should see is that all other instances of sniffer.exe wink in and
out, with an ever-changing PID.  So far, so good.

Under a heavy load, your system is slow enough that you will see multiple
sniffer.exe instances, and maybe they are using CPU and maybe not, depending
on where the CPU load on your system is coming from.

If those multiple instances are all using a small amount of RAM, and only
the persistent instance uses 4,000 KB of memory, then the code is working
well for you.  The client instances are loading the rulebase.

If some of those instances also have 4,000 KB of memory allocated, then they
have gotten impatient and decided to load the rulebase and process the
message for themselves.  If you have a lot of impatient clients, they will
exacerbate your memory and CPU stress, thus the new 2-3.0i8 code that lets
them wait longer.

Andrew 8)

-Original Message-
From: Frank Osako [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 20, 2004 9:54 AM
To: [EMAIL PROTECTED]
Subject: RE: Re[2]: [sniffer] Version 2-3.0i8 published.


Hello _M

_ Systems with heavier loads _should_ see a reduction in their backlog

See a reduction of what in their backlog? Can you give an example of how
to see this type of measurement?

Thanks 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Pete McNeil
Sent: Wednesday, October 20, 2004 11:44 AM
To: Jorge Asch
Subject: Re[2]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 12:19:12 PM, Jorge wrote:


  I am particularly interested to hear from MDaemon users who should
 realize a multi-fold improvement in processing speed by using this  
 new version of persistent server. This is one of the critical goals  
 of these modifications and preliminary responses support that we  
 have achieved this goal.
  

JA I run Mdaemon and I proces about 10K message a day. What things
JA should I look for? How can I know the performance has actually improved?

That's a good question. 10K/day is not very large so you may not see an
improvement easily. What you are looking for is higher throughput, or more
precisely, that your system is able to process more messages in a given
period of time.

Systems with heavier loads _should_ see a reduction in their backlog.

Systems that have periods of heavy activity should see the these peaks
handled more quickly.

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 Declude Virus]



---
[This E-mail scanned for viruses by 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

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

RE: Re[2]: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Colbeck, Andrew

Whups, I missed out an important NOT in the second-to-last paragraph.
Corrected version is below:

-Original Message-
From: Colbeck, Andrew 
Sent: Wednesday, October 20, 2004 10:29 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Re[2]: [sniffer] Version 2-3.0i8 published.

If I might butt in ...

If you fire up Task Manager on a windows machine (or your favourite ps tool
elsewhere), and set the View, Update Speed to High, then sort by the name in
reverse, you will see multiple sniffer.exe and one with a PID that doesn't
change.  That's your persistent instance.

What you should see is that all other instances of sniffer.exe wink in and
out, with an ever-changing PID.  So far, so good.

Under a heavy load, your system is slow enough that you will see multiple
sniffer.exe instances, and maybe they are using CPU and maybe not, depending
on where the CPU load on your system is coming from.

If those multiple instances are all using a small amount of RAM, and only
the persistent instance uses 4,000 KB of memory, then the code is working
well for you.  The client instances are NOT loading the rulebase.

If some of those instances also have 4,000 KB of memory allocated, then they
have gotten impatient and decided to load the rulebase and process the
message for themselves.  If you have a lot of impatient clients, they will
exacerbate your memory and CPU stress, thus the new 2-3.0i8 code that lets
them wait longer.

Andrew 8)

-Original Message-
From: Frank Osako [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 20, 2004 9:54 AM
To: [EMAIL PROTECTED]
Subject: RE: Re[2]: [sniffer] Version 2-3.0i8 published.

Hello _M

_ Systems with heavier loads _should_ see a reduction in their backlog

See a reduction of what in their backlog? Can you give an example of how
to see this type of measurement?

Thanks 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Pete McNeil
Sent: Wednesday, October 20, 2004 11:44 AM
To: Jorge Asch
Subject: Re[2]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 12:19:12 PM, Jorge wrote:

  I am particularly interested to hear from MDaemon users who should 
 realize a multi-fold improvement in processing speed by using this
 new version of persistent server. This is one of the critical goals  
 of these modifications and preliminary responses support that we  
 have achieved this goal.

JA I run Mdaemon and I proces about 10K message a day. What things 
JA should I look for? How can I know the performance has actually 
JA improved?

That's a good question. 10K/day is not very large so you may not see an
improvement easily. What you are looking for is higher throughput, or more
precisely, that your system is able to process more messages in a given
period of time.

Systems with heavier loads _should_ see a reduction in their backlog.

Systems that have periods of heavy activity should see the these peaks
handled more quickly.

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 Declude Virus]

---
[This E-mail scanned for viruses by 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

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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

Re: Re[2]: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Ken Scott



 Hello _M

 _ Systems with heavier loads _should_ see a reduction in their backlog

 See a reduction of what in their backlog? Can you give an example of how
 to see this type of measurement?

a reduction of mail waiting for processing in your spool of course.

for example, right now, my backlog is at around 800,
if this new sniffer works the way they say, we should only
have around 200-300 in our backlog, which is normal for emails
waiting for resend because a host  was unavailable, something like that,

we have no installed the new updated as of yet, since our production server
moves around 800,000 emails per day. we cannot take any chances.

-Ken


 Thanks

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 On Behalf Of Pete McNeil
 Sent: Wednesday, October 20, 2004 11:44 AM
 To: Jorge Asch
 Subject: Re[2]: [sniffer] Version 2-3.0i8 published.

 On Wednesday, October 20, 2004, 12:19:12 PM, Jorge wrote:


   I am particularly interested to hear from MDaemon users who should
  realize a multi-fold improvement in processing speed by using this
  new version of persistent server. This is one of the critical goals
  of these modifications and preliminary responses support that we
  have achieved this goal.
 
 
 JA I run Mdaemon and I proces about 10K message a day. What things
 JA should I look for? How can I know the performance has actually
improved?

 That's a good question. 10K/day is not very large so you may not see an
 improvement easily. What you are looking for is higher throughput, or more
 precisely, that your system is able to process more messages in a given
 period of time.

 Systems with heavier loads _should_ see a reduction in their backlog.

 Systems that have periods of heavy activity should see the these peaks
 handled more quickly.

 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 Declude Virus]



 ---
 [This E-mail scanned for viruses by 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
 ---
 [This E-mail scanned for viruses by Declude Virus]



---
[This E-mail scanned for viruses by 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

Re[4]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 12:54:04 PM, Frank wrote:

FO Hello _M

_ Systems with heavier loads _should_ see a reduction in their backlog

FO See a reduction of what in their backlog? Can you give an example of how
FO to see this type of measurement?

Another good question - I will try to get a solid, detailed answer.
I'm not an MDaemon expert so I'm not sure what the best strategies are
for measuring throughput performance and backlog (inbound/outbound
queue length).

Perhaps there are some MDaemon experts on list that can share their
strategies for making these measurements? In particular, how best to
measure these things when the system in question is not overloaded?

Thanks,
_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

RE: Re[4]: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Keith Johnson

If we don't run the Mdaemon on our systems and just use the new
download, will we also see a speed increase on processing.  Thanks for
the time.

Keith 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil
Sent: Wednesday, October 20, 2004 1:50 PM
To: Frank Osako
Subject: Re[4]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 12:54:04 PM, Frank wrote:

FO Hello _M

_ Systems with heavier loads _should_ see a reduction in their backlog

FO See a reduction of what in their backlog? Can you give an example 
FO of how to see this type of measurement?

Another good question - I will try to get a solid, detailed answer.
I'm not an MDaemon expert so I'm not sure what the best strategies are
for measuring throughput performance and backlog (inbound/outbound queue
length).

Perhaps there are some MDaemon experts on list that can share their
strategies for making these measurements? In particular, how best to
measure these things when the system in question is not overloaded?

Thanks,
_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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: Re[4]: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Michiel Prins

What we did was write a wrapper around sniffer, and fire that wrapper from
the Content Filter. that wrapper measures how long each sniffer instance
takes. In the previous version, it took way longer when using the persistent
version than when not using the persistent version. You would expect it to
be the other way around.

I could try the new version tomorrow to see if this one is actually faster,
but if I don't get around to doing it tomorrow, I can't check it anymore,
coz I'm going down under for a month.


Regards,
Michiel

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Pete McNeil
Sent: woensdag 20 oktober 2004 19:50
To: Frank Osako
Subject: Re[4]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 12:54:04 PM, Frank wrote:

FO Hello _M

_ Systems with heavier loads _should_ see a reduction in their backlog

FO See a reduction of what in their backlog? Can you give an example 
FO of how to see this type of measurement?

Another good question - I will try to get a solid, detailed answer.
I'm not an MDaemon expert so I'm not sure what the best strategies are for
measuring throughput performance and backlog (inbound/outbound queue
length).

Perhaps there are some MDaemon experts on list that can share their
strategies for making these measurements? In particular, how best to measure
these things when the system in question is not overloaded?

Thanks,
_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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Michiel Prins

But did you run the persistent version also? 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jorge Asch
Sent: woensdag 20 oktober 2004 22:03
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Version 2-3.0i8 published.

If you fire up Task Manager on a windows machine (or your favourite ps 
tool elsewhere), and set the View, Update Speed to High, then sort by 
the name in reverse, you will see multiple sniffer.exe and one with a 
PID that doesn't change.  That's your persistent instance.

I fired up Task Manager. Could't see Sniffer.EXE nor [mylicense].exe as a
persistent instance. Could even see the 'clients'.

Funny, since I know it is running (since the logs it's being created, and
messages are being sniffed)

--
Jorge Asch Revilla
CONEXION DCR
www.conexion.co.cr
800-CONEXION

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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

Re[6]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 3:05:35 PM, Keith wrote:

KJ If we don't run the Mdaemon on our systems and just use the new
KJ download, will we also see a speed increase on processing.  Thanks for
KJ the time.

Yes. The changes that have been made should remove administrative
overhead and improve the response time of the persistent server on all
systems.

_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

RE: [sniffer] Version 2-3.0i8 published.

2004-10-20 Thread Colbeck, Andrew

Exactly, Michiel.

And Jorge, it may be stating the obvious, but you may well have to check the
tickbox at the bottom of Task Manager to Show processes from all users.  I
said sniffer.exe merely as an example, the actual executable will be [your
licence here].exe or snfrv2r3.exe if you're using the trial.

I use FireDaemon to start my persistent process as a service, so it appears
as SYSTEM, whereas my desktop session appears as my Windows username.  You
can see the username under which each executable is running by pulling down
View, Select Columns, and ticking Username.

Andrew 8)

-Original Message-
From: Michiel Prins [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 20, 2004 1:15 PM
To: [EMAIL PROTECTED]
Subject: RE: [sniffer] Version 2-3.0i8 published.


But did you run the persistent version also? 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jorge Asch
Sent: woensdag 20 oktober 2004 22:03
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Version 2-3.0i8 published.


If you fire up Task Manager on a windows machine (or your favourite ps
tool elsewhere), and set the View, Update Speed to High, then sort by 
the name in reverse, you will see multiple sniffer.exe and one with a 
PID that doesn't change.  That's your persistent instance.
  

I fired up Task Manager. Could't see Sniffer.EXE nor [mylicense].exe as a
persistent instance. Could even see the 'clients'.

Funny, since I know it is running (since the logs it's being created, and
messages are being sniffed)

--
Jorge Asch Revilla
CONEXION DCR
www.conexion.co.cr
800-CONEXION




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 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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

Re[6]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 4:15:09 PM, Michiel wrote:

MP What we did was write a wrapper around sniffer, and fire that wrapper from
MP the Content Filter. that wrapper measures how long each sniffer instance
MP takes. In the previous version, it took way longer when using the persistent
MP version than when not using the persistent version. You would expect it to
MP be the other way around.

The only caution I have about this is that it's only true in a single
threaded scenario. On systems that use multiple threads
(IMail/Declude, Postfix, Qmail, etc...) one might see long times for
single client instances, but many more of them might be completed
within a given period. Think of it as a wider road rather than a
higher speed limit.

In a single threaded environment or one where the number of client
instances is highly constrained then there should definitely be an
improvement in the time sniffer runs.

-- The key to the faster times is a better coordination between the
persistent server and the client instance. Here's how that works:

In the newest test versions (currently i8) the persistent server
advertises it's presence by publishing a .stat file. This reduces
overhead by allowing the client instances to avoid scanning the
workspace for .SVR files thus reducing overhead.

In addition to this savings, the persistent server publishes the best
delay for the client(s) to use before checking to see if their job is
complete. This ensures that the client is always using an optimal
delay.

On a busy single threaded system this delay would be roughly equal to
the time it took to process the last job (usually a few milliseconds).
When the first process is complete the next one should start almost
immediately and it will be picked up by the server instance quickly.
In theory (and some testing of course) this has the effect of creating
a synchronized pipeline between the mail server, sniffer client, and
sniffer persistent server. As long as there is a continuous flow of
messages each will be processed as quickly as each can be handed off
and scanned.

In a multithreaded environment there is an additional optimization. In
the previous versions a persistent server instance would scan for a
job and would stop at the first one that it found. As a result, the
entire directory would be scanned for each job that was processed.
This is because the persistent server was simply a normal peer-server
instance tricked into staying alive for long periods.

In the latest test versions a persistent server scans the entire
workspace once and picks up all of the available jobs (.QUE files) in
that pass. Then it processes all of the jobs before scanning again. As
a result the workspace directory is scanned far less frequently on
busy systems and all additional overhead associated with that process
is eliminated. While a single job may see a longer processing time
(outside measurement vs sniffer log) many more jobs can be processed
in a given period so the throughput is much better.

MP I could try the new version tomorrow to see if this one is actually faster,
MP but if I don't get around to doing it tomorrow, I can't check it anymore,
MP coz I'm going down under for a month.

Hopefully you'll get to this -- I'd love to have the data.

In any event, have a great trip!
_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

Re[2]: [sniffer] Version 2-3.0i8 published.

On Wednesday, October 20, 2004, 4:03:15 PM, Jorge wrote:


If you fire up Task Manager on a windows machine (or your favourite ps tool
elsewhere), and set the View, Update Speed to High, then sort by the name in
reverse, you will see multiple sniffer.exe and one with a PID that doesn't
change.  That's your persistent instance.
  

JA I fired up Task Manager. Could't see Sniffer.EXE nor [mylicense].exe as
JA a persistent instance. Could even see the 'clients'.

JA Funny, since I know it is running (since the logs it's being created,
JA and messages are being sniffed)

It definitely has to be there if it's producing a log. Sniffer does
nothing to hide itself.

Did you try sorting by name?

_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

[sniffer] Version 2-3.0i8 published.

2004-10-18 Thread Pete McNeil

Hello Sniffer Folks,

  
http://www.sortmonster.com/MessageSniffer/Betas/MessageSniffer2-3.0i8-Distribution.zip

  This version radically adjusts the client timing when a persistent
  server is detected. This new logic avoids a potentially catastrophic
  failure when a system is under EXTREMELY heavy loads.

  The prior versions used a standard peer-server timing model with the
  persistent server. This was ok while the persistent server captured
  a single job at a time. The enhanced persistent server captures all
  available jobs in a batch and then processes all of them before
  making it's next loop through the workspace. As a result, a system
  under extremely heavy loads might reach a condition where the batch
  processing or loop time approaches the length of the standard
  Client Death Clock - - about 8 seconds. If this condition occurs
  some of the clients will defect and abandon the server to process
  their own jobs. This causes the overloaded server to process work
  more slowly so that additional batches also take 8 or more seconds
  thus causing additional clients to defect until the entire advantage
  of the persistent server is lost and converted to an additional
  delay in processing. Under these conditions an overloaded server is
  usually unable to recover without stopping all message processing.

  The new timing model allows clients to wait for 30 seconds if they
  have detected a persistent server. As a result the persistent server
  is always able to process a batch before any clients will defect. In
  testing on our server we seldom see a batch take longer than 10
  seconds even under the most extreme conditions. At this point the
  operations on the server become slow enough that additional jobs
  arrive at a much reduced rate so that a natural limiting occurs.
  After such a spike the server recovers, even though it is obviously
  overloaded.

  (Our testing server is a P2/450 w/ 256KRam, 2x IDE33 HD in software
  (NT4) mirror raid, processing about 30K messages per day - almost all
  spam. Nominally Message Sniffer processes a message in under 200ms
  on this server, however under heavy loads the processing time can
  become quite large. Also, this system uses the most aggressive
  rulebase settings. After the upgrade to i8 on this server it has
  sustained a throughput of 42msg/sec for approximately 6 hours now
  (still going) without reaching a breakdown condition and while
  remaining characteristically responsive to other requests (pop3,
  imap, webmsg... 42ms/sec is about 60K msg/day if sustained. The
  additional load in this case is due to our gateway server unloading
  a heavy backlog of messages after some adjustments to it's queue
  handling characteristics.)

  It is unlikely that production mail servers will be operated in such
  extreme conditions but now if they are Message Sniffer is ready to
  deal with them gracefully. After all, planned or not - these things
  do happen and critical servers should not fail no matter the
  conditions (if possible).

  This version has taken a real beating on our server today. Please
  let us know how it does on your systems. I am anxious to move
  forward with the next round of updates to the code and then finally
  to publish this new version as production ready once enough positive
  reports have been received.

  I am particularly interested to hear from MDaemon users who should
  realize a multi-fold improvement in processing speed by using this
  new version of persistent server. This is one of the critical goals
  of these modifications and preliminary responses support that we
  have achieved this goal.

  I look forward to any and all comments.

Thanks,
_M

Pete McNeil (Madscientist)
President, MicroNeil Research Corporation
Chief SortMonster (www.sortmonster.com)

PS: The remaining updates for this next version (2-3.1) will be the
addition of minor filtering capabilities that will largely be of
internal use, such as masking rules, and some message condition
tagging and image/file hashing functions.



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

RE: [sniffer] Version 2-3.0i5 posted for testing

2004-10-15 Thread Harry Vanderzand

Let me know when it is safe to run this on a production server

Thank you

Harry Vanderzand 
inTown Internet  Computer Services 
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil
 Sent: Friday, October 15, 2004 1:10 AM
 To: [EMAIL PROTECTED]
 Subject: [sniffer] Version 2-3.0i5 posted for testing
 
 Hello Sniffer Folks,
 
   Version 2-3.0i5 has been posted for testing.
 
   
 http://www.sortmonster.com/MessageSniffer/Betas/MessageSniffe
 r2-3.0i5-Distribution.zip
 
   This version implements a number of performance enhancements
   relating to the use of a Persistent server instance.
 
   Be careful - this version has not been heavily tested. However it
   appears to be quite stable and extremely fast.
 
   MDaemon users should see a significant improvement in performance.
   Please let me know if this is true. The reason is that since most
   MDaemon system integrate Message Sniffer through the content filter
   and the content filter in MDaemon is apparently single threaded. The
   performance tuning features of this version allow the client and
   persistent server instances to coordinate much more closely with
   regard to the available computing power in the system so that
   polling delays _should be_ reduced significantly. _IN THEORY_ the
   improved signaling between client and persistent server instances
   will allow polling synchronization such that the highest possible
   performance for the hardware and load conditions can be achieved.
 
   Having said that, I hope it turns out to be true ;-) Let me know!!
 
   Multi-Threaded systems should see a significant improvement in
   performance also. In particular, jobs are now collected in batches
   by the persistent server instance. This eliminates a great deal of
   overhead (directory scans, locking, etc) on the part of the server
   instance. In addition, client instances can now detect the presence
   of a persistent server without locking and scanning the workspace.
   The combination virtually eliminates locking conflicts and any
   overhead usually associated with coordinating the peer-server
   process.
 
   I don't know precisely what performance increases you should expect
   from this. However I will say that in static tests the program ran
   so quickly that I thought it was broken. Message processing rates on
   my Toshiba 6100 were consistently above 14.2 Msg/Sec with CPU loads
   in the high 80s.
 
   I have not yet tested this version on *nix systems... but I expect
   similar performance improvements.
 
   I urge caution again - this is a somewhat radical set of changes
   with some unexpectedly good _apparent_ performance improvements. I'm
   not sure that I trust it yet... but I also haven't seen it fail.
   More testing needs to be done... (I appreciate your help!)
 
   Please do keep me informed.
 
 Thanks,
 _M
 
 Pete McNeil (Madscientist)
 President, MicroNeil Research Corporation Chief SortMonster 
 (www.sortmonster.com)
 
 
 
 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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

Re[2]: [sniffer] Version 2-3.0i5 posted for testing

2004-10-15 Thread Pete McNeil

On Friday, October 15, 2004, 9:15:00 AM, Harry wrote:

HV Let me know when it is safe to run this on a production server

We will announce all production-ready releases on this list.
Thanks,
_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

[sniffer] Version 2-3.0i5 posted for testing

2004-10-14 Thread Pete McNeil

Hello Sniffer Folks,

  Version 2-3.0i5 has been posted for testing.

  
http://www.sortmonster.com/MessageSniffer/Betas/MessageSniffer2-3.0i5-Distribution.zip

  This version implements a number of performance enhancements
  relating to the use of a Persistent server instance.

  Be careful - this version has not been heavily tested. However it
  appears to be quite stable and extremely fast.

  MDaemon users should see a significant improvement in performance.
  Please let me know if this is true. The reason is that since most
  MDaemon system integrate Message Sniffer through the content filter
  and the content filter in MDaemon is apparently single threaded. The
  performance tuning features of this version allow the client and
  persistent server instances to coordinate much more closely with
  regard to the available computing power in the system so that
  polling delays _should be_ reduced significantly. _IN THEORY_ the
  improved signaling between client and persistent server instances
  will allow polling synchronization such that the highest possible
  performance for the hardware and load conditions can be achieved.

  Having said that, I hope it turns out to be true ;-) Let me know!!

  Multi-Threaded systems should see a significant improvement in
  performance also. In particular, jobs are now collected in batches
  by the persistent server instance. This eliminates a great deal of
  overhead (directory scans, locking, etc) on the part of the server
  instance. In addition, client instances can now detect the presence
  of a persistent server without locking and scanning the workspace.
  The combination virtually eliminates locking conflicts and any
  overhead usually associated with coordinating the peer-server
  process.

  I don't know precisely what performance increases you should expect
  from this. However I will say that in static tests the program ran
  so quickly that I thought it was broken. Message processing rates on
  my Toshiba 6100 were consistently above 14.2 Msg/Sec with CPU loads
  in the high 80s.

  I have not yet tested this version on *nix systems... but I expect
  similar performance improvements.

  I urge caution again - this is a somewhat radical set of changes
  with some unexpectedly good _apparent_ performance improvements. I'm
  not sure that I trust it yet... but I also haven't seen it fail.
  More testing needs to be done... (I appreciate your help!)

  Please do keep me informed.

Thanks,
_M

Pete McNeil (Madscientist)
President, MicroNeil Research Corporation
Chief SortMonster (www.sortmonster.com)



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

[sniffer] Version 2-3.0i2 release.

2004-09-13 Thread Pete McNeil

Hello Sniffer Folks,

  Please find interim update 2 at the following link:

  
http://www.sortmonster.com/MessageSniffer/Betas/MessageSniffer2-3.0i2-Distribution.zip

  This distribution patches a hole in the FilterChain module of the
  scanner. In prior versions it was possible for the unexpected
  presence of a 'null' character to prevent the remainder of a message
  from being scanned. In theory (not yet proven) this could cause some
  rules not to fire on a message even though the rules would be
  present in the rule base.

  This is a minor adjustment which has tested well on our servers. We
  will be making this the official distribution after a little more
  testing. No problems have been observed or reported so far.

Thanks,
_M

Pete McNeil (Madscientist)
President, MicroNeil Research Corporation
Chief SortMonster (www.sortmonster.com)



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

RE: [sniffer] Version 2-3.0i2 release.

2004-09-13 Thread Keith Johnson

Pete,
  I take it this can be run without the persistent mode?  Thanks for the aid.

Keith

-Original Message- 
From: [EMAIL PROTECTED] on behalf of Pete McNeil 
Sent: Mon 9/13/2004 9:15 PM 
To: [EMAIL PROTECTED] 
Cc: 
Subject: [sniffer] Version 2-3.0i2 release.

Hello Sniffer Folks,

  Please find interim update 2 at the following link:

http://www.sortmonster.com/MessageSniffer/Betas/MessageSniffer2-3.0i2-Distribution.zip

  This distribution patches a hole in the FilterChain module of the
  scanner. In prior versions it was possible for the unexpected
  presence of a 'null' character to prevent the remainder of a message
  from being scanned. In theory (not yet proven) this could cause some
  rules not to fire on a message even though the rules would be
  present in the rule base.

  This is a minor adjustment which has tested well on our servers. We
  will be making this the official distribution after a little more
  testing. No problems have been observed or reported so far.

Thanks,
_M

Pete McNeil (Madscientist)
President, MicroNeil Research Corporation
Chief SortMonster (www.sortmonster.com)

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

winmail.dat

Re[2]: [sniffer] Version 2-3.0i2 release.

2004-09-13 Thread Pete McNeil

On Monday, September 13, 2004, 10:20:06 PM, Keith wrote:

KJ Pete,
KJ   I take it this can be run without the persistent mode?  Thanks for the aid.

Yes. It is no different than the current version except for the patch.

_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

[sniffer] Version 2-3 posted on C|Net - please help.

2004-05-19 Thread Pete McNeil

Hello folks,
The latest version of Message Sniffer (Version 2-3) has been posted on 
C|Net Download.com. The previous version survived for several months as the 
only anti-spam solution on C|Net with a 100% approval rating thanks to your 
comments!!!

Whenever a new version is posted, the reviews for the previous version are 
removed. If you can, please take a few moments to download the latest 
version (if you don't already have it) and post your review of Message 
Sniffer at C|Net. This will help us grow and continue to improve.

The best way to get there is to click on the graphic on our Try-It page:
http://www.sortmonster.com/MessageSniffer/Try-It.html
As always, thanks for your support!
_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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-14 Thread Pete McNeil

At 11:33 AM 5/14/2004, [EMAIL PROTECTED] wrote:
HI Pete,

I uploaded the new .exe file, renamed it to my number.

I don't get this persistant instance thing...can you give this to me in
laymans terms? Im just a simple network engineer with 17 years of
experience. How do I get it working? I need an example..
Thanks, andy
:)
Thumpernet
First, treat this like a normal upgrade - looks like you did that part.

Now, a little background so you will know what's going on...

Under normal conditions your mail server will create one instance of
Message Sniffer for each message.

Usually this means that more than one of these might be running at once.

Beginning with version 2-2, when more than one of these is running at the
same time the group will coordinate to elect one of them as a server so
that the others can be clients and avoid loading the rulebase. This is
cellular peer-server technology. This speeds thins up a lot and reduces the
loads on the server.

Although cellular peer-server technology makes things very efficient, there
are still some times that more than one instance might elect to be a
server, and under lower system loads when only one message at a time is
being processed that could mean the rulebase is loaded for every message.
This can slow down other processes on your server... Also, if you are
running a system that somehow will only scan one message at a time through
Message Sniffer you will be guaranteed to load the rulebase every time
because there will never be more than one instance running. So... there is
clearly room for improvement.

Beginning with version 2-3, you can launch an instance of Message Sniffer
outside of your mail server and run it in persistent mode. This instance
will look to the others like it has already been elected as the server - so
every time your mail server launches an instance to process a message, that
instance will elect to be a client and so it will not load the rulebase.

In version 2-2, and in 2-3 when there is no persistent instance running,
server instances show up as needed to save a good deal of computing power
and make things go quickly on the server. Version 2-3 implements the same
cellular peer-server technology as version 2-2.

However, with version 2-3 when a persistent instance is running then
messages are always processed by clients so things are very efficient and a
bit more predictable. The persistent instance tricks the peers into
following a client-server model. For safety, if the persistent instance
crashes or goes away for some reason then things drop back to normal.

To take the second step and use persistence - you need to run one extra
instance of Message Sniffer and replace the message file name on the
command line with persistent. This instance will stay alive between
messages and act as a persistent server.

On Win32 systems you can run this instance as a service using the Win 2K
toolkit or a utility like FireDaemon, or RunSvcExe. Unix type systems will
probably launch this instance in a script at boot time and detach it like
any other daemon.

Here's a link to the mail archive that will help with the details and get
you started:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg00165.html

Here's another useful thread for the Unix folks...

http://www.mail-archive.com/[EMAIL PROTECTED]/msg00382.html

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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-11 Thread Mike Nice

Installed it here and it works as advertised!

- Original Message - 
 This new version of Message Sniffer Screams! when using the new
 Persistent Instance option consistently achieving message scans in tens
 of milliseconds without the need for high-end hardware or additional
 network resources. 



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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-11 Thread Pete McNeil

Thanks!
_M
At 10:09 PM 5/11/2004, you wrote:
Installed it here and it works as advertised!

- Original Message -
 This new version of Message Sniffer Screams! when using the new
 Persistent Instance option consistently achieving message scans in tens
 of milliseconds without the need for high-end hardware or additional
 network resources.


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 came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: [sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-10 Thread Matt Day

Hi _M

Just a quick note on monitoring:

I for one would *love* to see something like what you've mentioned below - A
scoreboard file that could be used to graph or otherwise provide pretty
'Management Information' would go a very long way indeed. 
It's a bit like your comment about a program being seen to be working - this
monitoring info could really demonstrate the power and speed of message
sniffer as well as help all those admins keep their management happier :)

Matt

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Pete McNeil
Sent: 10 May 2004 04:59
To: [EMAIL PROTECTED]
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

At 10:06 PM 5/9/2004, you wrote:
Same problem here.  (MDaemon ver. 7.01 - Latest)

I've replaced the old .exe with the new 2.3 and renamed it with my license.
Is there anything else?
Persistent now hangs when executed.  Are we not supposed to see the 
'polling' anymore?

Yes. Sorry for the confusion.

The production version should normally produce _no_ text output. This is
normal.

The Polling messages in the beta were only for tuning and debugging. Now
that the engine is out of testing those messages have been removed. Since
it's supposed to be running as a lightweight service it's presumed that
nobody would be watching.

I have plans to develop performance monitoring code which posts to a
scoreboard file but those plans are not high on the list (in fact they are
currently shelved).

If there is a strong desire for monitoring features and messages then I will
think about putting these plans back on the development schedule.

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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

[sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-08 - Message Sniffer Version 2-3 Official Release!

We are proud to release the newest version of Message Sniffer. This version
includes important performance and system integrity improvements including
full rulebase integrity checking to protect against corrupted or failed
rulebase downloads and persistent instance support which allows Message
Sniffer to run as a lightweight service.
This new version of Message Sniffer Screams! when using the new
Persistent Instance option consistently achieving message scans in tens
of milliseconds without the need for high-end hardware or additional
network resources. While comparable anti-spam solutions can take several
seconds to process each message, this new version of Message Sniffer can
consistently produce accurate results in small fractions of a second. This
means that Message Sniffer is typically two orders of magnitude (as much as
100 times!) faster than many other anti-spam solutions without sacrificing
accuracy!
Version 2-3 also includes a number of additional features including
Rule-Panic entries to mitigate critical false positive issues immediately
without reverting to backups, on-demand log file rotation to make
management tasks easier, and adjustable logging levels to reduce the size
of log files when full details are not required.
Get the newest distribution from our Try-It page:

http://www.sortmonster.com/MessageSniffer/Try-It.html

Details about the new features are on the Sniffer Basics page:

http://www.sortmonster.com/MessageSniffer/SnifferBasics.html 

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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

Pete.

Should we be able to just replace our .exe file with this one

Fred
- Original Message - 
From: Pete McNeil [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 6:59 PM
Subject: [sniffer] Message Sniffer Version 2-3 Official Release!

 2004-05-08 - Message Sniffer Version 2-3 Official Release!

 We are proud to release the newest version of Message Sniffer. This
version
 includes important performance and system integrity improvements including
 full rulebase integrity checking to protect against corrupted or failed
 rulebase downloads and persistent instance support which allows Message
 Sniffer to run as a lightweight service.

 This new version of Message Sniffer Screams! when using the new
 Persistent Instance option consistently achieving message scans in tens
 of milliseconds without the need for high-end hardware or additional
 network resources. While comparable anti-spam solutions can take several
 seconds to process each message, this new version of Message Sniffer can
 consistently produce accurate results in small fractions of a second. This
 means that Message Sniffer is typically two orders of magnitude (as much
as
 100 times!) faster than many other anti-spam solutions without sacrificing
 accuracy!

 Version 2-3 also includes a number of additional features including
 Rule-Panic entries to mitigate critical false positive issues
immediately
 without reverting to backups, on-demand log file rotation to make
 management tasks easier, and adjustable logging levels to reduce the size
 of log files when full details are not required.

 Get the newest distribution from our Try-It page:

 http://www.sortmonster.com/MessageSniffer/Try-It.html

 Details about the new features are on the Sniffer Basics page:

 http://www.sortmonster.com/MessageSniffer/SnifferBasics.html

 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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-09 Thread Computer House Support

Are there step-by-step upgrade instructions posted anywhere?  Our
configuration is Windows 2000 server with Declude.  I don't quite understand
what needs to be done to enable the Persistent Instance option.


Thank you,

Michael Stein
Computer House
www.computerhouse.com
609 652-3222


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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

At 11:36 AM 5/9/2004, you wrote:
Pete.

Should we be able to just replace our .exe file with this one
Yes. It will act just like the current version.
The persistent server option doesn't take effect until you launch an 
instance in persistent mode. Until then (or if the persistent server fails) 
the program will act exactly like version 2-2, except that you can still 
configure the log format if you wish.

Most importantly the snf2check.exe utility is much improved with this new 
version.

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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

At 12:35 PM 5/9/2004, you wrote:
Are there step-by-step upgrade instructions posted anywhere?  Our
configuration is Windows 2000 server with Declude.  I don't quite understand
what needs to be done to enable the Persistent Instance option.
Step-by-step instructions will depend on how you intend to run the 
persistent instance.

The first step in all cases is simply to replace your .exe files with the 
ones in the new distribution. Be sure to rename (brand) the snfrv2r3.exe 
file for your license ID of course.

The way I run a persistent instance is using RunSvcExe, others have 
reported good results with Fire Daemon. Links to these are on the 
SnifferBasics page along with the basic command line for starting a Message 
Sniffer instance in persistent mode.

Essentially, launch sniffer with the word persistent in place of the usual 
file name to be scanned.

Here is a link to earlier discussions along with some more detailed 
information about getting a persistent instance set up. Follow the thread 
through and you will find more than one example:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg00165.html

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

RE: [sniffer] Message Sniffer Version 2-3 Official Release!

Pete, am I correct in assuming that the configuration file (snfrv2r3.cfg)
should also be renamed for your license ID, as well?

Bill

-Original Message-
From: Pete McNeil [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 10, 2004 2:08 AM
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

At 12:35 PM 5/9/2004, you wrote:
Are there step-by-step upgrade instructions posted anywhere?  Our 
configuration is Windows 2000 server with Declude.  I don't quite 
understand what needs to be done to enable the Persistent Instance 
option.

Step-by-step instructions will depend on how you intend to run the 
persistent instance.

The first step in all cases is simply to replace your .exe files with the 
ones in the new distribution. Be sure to rename (brand) the snfrv2r3.exe 
file for your license ID of course.

The way I run a persistent instance is using RunSvcExe, others have 
reported good results with Fire Daemon. Links to these are on the 
SnifferBasics page along with the basic command line for starting a Message 
Sniffer instance in persistent mode.

Essentially, launch sniffer with the word persistent in place of the usual 
file name to be scanned.

Here is a link to earlier discussions along with some more detailed 
information about getting a persistent instance set up. Follow the thread 
through and you will find more than one example:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg00165.html

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 message and any included attachments are from Siemens Medical Solutions 
USA, Inc. and are intended only for the addressee(s).  
The information contained herein may include trade secrets or privileged or 
otherwise confidential information.  Unauthorized review, forwarding, printing, 
copying, distributing, or using such information is strictly prohibited and may 
be unlawful.  If you received this message in error, or have reason to believe 
you are not authorized to receive it, please promptly delete this message and 
notify the sender by e-mail with a copy to [EMAIL PROTECTED] 

Thank you

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

RE: [sniffer] Message Sniffer Version 2-3 Official Release!


Thanks Pete!  One other question.  I am now downloading my rulebase files as
.gz files (much faster downloads now).  Are you prepared to receive our log
file uploads either zipped or gzipped?

Bill

-Original Message-
From: Pete McNeil [mailto:[EMAIL PROTECTED] 
Sent: Sunday, May 09, 2004 2:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!


At 05:19 PM 5/9/2004, you wrote:

Pete, am I correct in assuming that the configuration file 
(snfrv2r3.cfg) should also be renamed for your license ID, as well?

Bill

Yes, that is correct.

.cfg files are branded in the same way as the scanner (.exe) file.

_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 message and any included attachments are from Siemens Medical Solutions 
USA, Inc. and are intended only for the addressee(s).  
The information contained herein may include trade secrets or privileged or 
otherwise confidential information.  Unauthorized review, forwarding, printing, 
copying, distributing, or using such information is strictly prohibited and may 
be unlawful.  If you received this message in error, or have reason to believe 
you are not authorized to receive it, please promptly delete this message and 
notify the sender by e-mail with a copy to [EMAIL PROTECTED] 

Thank you

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

RE: [sniffer] Message Sniffer Version 2-3 Official Release!

At 05:28 PM 5/9/2004, you wrote:

Thanks Pete!  One other question.  I am now downloading my rulebase files as
.gz files (much faster downloads now).  Are you prepared to receive our log
file uploads either zipped or gzipped?


I'm not ready to do that yet, but it does seem like a good idea. I'll look 
into the scripting this week and see if I can come up with something slick 
for that purpose. First priority is to avoid breaking anything that's 
already happy.

I _may_ simply run a conversion on anything with .gz in the file name 
before beginning the normal scan process. This way folks will be able to 
upload logs either way.

I have to think through the implications first though.

_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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

The persistent mode stopped working after installing new program.

Revert back to old one and it works???

Start xx.exe x persistent

- Original Message - 
From: Pete McNeil [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, May 10, 2004 4:59 AM
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

 At 11:36 AM 5/9/2004, you wrote:
 Pete.

 Should we be able to just replace our .exe file with this one

 Yes. It will act just like the current version.
 The persistent server option doesn't take effect until you launch an
 instance in persistent mode. Until then (or if the persistent server
fails)
 the program will act exactly like version 2-2, except that you can still
 configure the log format if you wish.

 Most importantly the snf2check.exe utility is much improved with this new
 version.

 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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: [sniffer] Message Sniffer Version 2-3 Official Release!

2004-05-09 Thread Peer-to-Peer, LLC

Same problem here.  (MDaemon ver. 7.01 - Latest)

I've replaced the old .exe with the new 2.3 and renamed it with my license.
Is there anything else?
Persistent now hangs when executed.  Are we not supposed to see the
'polling' anymore?

Paul R.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Frederick Samarelli
Sent: Sunday, May 09, 2004 8:10 PM
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


The persistent mode stopped working after installing new program.

Revert back to old one and it works???

Start xx.exe x persistent

- Original Message -
From: Pete McNeil [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, May 10, 2004 4:59 AM
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


 At 11:36 AM 5/9/2004, you wrote:
 Pete.
 
 Should we be able to just replace our .exe file with this one

 Yes. It will act just like the current version.
 The persistent server option doesn't take effect until you launch an
 instance in persistent mode. Until then (or if the persistent server
fails)
 the program will act exactly like version 2-2, except that you can still
 configure the log format if you wish.

 Most importantly the snf2check.exe utility is much improved with this new
 version.

 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 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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: [sniffer] Message Sniffer Version 2-3 Official Release!


It seems to be working fine for me.  I have it running as a service, per
Matt's instructions using the W2K resource kit files, and it has been
running fine all day.

Bill

-Original Message-
From: Frederick Samarelli [mailto:[EMAIL PROTECTED] 
Sent: Sunday, May 09, 2004 5:10 PM
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


The persistent mode stopped working after installing new program.

Revert back to old one and it works???

Start xx.exe x persistent

- Original Message - 
From: Pete McNeil [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, May 10, 2004 4:59 AM
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


 At 11:36 AM 5/9/2004, you wrote:
 Pete.
 
 Should we be able to just replace our .exe file with this one

 Yes. It will act just like the current version.
 The persistent server option doesn't take effect until you launch an 
 instance in persistent mode. Until then (or if the persistent server
fails)
 the program will act exactly like version 2-2, except that you can 
 still configure the log format if you wish.

 Most importantly the snf2check.exe utility is much improved with this 
 new version.

 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 came from the Message Sniffer mailing list. For information and
(un)subscription instructions go to
http://www.sortmonster.com/MessageSniffer/Help/Help.html

---
This message and any included attachments are from Siemens Medical Solutions 
USA, Inc. and are intended only for the addressee(s).  
The information contained herein may include trade secrets or privileged or 
otherwise confidential information.  Unauthorized review, forwarding, printing, 
copying, distributing, or using such information is strictly prohibited and may 
be unlawful.  If you received this message in error, or have reason to believe 
you are not authorized to receive it, please promptly delete this message and 
notify the sender by e-mail with a copy to [EMAIL PROTECTED] 

Thank you

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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

I am having problems getting it started from the command prompt.
- Original Message - 
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 10:30 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

 It seems to be working fine for me.  I have it running as a service, per
 Matt's instructions using the W2K resource kit files, and it has been
 running fine all day.

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 5:10 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

 The persistent mode stopped working after installing new program.

 Revert back to old one and it works???

 Start xx.exe x persistent

 - Original Message - 
 From: Pete McNeil [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, May 10, 2004 4:59 AM
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

  At 11:36 AM 5/9/2004, you wrote:
  Pete.

  Should we be able to just replace our .exe file with this one

  Yes. It will act just like the current version.
  The persistent server option doesn't take effect until you launch an
  instance in persistent mode. Until then (or if the persistent server
 fails)
  the program will act exactly like version 2-2, except that you can
  still configure the log format if you wish.

  Most importantly the snf2check.exe utility is much improved with this
  new version.

  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 came from the Message Sniffer mailing list. For information
and
 (un)subscription instructions go to
 http://www.sortmonster.com/MessageSniffer/Help/Help.html

 --
-
 This message and any included attachments are from Siemens Medical
Solutions
 USA, Inc. and are intended only for the addressee(s).
 The information contained herein may include trade secrets or privileged
or
 otherwise confidential information.  Unauthorized review, forwarding,
printing,
 copying, distributing, or using such information is strictly prohibited
and may
 be unlawful.  If you received this message in error, or have reason to
believe
 you are not authorized to receive it, please promptly delete this message
and
 notify the sender by e-mail with a copy to
[EMAIL PROTECTED]

 Thank you

 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 came from the Message Sniffer mailing list. For information and 
(un)subscription instructions go to 
http://www.sortmonster.com/MessageSniffer/Help/Help.html

RE: [sniffer] Message Sniffer Version 2-3 Official Release!


Fredrick, I stopped the Sniffer service and tested from the command prompt
with:

Start xx.exe x persistent

and this is working fine, as well.  These messages have come in since
starting sniffer persistence from the command prompt:

LicenseID   20040510024905  Ded96001d093c201a.SMD   40  150
Clean   0   0   03720   60
LicenseID   20040510024908  Ded96003f080c201b.SMD   10  20
Clean   0   0   0   149451
LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
Match   117330  57  3301331578
LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
Final   117330  57  0   661178
LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
Match   117330  57  2478249273
LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
Final   117330  57  0   264373
LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
Match   118825  52  1560157266
LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
Final   118825  52  0   528566
LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
Match   118825  52  1588160059
LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
Final   118825  52  0   184759
LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
Match   54070   52  884 924 70
LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
Final   54070   52  0   617970
LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
Match   54070   52  1103116862
LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
Final   54070   52  0   274862
LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
Match   40539   62  5135517867
LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
Final   40539   62  0   579167

Bill

-Original Message-
From: Frederick Samarelli [mailto:[EMAIL PROTECTED] 
Sent: Sunday, May 09, 2004 7:32 PM
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


I am having problems getting it started from the command prompt.
- Original Message - 
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 10:30 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!



 It seems to be working fine for me.  I have it running as a service, 
 per Matt's instructions using the W2K resource kit files, and it has 
 been running fine all day.

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 5:10 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


 The persistent mode stopped working after installing new program.

 Revert back to old one and it works???

 Start xx.exe x persistent

 - Original Message -
 From: Pete McNeil [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, May 10, 2004 4:59 AM
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


  At 11:36 AM 5/9/2004, you wrote:
  Pete.
  
  Should we be able to just replace our .exe file with this one
 
  Yes. It will act just like the current version.
  The persistent server option doesn't take effect until you launch an 
  instance in persistent mode. Until then (or if the persistent server
 fails)
  the program will act exactly like version 2-2, except that you can 
  still configure the log format if you wish.
 
  Most importantly the snf2check.exe utility is much improved with 
  this new version.
 
  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 came from the Message Sniffer mailing list. For 
 information
and
 (un)subscription instructions go to 
 http://www.sortmonster.com/MessageSniffer/Help/Help.html

 --
 
-
 This message and any included attachments are from Siemens Medical
Solutions
 USA, Inc. and are intended only for the addressee(s).
 The information contained herein may include trade secrets or 
 privileged
or
 otherwise confidential information.  Unauthorized review, forwarding,
printing,
 copying, distributing, or using such information is strictly 
 prohibited
and may
 be unlawful.  If you received this message in error, or have reason to
believe
 you are not authorized to receive it, please promptly delete this 
 message
and
 notify the sender by e-mail with a copy to
[EMAIL PROTECTED]

 Thank you

 This E-Mail came from the Message Sniffer mailing list. For 
 information
and (un)subscription instructions go to
http://www.sortmonster.com/MessageSniffer/Help

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

When I do it the window pop-up is blank
- Original Message - 
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 10:59 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

 Fredrick, I stopped the Sniffer service and tested from the command prompt
 with:

 Start xx.exe x persistent

 and this is working fine, as well.  These messages have come in since
 starting sniffer persistence from the command prompt:

 LicenseID   20040510024905  Ded96001d093c201a.SMD   40  150
 Clean   0   0   03720   60
 LicenseID   20040510024908  Ded96003f080c201b.SMD   10  20
 Clean   0   0   0   149451
 LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
 Match   117330  57  3301331578
 LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
 Final   117330  57  0   661178
 LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
 Match   117330  57  2478249273
 LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
 Final   117330  57  0   264373
 LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
 Match   118825  52  1560157266
 LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
 Final   118825  52  0   528566
 LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
 Match   118825  52  1588160059
 LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
 Final   118825  52  0   184759
 LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
 Match   54070   52  884 924 70
 LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
 Final   54070   52  0   617970
 LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
 Match   54070   52  1103116862
 LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
 Final   54070   52  0   274862
 LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
 Match   40539   62  5135517867
 LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
 Final   40539   62  0   579167

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 7:32 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

 I am having problems getting it started from the command prompt.
 - Original Message - 
 From: Landry William [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 10:30 PM
 Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

  It seems to be working fine for me.  I have it running as a service,
  per Matt's instructions using the W2K resource kit files, and it has
  been running fine all day.

  Bill

  -Original Message-
  From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 5:10 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

  The persistent mode stopped working after installing new program.

  Revert back to old one and it works???

  Start xx.exe x persistent

  - Original Message -
  From: Pete McNeil [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Monday, May 10, 2004 4:59 AM
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

   At 11:36 AM 5/9/2004, you wrote:
   Pete.

   Should we be able to just replace our .exe file with this one

   Yes. It will act just like the current version.
   The persistent server option doesn't take effect until you launch an
   instance in persistent mode. Until then (or if the persistent server
  fails)
   the program will act exactly like version 2-2, except that you can
   still configure the log format if you wish.

   Most importantly the snf2check.exe utility is much improved with
   this new version.

   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 came from the Message Sniffer mailing list. For
  information
 and
  (un)subscription instructions go to
  http://www.sortmonster.com/MessageSniffer/Help/Help.html

  --

 -
  This message and any included attachments are from Siemens Medical
 Solutions
  USA, Inc. and are intended only for the addressee(s).
  The information contained herein may include trade secrets or
  privileged
 or
  otherwise confidential information.  Unauthorized review, forwarding,
 printing,
  copying, distributing, or using such information is strictly
  prohibited
 and may
  be unlawful.  If you received this message in error

RE: [sniffer] Message Sniffer Version 2-3 Official Release!

Same here, but if you check your logs, I think you will find that it is
working.

Bill

-Original Message-
From: Frederick Samarelli [mailto:[EMAIL PROTECTED] 
Sent: Sunday, May 09, 2004 8:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

When I do it the window pop-up is blank
- Original Message - 
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 10:59 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

 Fredrick, I stopped the Sniffer service and tested from the command 
 prompt
 with:

 Start xx.exe x persistent

 and this is working fine, as well.  These messages have come in since 
 starting sniffer persistence from the command prompt:

 LicenseID   20040510024905  Ded96001d093c201a.SMD   40  150
 Clean   0   0   03720   60
 LicenseID   20040510024908  Ded96003f080c201b.SMD   10  20
 Clean   0   0   0   149451
 LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
 Match   117330  57  3301331578
 LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
 Final   117330  57  0   661178
 LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
 Match   117330  57  2478249273
 LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
 Final   117330  57  0   264373
 LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
 Match   118825  52  1560157266
 LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
 Final   118825  52  0   528566
 LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
 Match   118825  52  1588160059
 LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
 Final   118825  52  0   184759
 LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
 Match   54070   52  884 924 70
 LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
 Final   54070   52  0   617970
 LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
 Match   54070   52  1103116862
 LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
 Final   54070   52  0   274862
 LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
 Match   40539   62  5135517867
 LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
 Final   40539   62  0   579167

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 7:32 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

 I am having problems getting it started from the command prompt.
 - Original Message -
 From: Landry William [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 10:30 PM
 Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

  It seems to be working fine for me.  I have it running as a service, 
  per Matt's instructions using the W2K resource kit files, and it has 
  been running fine all day.

  Bill

  -Original Message-
  From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 5:10 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

  The persistent mode stopped working after installing new program.

  Revert back to old one and it works???

  Start xx.exe x persistent

  - Original Message -
  From: Pete McNeil [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Monday, May 10, 2004 4:59 AM
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!

   At 11:36 AM 5/9/2004, you wrote:
   Pete.

   Should we be able to just replace our .exe file with this one

   Yes. It will act just like the current version.
   The persistent server option doesn't take effect until you launch 
   an instance in persistent mode. Until then (or if the persistent 
   server
  fails)
   the program will act exactly like version 2-2, except that you can 
   still configure the log format if you wish.

   Most importantly the snf2check.exe utility is much improved with 
   this new version.

   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 came from the Message Sniffer mailing list. For 
  information
 and
  (un)subscription instructions go to 
  http://www.sortmonster.com/MessageSniffer/Help/Help.html

  --

 -
  This message and any included attachments are from Siemens Medical
 Solutions
  USA, Inc. and are intended only

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

Is this by design
- Original Message - 
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 11:08 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!



 Same here, but if you check your logs, I think you will find that it is
 working.

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 8:04 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


 When I do it the window pop-up is blank
 - Original Message - 
 From: Landry William [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 10:59 PM
 Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!


 
  Fredrick, I stopped the Sniffer service and tested from the command
  prompt
  with:
 
  Start xx.exe x persistent
 
  and this is working fine, as well.  These messages have come in since
  starting sniffer persistence from the command prompt:
 
  LicenseID   20040510024905  Ded96001d093c201a.SMD   40  150
  Clean   0   0   03720   60
  LicenseID   20040510024908  Ded96003f080c201b.SMD   10  20
  Clean   0   0   0   149451
  LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
  Match   117330  57  3301331578
  LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
  Final   117330  57  0   661178
  LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
  Match   117330  57  2478249273
  LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
  Final   117330  57  0   264373
  LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
  Match   118825  52  1560157266
  LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
  Final   118825  52  0   528566
  LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
  Match   118825  52  1588160059
  LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
  Final   118825  52  0   184759
  LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
  Match   54070   52  884 924 70
  LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
  Final   54070   52  0   617970
  LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
  Match   54070   52  1103116862
  LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
  Final   54070   52  0   274862
  LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
  Match   40539   62  5135517867
  LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
  Final   40539   62  0   579167
 
  Bill
 
  -Original Message-
  From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 7:32 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
 
 
  I am having problems getting it started from the command prompt.
  - Original Message -
  From: Landry William [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 10:30 PM
  Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!
 
 
  
   It seems to be working fine for me.  I have it running as a service,
   per Matt's instructions using the W2K resource kit files, and it has
   been running fine all day.
  
   Bill
  
   -Original Message-
   From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
   Sent: Sunday, May 09, 2004 5:10 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
  
  
   The persistent mode stopped working after installing new program.
  
   Revert back to old one and it works???
  
   Start xx.exe x persistent
  
   - Original Message -
   From: Pete McNeil [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Monday, May 10, 2004 4:59 AM
   Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
  
  
At 11:36 AM 5/9/2004, you wrote:
Pete.

Should we be able to just replace our .exe file with this one
   
Yes. It will act just like the current version.
The persistent server option doesn't take effect until you launch
an instance in persistent mode. Until then (or if the persistent
server
   fails)
the program will act exactly like version 2-2, except that you can
still configure the log format if you wish.
   
Most importantly the snf2check.exe utility is much improved with
this new version.
   
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 came from the Message Sniffer mailing list

RE: [sniffer] Message Sniffer Version 2-3 Official Release!


Don't know, since I have not been running the persistence feature until
today, and I am running it as a service rather than executing it from the
command prompt.

Pete?

Bill

-Original Message-
From: Frederick Samarelli [mailto:[EMAIL PROTECTED] 
Sent: Sunday, May 09, 2004 8:11 PM
To: [EMAIL PROTECTED]
Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


Is this by design
- Original Message - 
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 11:08 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!



 Same here, but if you check your logs, I think you will find that it 
 is working.

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 8:04 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


 When I do it the window pop-up is blank
 - Original Message -
 From: Landry William [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 10:59 PM
 Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!


 
  Fredrick, I stopped the Sniffer service and tested from the command 
  prompt
  with:
 
  Start xx.exe x persistent
 
  and this is working fine, as well.  These messages have come in 
  since starting sniffer persistence from the command prompt:
 
  LicenseID   20040510024905  Ded96001d093c201a.SMD   40  150
  Clean   0   0   03720   60
  LicenseID   20040510024908  Ded96003f080c201b.SMD   10  20
  Clean   0   0   0   149451
  LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
  Match   117330  57  3301331578
  LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
  Final   117330  57  0   661178
  LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
  Match   117330  57  2478249273
  LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
  Final   117330  57  0   264373
  LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
  Match   118825  52  1560157266
  LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
  Final   118825  52  0   528566
  LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
  Match   118825  52  1588160059
  LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
  Final   118825  52  0   184759
  LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
  Match   54070   52  884 924 70
  LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
  Final   54070   52  0   617970
  LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
  Match   54070   52  1103116862
  LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
  Final   54070   52  0   274862
  LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
  Match   40539   62  5135517867
  LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
  Final   40539   62  0   579167
 
  Bill
 
  -Original Message-
  From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 7:32 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
 
 
  I am having problems getting it started from the command prompt.
  - Original Message -
  From: Landry William [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 10:30 PM
  Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!
 
 
  
   It seems to be working fine for me.  I have it running as a 
   service, per Matt's instructions using the W2K resource kit files, 
   and it has been running fine all day.
  
   Bill
  
   -Original Message-
   From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
   Sent: Sunday, May 09, 2004 5:10 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [sniffer] Message Sniffer Version 2-3 Official 
   Release!
  
  
   The persistent mode stopped working after installing new program.
  
   Revert back to old one and it works???
  
   Start xx.exe x persistent
  
   - Original Message -
   From: Pete McNeil [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Monday, May 10, 2004 4:59 AM
   Subject: Re: [sniffer] Message Sniffer Version 2-3 Official 
   Release!
  
  
At 11:36 AM 5/9/2004, you wrote:
Pete.

Should we be able to just replace our .exe file with this 
one
   
Yes. It will act just like the current version.
The persistent server option doesn't take effect until you 
launch an instance in persistent mode. Until then (or if the 
persistent server
   fails)
the program will act exactly like version 2-2, except that you 
can still configure the log

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

At 08:09 PM 5/9/2004, you wrote:
The persistent mode stopped working after installing new program.

Revert back to old one and it works???

Start xx.exe x persistent
I've not tried running it that way - though it should work if you're 
willing to remain logged in. Normally you would run the persistent instance 
using a utility that allows it to run as a service.

At any rate - there are only cosmetic differences between the beta and the 
release version - and the release version has been running live on our 
server for more than 48 hours without a hitch.

Can you be more specific about what you mean by stopped working ?
Did it crash with an error?
Did it crash without an error?
Some other indication?
Please note: the production version of the persistent mode does not produce 
any output under normal conditions. The beta version did emit a number of 
messages for debugging and monitoring purposes. If you are seeing a blank 
screen where the persistent instance is running that would be normal.

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

RE: [sniffer] Message Sniffer Version 2-3 Official Release!

At 10:06 PM 5/9/2004, you wrote:
Same problem here.  (MDaemon ver. 7.01 - Latest)

I've replaced the old .exe with the new 2.3 and renamed it with my license.
Is there anything else?
Persistent now hangs when executed.  Are we not supposed to see the
'polling' anymore?
Yes. Sorry for the confusion.

The production version should normally produce _no_ text output. This is 
normal.

The Polling messages in the beta were only for tuning and debugging. Now 
that the engine is out of testing those messages have been removed. Since 
it's supposed to be running as a lightweight service it's presumed that 
nobody would be watching.

I have plans to develop performance monitoring code which posts to a 
scoreboard file but those plans are not high on the list (in fact they 
are currently shelved).

If there is a strong desire for monitoring features and messages then I 
will think about putting these plans back on the development schedule.

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

Re: [sniffer] Message Sniffer Version 2-3 Official Release!

Yes.

At 11:10 PM 5/9/2004, you wrote:
Is this by design
- Original Message -
From: Landry William [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, May 09, 2004 11:08 PM
Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!

 Same here, but if you check your logs, I think you will find that it is
 working.

 Bill

 -Original Message-
 From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 8:04 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!


 When I do it the window pop-up is blank
 - Original Message -
 From: Landry William [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Sunday, May 09, 2004 10:59 PM
 Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!


 
  Fredrick, I stopped the Sniffer service and tested from the command
  prompt
  with:
 
  Start xx.exe x persistent
 
  and this is working fine, as well.  These messages have come in since
  starting sniffer persistence from the command prompt:
 
  LicenseID   20040510024905  Ded96001d093c201a.SMD   40  150
  Clean   0   0   03720   60
  LicenseID   20040510024908  Ded96003f080c201b.SMD   10  20
  Clean   0   0   0   149451
  LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
  Match   117330  57  3301331578
  LicenseID   20040510025416  Deecf003708b6201f.SMD   10  190
  Final   117330  57  0   661178
  LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
  Match   117330  57  2478249273
  LicenseID   20040510025417  Deecf003d094e2020.SMD   10  30
  Final   117330  57  0   264373
  LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
  Match   118825  52  1560157266
  LicenseID   20040510025437  Deee7003908b62023.SMD   10  50
  Final   118825  52  0   528566
  LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
  Match   118825  52  1588160059
  LicenseID   20040510025445  Deee70041094e2024.SMD   10  20
  Final   118825  52  0   184759
  LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
  Match   54070   52  884 924 70
  LicenseID   20040510025508  Def05007c04c02027.SMD   10  81
  Final   54070   52  0   617970
  LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
  Match   54070   52  1103116862
  LicenseID   20040510025523  Def05007d04c02029.SMD   10  30
  Final   54070   52  0   274862
  LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
  Match   40539   62  5135517867
  LicenseID   20040510025639  Def62008204c0202c.SMD   10  60
  Final   40539   62  0   579167
 
  Bill
 
  -Original Message-
  From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 7:32 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
 
 
  I am having problems getting it started from the command prompt.
  - Original Message -
  From: Landry William [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Sunday, May 09, 2004 10:30 PM
  Subject: RE: [sniffer] Message Sniffer Version 2-3 Official Release!
 
 
  
   It seems to be working fine for me.  I have it running as a service,
   per Matt's instructions using the W2K resource kit files, and it has
   been running fine all day.
  
   Bill
  
   -Original Message-
   From: Frederick Samarelli [mailto:[EMAIL PROTECTED]
   Sent: Sunday, May 09, 2004 5:10 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
  
  
   The persistent mode stopped working after installing new program.
  
   Revert back to old one and it works???
  
   Start xx.exe x persistent
  
   - Original Message -
   From: Pete McNeil [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Sent: Monday, May 10, 2004 4:59 AM
   Subject: Re: [sniffer] Message Sniffer Version 2-3 Official Release!
  
  
At 11:36 AM 5/9/2004, you wrote:
Pete.

Should we be able to just replace our .exe file with this one
   
Yes. It will act just like the current version.
The persistent server option doesn't take effect until you launch
an instance in persistent mode. Until then (or if the persistent
server
   fails)
the program will act exactly like version 2-2, except that you can
still configure the log format if you wish.
   
Most importantly the snf2check.exe utility is much improved with
this new version.
   
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 came from

RE: [sniffer] Message Sniffer Version 2-3 Official Release!