Re: dsync for subscription on public/shared folder

Hello, since nobody replied to this issue it might be a bug. Until bug reports are also going to this mailing list, I would like to tell this is a bug for me. I will add the dovecot -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux

Re: Auth-policy: auth_policy_server_url and https support

> On January 6, 2017 at 11:03 PM gr...@olypensupport.com wrote: > > > When using Auth policy server it doesn’t currently doesn’t support https. > > In version 2.2.27: > Policy server HTTP error: 9002 Couldn't initialize SSL context: Can't > verify remote server certs without trusted CAs

Re: .dovecot.sieve location issue

On Sunday 08 January 2017 18:14:20 Jibeji wrote: @other_domain.com"; > >> > >> > >> Here are the logs: > >> > >> dovecot: lda(u...@domain.com): Debug: sieve: Pigeonhole version 0.4.2 > >> initializing > >> lda(u...@domain.com): Debug: sieve: include: sieve_global_dir is not set; > >> it is

Re: .dovecot.sieve location issue

Hello, Here it is: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.14.32--grs-ipv6-64 x86_64 first_valid_gid = 5000 first_valid_uid = 5000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_access_groups = vmail mail_location = /home/mail/%d/%n mail_privileged_group = vmail

Re: Dovecot Selinux Setting

Am 08.01.2017 um 18:04 schrieb Günther J. Niederwimmer: Hello, can any tell me the correct selinux Settings for the Maildir Setting ? in the Moment I have this setting Jan 8 15:04:52 2017 from 192.168.100.100 [root@mx03 ~]# ls -Z /srv/vmail drwx--. vmail vmail

Re: .dovecot.sieve location issue

Am 08.01.2017 um 17:31 schrieb Jibeji: Hello, I am trying to set sieve up on a Centos 7 server. It's a configuration with postfix, Maildir, MySQL and virtual domains which works fine. I have created a simple .dovecot.sieve in the user's directory: # cat

Dovecot Selinux Setting

Hello, can any tell me the correct selinux Settings for the Maildir Setting ? in the Moment I have this setting Jan 8 15:04:52 2017 from 192.168.100.100 [root@mx03 ~]# ls -Z /srv/vmail drwx--. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 example.com drwx--. vmail vmail

.dovecot.sieve location issue

Hello, I am trying to set sieve up on a Centos 7 server. It's a configuration with postfix, Maildir, MySQL and virtual domains which works fine. I have created a simple .dovecot.sieve in the user's directory: # cat /home/mail/domain.com/user/.dovecot.sieve require "fileinto"; redirect

Re: dovecot-pigeonhole running external script ends with signal 11

There were some non-compatible changes in 2.2.27 that makes older versions of pigeonhole incompatible, when external programs are used. We moved the program-client code from pigeonhole to dovecot core and made some changes to it to facilitate other uses for it. Aki > On January 8, 2017 at

Re: dovecot-pigeonhole running external script ends with signal 11

Hi Stephan thanks for insisting on the pigeonhole version. That seems to be the reason. With 0.4.16 I built the rpms again and after yum install on my mailbox servers the script "terminated normally" Just one thing that does not go in my brain so far: in 1 out of maybe 20 cases the script

Re: dovecot-pigeonhole running external script ends with signal 11

Hi Stephan currently the rpm is built based on 0.4.14 Should I try with 0.4.16? I will build it again this afternoon with the version you suggested and report back with the results. Thanks for the help here tobi - Originale Nachricht - Von: Stephan Bosch

Re: dovecot-pigeonhole running external script ends with signal 11

Op 1/8/2017 om 10:00 AM schreef Tobi: > Hi Stephan > > according to ps aux the process that segfaults is (pid 18261) > > vmail18261 0.0 0.0 0 0 pts/0Z09:39 0:00 [lmtp] > > > the gdb backtrace I attached to my mail was the deepest one I got That looks like it happens in

auth: Error: BUG: Authentication client sent unknown handshake command

Hello! I run dovecot for many years now, but today it ran into a bug I've never seen before. Searching the archives, this bug seems to occur very seldom. The current server installation & configuration is running since mid 2015, uptime of the server today is more than two months. It is a virtual