-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 18 May 2016, Tom Sommer wrote:
On 2016-05-18 11:52, Aki Tuomi wrote:
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using
dovecot-uidlist.lock, but when a user with mailbox.auto = create logs
in,
Hi,
It appears that dsync closes the file handle once it gets the F (finish)
response even if it hasn’t received the X (done) response.
If the X (done) response gets delivered in another write this will generate
EPIPE in the connected process.
This is much easier to replicate over SSL, however
I have been trying to follow the "instructions" at
"http://blog.iandreev.com/?p=1975#dovecot"; and they seem to be pretty
good. everything works until I get to the part were I test the dovecot
installation and it keeps failing.
I get an AUTH fail error at the "telnet localhost 110" login comma
Problem worked-around.. After working on this for a couple of days, I
finally found this post;
http://askubuntu.com/questions/760026/problem-with-pam-authorization-in-dovecot
in /etc/dovecot/conf.d/10-master.conf uncomment this line;
#default_vsz_limit = 256M
and increase the vsz_limit. e.g.
Hi,
i see in this page
(http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html)
:
"Optionally the replication plugin can also support synchronous
replication of new mail deliveries. In this way it connects to
replication-notify UNIX socket, tells it to replicate the user w
On 2016-05-18 11:52, Aki Tuomi wrote:
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using
dovecot-uidlist.lock, but when a user with mailbox.auto = create logs
in, then the folder is created regardless of dovecot-uidlist.lock
existing or not.
Is the
I'm having great difficulty debugging this problem.. I'm having
intermittant problems connecting to dovecot. This started a couple of
days ago following an apt-get update on the server.
I'm running Ubuntu 14.04, dovecot 2.2.9. Here's my dovecot -n
---
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Li
On 18.05.2016 12:44, Tom Sommer wrote:
> I'm trying to lock down a maildir from modifications using
> dovecot-uidlist.lock, but when a user with mailbox.auto = create logs
> in, then the folder is created regardless of dovecot-uidlist.lock
> existing or not.
>
> Is there no way to prevent dovecot
I'm trying to lock down a maildir from modifications using
dovecot-uidlist.lock, but when a user with mailbox.auto = create logs
in, then the folder is created regardless of dovecot-uidlist.lock
existing or not.
Is there no way to prevent dovecot from touching anything in a maildir
folder?
On 18.05.2016 11:40, Tom wrote:
> I'm running dovecot 2.0.9
> According to the man page, the command:
> # doveconf -f service=imap
> is supposed to show just the settings for imap. Is this correct?
>
> When I issue the command it shows everything. Why?
Hi!
it seems to be broken, we are going to
I'm running dovecot 2.0.9
According to the man page, the command:
# doveconf -f service=imap
is supposed to show just the settings for imap. Is this correct?
When I issue the command it shows everything. Why?
11 matches
Mail list logo
