Hello,
I have a question regarding vpopmail upgrades. The UPGRADE
documentation states:
When recompiling vpopmail, you need to recompile all binaries that link
into the vpopmail libraries. These include QmailAdmin, qmail-smtpd (if
you have the chkuser patch applied), Courier-IMAP etc.
I
Hello,
I have a question regarding vpopmail upgrades. The UPGRADE
documentation states:
When recompiling vpopmail, you need to recompile all binaries that link
into the vpopmail libraries. These include QmailAdmin, qmail-smtpd (if
you have the chkuser patch applied), Courier-IMAP etc.
Following up on my recent post to [vchkpw], I did some digging back into
the history of the shared libvpopmail patch and the discussions
surrounding it, and have the following thoughts.
First off, let me prefice this by saying that while I understand the
concept of shared libraries, I don't
I only recompile Qmailadmin, I run Dovecot as my imap server.
On Mon, 24 Sep 2007 08:08:16 -0600, mlist [EMAIL PROTECTED] wrote:
Hello,
I have a question regarding vpopmail upgrades. The UPGRADE
documentation states:
When recompiling vpopmail, you need to recompile all binaries that link
Joshua,
I think this is a worthwhile endeavour for many of the reasons you
discuss below, as well as one more. It makes linking applications
such as courier-authlib much easier. I recently ran into trouble with
this under NetBSD-i386. I did not know of a historical patch, I have
not been with
Also, just a supposition on my part, but if you're running (e.g.)
courier-authdaemon linked against libvpopmail.so all the time, wouldn't
that (theoretically) mean that other dynamically linked vpopmail programs
would run faster than the static version since the library would already
be loaded
On 2007-09-24, at 1008, mlist wrote:
I have a test machine that I upgraded to vpopmail 5.4.23. I
recompiled/reinstalled qmailadmin and vqadmin. I didn't recompile
courier-imap nor did I recompile qmail-smtpd.
I was able to telnet and successfully login to ports 25, 110, 143.
So, is
