-----Original
Message-----
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Matt
Sent: Tuesday, December 28, 2004 10:17
PM
To:
[email protected]
Subject: Re: [sniffer] Triggered
rulebase update instructions
Bill,
I think that this is overwhelmingly
much better (the whole thing), but I have a few suggestions to
add.
1) The commenting in the
CMD file seemed a bit excessive and that made it a little hard to
follow. It might be nice to arrange all of the tweakable variables in
a single section instead of separating each one out, and then block coding
the main program with a standard amount of commenting. I think that
would make the script more readable for both programmers as well as
beginners.
2) I personally find it to be a bit messy to have
everything running from within my Sniffer directory. After all of the
other CMD files, old rulebases, service related files, logs, etc., it's not
obvious what is needed or not. I would suggest coding this up with a
default directory structure of using a subdirectory called "updates".
This would require a separation of variables for the updates directory and
the destination directory I believe.
3) I think it would be a good
idea to consider a different default directory structure. With Sniffer
evolving to support other platforms, IMail effectively abandoning us, and
Declude moving to SmarterMail and possibly others, I could very well see
Sniffer establishing a non-dependant directory structure. I would
suggest that the default recommendation become "C:\Sniffer", which might
also necessitate a change in some of Pete's other documentation. Keep
in mind that it is confusion and convolution that contributes to the lack of
efficient rulebase downloads and not the lack of resources or help.
IMO, things would benefit from standardization of this sort, and it should
all be done with purpose.
4) Since this setup is targeted
specifically at IMail, I would recommend that different packages be provided
for different platforms, and these should probably be in separate zip's so
that one doesn't get all sorts of extra stuff. This could be
"Rulebase_Updater_IMail.zip", but there should also be a Linux, MDaemon and
SmarterMail updater added to the list.
5) I'm thinking that including
the notification process within this script might be too much. The
primary goal is to get people to use the automated system and compressed
files, and this adds complexity to the setup. My thought here would be
to create a "chaining" option that could be used to kick off any script, not
necessarily IMail1.exe. You could then include this separate
notification script in the package and have it configured from within that
file, leaving only the optional chaining command within the primary script
and stripping out the rest of the stuff. I do know that from interface
design there is a basic tenet where you don't want to overwhelm the
viewer/visitor, otherwise they retain even less than they would with a
smaller group of things. Programming is often at odds with this tenet,
which is fine for programmers because the functionality necessitates
complication, but the issue being addressed here is really ease of use for
the lowest common denominator, and the primary goal is just the
downloads. You should consider that this whole thing will be used by
people with very little administration experience, no programming
experience, and in some cases, English will be a second language to them (or
only translated by a tool of some sort).
Most of this stuff is somewhat minor taken in
isolation from each other, but I believe that it could be a bit tighter in
one way or another for a better result. I'll volunteer my own services
if you would like for me to provide examples of any one of these things, but
I'll wait for your direction before doing so. I think the most
important thing would be for Pete to provide some guidance for the preferred
directory structure (independent of the app), so that this could be used for
the default settings in this and other
scripts.
Matt
Landry William wrote:
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, distribut!
ing, or using such information is strictly prohibited and may <
/FONT>
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
==============================================
Sniffer triggered rulebase update instructions
==============================================
By [EMAIL PROTECTED]
These are instruct!
ions on how to!
setup triggered downloads of new rulebase files from
the Sniffer rulebase update e-mail notifications.
Included with this distribution are the open-source "wget" and "gzip" files. They are
needed to support the download and uncompression of rulebase files.
St!
ep one:
=========
Copy all files from this distribution into your "sniffer" directory.
Step two:
=========
Edit the "snfupd.cmd" file (this is the rulebase download script).
1. Open the snfupd.cmd file in you sniffer directory with a text editor like "Notepad".
2. Edit all entries labeled "EDIT NEXT LINE" with your specific configuration information.
3. Save your changes.
Step three:
===========
Create an IMail "Program Alias" account
1. Open the "IMail Administrator"
2. Select the domain to create the "program a!
lias" account under
3. Click on "Aliases" under the chosen domain
4. Click on the "Add Alias..." button
5. Type in the "Alias ID" for this account (something like: snifferupdate),
then click "Next"
6. Select "Program" as the alias type and click "Next"
7. Click "Browse..." and browse to the location of your "sniffer" directory
and select "snfupd.cmd", then click "Next"
8. Click "Finish" and you're done setting !
up your Sniffer "Program Alias" account
Step four (optional):
=====================
Create a "Standard Alias" account (only necessary if you want to receive a copy
of the Sniffer update!
notifications).
1. Open the "IMail Administrator"
2. Select the domain to create the "standard alias" account!
under
3. Click on "Aliases" under the chosen domain
4. Click on the "Add Alias..." button
5. Type in the "Alias ID" for this account (something like: snfupd), then click "Next"
6. Select "Standard" as the alias type and click "Next"
7. Add the e-mail address that you would like the Sniffer update messages to be
forwarded to. Also add the "program alias" address you created in Step Three
above. This will send a copy of the update notification to all listed accounts,
including the "program alias", which will trigger the new rulebase download.
8. Click "Finish" and you're done setting up your Sniffer "Standard Alias" account
Step five:
==========
Test the new "program alias" account.
!
1. If you setup a "standard alias", as defined in "Step four" above, send a test
message to your "standard alias" e-mail address. This should trigger a copy of
the test message to your e-mail forwarding address and set-!
off the rulebase download.
2. Check to see that you received a copy of the test message to your forwarding address.
3. Check to see that a rulebase download was triggered (check the timestamp of your
rulebase file - you can also vi!
ew the snfupd.txt file to see the complete status of
the update. Also, if you opted to receive the update results via e-mail (via the
!
snfupd.cmd download script), check to see that you receiv
ed the results e-mail.
4. If you skipped "Step four" above, send a test message to your "program alias" address
and check to see if it triggered a rulebase download.
Step six:
=========
Advise SortMonster of the new e-mail address to send update notifications to.
1. If you created a "standard alias" account as defined in "Step four", send an e-mail
to Sniffer Support ([EMAIL PROTECTED]) and ask them to send your rulebase update
notifications to your "standard alias" e-mail address.
2. If you skipped "Step four" above, ask Sniffer Support to send!
your rulebase update
notifications to your "program alias" address.
3. Monitor to make sure your rulebase update e-mails are successfully triggering your
rulebase downloads.
============
That's it...
============
--
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================
