Anyone know of?

I'd like to do statistical analysis on the maillog file on my openprotect
server.  I'd like to show a graph of total e-mail scanned, how many viruses
were found and how many spam messages were flagged.

I'm newer to Linux so I have no idea how to code anything like this (not a
programmer at all).

I love Openprotect!

Thanks.

C. Scott Heisler


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, March 01, 2004 10:07 PM
To: [EMAIL PROTECTED]
Subject: Opencomputing-openprotect digest, Vol 1 #23 - 6 msgs


Send Opencomputing-openprotect mailing list submissions to
        [EMAIL PROTECTED]

To subscribe or unsubscribe via the World Wide Web, visit
        
https://lists.sourceforge.net/lists/listinfo/opencomputing-openprotect

or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Opencomputing-openprotect digest..."


Today's Topics:

   1. $HOME/.spamassassin/user_prefs (Ruairi Newman)
   2. Re: $HOME/.spamassassin/user_prefs (KM Ganesh)
   3. Re: $HOME/.spamassassin/user_prefs (Ruairi Newman)
   4. Re: $HOME/.spamassassin/user_prefs (KM Ganesh)
   5. Re: $HOME/.spamassassin/user_prefs (Ruairi Newman)
   6. Re: $HOME/.spamassassin/user_prefs (KM Ganesh)

--__--__--

Message: 1
From: Ruairi Newman <[EMAIL PROTECTED]>
To: Openprotect <[EMAIL PROTECTED]>
Date: Mon, 01 Mar 2004 08:45:18 +0300
Subject: [Opencomputing-openprotect] $HOME/.spamassassin/user_prefs


Hi all,

This is my first time posting to the list, so I hope you'll bear with me
as I ask what I presume is a common question (thought I can find no
reference to it in the archives).

The question, as you may have guessed from the subject line, is can I
give all users their own personal user_prefs file for Spamassassin,
located in their respective homedirs, or does Openprotect have to use a
system-wide configuration?

Kind Regards,

Ruair� Newman


-- 
"An email worm is, is a computer virus and a computer virus is a program
 that runs like Microsoft Word on your computer..."
        -- William Campbell, BUA Training on RTE Radio



--__--__--

Message: 2
Date: Mon, 01 Mar 2004 13:04:21 +0530
From: KM Ganesh <[EMAIL PROTECTED]>
Reply-To:  [EMAIL PROTECTED]
Organization: Opencomputing Technologies
To: Ruairi Newman <[EMAIL PROTECTED]>
CC: Openprotect <[EMAIL PROTECTED]>
Subject: Re: [Opencomputing-openprotect] $HOME/.spamassassin/user_prefs

Dear Ruairi Newman,

> This is my first time posting to the list, so I hope you'll bear with me
> as I ask what I presume is a common question (thought I can find no
> reference to it in the archives).
> 
> The question, as you may have guessed from the subject line, is can I
> give all users their own personal user_prefs file for Spamassassin,
> located in their respective homedirs, or does Openprotect have to use a
> system-wide configuration?

The per-user files (bayes, auto-whitelist, user_prefs) are looked for in 
  SpamAssassin User State Dir (/etc/MailScanner/MailScaner.conf) and in 
~/.spamassassin/.

cheers,
Ganesh, KM.
-- 
K.M.Ganesh | Mobile: +91 (0) 9444080290
Opencomputing Technologies | http://opencompt.com
Server Side E-Mail Protection.


--__--__--

Message: 3
Subject: Re: [Opencomputing-openprotect] $HOME/.spamassassin/user_prefs
From: Ruairi Newman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: Openprotect <[EMAIL PROTECTED]>
Date: Mon, 01 Mar 2004 13:05:10 +0300

On Mon, 2004-03-01 at 10:34, KM Ganesh wrote:

> > The question, as you may have guessed from the subject line, is can I
> > give all users their own personal user_prefs file for Spamassassin,
> > located in their respective homedirs, or does Openprotect have to use a
> > system-wide configuration?
> 
> The per-user files (bayes, auto-whitelist, user_prefs) are looked for in 
>   SpamAssassin User State Dir (/etc/MailScanner/MailScaner.conf) and in 
> ~/.spamassassin/.

Thanks for the prompt response.

That's what I thought, but it seems to be ignoring the user_prefs files
in my users ~/.spamassassin/ directories.  Any idea why it would be
doing this?

