>> passdb {
>> driver = pam
>> }
>> passdb {
>> driver = pam
>> name = pam
>> }
> Are those two passdb blocks intentional?
>
> One of them is missing the name parameter.
doh. first removed.
Aug 3 06:49:23 psg auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1):
missing or invalid faci
>passdb {
> driver = pam
>}
>passdb {
> driver = pam
> name = pam
>}
Are those two passdb blocks intentional?
One of them is missing the name parameter.
--
Christian Kivalo
# dovecot --version
2.2.31 (65cde28)
on freebsd 64 10.3
system converted to dovecot 2 against my will and consuming a lot of
time sorting it out. i am glad google does not charge. have spent
two hours on this one alone; and undoubtedly it is my st00pidity. so
excuse my desperate posting to lazy
Hi,
Trying to get rawlog working on dovecot 2.2.31 configured as per
https://wiki2.dovecot.org/Debugging/Rawlog
but
a) it doesnt appear to be loggin anything
b) rawlog_dir which is supposed to be v2.2.26+ seems no where in site ..
in fact complains about unknown variable
So does rawlog still d
Is there explicit documentation available for the (probably trivial)
configuration needed for Dovecot and Wforce? I'm probably missing
something that should be perfectly obvious...
Wforce appears to start without errors. I added a file to dovecot's conf.d:
95-policy.conf:
auth_policy_server_
Hi,
The documentation is somewhat silent on this subject.
What permissions does the SSH user need ? How associated does it need
to be with things like dovecot directory ownership etc ?
Obviously my dovecot daemon processes are running as restricted users
with "nologin" shells etc., and I don't
Thank you for your reply.
> > Result of uid sort by subject is not expected.
> > for example: Japanese => English => Japanese => English
>
> you don't mean those 4 words, but phrases in these languages, right?
In my case, sorting result is something strange.
Miss-sorted subjects were as bellow
