[sniffer] Re: Transition to new deliver server completed. Watch Out For The Minor Changes!

2007-01-05 Thread Pete McNeil
Hello george,

Friday, January 5, 2007, 9:48:40 AM, you wrote:

 Pete,

 Mine is also failing on a connection time out.

We are working on a firewall issue that was discovered late yesterday.

As a temporary measure you should be able to connect w/ ftp to:
tempftp.armresearch.com -- Once we have the firewall issue cleared the
tempftp host will go away.

Sorry for the trouble.

_M

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


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



[sniffer] Re: Transition to new deliver server completed. Watch Out For The Minor Changes!

2007-01-05 Thread Pete McNeil
Hello Chris,

Friday, January 5, 2007, 2:34:48 AM, you wrote:

 Pete,

 Every so often I end up with thousands of .snf, .xxx and .que files in
 my sniffer directory, and it stops filtering spam. Any ideas??

You should never find thousands of .snf files...

The other files are job files -- each representing it's own message.

This condition can occur if the system is restarted uncleanly or if it
becomes badly overloaded. In particular, on Declude systems, if the
system gets too many messages it may take too long for some messages
to get scanned -- in those cases Declude will kill off the process
before it can finish or clean up-- once a numger of job files is
abandoned in the SNF working directory, all of the SNF instances will
relax their timing to compensate for the apparently high load -- as a
result more of them get killed off and a vicious cycle is created --
eventually there are so many scan jobs that none of them can be
processed in a reasonable time.

In a true overload condition there is almost no way to prevent this--
at least w/ Imail/Declude systems, because there is no inbound
throttling - the server will keep accepting and queueing messages even
as it is choking on them.

However - you can make the system more resilient by significantly
extending the timeout for external filters so that SNF instances don't
get killed off.

 I have to delete them, and restart my smtp server  sniffer engine

Done cleanly this is the fix for this condition. Cleanly = stop smtp
first, stop your persistent instance, Then (once no more messages are
being processed) clean out any abandoned job files (.xxx, .que, .fin,
.wrk, .err, .abt) then restart your persistent instance, then restart
smtp.

Hope this helps,

Thanks,

_M


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


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



[sniffer] Re: Transition to new deliver server completed. Watch Out For The Minor Changes!

2007-01-04 Thread Chris Bunting
Pete,

Every so often I end up with thousands of .snf, .xxx and .que files in
my sniffer directory, and it stops filtering spam. Any ideas?? 

I have to delete them, and restart my smtp server  sniffer engine

Thank You,
Chris Bunting
Enterprise Account Manager
Lancaster Networks

Direct: 717-278-6639
Office: 888-LANCNET x703
Fax: 717-431-6262

1085 Manheim Pike 
Lancaster PA 17601 
www.lancasternetworks.com
--
Corporate Technology Solutions...
Specializing in 3com NBX Telephony Solutions
IT Services - Phone Systems - Digital CCTV
--
The information in this e-mail is confidential and may be privileged or
subject to copyright. It is intended for the exclusive use of the
addressee(s). 
If you are not an addressee, please do not read, copy, distribute or
otherwise act upon this email. If you have received the email in error, 
please contact the sender immediately and delete the email. The
unauthorized use of this email may result in liability for breach of
confidentiality, privilege or copyright.

-Original Message-
From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On
Behalf Of Pete McNeil
Sent: Thursday, January 04, 2007 5:07 PM
To: Message Sniffer Community
Subject: [sniffer] Transition to new deliver server completed. Watch Out
For The Minor Changes!

Hello Message,

  So far the upgrade seems to have gone off with only one minor hitch.

  The new server's authentication realm is SNF

  It used to be SortMonster

  If you are using the perl script from khera@kcilink.com then you
  will need to make this minor adjustment or else the script will fail
  to authenticate.

  As far as I can tell from watching the logs there are no other
  issues so far.

  Thanks to Matt Reimer for tracking this down and reporting the fix.

  Best,

  _M

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


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



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