XMailforum is a readonly knowledge archive now.

Registering as a new user or answering posts is not possible anymore.

Might the force be with you, to find here what you are looking for.

2019-09-20 - hschneider, Admin

Cookie Disclaimer: This forum uses only essential, anonymous session cookies (xmailforum*), nothing to be scared of.

Posted by: smago Jul 10 2003, 04:42 PM

I try to install Spamassassin on win2k advanced server and I found an "XMSpamAssassinFilterInstaller.msi" file but when I run it it ask me to install Xmail server or I installed it.... Thx

Posted by: smago Jul 11 2003, 09:43 AM

I found my a solution : It a Path problem ... because I have space in Path... c:\perl\bin\perl.exe c:\Program Files\xmail-1.15\MailRoot\filters\sa\sa_filter.pl --> c:\perl\bin\perl.exe c:\Progra~1\xmail-1.15\MailRoot\filters\sa\sa_filter.pl Sorry for my stupide question

Posted by: smago Jul 16 2003, 09:47 AM

Spamassassin don't work with XMail 1.16 but it work with XMail 1.15. I think it's a Header probleme...

Posted by: bim Aug 12 2003, 06:57 PM

Hmmm, I just rebooted and now things work sorry about that one I'm on to the next problem now however... So if anyone knows why every newline now is turned into a double newline, let me know!

Posted by: bim Sep 23 2003, 08:15 PM

Not much of an update, but I like the feature and I guess those who don't know any Perl will appreciate not having to code even this one line of Perl : I want to be able to instantly see which message is spam and which isn't. Changing the subject seemed like the best way to do this. I changed QUOTE if ($checkedEmail=~/X-Spam-Flag: YES/) { $isSpam="SPAM"; #$checkedEmail=~s/(?<!\r)\n/\r\n/g; $xmailHeader=~s/(?<!\r)\n/\r\n/g; } into QUOTE if ($checkedEmail=~/X-Spam-Flag: YES/) { $isSpam="SPAM"; #$checkedEmail=~s/(?<!\r)\n/\r\n/g; $xmailHeader=~s/(?<!\r)\n/\r\n/g; #modify subject $checkedEmail =~ s/\nSubject: /\nSubject: [spam] /i; } This way every message that is marked as spam bij SA will have a subject that starts with [spam].

Posted by: whitedaisy Oct 14 2003, 08:58 AM

I am running with Windows 2003. No problems per say yet. I am currently in the process of rewriting the filter provided by Don Drake (thanks!!!) to be more optimized for Windows since we don't have the use of SPAMD and SPAMC yet. http://www.variummedia.com/OptSpamAssassin.zip I've attached the optimized filter as well as some performance results I have collected in the past day or two (I'll send them again after a full week) - basically the new filter is running 40% or so faster (so far) - primarily because it uses the SpamAssassin API directly instead of calling out via system(). When system() is called it launches the .BAT file in the perl directory, then it launches perl.exe again. In effect your process tree ends up looking like this (using tlist.exe): XMail.exe (680)   perl.exe (1340)         cmd.exe (744)             perl.exe (2112)     perl.exe (964)         cmd.exe (2144)             perl.exe (2152)     perl.exe (2048)         cmd.exe (2056)             perl.exe (2120) ... etc Instead of like this as you would want: XMail.exe (680)     perl.exe (1340)     perl.exe (964)     perl.exe (2048) The use of memory was killing my server even though I run with 512 MB of ram. A secondary advantage of using SpamAssassin in this way is you can make different decisions about what to do with spam by using the instance of the status returned by check_message() or check_message_text(). Another interesting option might be to generate domain SpamAssassin prefs on the fly (like turning the threshold down to 5 or something like that), and passing them in via the factory constructor. Note that I am using an older version of XMail so you will have to adapt the code to the newer return codes. Let me know if there are further ways to optimize this code that you see....we need the assassin to slice faster

Posted by: whitedaisy Oct 14 2003, 09:03 AM

QUOTE (bim @ Sep 23 2003, 08:15 PM) Not much of an update, but I like the feature and I guess those who don't know any Perl will appreciate not having to code even this one line of Perl : I want to be able to instantly see which message is spam and which isn't. Changing the subject seemed like the best way to do this. I changed QUOTE if ($checkedEmail=~/X-Spam-Flag: YES/) { $isSpam="SPAM"; #$checkedEmail=~s/(?<!\r)\n/\r\n/g; $xmailHeader=~s/(?<!\r)\n/\r\n/g; } into QUOTE if ($checkedEmail=~/X-Spam-Flag: YES/) { $isSpam="SPAM"; #$checkedEmail=~s/(?<!\r)\n/\r\n/g; $xmailHeader=~s/(?<!\r)\n/\r\n/g; #modify subject $checkedEmail =~ s/\nSubject: /\nSubject: [spam] /i; } This way every message that is marked as spam bij SA will have a subject that starts with [spam]. If I understand what you are trying to do here - it can be accomplished in SA's local.cf by using these two lines: subject_tag *****SPAM***** rewrite_subject 1