Regards,

Ruair�

-- 
"An email worm is, is a computer virus and a computer virus is a program
 that runs like Microsoft Word on your computer..."
        -- William Campbell, BUA Training on RTE Radio



--__--__--

Message: 4
Date: Mon, 01 Mar 2004 17:30:51 +0530
From: KM Ganesh <[EMAIL PROTECTED]>
Reply-To:  [EMAIL PROTECTED]
Organization: Opencomputing Technologies
To: Ruairi Newman <[EMAIL PROTECTED]>
CC: Openprotect <[EMAIL PROTECTED]>
Subject: Re: [Opencomputing-openprotect] $HOME/.spamassassin/user_prefs

Dear Ruairi Newman,

>>The per-user files (bayes, auto-whitelist, user_prefs) are looked for in 
>>  SpamAssassin User State Dir (/etc/MailScanner/MailScaner.conf) and in 
>>~/.spamassassin/.

well, my mistake, actually the user-prefs file in ~/.spamassassin is not 
used when running SA... it's replaced by 
/etc/MailScanner/spam.assassin.prefs.conf.

cheers,
Ganesh, KM.
-- 
K.M.Ganesh | Mobile: +91 (0) 9444080290
Opencomputing Technologies | http://opencompt.com
Server Side E-Mail Protection.


--__--__--

Message: 5
Subject: Re: [Opencomputing-openprotect] $HOME/.spamassassin/user_prefs
From: Ruairi Newman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: Openprotect <[EMAIL PROTECTED]>
Date: Mon, 01 Mar 2004 15:06:11 +0300

On Mon, 2004-03-01 at 15:00, KM Ganesh wrote:

> well, my mistake, actually the user-prefs file in ~/.spamassassin is not 
> used when running SA... it's replaced by 
> /etc/MailScanner/spam.assassin.prefs.conf.

That's what I was afraid of.  There's no way - other than a separate
independent install of spamassassin - to control the Spamassassin
threshold on a per user basis?  And add per user whitelists?

Regards,

Ruair�


-- 
"An email worm is, is a computer virus and a computer virus is a program
 that runs like Microsoft Word on your computer..."
        -- William Campbell, BUA Training on RTE Radio



--__--__--

Message: 6
Date: Mon, 01 Mar 2004 18:00:53 +0530
From: KM Ganesh <[EMAIL PROTECTED]>
Reply-To:  [EMAIL PROTECTED]
Organization: Opencomputing Technologies
To: Ruairi Newman <[EMAIL PROTECTED]>
CC: Openprotect <[EMAIL PROTECTED]>
Subject: Re: [Opencomputing-openprotect] $HOME/.spamassassin/user_prefs

Dear Ruairi Newman,

> That's what I was afraid of.  There's no way - other than a separate
> independent install of spamassassin - to control the Spamassassin
> threshold on a per user basis?  And add per user whitelists?

Some Clarifications about Spamassassin Calling from MailScanner:

MailScanner calls the function library Mail::Spamassassin directly from 
Perl, gives the message directly to the function library, and gets the 
results straight back from it.

SA user_prefs files in individual people's home directories are not 
consulted by MailScanner, as it doesn't know where the mail is going or 
how to map an email address onto a user's home dir. You can only do that 
for local email accounts and even then only at the delivery stage, which 
means MailScanner would have to be involved in mail delivery.

~/.spamassassin is consulted only for restricted values of ~. 
Specifically, ~ here refers to the home directory of the mail user 
(users like root, mail, smmsp, postfix, qmailq ...etc). ~ does not refer 
to each user on the machine.

SpamAssassin User State Dir
This is the directory where SpamAssassin should store its state 
information for things like the Bayes database. It avoids having them 
pile up somewhere unhelpful such as /root or /home/smmsp. Note that only 
one directory can be specified, therefore it does not apply for each 
user on the system; there is only one setting.

hope that helps,
cheers,
Ganesh, KM.
-- 
K.M.Ganesh | Mobile: +91 (0) 9444080290
Opencomputing Technologies | http://opencompt.com
Server Side E-Mail Protection.



--__--__--

_______________________________________________
Opencomputing-openprotect mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opencomputing-openprotect


End of Opencomputing-openprotect Digest




Reply via email to