Hagen: Would you be willing to share your filters? I've in dire need of exactly = what you're doing. I wish I could code in Perl.
Thanks in advance. >>> [EMAIL PROTECTED] 01/22/04 02:27PM >>> Hello Spyros, >>Are You sure that it is a spamc problem or a problem with Your $PATH? >>What happens exactly? >Well it looks like everything is in place. "spamc" is living in /usr/bin >which is in the path of the system. >spamd runs as a daemon from "/usr/local/bin/sa/spamd/spamd" >To tell you the truth, I don't know. I've read so much stuff. Most of it >conflicting. I just had a chat with Don Drake (I think it's the chap who >built >sa_filter) and he says I am _not_ supposed to run "sa-learn" if I have = his >piece of code installed (which I have). Auto-Learing is turned on by default. This is done in /etc/mail/spamassassin/local.cf or where Your site config usually resides. It could be overwritten by the file ~root/.spamassassin/user_prefs, if spamd runs as root. I assume that suid arguments are not used in Your configuration. >At the moment, all I know is that I have people breathing down my neck >for spam mail on this establishment. And, basically, I am trying to >understand >how to proceed with all this. But how can you proceed with something, = when >you don't have concrete evidence of what is going on ? Tell these people that establishing spamfilter takes a lot of time and will never be 100% reliable. Never. Either they have to expect some spam, or they have to expect mails incorrectly declared as spam and. Auto-learing of spamassassin (and others) takes really time. I set up an email account "spammaster", where people report spam manually to by just forwarding spam. I also set up a filter that attaches spam into a new mail and forwards it to spammaster. That filter is also able to do pattern matching with perl regular expressions in mail headers and bodies. If matches are found, mail gets attached to a new one and sent to spammaster. Users will never see mails found to be spam by spamassassin or by my filter. This is a very strict solution, normal mails might never reach users. However, Users reporting spams to the spammaster account could help You to set up more rules for spamassassin. E.g. blacklists or filters with scores. But someone has to review spammaster account... .....so I also started another filter that will act as a blacklist/whitelist operator for users. They can send eg. ADD BLACKLIST [EMAIL PROTECTED] to that filter and the address gets blacklisted. Same for whitelisting. Furthermore, target mailaddresses could be automatically whitelistet by that filter, if the sender comes from Your domain(s). These things are not difficult to implement, but it can be dangerous using them. Let me know if there is an interest here. > E.g. how do I know that mail gets filtered now ? Did You run XMail as follows from command line: --- cut --- one line: XMail -Pl -Sl -Ql -Yl -Fl -Cl -Ll -Md 2>&1 | tee /tmp/xmaildebug --- cut --- This logs nearly everything to XMail log files. The daemon itself will stay in the foreground and write a lot of debug messages. They can be seen in Your terminal and they will go to /tmp/xmaildebug for futher work. Stop xmail with CTRL-C after a whhile and put it back to normal mode. Review /tmp/xmaildebug, look for sa_filter.pl. Bye, Hagen - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]