similar to: dovecot.conf from problem installation

Got all the Postfix errors fixed but maybe one, so I don't think that's involved in this mix any more. I had a domain definition problem, got that sorted. The accounts' logins are correct. I tried several from the shell, and they let me in. Here's the minus-n output, not very different from the first time I posted it: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf #

Sorry for having lost the original chain of this problem. It's been a very long day. New output from 'dovecot -n output', including the contents of dovecot.conf, conf.d/10-master.conf, conf.d/10-mail.conf and conf.d/10-ssl.conf: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS ext4

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:

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

On 22.10.2019 10.33, Steve Matzura via dovecot wrote: > Sorry for having lost the original chain of this problem. It's been a > very long day. > > <snip/> > There is no user 'rock', it's just a Postfix mailbox. > You problem stems from dovecot doing user lookup using 'rock at theglobalvoice.info' which is why it breaks. So, to fix this, and

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

Yes, well, can you paste your entire dovecot.conf file then? Remember to redact passwords. Aki On 22.10.2019 12.01, Steve Matzura via dovecot wrote: > 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

On Wed, May 13, 2020 at 11:03:37AM +0300, Aki Tuomi wrote: > Edit your dovecot.conf and add > > namespace { > inbox = yes > # or use '.' here. > separator = / > } Thanks for the suggestion! I added those lines to the bottom of /etc/dovecot/dovecot.conf . However, when I attempted the mbox to maildir conversion afterwards, I still received an error, albeit a

Hi, We recently shutdown our old LDAP server and repointed our mail server (dovecot + postfix) to our new LDAP server and ever since we've been unable to fetch mail. Mail is getting delivered, but we just can't pop it. We're using Ubuntu 16.04, btw. We keep on getting the following error messages in /var/log/dovecote: 2019-05-15 16:27:43 auth: Error: LDAP

On 13. Aug 2020, at 11.29, Timo Sirainen <timo at sirainen.com> wrote: > > On 13. Aug 2020, at 11.00, Arjen de Korte <build+dovecot at de-korte.org> wrote: >> >> I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: >>

I made a special pair of keys just for Icecast with this command: $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem I combined the two files like this: $ cat cert.pem key.pem > icecast.pem I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast icecast.pem' to change owner to icecast2:icecast. I also changed its protection to

Greetings im new to the list dovecot --version 2.0.13 ubuntu 11.10 i want to use dovecot to authenticate my ldap users. My local users can authenticate and send email. Using postfix sasl/tls dovecot pam. I have read many docs/tutorials, which all have a plethora of options and information. my file structure is different than most of the documentation. I have ../etc/dovecot.conf which points

Hey guys, This patch will allow you to include different configuration files in the main dovecot.conf by using globbing [1] (like Apache for instance). !include = conf.d/*.conf !include_try = /etc/dovecot/extra* So with this you can split the dovecot.conf in different smaller configuration files. It's more the debian way to do that. But it's very handy if you have to generate

Wiley is definitely right. It would be dangerous not to have a firewall for security reasons. -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Wiley Siler Sent: Wednesday, August 10, 2005 2:27 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] Firewall will definately

Hi, I am trying to query a Sybase database on my new windows 7 machine. I am using native sybase driver "Adaptive server Enterprise" following is example code conn <- sprintf("driver=Adaptive server Enterprise;server=PHKSESMD01;database=smd_live;uid=temp_user;password=temp_pass;port=2301") chan <- odbcDriverConnect(conn) x <- sqlQuery(chan,sql,as.is=as.is)

Citeren Timo Sirainen <timo at sirainen.com>: > On 13. Aug 2020, at 11.29, Timo Sirainen <timo at sirainen.com> wrote: >> >> On 13. Aug 2020, at 11.00, Arjen de Korte >> <build+dovecot at de-korte.org> wrote: >>> >>> I allow users to run 'doveadm' for mailbox maintenance (to expunge >>> mail for instance). Since the

Hi, could I request that the example config in doc/dovecot/example-config/dovecot.conf be slightly altered to uncomment the last line? The point of include_try is that it only includes if such a file exists, and doesn't break anything if the file does not exist. My distro (Arch) has a policy not to apply non-essential patches, rather asking users to forward requests upstream, hence this

On Thu, Aug 13, 2020 at 21:16:42 +0200, Arjen de Korte wrote: > Citeren Timo Sirainen <timo at sirainen.com>: > > !include_try ssl-keys.conf > > That will only work to include an optional configuration file and > suppress errors if it doesn't exist. I put > > ssl_key = </etc/ssl/private/de-korte.org.key > > in a separate configuration file and it

Hi, sorry to post about that but I have some issues to migrate my dovecot 1.x to 2.x. I have installed dovecot 2.x package on ubuntu natty(package were generated from sources found in debian testing), and I have modified config files like that : dovecot.conf: ------------- !include_try /usr/share/dovecot/protocols.d/*.protocol listen = *, :: !include conf.d/*.conf !include_try local.conf

http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP