omail-ospam

[Omail-ospam] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Olivier M. <qm...@or...>]

Hello,

I'm currently working on oSpam: feedback, feature requests
etc. are welcome (if possible per mail or directely on the 
project's mailing list). 

 oSpam uses omail-admin as web frontend which manage the
 SpamAssassin sql userprefs table. oSpam itself is a Perl script
 which will look at this table, and dynamicaly (on a cronjob basis)
 create/ modify/remove .qmail-files according to the users
 preferences. It will take care not overwritting existing .qmail-x
 files, and keeps md5sum tracks of the created files to make sure it
 will only remove self- created files.  

* Project homepage :  (files to download)
  http://omail.omnis.ch/ospam/

* Mailing lists is now working : check
  http://lists.sourceforge.net/lists/listinfo/omail-ospam

* omail-Admin demo: http://admin.omnis.ch/admin2/
  login with "test.com" / "test", then click on "AntiSpam"

* status: exists since 2 days, it (seems to) works fine on my
  production server :)

* pros: not all the incomming mails are scanned for spam (takes time
  and CPU load), but only for the selected accounts.  cons: currently
  work only with qmail+vmailmgr. suppport for "qmail-only" may come
  later


======================================================================

CONCEPT:
--------

Mail users and administrators can turn on and off the anti-spam system
and set their settings (score, what to do with spams, white/blacklists),
which are saved in the standard SpamAssassin SQL base.
(cf. http://spamassassin.rediris.es/dist/sql/README and ./sql/nospam.sql
for the table structure).


The last solution I used before was to do the spam-scanning of incoming mails
via qmail-scanner, directely on smtp server level: it worked fine, but
solution as not optimal because of a few problems with multiple recipients
and compatibility problems with vmailmgr. That's why I now started to
work on a solution based on .qmail-xxx files.


Steps:

1. the user logs in into omail-admin and use the "Antispam" panel
   (screenshot:  http://www.omnis.ch/stuff/ospam/oadmin.jpg )

2. settings are saved into the sql table "userpref"

   At this moment, the mail server don't know yet it has to
   scan the mails for this user.

3. cron or a trigger runs the ospam-dotqmail.pl script

4. ospam will compare the SpamAssassin table with its internal
   table (dotqmail) and will create (or edit/remove) the according .
   qmail-xxx file.  For example:

   omega:/home/omx.ch # more .qmail-scan_and_trash
   # =================================================================================
   # /home/omx.ch/.qmail-scan_and_trash generated on Sat May  3 19:35:08 2003
   # by oSpam version 1.1000 for <sca...@om...> [o1a336]
   # ___ DO NOT EDIT ___      -== http://ospam.omnis.ch/ ==-
   #
   |/usr/local/nospam/ifspamh _trash_ sca...@om...
   |/var/qmail/bin/preline -d /usr/bin/spamc -f -u sca...@om... | /usr/local/nospam/filepipe /usr/local/bin/vdeliver
   #
   # =================================================================================

5. on further user settings changes (in omail-admin):
   - settings like score and white/blacklists are fetched directely
     by spamc, so it will be valid just after the change
   - spam scanning on/off, action with the spams (forward/trash/tag)
     are updated only on ospam-dotqmail.pl run

Voila, I hope you see the concept a little bit better... :)

======================================================================


Suggestions / opinions welcome, to let me set the priorities: 
I'll continue to work on the code the next days (optimize the code). 

Regards,
Olivier


-- 
_________________________________________________________________
 Olivier Mueller - om...@83... - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch  -  http://webmail.omnis.ch

[Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Markus L. <ml...@vt...>]

Olivier,

thank you for your contributions to the community. 

I have looked at your new ospam implementation and have two questions:

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?

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
helper tool to change the settings on demand, than then rather complex
approach of checking the DB frequently for changes

Just comments :) Would love to hear from you.

Thanks
Markus 

