Maybe I am challenged today - I don't know.  I extracted the files in my
directory.

Then:
[r...@mail spamdyke]# chmod +x /etc/spamdyke/spamdyke-stats

Since my Spamdyke logs are in /var/log/qmail/smtp/ I sent this command:
[r...@mail spamdyke]# cat /var/log/qmail/smtp/current | egrep -i -e "(^Feb
23 )" | /etc/spamdyke/spamdyke-stats

I get this in return:

[r...@mail spamdyke]# cat /var/log/qmail/smtp/current | egrep -i -e "(^Feb
23 )" | /etc/spamdyke/spamdyke-stats
Missing right curly or square bracket at /etc/spamdyke/spamdyke-stats line
185, at end of line
syntax error at /etc/spamdyke/spamdyke-stats line 185, at EOF
Execution of /etc/spamdyke/spamdyke-stats aborted due to compilation
errors (#1)
    (F) The lexer counted more opening curly or square brackets than closing
    ones.  As a general rule, you'll find it's missing near the place you
    were last editing.

Uncaught exception from user code:
        Missing right curly or square bracket at
/etc/spamdyke/spamdyke-stats line 185, at end of line
syntax error at /etc/spamdyke/spamdyke-stats line 185, at EOF
Execution of /etc/spamdyke/spamdyke-stats aborted due to compilation errors.
 at /etc/spamdyke/spamdyke-stats line 185


What did I do to it???

Jack

> MagicWISP Sales wrote:
>> I'm also looking for a good Spamdyke Statistics script.  I know this
>> isn't
>> their list, but all of the scripts on their list fail.  I read many QMT
>> users that said they didn't work.  I am using QTP on CentOS 5.
>> Hopefully
>> somebody will have an idea on where I can find one.
>>
> I've attached a script I use to get stats out of Spamdyke:
>
> spamdyke-stats
>
> This is a statistics generator.  I found it on the spamdyke-users
> mailing list.  It seemed to have some bugs so I tried to fix those and
> otherwise tweaked it a bit.  I'm not entirely sure that it's accurate
> yet so I haven't contributed it back to spamdyke-users yet.
>
> It generates Spamdyke stats from whatever you feed it on stdin, so if
> your Spamdyke is logging to /var/log/maillog you can use it like this:
>
> cat /var/log/maillog | spamdyke-stats
>
>
> It doesn't differentiate based on date, so you'll have to figure that
> out yourself.  I do it like this:
>
> cat /var/log/maillog | egrep -i -e "(^Feb 22 )" | spamdyke-stats
>
>
> Actually, I use a wrapper script and a crontab entry to run it daily and
> send me a report.  I've included my wrapper script:
>
> Spamdyke-Stats-Report.sh
>
>
> This script runs spamdyke-stats against recent maillog files using
> yesterday's date and emails a report containing the stats to a specified
> email address.
>
> I place these scripts in a directory with a 'tmp' subdirectory to
> contain temporary data generated by the scripts.
>
> I call the scripts using a crontab entry like this:
>
>   00  1  *  *  *  root  /usr/share/qmt/scripts/Spamdyke-Stats-Report.sh
> 2>&1 > /dev/null
>
>
> HTH
>
>
> Brent Gardner
>
>
> ---------------------------------------------------------------------------------
> Qmailtoaster is sponsored by Vickers Consulting Group
> (www.vickersconsulting.com)
>     Vickers Consulting Group offers Qmailtoaster support and
> installations.
>       If you need professional help with your setup, contact them today!
> ---------------------------------------------------------------------------------
>      Please visit qmailtoaster.com for the latest news, updates, and
> packages.
>
>       To unsubscribe, e-mail:
> [email protected]
>      For additional commands, e-mail:
> [email protected]
>



---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: [email protected]
     For additional commands, e-mail: [email protected]


Reply via email to