Hello,
I am currently trying to setup my chkuer 2.0.8 to log to syslog.
Currently all of the information is coming out on /dev/console.
I currently have the following setup
#define CHKUSER_ENABLE_LOGGING
/*
* Uncomment to enable logging of good rcpts
* valid only if CHKUSER_ENABLE_LOGGING is
tonix (Antonio Nati) wrote:
At 17.59 17/05/2005, you wrote:
On Tuesday 17 May 2005 11:47 am, tonix (Antonio Nati) wrote:
Hi Jimmy,
this does not look as a chkuser problem, but as a general qmail
problem (as
chkuser uses same logging routines of qmail). chkuser log goes whenever
qmail logs
Thanks that worked really well!
tonix (Antonio Nati) wrote:
At 08.52 18/05/2005, you wrote:
tonix (Antonio Nati) wrote:
At 17.59 17/05/2005, you wrote:
On Tuesday 17 May 2005 11:47 am, tonix (Antonio Nati) wrote:
Hi Jimmy,
this does not look as a chkuser problem, but as a general qmail
problem
tonix (Antonio Nati) wrote:
At 08.52 18/05/2005, you wrote:
tonix (Antonio Nati) wrote:
At 17.59 17/05/2005, you wrote:
On Tuesday 17 May 2005 11:47 am, tonix (Antonio Nati) wrote:
Hi Jimmy,
this does not look as a chkuser problem, but as a general qmail
problem (as
chkuser uses same logging
tonix (Antonio Nati) wrote:
At 10.48 18/05/2005, you wrote:
I currently have no problems with email logging. I have also got the
rblsmtpd syslogd patch working its only the chkuser stuff that does
not end up in syslog.
This is my configuration for qmail-smtpd. It logs everything (chkuser
Hello,
I am currently running a fairly busy email server with around 30 domains
and several hundred high usage users sending and receiving email. I have
currently setup the system so that It is running without any virus
scanning. Its setup something like this
rblsmtpd -- qmail -- .qmail file
Hello,
I am managing a group of servers that is running Redhat Enterprise Linux
v3. The Issue that I have just discovered is that we have now over 32000
users. Thats causing a problem as ext3 file system does not support more
than 32000 folders in any one particular folder.
Is there any way to
Hello,
It appears that the server has not created the users in a hash format.
Is there any way to convert the format to a hash easily?
Regards,
Jimmy
Rick Macdougall wrote:
Jimmy Stewpot wrote:
Hello,
I am managing a group of servers that is running Redhat Enterprise Linux
v3. The Issue
Rick Macdougall wrote:
Jimmy Stewpot wrote:
Hello,
It appears that the server has not created the users in a hash format.
Is there any way to convert the format to a hash easily?
Hi,
Not without deleting and re-adding all the users I think. Do you know
how vpopmail
Hi,
I've done it a few times (sendmail to vpopmail, 30K+ users) with scripts
etc to create the new users using the vpopmail tools, then again using
scripts to get their Maildir directories from vpopmail and then moving
the mail over.
I've never just moved over an existing mail store
There are a few different ways to do it depending on your backend, if
you are using MySQL, then you can just update the mysql database with
the user and password, leaving the maildir directory blank and it will
automatically be updated when you pop into the account or sendmail to
the account
Rick Macdougall wrote:
Jimmy Stewpot wrote:
I have just written a script that would do a mysql update query to
md5('password'); into the mysql database. However the problem appears to
be that the passwords set by the vpasswd utility dont appear to be md5
in the same way that the mysql
Hi,
$encpass = crypt('password','$1$salthere$');
Where does vpopmail keep the salt or how does that work in regards to
the vpasswd utility etc?
See http://ca.php.net/manual/en/function.crypt.php
Regards,
Rick
Rick Macdougall wrote:
Jimmy Stewpot wrote:
Hello,
I have got a system now working brilliantly after some issues with
massive mail stores. (see the Massive folders thread for more
information and thanks to everyone that helped me with that one).
I have an issue now where I am creating
Hello,
I have a server that is setup as having vpopmail installed to run all of
the emails without having system accounts. I have got users on the
system that have cronjobs running. If those users have a crontab that
runs and has an error it will email [EMAIL PROTECTED] the hostname of the
15 matches
Mail list logo