> -----Original Message-----
> From: Olivier M. [mailto:qm...@or...] 
> Sent: Saturday, May 03, 2003 10:48 PM
> To: vma...@li...; 
> spa...@li...; qm...@li...
> Cc: oma...@li...
> Subject: [vmailmgr] oSpam 0.01 - a system-wide anti-spam 
> solution for qmail and vmailmgr with spamassassin
> 
> 
> Hello,
> 
> I'm currently working on oSpam: feedback, feature requests
> etc. are welcome (if possible per mail or directely on the 
> project's mailing list). 
> 
>  oSpam uses omail-admin as web frontend which manage the
>  SpamAssassin sql userprefs table. oSpam itself is a Perl script
>  which will look at this table, and dynamicaly (on a cronjob basis)
>  create/ modify/remove .qmail-files according to the users
>  preferences. It will take care not overwritting existing .qmail-x
>  files, and keeps md5sum tracks of the created files to make sure it
>  will only remove self- created files.  
> 
> * Project homepage :  (files to download)
>   http://omail.omnis.ch/ospam/
> 
> * Mailing lists is now working : check
>   http://lists.sourceforge.net/lists/listinfo/omail-ospam
> 
> * omail-Admin demo: http://admin.omnis.ch/admin2/
>   login with "test.com" / "test", then click on "AntiSpam"
> 
> * status: exists since 2 days, it (seems to) works fine on my
>   production server :)
> 
> * pros: not all the incomming mails are scanned for spam (takes time
>   and CPU load), but only for the selected accounts.  cons: currently
>   work only with qmail+vmailmgr. suppport for "qmail-only" may come
>   later
> 
> 
> ======================================================================
> 
> CONCEPT:
> --------
> 
> Mail users and administrators can turn on and off the anti-spam system
> and set their settings (score, what to do with spams, 
> white/blacklists),
> which are saved in the standard SpamAssassin SQL base.
> (cf. http://spamassassin.rediris.es/dist/sql/README and 
> ./sql/nospam.sql
> for the table structure).
> 
> 
> The last solution I used before was to do the spam-scanning 
> of incoming mails
> via qmail-scanner, directely on smtp server level: it worked fine, but
> solution as not optimal because of a few problems with 
> multiple recipients
> and compatibility problems with vmailmgr. That's why I now started to
> work on a solution based on .qmail-xxx files.
> 
> 
> Steps:
> 
> 1. the user logs in into omail-admin and use the "Antispam" panel
>    (screenshot:  http://www.omnis.ch/stuff/ospam/oadmin.jpg )
> 
> 2. settings are saved into the sql table "userpref"
> 
>    At this moment, the mail server don't know yet it has to
>    scan the mails for this user.
> 
> 3. cron or a trigger runs the ospam-dotqmail.pl script
> 
> 4. ospam will compare the SpamAssassin table with its internal
>    table (dotqmail) and will create (or edit/remove) the according .
>    qmail-xxx file.  For example:
> 
>    omega:/home/omx.ch # more .qmail-scan_and_trash
>    # 
> ==============================================================
> ===================
>    # /home/omx.ch/.qmail-scan_and_trash generated on Sat May  
> 3 19:35:08 2003
>    # by oSpam version 1.1000 for <sca...@om...> [o1a336]
>    # ___ DO NOT EDIT ___      -== http://ospam.omnis.ch/ ==-
>    #
>    |/usr/local/nospam/ifspamh _trash_ sca...@om...
>    |/var/qmail/bin/preline -d /usr/bin/spamc -f -u 
> sca...@om... | /usr/local/nospam/filepipe 
> /usr/local/bin/vdeliver
>    #
>    # 
> ==============================================================
> ===================
> 
> 5. on further user settings changes (in omail-admin):
>    - settings like score and white/blacklists are fetched directely
>      by spamc, so it will be valid just after the change
>    - spam scanning on/off, action with the spams (forward/trash/tag)
>      are updated only on ospam-dotqmail.pl run
> 
> Voila, I hope you see the concept a little bit better... :)
> 
> ======================================================================
> 
> 
> Suggestions / opinions welcome, to let me set the priorities: 
> I'll continue to work on the code the next days (optimize the code). 
> 
> Regards,
> Olivier
> 
> 
> -- 
> _________________________________________________________________
>  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...
> 

Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Olivier M. <qm...@or...>]

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

Re: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Flinn M. <fl...@ac...>]

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...
>
>

RE: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Markus L. <ml...@vt...>]

