RE: [sniffer] Triggered rulebase update instructions
I agree on the simplicity, just thought it would be a bonus not to involve sortmonster with the address changes. Woody -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Landry William Sent: Wednesday, December 29, 2004 2:37 PM To: 'sniffer@SortMonster.com' Subject: RE: [sniffer] Triggered rulebase update instructions There are many ways to skin this cat. For Declude JunkMail Pro users, you could also setup a COPYTO action to notify the program alias. However, the dual alias setup appeared to be the simplest way for the novice mail admin to get this working. More experienced admins will have the ability to tweak the scripts and setup their configurations to meet their own specific needs. Again, I am attempting to make the process as simple as possible so that anyone using IMail/Declude/Sniffer can setup triggered updates. More experienced users are always going to do things their own way. Bill -Original Message----- From: Woody G Fussell [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 7:57 AM To: sniffer@SortMonster.com Subject: RE: [sniffer] Triggered rulebase update instructions Bill This would apply to Imail users. I suggest that rather than creating two aliases that you use only a program alias. Trigger it using an inbound Imail subject rule to send a copy to the alias. Everyone has a unique subject line based on your rule base ID therefore you can create a unique rule to trigger the updates. The uniqueness of the subject may reduce the frequency of spam triggering an update. Example subject rule S~abcde123.snf Update:[EMAIL PROTECTED] This eliminates having to contact sortmonster to change the address where your updates are delivered (also allows flexibility to change your programs alias name as necessary with out involving sortmonster) You will also continue to receive the notifications where ever you were getting them before. Woody Fussell Wilbur Smith Associates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Landry William Sent: Tuesday, December 28, 2004 9:08 PM To: 'sniffer@SortMonster.com' Subject: RE: [sniffer] Triggered rulebase update instructions Attached is an updated instructions file to fix some typos and missed information. I'll send out another update after receiving feedback from others. Bill --- 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 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] Triggered rulebase update instructions
Bill This would apply to Imail users. I suggest that rather than creating two aliases that you use only a program alias. Trigger it using an inbound Imail subject rule to send a copy to the alias. Everyone has a unique subject line based on your rule base ID therefore you can create a unique rule to trigger the updates. The uniqueness of the subject may reduce the frequency of spam triggering an update. Example subject rule S~abcde123.snf Update:[EMAIL PROTECTED] This eliminates having to contact sortmonster to change the address where your updates are delivered (also allows flexibility to change your programs alias name as necessary with out involving sortmonster) You will also continue to receive the notifications where ever you were getting them before. Woody Fussell Wilbur Smith Associates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Landry William Sent: Tuesday, December 28, 2004 9:08 PM To: 'sniffer@SortMonster.com' Subject: RE: [sniffer] Triggered rulebase update instructions Attached is an updated instructions file to fix some typos and missed information. I'll send out another update after receiving feedback from others. Bill --- 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] Downloads are slow...
Why do you not use a "program alias" and only download when you receive notification that a new rule base is available? If everyone used gzip and only downloaded when notified the bandwidth could be controlled by staggering the notifications. Woody Fussell Wilbur Smith Associates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Matuska Sent: Tuesday, December 28, 2004 12:49 PM To: sniffer@SortMonster.com Subject: Re: [sniffer] Downloads are slow... I agree that something needs to be done about the update scripts that are inadvertently downloading the full rulebase all the time. I didn't even know it but we were doing this until I went through our update script again this morning and found it didn't have the -N option in Wget, so we were downloading the entire rulebase whether we needed it or not. The gzip compression is cool, and I will likely implement it soon, but I think the major problem is everyone that is using scripts that keep downloading the same file over and over again tying up the bandwidth. I would recommend 2 things to help alleviate this problem: 1. Monitor connections to rulebase downloads to see who is downloading the rulebase everytime they connect on a schedule to determine who has their scripts setup wrong, and contact them to correct it. It took me under a minute to add the -N option to wget, it should be a no brainer. 2. Correct the scripts posted on the Sniffer website to include date checking, and possibly gzip compression, I used one of those scripts for our system and assumed it would be setup correctly, but it was not. Jim Matuska Jr. Computer Tech2, CCNA Nez Perce Tribe Information Systems [EMAIL PROTECTED] - Original Message - From: "Matt" <[EMAIL PROTECTED]> To: Sent: Monday, December 27, 2004 10:03 PM Subject: Re: [sniffer] Downloads are slow... >I agree entirely. If bandwidth has become an issue, it would be resolved >with a focus on producing very tight and easily customizable scripts (a >variables section in the top of the scripts). I believe that going the >VBScript route might be the best way to go, or at least I believe that more >of us can hack a more involved VBScript than a batch or CMD file. >Enforcing compressed downloads and checking for timestamps prior to >downloading should be done in these scripts as well. > > Right now the script examples assume a familiarity with scripting, and > while local participants can mostly handle that stuff, the non-vocal ones > are most likely to not even be aware of the issues or how to fix them, and > might have scripted timed downloads because it is definitely the easiest > way to go. This is probably the majority of the customer base. There is > an impression for instance with Declude's user base that +80% use > primarily the default config which most of us know is severely lacking in > comparison to the potential that exists by tweaking the settings. > > With better script examples and a careful step-by-step readme promoted in > a mailing to your customers, I believe that this issue could go away, or > at least theoretically it should. > > Personally, I have mine tied to the E-mails, I download the zipped > versions, I don't bother checking on the status, and have never noticed > any issues as a result. It would be a small shame if I was missing > downloads due to timeouts, but not that big of a deal if this has never > caused a noticeable problem. > > Matt > > > > > Andy Schmidt wrote: > >>Pete, >> >>With all due respect - I think the download problem is "self-inflicted", >>because your web site is providing unsuitable examples to your customers! >>Even with moderate bandwidth, your server would be able to handle tens of >>thousands of hits a day. Checking if an updated file exists should barely >>be noticeable - as long as it doesn't result in an unnecessary download. >>You probably suffer TWO problems: >> >>A) Most of your customers are downloading rules based on a schedule, even >>if >>no rules exists. Potential savings: 100% per download attempt. >> >>B) Your customers are not downloading "compressed" rule files. Potential >>savings: about 66%, but that's not bad either. >> >> >>One likely explanation is that at least THREE of your sample scripts do an >>unconditional and uncompressed download! Here the 3 URLs you list on your >>web site and WGET command they are using: >> >>http://www.sortmonster.com/MessageSniffer/Help/UserScripts/david_snifferUp da >>teMethod.zip >>wget http://www.sortmonster.net/Sniffer/Updates/.snf -O >>.new >>--http-user=username --http-passwd=password >> >> >>http://www.sortmonster.com/MessageSniffer/Help/UserScripts/Hank_SnifferScr ip >>ts.zip >>wget http://www.sortmonster.net/Sniffer/Updates/.snf -O >>.new >>--http-user=sniffer --http-passwd=ki11sp8m >> >> >>http://www.sortmonster.com/MessageSniffer/Help/UserScripts/Michiel_AutoUpd at >>e.zip >>wget >>ht
[sniffer] Sniffer Updates-- am I missing something
What am I missing in this thread? I use an Imail “program alias” that automatically runs a download script when I am notified by [EMAIL PROTECTED] when a new rule base is available; therefore only a validation needs to be preformed. I took this procedure from this list, so I know it must be common knowledge. What advantage is there to a scheduled or manual rule base update that requires conditional test? It seems to me that I have no need to check for rule base updates until I have been advised by support that one is available. Will there ever be a rule base update available before I have been notified? Woody Fussell Wilbur Smith Associates [EMAIL PROTECTED]
