Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hi, Dovecot 2.3 (release and current -git) versions compile, but fail to run when compiled against glibc-2.28. This is what is logged on startup: Aug 8 08:24:39 thunderstorm.reub.net dovecot[569]: master: Dovecot v2.3.2.1 (0719df592) starting up for imap, lmtp, sieve, submission, sieve Aug

Re: Best practices for backing up small mailserver to remote location

On 08-08-2018 7:48, Ian Evans wrote: My webserver also houses our mailserver. There's about six users on that mail system and I'm thinking it would be good to back up the mailboxes to my always on HTPC computer at home, which is reachable via a dynamic IP service. I know (or think) I need to

Best practices for backing up small mailserver to remote location

My webserver also houses our mailserver. There's about six users on that mail system and I'm thinking it would be good to back up the mailboxes to my always on HTPC computer at home, which is reachable via a dynamic IP service. I know (or think) I need to use doveadm-backup for this but rather

Re: Set X-Original-To based an ORCPT?

On 2018-08-07 13:07, Marco Giunta wrote: Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command

Re: Set X-Original-To based an ORCPT?

Hi, to get a 'Delivered-to' header based on ORCPT, I wrote a patch (attached) to force Dovecot lmtp to advertise DSN after a LHLO command. In this way, Postfix add an ORCPT to the RCTP command (http://postfix.1071664.n5.nabble.com/pipe-flags-vs-lmtp-td11587.html#a11596). Be carefully: in this way

Re: limit sharing ability to certain users

still the same… root@buserver:/etc/dovecot# doveadm user te...@onnet.ch field valueuserdb lookup: user te...@onnet.ch doesn't exist relevant config output from doveconf -n userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap result_success = continue-ok } userdb { args =

Re: limit sharing ability to certain users

Hmm. if you put it *after* the ldap userdb, it should not have prevented users from logging in. What happens if you do userdb {   driver = passwd-file   args =   skip = notfound   result_failure = continue-ok } Aki On 07.08.2018 12:58, Simeon Ott wrote: > Now the attributes are correctly

Re: limit sharing ability to certain users

Now the attributes are correctly read for the user t...@onnet.ch , but other users are not able to authenticate anymore. root@buserver:/var/spool/postfix/virtual/onnet.ch/test/Maildir/.super# doveadm user t...@onnet.ch field value uid 5000 gid 5000 home

Re: Set X-Original-To based an ORCPT?

On 2015-09-02 22:01, Peer Heinlein wrote: Since http://dovecot.org/pipermail/dovecot-cvs/2014-November/025241.html Dovecot's LMTP does support ORCPT. Is it possible to set X-Original-To-Header based on that ORCPT? Any news or response on this? I too am in need of this header being passed

Re: limit sharing ability to certain users

… attached the dovecot -n, linked files, debug log lines during a standard client login root@buserver:/etc/dovecot/conf.d# doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-6-amd64 x86_64 Debian 8.11 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login

Re: limit sharing ability to certain users

Ah. You probably need to change ldap userdb so that you add userdb { driver = ldap   args = /etc/dovecot/dovecot-ldap.conf result_success = continue-ok } so that the next one is processed. you can use 'doveadm user t...@onnet.ch' to verify that the attributes are read for this user, and

Re: limit sharing ability to certain users

Can you provide your doveconf -n after adding the database *after* LDAP. You probably need to add 'noauthenticate' as one parameter after the userdb ones. Aki On 07.08.2018 11:05, Simeon Ott wrote: > May you please clarify that? Where should I omit the userdb_ prefix? Which of > my attempts

Re: limit sharing ability to certain users

May you please clarify that? Where should I omit the userdb_ prefix? Which of my attempts are you pointing at? As stated, I omitted the userdb_ prefix when working with an LDAP attribute. > On 7 Aug 2018, at 10:03, Aki Tuomi wrote: > > with ldap userdb, you need to omit the userdb_ prefix. >

Re: limit sharing ability to certain users

with ldap userdb, you need to omit the userdb_ prefix. Aki On 07.08.2018 10:54, Simeon Ott wrote: > Sorry for that! I was offline during writing my answer to your mail and so it > left my outbox after the advice from Sami. > > The solution works well when using passwd userdbs only. I didn’t

Re: limit sharing ability to certain users

Sorry for that! I was offline during writing my answer to your mail and so it left my outbox after the advice from Sami. The solution works well when using passwd userdbs only. I didn’t get it running in conjunction with ldap userdb. I tried to use an LDAP attribute and mapping it to

Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3

Hi all, we are upgrading our dovecot platform from: # dovecot --version 2.2.15.14 (39f57c379ded+) to # dovecot --version 2.3.2.1 (0719df592) Our platform is debian based and it is configured as director and backend proxy. We have just upgrade only 4 servers (2 directors and 2 backends) and

Re: limit sharing ability to certain users

As Sami pointed out, I had wrong syntax: > close, but few typos. userdb should be: > > userdb { >   driver = passwd-file >   args = username_format=%Lu /etc/dovecot/share.passwd > } > > Sami On 06.08.2018 22:52, Simeon Ott wrote: > Thanks for the advice Aki > >> On 6 Aug 2018, at 07:26, Aki