Here is the big problem I'm facing:
The various POP daemons (qpopper, solid-pop3d, etc.) all use the getpwnam
function to get information about the user.
My user "accounts" do not exist in the NSS/getpwnam environment. They only
exist in a list of usernames/passwords and a list of files in a directory.
Hence, I need a POP daemon which ONLY uses PAM, and can have the mail
storage directory specified.
qpopper explicitly says it needs pwnam entries in its FAQs. solid-pop3d
needs it as well although I had to browse the source code to determine this
dependency.
Any other ideas?
Many thanks,
Doug
At 01:17 AM 10/7/2001, CaT wrote:
On Sun, Oct 07, 2001 at 01:04:00AM -0400, Doug Fields wrote:
> Hello all,
>
> I've been trying to decide which POP3 server to use.
>
> My requirements include:
>
> 1) Ability to use PAM for authentication, or have a simple way of
extending
> the authentication to use a highly customized authentication scheme (for
> which I will write a PAM module)
> 2) Ability to have a special directory specified where the UNIX
> mailbox-format files reside
> 3) Uses standard UNIX mailbox-format files
qpopper is your friend I believe. I use it with SSL to have a nice
encrypted pop experience and it hasn't given me grief aswell.
major downside to it: the docs are pdf but if you can get around that
then you're sweet.
it's very configurable and has not given me grief after about 7-8 months
of use. be sure to get the latest version though (which I believe is 4.0.3).
> In the past I have used the qpopper modified for 1 and 2 above. However, I
> would like to use a more feature filled version (e.g., qpopper does not
> have UIDL support).
You mean this stuff?
X-UIDL: p0P!!&X&"!p^(#!B,n"!
