Re: rawlog

Sigh ... one issue was misconfig kinda forgot to add the script into imap service .. the other is I thought I had updated the dovecot package but that was on another instance to rawlog_dir wouldnt have been in that version. Rats .. its a shame there is not auto create though mis-read that one.

Re: rawlog

Matt Bryant wrote: 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 ... service postlogin { executable = script-login -d rawlog unix_listener postlogin { group = atmail mode =

Re: Doveadm-sync SSH practicalities

Terry Jones wrote: The documentation is somewhat silent on this subject. If you mean https://wiki.dovecot.org/Tools/Doveadm/Sync the answers seem implicit to what's been stated. What permissions does the SSH user need ? To be able to run the doveadm executable (or a wrapper script that

Re: rawlog

> On August 3, 2017 at 8:57 PM Alexander Dalloz wrote: > > > Am 03.08.2017 um 01:04 schrieb Matt Bryant: > > Hi, > > > > Trying to get rawlog working on dovecot 2.2.31 configured as per > > > > https://wiki2.dovecot.org/Debugging/Rawlog > > > > but > > > > a) it doesnt

Re: rawlog

Am 03.08.2017 um 01:04 schrieb Matt Bryant: 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

Re: proxy-dict with tcp connection

> On August 3, 2017 at 2:10 PM Ralf Becker wrote: > > > I try to create a patch to allow (proxy-)dict to use tcp connections > instead of a unix domain socket. > > I'm replacing connection_init_client_unix with connection_init_client_ip: > > ---

Re: pam auth problem

>> # cat /etc/pam.d/dovecot >> passdb { >> driver = pam >> # args = failure_show_msg=yes >> # args = max_requests=12 >> args = %s >> } > > this info belongs into Dovecot's conf files, not into /etc/pam.d. doh. i misread the wiki page. thanks. > copy or link /etc/pam.d/imap do

Re: pam auth problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 3 Aug 2017, Randy Bush wrote: # cat /etc/pam.d/dovecot passdb { driver = pam # args = failure_show_msg=yes # args = max_requests=12 args = %s } this info belongs into Dovecot's conf files, not into /etc/pam.d. and

Re: pam auth problem

> do you have a /etc/pam.d/dovecot file, does it define all necessary > settings? probably not, as i do not know what the necessary ones are :) i did as best i could using https://wiki.dovecot.org/PasswordDatabase/PAM as guidance randy

Re: pam auth problem

> What is in the pam.d/dovecot file? (Remember to strip passwords if > included) # cat /etc/pam.d/dovecot passdb { driver = pam # args = failure_show_msg=yes # args = max_requests=12 args = %s } and /etc/pam.d/{imap,pop3} were untouched; both as follows # # $FreeBSD:

Re: pam auth problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 3 Aug 2017, Randy Bush wrote: Date: Thu, 03 Aug 2017 22:08:22 +0900 From: Randy Bush To: Remko Lodder Cc: Christian Kivalo , dovecot@dovecot.org Subject: Re: pam auth problem auth:

Re: pam auth problem

What is in the pam.d/dovecot file? (Remember to strip passwords if included) Cheers, Remko Lodder /* sent from my phone and thus brief and to the point *\ Op 3 aug. 2017 om 15:08 heeft Randy Bush het volgende geschreven: >>> auth: in openpam_parse_chain():

Re: Auth Policy Server/wforce/weakforced

On 02.08.2017 23:35, Daniel Miller wrote: > 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

Re: pam auth problem

>> auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid >> facility > > I do not think that it has something to do with the dovecot settings > itself but perhaps with the pam facility settings instead? i can believe that. any clues to debug? randy

proxy-dict with tcp connection

I try to create a patch to allow (proxy-)dict to use tcp connections instead of a unix domain socket. I'm replacing connection_init_client_unix with connection_init_client_ip: --- ./src/lib-dict/dict-client.c.orig +++ ./src/lib-dict/dict-client.c @@ -721,6 +721,10 @@ client_dict_init(struct dict

Replication and public folders with private (seen) flags

We started using Dovecot replication between two nodes and noticed that our configured private flags (INDEXPVT) in public/shared mailboxes are not replicated. We are only replicating INBOX namespace, as we dont want to replicate content of shared mailboxes for every user again. Is there a way to

Re: pam auth problem

Hi Randy, > On 3 Aug 2017, at 08:50, Randy Bush wrote: > > auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid > facility I do not think that it has something to do with the dovecot settings itself but perhaps with the pam facility settings instead?

Re: pam auth problem

>> 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

Re: pam auth problem

>passdb { > driver = pam >} >passdb { > driver = pam > name = pam >} Are those two passdb blocks intentional? One of them is missing the name parameter. -- Christian Kivalo

pam auth problem

# 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