similar to: Dovecot IMAPS and slow reconnections

Hi everybody I'm trying to set-up an IMAPS mail server using dovecot (version 2.1.7) with virtual email accounts for my family. I have already ran through the mysql phase of the virtual email configuration (and I'm quite confident it works well, because I can send mails from the server using postfix to gmail, e.g.). However, I am stucked configuring dovecot. I don't know why is

Hi list, I like to have public mailboxes in addition to other private in the same domain, and manage the public mailbox permissions through acls. For example: info at domain.com <- public, readable by user2 user1 at domain.com <- private user2 at domain.com <- private The mailboxes are virtual, authentication through pam (kerberos). The public mailbox doesn't have valid kerberos

How can i commit this as bug report? > Am 30.10.2016 um 11:04 schrieb Julian Sternberg <jules at ispire.me>: > > Dovecot Version 2.2.13 > Linux Distribution: Debian Jessie > CPU Architecture: x64 > Filesystem: GlusterFS/NFS, XFS for Base System/Index Files. > Two Dovecot/Postfix nodes accessing same GlusterFS/NFS Maildir. > > Regardless what i choose in

Hi! Thank you for reporting this, we'll look into it. Aki Tuomi Dovecot oy. > On November 5, 2016 at 11:31 PM Jules <jules at ispire.me> wrote: > > > How can i commit this as bug report? > > > Am 30.10.2016 um 11:04 schrieb Julian Sternberg <jules at ispire.me>: > > > > Dovecot Version 2.2.13 > > Linux Distribution: Debian Jessie >

Hi, I am trying to make shared folders work on my server (Ubuntu 18.04, Dovecot 1:2.2.33.2-1ubuntu4.1). Mails are on Maildir++ local filesystem with '.' as layout separator and ALL 100+ users logins fits a template name.lastname, with a dot in the middle. I set up listescape but no luck. When I test with doveadm: root at mail:/etc/dovecot/conf.d# doveadm acl debug -u marcio.merlone

This is my first experience of the mail server. Set up a mail server from Postfix + Dovecot with the MySQL authorization. When you create a new user dovecot makes strange folder structure: the 'inbox' contains 'juncus', 'tash', 'sent' etc. ie 'sent' and other folders are subdir to the 'inbox'. My result: 04 LIST "" "*" * LIST

Dovecot Version 2.2.13 Linux Distribution: Debian Jessie CPU Architecture: x64 Filesystem: GlusterFS/NFS, XFS for Base System/Index Files. Two Dovecot/Postfix nodes accessing same GlusterFS/NFS Maildir. Regardless what i choose in mail_location (:INDEX=MEMORY or :INDEX=/var/indexes/%d/%n) all Mailbox index files will still get created within the users mail_location maildir: ~/Maildir My

We have set up dovecot to use a shared namespace, and it works well. However, when a client attempts to create a folder in the namespace, although dovecot responds with permission denied, it still goes on to create a folder, but in the root of our virtual mailbox folder (more confusingly, even issuing a LIST command for a non-existent subfolder creates the folder in the root). I've checked

This is my first experience of the mail server. Set up a mail server from Postfix + Dovecot with the MySQL authorization. When you create a new user dovecot makes strange folder structure: the 'inbox' contains 'juncus', 'tash', 'sent' etc. ie 'sent' and other folders are subdir to the 'inbox'. How to make the imap folders 'sent',

Hi all! I've bumped into an issue which Dovecot which has me a bit stumped; All of a sudden (ie. no obvious changes made to the config as far as I know) Dovecot seems to never stop 'imap-login' processes. This continues to the point where it will hit the 'process_limit'. For a 50-ish user install the limit was set to 100 but I increased it to 512. The only thing this changes

hello, i get these lines in syslog when using post-login within imap-login: imap-login: Fatal: master: service(imap-login): child 574 killed with signal 11 (core dumps disabled) imap[5523]: segfault at 14 ip b7556276 sp bfc1c940 error 4 in libdovecot.so.0.0.0[b7529000+d4000] these are the relevant sections i added: service imap-login { executable = imap post-login } service post-login {

Hi, I have an fc18 system with postfix and dovecot-2.1.13 and have configured them to use sasl for SMTP Auth and Maildir with imaps. The system is running now, so I'm trying to set up thunderbird to autodetect all settings during the initial account setup. However, it seems to want to use port 143 and STARTTLS, and not port 993, which is what I would expect. When I force it to use 993, I

Hello! I've been trying to configure Dovecot to work as LDA for file-based virtual users with Postfix. Some part in the configuration seems to miss though, as mails are received by Postfix, but instead of giving it to Dovecot for delivery, it delivers the mails itself. Postfix drops the mail in /var/mail/<user>/mbox, if Dovecot would be called, it should deliver it to

Hello, I have been using flags in public folders for quite a while with no problems. Once the flags were added to all clients (Thunderbird), they were visible and synchronized properly. Now I have added some new flags, and in the dovecot-keywords files I see that I am now using more than 25 flags (in which case they are not stored using an additional letter in the filename). Now I see that

Hello In my installation the disable_plaintext_auth does not appear to take effect. I can see that the value is correct using doveconf -a but it doesn't change anything. Whenever attempting to log in using IMAP I get this: * BAD [ALERT] Plaintext authentication not allowed without SSL/TLS, but your client did it anyway. If anyone was listening, the password was exposed. ls NO

Hi, I just upgraded from version 1 to version on Debian Squeeze using their backports. Like I expected my dovecot1 config had to be converted using doveconf and this I did. However, I see problems with files inside directory: drwxr-xr-x 4 dovenull root 4096 Feb 25 20:35 /var/run/dovecot All of them were created owned by root:root rw. I tried to changed, for example : chown postfix:dovecot

Hi We recently installed a dovecot postfix roundcube debian wheezy serverIt is now in production and we are feeling our way as we progressivelyadd new users to this local server. I noticed that dovecot is creating user directory structures for unknown users withinour domain in /var/vmail, even though we have setup a static users.conf db file. I tried omiting the "allow_all_users=yes"

Hi, This morning I discovered what seemed to be a deliberate crash in auth_worker: Jun 7 23:02:09 localhost dovecot: auth-worker: Error: #007Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2) Jun 7 23:02:09 localhost dovecot: auth-worker: Error: Fatal error in defaults handling. Program aborted Jun 7 23:02:09 localhost dovecot: auth-worker: Error: *** glibc detected ***

This is a followup to my thread "Recommended Protocols?". The error message is as follows: dovecot: imap-login: Disconnected: TLS: SSL_read() failed: SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 I have selected both SSL/TLS and STARTTLS on the Thunderbird side, with identical results. The first question that I have is this. Is there any way to know

We're seeing a core dump for a user connecting from IPHONE. The user mail are in NFS mount. # dovecot --version 2.2.12 # doveconf -n # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 auth_cache_negative_ttl = 0 auth_cache_size = 20 M auth_verbose = yes default_client_limit = 4000 default_process_limit = 1000 default_vsz_limit = 2 G director_mail_servers =