Hello lloe, Tuesday, September 7, 2004, 9:47:13 AM, you wrote:
l> Hello Fellow Users, l> When I saw Don's email " How neophytes without mastery of l> computers can use spamassassin. " I felt that I am someone who is also l> in Don's shoes. My impression wasn't that Don was a neophyte, unable to get SA to work, but rather he had users whom he wanted to do their own tuning, and those users couldn't figure out how. Your problem is different. l> I am a fairly new person to PCs and do not feel strong enough in l> knowledge to understand what and how I need to personalize any of the l> SpamAssassin modules. To start with, SpamAssassin is /not/ designed to be set up or managed by someone without in-depth knowledge of the system SA runs on. It's not "plug and play." l> There are 7 of us here at home using this machine. Each of the l> family members has one Outlook Express e-mail account. I have three l> account - personal, business, and one I strictly use for school type l> issues. In other words, you have no direct control over what lands in your remote mailbox (which is where SpamAssassin excels). Most of my users are in the same situation you are. They only get non-spam in their mailboxes (well, 99.98% accurate -- one or two spam a week slips through). My system filters all spam and dumps it into a validation mailbox that I retrieve, to verify there are no false positives (non-spam wrongly flagged), and to help the Bayes system learn better and better how spam and non-spam differ. l> I originally started with version 2.55, ... l> All I have done with these upgrades [up through 2.64] is to l> 'unzip' and move all of those extracted folders and files to the l> program folder ' C:\Program Files\SpamAssassin POP3 Proxy ' [which l> was the program folder that 2.55 originally created]. I have kept the l> original saproxy.exe application program. It is version 1.0.0.0 dated l> June 6, 2003. I also kept the original sa-learn.exe application l> program. It is also version 1.0.0.0 dated June 6, 2003. I also l> propagated the above mentioned white-list to each of those files. I have no idea how SA Proxy worked, but I'm fairly certain that the method you're using to "upgrade" SA does not apply the new files to your system. If your system is working at all, I believe it's still working with mid-2003 software and parameters. l> Frankly, I do not know what version update of SpamAssassin I am running. Can you view the email headers that control your email's delivery and record its history? Should be something somewhere on the MSOE menu that allows you to view those headers. If so, you should find one that looks like > X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on > server3.arterytc3.net That will tell you what version you're using (mine is 2.63, as distributed Jan 11 2004). l> Would someone be willing to walk me through - step by step - the l> process - from start to finish? I had a head injury and believe that l> this is a bit confusing for me to decipher on my own. Can't do it myself, but you might find help at http://wiki.apache.org/spamassassin/UsingOnWindows Better, though, for you in my opinion, would be to look at http://wiki.apache.org/spamassassin/CommercialProducts and select one of the prepackaged systems, such as SAproxy Pro, or No Spam Today! for Workstations. You need to make sure it's software that runs with an email *client* like your MSOE, not an email /server/ (which is what your remote ISP uses). You'll need to pay for these commercial solutions, but they should be much more "plug and play", easier to install and use, and maybe easier to maintain. l> Thanking you in advance for any assistance - and willingness to at l> least hear me out. Hope this helps. > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.754 / Virus Database: 504 - Release Date: 9/6/2004 You do realize that modern viruses include these types of disclaimers in some of their emails, yes? You should never trust them in any email you receive -- never trust someone else's anti-virus system to work -- always make sure yours is up to date and operational. Bob Menschel
