Log Analysis

Rick Cooper rcooper at DWFORD.COM
Thu Dec 8 13:36:28 GMT 2005

    [ The following text is in the "iso-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

> -----Original Message-----
> From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
> Behalf Of Steve Campbell
> Sent: Wednesday, December 07, 2005 2:49 PM
> Subject: Re: Log Analysis
> Rick,
> This particular problem to which I am referring was a typo in the
> documentation which showed the command to add the user to the database. I
> used the errant one and ended up with a different
> username/password than the
> one I entered. So I just configured the scripts to use the wrong one and
> never looked back. This was before the OLD_PASSWORD problem
> existed. But if
> I hadn't queried the database, I would have ended up like you
> describe for
> yourself, and may have just given up.
> Steve

Well I got the latest of everything and installed it and everything went
fine, except for the addition of the MailWatch Admin user. When I tried to
add that I had a column count error and I just looked at the table structure
and added ,'0','0','0','0','' to the end of the command and all was well.
MailWatch.pm came right up and started logging. As I have very
geographically dispersed servers I have a program that each one uses to
retrieve updates or new items and process and install so I have to write
install scripts that will run unattended for anything like this. It was
actually easy so I had them all up and operational in about 10 min after
writing/testing the install script.

Now I have noted one problem I have to look into, and yes I will subscribe
to the MailWatch list, but I store and forward spam and when I did a test
release of one of the spams it was really messed up with the To name missing
in the display and looking a the headers it was ugly and the apparent to
name it released to was the forwarded mailbox user name not the originally
intended recipient.

Other than that all appears to be fine. Of course if you are not familiar
with MySql that admin user problem could get you into a real trick bag.

My apologies again to anyone who was offended or thought I was disrespecting
MailWatch, that wasn't my intention. I only wanted to point out that
installation wasn't as simple as following the docs, and still isn't, but
what ever the issue with the older version of MailWatch was when it came to
connection to the database it has certainly been solved.


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki (http://wiki.mailscanner.info/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list