More on problems with new install

Steve Matzura number6 at noisynotes.com
Tue Oct 22 12:01:40 EEST 2019


It was the three passdb blocks you sent me.


On 10/22/2019 4:43 AM, Aki Tuomi via dovecot wrote:
> Can you show what you ended up pasting?
>
> Aki
>
> On 22.10.2019 11.34, Steve Matzura via dovecot wrote:
>> I pasted that block at the end of dovecot.conf, restarted, and got the
>> following in syslog:
>>
>> Oct 22 08:24:32 tgvprod dovecot[7290]: doveconf: Fatal: Error in
>> configuration file /etc/dovecot/dovecot.conf line 106: Expecting '{'
>> Oct 22 08:24:32 tgvprod systemd[1]: dovecot.service: Main process
>> exited, code=exited, status=89/n/a
>> Oct 22 08:24:32 tgvprod systemd[1]: dovecot.service: Failed with
>> result 'exit-code'.
>>
>> On 10/22/2019 4:00 AM, Aki Tuomi via dovecot wrote:
>> block quote
>> On 22.10.2019 10.33, Steve Matzura via dovecot wrote:
>> block quote
>> Sorry for having lost the original chain of this problem. It's been a
>> very long day.
>>
>> block quote end
>> <snip/>
>>
>> block quote
>> There is no user 'rock', it's just a Postfix mailbox.
>> block quote end
>> You problem stems from dovecot doing user lookup using
>> 'rock at theglobalvoice.info'
>> which is why it breaks.
>>
>> So, to fix this, and retain what you have configured you need to do bit
>> silly config (this is hopefully getting fixed in 2.3 series at some
>> point).
>>
>> passdb {
>>      driver = static
>>      args = noauthenticate temp_user=%u user=%Ln
>> }
>>
>> passdb {
>>      driver  = pam
>> }
>>
>> passdb {
>>      driver = static
>>      args = noautenticate user=%{passdb:temp_user}
>>      skip = unauthenticated
>> }
>>
>> Aki
>> block quote end
>>


More information about the dovecot mailing list