----- Original Message ----- From: "Niklas Wikman" <[EMAIL PROTECTED]> Newsgroups: saltstorm.xmail Sent: Saturday, February 15, 2003 12:33 AM Subject: [xmail] SV: Re: SV: Re: BCware NoSPAM SMTP Proxy Daemon
> OK, I just tested the proxy solution... and Bang! I had an open relay :-( > I'll try this "scoop" thing tomorrow, thanx Thomas! scope that is, give it a try. In case of any Qs I am just around the corner. /thomas - Göteborg > /Niklas > > -----Ursprungligt meddelande----- > FrÃ¥n: Newsmirror [mailto:[EMAIL PROTECTED]] > Skickat: fr 2003-02-14 19:40 > Till: [EMAIL PROTECTED] > Kopia: > Ã"mne: [xmail] Re: SV: Re: BCware NoSPAM SMTP Proxy Daemon > > > > > Christian, > > > > > Hello Newsmirror, > > > > Do you have any opinion about the workload on a NT when using > > the spamassassin perl modules instead of the binary? > > > > I am thinking: the binarys must make the spam handling rather > > fast but if i use the NT perl module i will probably notice > > the diffrence in workload at some point... > > the binaries in Spamassassin context refers to the SPAMC/SPAMD frontend > supplied with the SA dist. The actual SA scanning engine is a vanilla perl module. > > SPAMD sits in the background with wrapped perl interpreter and forks > off children for each message passed in by SPAMC (client). Messages (I believe) > are passed via STDIN. SPAMD keeps SA in-core as perl bytecode. > > The scope setup. > scope daemon (scoped) sits in the background listening for socket connections. > scoped is written in perl aswell as SA (or any other scope procedure) > and are all running within the same process. Scoped keeps SA in-core as perl >bytecode. > Scope clients (a 4kb Win32 binary) are forked by XMail (as filters/mailprocs) > and passes the message by *file reference* to scoped which carries out the > requested procedure. > > > as you can see, basically the client/server concepts are the same, with > the exception that scope communicates over sockets and passes messages > as file reference rather than over STDIN (which is a real performance hog > under Win32). Both are using persistent perl interpreters and caches > bytecode for fast reuse. > > SPAMD works in conjunction with the OS userbase and allows many per > user setting and load configuration files + spam thresholds on a per request > basis. (perf hog) > > Scope::spamassassin runs slurps in a global configuration at start up, but > acknowledges per user spam thresholds (from Xmail user.tab settings or Mysql (in >1.20+)) > > > So, concluding I would say my initial tests showed that Scope::spamassassin is >somewhat > faster than the native SPAMD, this mostly due to the per user configuration > parsing. scanning-wise it is your CPU that'll dictate the performance. > SPAMD is as far I know not an option in a Win32 environment, due to compiling issues. > > > > > > Have anyone tested? Could it do maybe 200 spams per minute? I > > am just not sure about the performance i can espect... > > Maybe you could achieve that sort of numbers with a hotted p4. > I remember doing some SA performance tests back in October and got it to scan >something > like ~35 messages/min tops (standard size ~7kb) on a Win2k/Duron 1000. > > However, looking at the stats I posted in my previous message shows 26388 requests > handled in 6:38 hours = 398 min. That is about 66 message/min on average assuming > all were parsed, which isn't the real thruth really since scoped will decline > duplicate processing and messages larger that N kb. (N = 256kb in my setup). > the stats btw, are taken from a scope/XMail setup running on a NT4/P-Pro 200Mhz > > > > /thomas. > > > > Br, Christian Otrel [EMAIL PROTECTED] > > > > >=================================================================================== > > > > > > >> On Windows? I found some information, but it looked like a two day job to fix >the scripts :-( > > >> > > >> http://www.openhandhome.com/howtosa.html > > > > N> I suggest you check out Scope, it might do what you want. Scope comes with a > > N> procedure gluing a daemonized SpamAssassin with XMail filters on Win32 aswell > > N> as Linux/*bsd. Scope only uses the perl parts of SA (available via CPAN), > > N> the core, and thus the SPAMC/SPAMD parts (which are the troublesome parts > > N> on Win32 environments) gets obsolete. > > > > N> I have run SA 2.43 hosted by Scope over here on a XMail/NT4 box for 4½ months > > N> by now, works great. Snapshot of the current req stats follows: > > > > N> [Request Statistics] (since server startup, 2002-10-09 10:09:14) > > N> ---------------------Requests-------Errors--------CPU Load------------------ > > N> spamassassin 26388 (24.76%) 0 ( 0.00%) 06:38:11:208 (53.18%) > > N> nntpfwd 21062 (19.76%) 0 ( 0.00%) 04:04:33:719 (32.66%) > > N> h2t 20894 (19.60%) 0 ( 0.00%) 00:41:19:326 ( 5.52%) > > N> noop 19237 (18.05%) 0 ( 0.00%) 00:09:23:401 ( 1.25%) > > N> vanguard 17036 (15.98%) 0 ( 0.00%) 00:46:20:151 ( 6.19%) > > N> demime 1726 ( 1.62%) 0 ( 0.00%) 00:08:20:440 ( 1.11%) > > N> status 45 ( 0.04%) 2 ( 4.44%) 00:00:11:244 ( 0.03%) > > N> ----------------------------------------------------------------------------- > > N> -Server Total- 106590 - 2 ( 0.00%) 12:28:46:107 - > > > > - > > 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] > > > > > -- Binary/unsupported file stripped by Ecartis -- > -- Type: application/ms-tnef > -- File: winmail.dat > > > - > 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] > > > > -- > ---------------------------------------------------------------------------- > XMail::Scope::nntpfwd v1.00 | 2003-02-14 23:28:36Z > <nntp://news.saltstorm.net/saltstorm.xmail/3565> - 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]
