thanks to everyone for the insights. while i still think it's kind of
'ugly' to have to replicate a portion of the vpopmail directory structure
on my MXes, i suppose the benefits will surely outweigh the 'ugliness'.
At 03:07 PM 2/14/2005, you wrote:
We are doing exactly this with our gateway MX server. First we replicate
the MySQL database then we use rsync running every 30 minutes to just sync
the first couple of directory levels from
the /home/vpopmail/domains/x/domain.com on the vpopmail server (this
picks up the aliases, mailing lists and autoresponder names) and the
/var/qmail/users/assign file. chkuser works perfectly at the MX server.
SMTPROUTES sends everything to the vpop server. We do virus filtering and
spam analysis on the MX server and the balance on the pop server.
Basically, we just sync enough over to the MX server so chkuser can work.
At 03:00 PM 2/14/2005, you wrote:
Paul Theodoropoulos wrote:
> is there any way to run chkusr on these 'gateway' MX servers? i use
> MySQL authentication. The mysql server is the pop server, and i
> replicate that on the primary MX (where the majority of mail comes
> in). is there any way to 'hook' into the authentication info in the
> replicated database directly?
> that woudl be ideal, as it should be quite fast.
This isn't possible with the current version of chkuser. I'm wanting to do
the exact same thing. Vpopmail currently needs access to 1) the
authentication scheme (MySQL in your case) 2) the file system (to check the
~qmail/control files and .qmail- files for aliases and catchalls)
Also, keep in mind that you can set up vpopmail/chkuser to check against the
primary MySQL database. There is no need to replicate it.
I've been told that the Antonio wants to build client/server functionality
into chkuser but hasn't been able to find the time. I for one look forward
to seeing it.
Jeff Koch, Intersessions