Problem is, it says in the docs that the db2 portion has to be there to
support virtual pop servers. This is one of the main reasons we are
moving to cucipop. That, and the disk IO issue, which cucipop is
supposedly better at that qpopper.
But, you are right, it compiles easily without the db2 portion... Any way
we could have vpop servers without the db2? Any other popper we should
look at that is good on disk IO as well?
Then, configuring exim to do virtual pop server's is another issue,
because we will have to have different mail spool for each one, as well as
seperate password file for authenticating the pop3 into those spools.
Then, permissions will be in issue... Reason we need v-pop servers is
that we have multiple ISP that we bought out, and want to combine on one
box, but don't want customers to have to change their username. Figured
that v-pop server would be a good solution...
Sincerely,
Richard G. Duvall
On Fri, 22 Oct 1999, Joel Rowbottom wrote:
> "Richard G. Duvall" wrote:
>
> > Too bad cuci.nl doesn't have a mailing list! Probably a good *obvious*
> > reason for it too!
>
> Cuci is absolutely mad - in the end I rewrote a substantial portion of it rather than try and fix it up for
> our own OS (Slackware Linux 4, kernel 2.2.12, about 7,500 users). Runs almost like a dream now, but tends to
> leave zombie exim processes lying around (haven't worked out why it's doing that yet).
>
> Taking out the DB2 portion of it went a substantial way to fixing things.
>
>
>
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
