Re: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qm
Brought to you by:
swix
From: Flinn M. <fl...@ac...> - 2003-06-03 16:53:00
|
Can you post the code to filepipe for those of us not using Linux? Regards, Flinn ----- Original Message ----- From: "Olivier M." <qm...@or...> To: "Markus Lorch" <ml...@vt...>; <vma...@li...> Cc: <oma...@li...> Sent: Tuesday, June 03, 2003 11:29 AM Subject: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin > Re, > > On Tue, Jun 03, 2003 at 09:36:00AM -0400, Markus Lorch wrote: > > 1. it seems as with the created .qmail files email will be scanned > > for spam twice. Once by nospam, and if that did not delete/move the > > mail then again directly by spamc. Shouldn't we try to modify nospam > > and not run spamc in addition? > > This is because I like to be able to look at the X-Spam lines afterwards: > > X-Spam-Level: *** > X-Spam-Checker-Version: SpamAssassin 2.54-omnis.ch (1.174.2.17-2003-05-11-exp) > X-Spam-Report: ---- Start SpamAssassin results > 3.70 points, 5 required; > * 0.8 -- From: does not include a real name > * 0.1 -- BODY: HTML included in message > * 0.1 -- BODY: HTML font color is blue > * 1.4 -- BODY: Message is 10% to 20% HTML > * 1.3 -- Subject contains a unique ID > > > n both (non-spam)-deliverd mail, and also in the spam trash, for > further studies. When using spamc only in the ifspamh script, the > delivered mail would not contain these interesting lines. > > But I plan to add a parameter to let the people choose if they want > that or not: it's probably not the case for everybody, and it > takes twice more load... > > > > 2. why did you choose not to directly write the .qmail files through > > oadmin? Did you want to avoid changes to oadmin or was it a privilege > > issue? If it is a privilege issue wouldn't it be better to use a setuid > > mainly because of the privilege issue: omail-admin is running as web > service, user apache or wwwrun, and can't create/delete these files. > And creating another wrapper, well... I found that my cronjob based > solution would be simpler. > > > helper tool to change the settings on demand, than then rather complex > > approach of checking the DB frequently for changes > > these frequent disk and DB access are normaly pretty well cached > by "modern OS's", so it's not sooo bad, don't you think? :) > (but it's also not optimal, that's sure) > > Improvements suggestions welcome :) > regards, > Olivier > > PS: actual code is under http://omail.omnis.ch/ospam/dev/ > > -- > _________________________________________________________________ > Olivier Mueller - om...@83... - PGPkeyID: 0E84D2EA - Switzerland > qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch > > --------------------------------------------------------------------- > To unsubscribe, e-mail: vma...@li... > For additional commands, e-mail: vma...@li... > > |