see Olivier's install guidelines
(http://omail.omnis.ch/ospam/ospam-0.01/INSTALL):

6. install mess822 and filepipe if you don't have them already:
      http://www.nougen.com/test/filepipe.tgz
      http://cr.yp.to/software/mess822-0.58.tar.gz


Markus

> -----Original Message-----
> From: oma...@li... 
> [mailto:oma...@li...] On Behalf Of 
> Flinn Mueller
> Sent: Tuesday, June 03, 2003 12:52 PM
> To: vma...@li...; Markus Lorch
> Cc: oma...@li...
> Subject: Re: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] 
> oSpam 0.01 - a system-wide anti-spam solution for qmail and 
> vmailmgr with spamassassin
> 
> 
> 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...
> >
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: eBay
> Get office equipment for less on eBay!
> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> _______________________________________________
> Omail-ospam mailing list
> Oma...@li...
> https://lists.sourceforge.net/lists/listinfo/omail-ospam
> 

Re: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Flinn M. <fl...@ac...>]

Wow...I'm slow ;)

----- Original Message ----- 
From: "Markus Lorch" <ml...@vt...>
To: "'Flinn Mueller'" <fl...@ac...>; <vma...@li...>
Cc: <oma...@li...>
Sent: Tuesday, June 03, 2003 1:38 PM
Subject: RE: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr] oSpam 0.01 - a
system-wide anti-spam solution for qmail and vmailmgr with spamassassin


> see Olivier's install guidelines
> (http://omail.omnis.ch/ospam/ospam-0.01/INSTALL):
>
> 6. install mess822 and filepipe if you don't have them already:
>       http://www.nougen.com/test/filepipe.tgz
>       http://cr.yp.to/software/mess822-0.58.tar.gz
>
>
> Markus
>
> > -----Original Message-----
> > From: oma...@li...
> > [mailto:oma...@li...] On Behalf Of
> > Flinn Mueller
> > Sent: Tuesday, June 03, 2003 12:52 PM
> > To: vma...@li...; Markus Lorch
> > Cc: oma...@li...
> > Subject: Re: [vmailmgr] Re: [Omail-ospam] RE: [vmailmgr]
> > oSpam 0.01 - a system-wide anti-spam solution for qmail and
> > vmailmgr with spamassassin
> >
> >
> > 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...
> > >
> > >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: eBay
> > Get office equipment for less on eBay!
> > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> > _______________________________________________
> > Omail-ospam mailing list
> > Oma...@li...
> > https://lists.sourceforge.net/lists/listinfo/omail-ospam
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: vma...@li...
> For additional commands, e-mail: vma...@li...
>
>

Re: [Omail-ospam] oSpam 0.01 - a system-wide anti-spam solution for qmail and vmailmgr with spamassassin

[Markus L. <ml...@vt...>]

Olivier,

see my comments embedded in your message:

> 
> 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.

Yes, I figgured so much. I was just thinking that in the long run we
want to modify ifspamh and avoid running the spamc twice. I myself also
like the X-headers. So I had a closer look at the ifspamh script and
came up with
the following:
  
if you replace the exit 0 (clean message) at the very end of the script 
with the following:

     # deliver the clean message using local delivery agent
    delivery=`printf "%s\n" "$output" | $DELIVER`
    exit $?

where at the beginning of the script I set

    # NEW (Markus Lorch) setting for direct delivery of clean messages
    DELIVER="/usr/local/nospam/filepipe /usr/local/bin/vdeliver"

   
then you get the scanf headers in the delivered mail and don't need to
scan a clean 
mail again. (i've put a copy of my modified ifspamh at
http://www.lorch.net/nospam/ifspamh)

thus all that needs to be in the .qmail-ext file is:

  |/usr/local/nospam/ifspamh sp...@lo... ma...@lo...
   
and if no redirection or "trashing" is wanted, then you can use the
following (from your example):

  |/var/qmail/bin/preline -d /usr/bin/spamc -f -u sca...@om...
| /usr/local/nospam/filepipe /usr/local/bin/vdeliver
 
> 
> > 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.  

understood, I would argue against your point that the current solution
is more complex as I have more things that can go wrong and the sequence
of the action is somewhat interrupted (the change is done sometime after
the user has completed his actions)

> 
> > 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)

I am not concerned about system utilization, don't think thats an
issue.

> 
> 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...
>