On Fri, Jun 27, 2003 at 09:33:00PM +0300, Vasantha Narayanan wrote: > Can you explain this further. Previously when i made SpamAssassin > work with MailScanner, in the MailScanner.conf file, I had to set > "Use SpamAssassin" to "yes". Are you saying I don't have to do > that now? If so, how do I tell MailScanner that the messages have > to scanned for spam as well? If Spamd/SpamC work independant of > MailScanner, then how exactly does it work. When mail arrives in > the incoming queue, how does spamd know to scan it? After the > spam check where does it get returned?
I don't know how exactly MailScanner works, but of course you need to have the 'use spamassassin' set to yes to make MailScanner use SpamAssassin. Difference to running spamd in the background and calling it with spamc, or just calling 'spamassassin', is that MailScanner and MIMEDefang load the SpamAssassin modules/libraries in their own code (MailScanner and MIMEDefang are mostly perl just like SpamAssasin) and use the functions in the modules/libraries. So what you get is SpamAssassin tightly integrated into the scanning program itself and you do not run any spamd processes in the background of the system or call spamc/spamassassin. MailScanner and MIMEDefang just call directly the SpamAssassin functions that check the mail, feeding the function your mail as an input and waiting the function return the report, scoring, tests that hit the mail and so on. Perhaps in reality it's a little more complicated than that, but anyways. You can not use spamc/spamd or the 'spamassassin' command to check the mail when you're using MailScanner or MIMEDefang. As I said on the mailing list, there's patches to use spamd/spamc with MIMEDefang - but again, just because you're not using spamd/spamc/spamassassin executables anywhere does not mean SpamAssassin isn't working. I don't know if someone wants to or has patched MailScanner similarly - you need to figure it out. However I can't think of any real reason to patch either of the systems to use anything else but the SpamAssasin functions directly (maybe some per-user settings for SpamAssassin are one reason). The scanning and analysing works fine as it is. Depenging on how MailScanner was programmed, in essence it can work exactly the same as spamd/spamc or 'spamassassin' executables. I know MIMEDefang includes AWL (needs few lines of code to 2.33, no idea about 2.34) and Bayes support so with all those and more SpamAssassin works with it just the same as it would when running the spamd/spamc or 'spamassassin' software seperately. Then again not everyone use AWL and Bayes, so everything depends on how and what you want to use. Calling the SpamAssassin functions directly in these situations also means SpamAssassin can not change the mail: telling SpamAssassin in its configuration to change the subject or attach the original spam along with the report will not work. This is why MailScanner and MIMEDefang need to be told to make changes to the mail according to what the directly called SpamAssassin functions return. You might want to study all the documentation you can find, read mailing lists and test things out. -- (Mr.) Hannu Liljemark | Appelsiini Finland Oy | http://appelsiini.com ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
