Fwd: maildrop and qmail with virtual users, a howto. Also, please help with setting up sqlite3
-------- Beginning of forwarded message --------
> Robert Johnson writes:
>> Authenticated: [hidden email] (uid 1000, gid 1000)
>> Home Directory: /home/user/vusers/test
>> Maildir: (none)
>> Quota: (none)
>> Encrypted Password:
>> Cleartext Password: pass
>> Options: (none)
>> domain1.com exists (as a different, functional domain), as does the
>> directory /home/user/vusers/test/Maildir and its three subdirs, cur, new,
>> and tmp).
>> /etc/courier/authdaemonrc is set at defaults with the following,
>> authmodulelist="authuserdb authpwd authpgsql authldap authmysql authsqlite
>> authsqliterc also is still set at defaults.
>> When I try to login via sqwebmail, I see
>> "invalid user id or password"
>> tail /var/log/maillog shows
>> sqwebmaild: LOGIN FAILED, user=[hidden email], ip=[192.168.1.100]
>> Why would authtest succeed but sqwebmail fail to login? What can I do to
>> make sqwebmail work with sqlite?
> The only thing I can think of is that sqwebmail is different installation of
> courier-authlib on the same box, and sqwebmail is compiled to point to the
> wrong one.
Certainly seems likely. I have installed packages from OpenBSD6.0:
but, as suggested in the list above, I installed sqwebmail-5.8.3 from source.
Which packages would you suggest I compile from source?
Both courier-authlib- packages? Just one? And what about the courier-unicode and courier-utils-?
And how about maildrop?
> Certainly seems likely. I have installed packages from OpenBSD6.0:
> but, as suggested in the list above, I installed sqwebmail-5.8.3 from source.
> Which packages would you suggest I compile from source?
> Both courier-authlib- packages? Just one? And what about the courier-unicode
> and courier-utils-?
> And how about maildrop?
This is not about picking which packages to install from source.
It's about installing a correctly-configured package. If you have all the
packages you need already prebuilt, that's the best option.
For example, you might have a pre-built courier-authlib package that's been
set up with some non-default options which are customized for your platform.
By default, manually-compiled software typically gets configured and
installed in /usr/local/bin (with some exceptions, check INSTALL for
details); but a pre-built package for your platform might explicitly
configure and set it up like other system packages, in /usr/bin.
But then, another copy of the same add-on software package goes into
/usr/local, and now you have two copies installed. Then another add-on
software with the dependency on the first one gets installed, and it sets
itself up to be dependent on the installation in /usr/local, however it's
the system package that's installed in /usr is the one that's actually used.
Something along those lines is probably the case with you. I can't really
tell you what you should or should not install, and how. Only you can figure
out what you have installed, and how. My rule of thumb is to recommend
always using the system platform's native software package management tools
to install software packages. That's what its job is, which includes
managing all dependencies.
If you need a newer version of a software package, use your software package
management tool to create one, from the newer source package, and then