Re: limit sharing ability to certain users

Thanks Sami, thanks Aki I just updated the packages on our testing server and now it works like expected. There are some LDAP tests to come. Are there many productive server out there using this repository? Simeon > On 8 Aug 2018, at 09:41, Sami Ketola wrote: > > > http://repo.dovecot.org/

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

On 09-08-2018 10:05, Kenneth Porter wrote: On 8/7/2018 5:08 PM, Adi Pircalabu wrote: - Since you're on dynamic IP at home, set up a VPN tunnel using the mailserver as server and HTPC as client. OpenVPN is ubiquitous and widely supported. - rsync your mailboxes using the tunnel connection.

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

On 8/7/2018 5:08 PM, Adi Pircalabu wrote: - Since you're on dynamic IP at home, set up a VPN tunnel using the mailserver as server and HTPC as client. OpenVPN is ubiquitous and widely supported. - rsync your mailboxes using the tunnel connection. This way you can back up your entire server,

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

On Wed, 8 Aug 2018, daniel_1...@protonmail.com wrote: - rsync may not be the best option depending on the format of mailboxes. If you're using maildir or maildir+ that's fine, but what about mbox or dbox ? It depends on the situation. I can't speak for dbox, but if the mbox file is not

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

Op 07/08/2018 om 15:29 schreef Tom Sommer: 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: Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3

Hi, Op 07/08/2018 om 09:35 schreef Gabriele Nencioni: Hi all, we are upgrading our dovecot platform from: # dovecot --version 2.2.15.14 (39f57c379ded+) Great! A mummy from ancient times. That is going to make reproducing the circumstances here a bit difficult (difficult to get that

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

I really wish this was foxed. this is the only thing preventing me from using LMTP... On Tue Aug 07 2018 09:29:18 GMT-0400 (Eastern Standard Time), Tom Sommer wrote: > On 2018-08-07 13:07, Marco Giunta wrote: >> Hi, >> to get a 'Delivered-to' header based on ORCPT, I wrote a patch >> (attached)

Re: dovecot Panic: file mail-index-sync-update.c: line 1013

This has been fixed on later release. You are using very old version. ---Aki TuomiDovecot oy Original message From: Eugen I Date: 08/08/2018 15:12 (GMT+02:00) To: dovecot@dovecot.org Subject: dovecot Panic: file mail-index-sync-update.c: line 1013 An email came to several

dovecot Panic: file mail-index-sync-update.c: line 1013

An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message. As I see from the log below, there were broken index file. Then dovecot repaired that index and we got the error: Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map):

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

‐‐‐ Original Message ‐‐‐ On August 8, 2018 1:08 AM, Adi Pircalabu wrote: > - rsync may not be the best option depending on the format of mailboxes. If you're using maildir or maildir+ that's fine, but what about mbox or dbox ?

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

On 08.08.2018 10:55, Reuben Farrelly wrote: > > On 8/08/2018 5:29 pm, Thore Bödecker wrote: >> Hey, >> >> you mentioned that dovecot builds fine, but does "make check" also >> complete successfully with a glibc-2.28 build on a glibc-2.28 system? >> >> We have been seeing segfaults during "make

Error: connect(ipc-proxy) failed: Permission denied

Hello: We have got 2 directors and three backend mailbox servers. I get the following error " Error: connect(ipc-proxy) failed: Permission denied". I have read the article https://www.dovecot.org/list/dovecot/2012-August/137349.html and we have done as signaled in the two director servers with

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

On 8/08/2018 5:29 pm, Thore Bödecker wrote: Hey, you mentioned that dovecot builds fine, but does "make check" also complete successfully with a glibc-2.28 build on a glibc-2.28 system? We have been seeing segfaults during "make check" and it seems the following patch was able to make the

Re: limit sharing ability to certain users

http://repo.dovecot.org/ Sami > On 8 Aug 2018, at 10.27, Simeon Ott wrote: > > Okay, this seems to be due to the fact that the option “use_globals_only" is > supported only in v2.2.31+ > We are on Debian jessie with dovecot v2.2.13 – even an upgrade to current >

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hey, you mentioned that dovecot builds fine, but does "make check" also complete successfully with a glibc-2.28 build on a glibc-2.28 system? We have been seeing segfaults during "make check" and it seems the following patch was able to make the testsuite run successfully. Just out of

Re: limit sharing ability to certain users

Okay, this seems to be due to the fact that the option “use_globals_only" is supported only in v2.2.31+ We are on Debian jessie with dovecot v2.2.13 – even an upgrade to current stable stretch won’t help (dovecot v2.2.27). So we will wait until the packages find their way into the repository.

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Was able to find a way to get glibc-2.28 and it seems that they have changed how crypt return value behaves. I am not sure if this is intentional or not, but it appears that the return value becomes invalidated as soon as function ends. Dovecot calls crypt inside mycrypt. While in mycrypt, the

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hi, The link to the release notes seems should have an 'l' on the end: Try: https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html This with gdb: thunderstorm /usr/src/dovecot/dovecot-2.3/src/auth # gdb /root/dovecot-auth-crash/auth /root/dovecot-auth-crash/core.auth.29667 GNU gdb

Re: Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28

Hi! Thank you for the report, few points though:  - The link you provided is broken  - getting glibc-2.28 prebuilt seems to be bit problematic, and what I read from their changelog, the crypt function should work as normal. That said, it would be somewhat helpful if you could use gdb to find