The 'noreplicate' user database field described in the wiki appears to
make no difference as to whether an account gets replicated or not.
My sql user query returns a 'noreplicate' field and I can confirm that
this is getting set using 'doveadm user', however when I add a new
account with
For reasons of user privacy and security I usually configure submission servers
to not include accurate IP address and HELO information of authenticated users.
(Usually replacing it with a private-use domain / IPv6 address.)
Dovecot submission (2.3.2) will produce a header something like this
I mean same user having concurrent session on more than one backend. This will likely cause index corruption. Same applies for dovecot doing delivery on differenr backend than where the user is currently logged in.
Aki
On 19 October 2018 at 17:57
Maybe I misunderstand. Each user is only able to access their mailbox from a
single connection at a time. Other users can access the NFS Spool from other
connections, I think that is what I am calling Concurrent connections.
Is that the same definition you have?
From: dovecot
Concurrent access is not supported. One user should access mail using one backend at a time. You can use dovecot in director mode to prevent this.
Aki
On 19 October 2018 at 16:47 Albert Whale <
albert.wh...@it-security-inc.com> wrote:
Yes, there is currently concurrent usage because the Mail spool is NFS
Mounted.
Here is the current configuration:
dovecot -n
# 2.1.15: /etc/dovecot/dovecot.conf
# OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3
base_dir = /var/run/dovecot/
disable_plaintext_auth = no
lock_method =
>
> On 18.10.2018 21.24, J. de Meijer wrote:
>>> On 16.10.2018 21.32, J. de Meijer wrote:
I'm still trying to fix this problem. Hopefully someone can help.
I've upgraded dovecot to 2.3.3
# dovecot --version
2.3.3 (dcead646b)
That didn't help.
Next I
Yes,
After I changed mode and user/group
Oct 18 19:17:50 server dovecot:
imap(em...@example.com)<57613>: Error: kevent(-1) for
notify remove fail
ed: Bad file descriptor
Oct 18 19:17:50 server dovecot:
imap(em...@example.com)<57613>: Error: close(-1) for
notify remove failed: Bad file
On 18.10.2018 21.24, J. de Meijer wrote:
>> On 16.10.2018 21.32, J. de Meijer wrote:
>>> I'm still trying to fix this problem. Hopefully someone can help.
>>>
>>> I've upgraded dovecot to 2.3.3
>>> # dovecot --version
>>> 2.3.3 (dcead646b)
>>>
>>> That didn't help.
>>>
>>> Next I switched
On 18.10.2018 15.15, Albert Whale wrote:
>
> In attempting to reactivate my IMAP communications with my Email Spool
> (NFS Mounted), I have gotten the following while attempting to
> download the Emails via POP3.
>
>
>
> Oct 18 08:00:45 ns4 dovecot: pop3-login: Login: user=,
> method=PLAIN,
Does this happen every time? -1 is really not a valid file descriptor,
which is why these errors occur.
Aki
On 19.10.2018 5.23, Alex wrote:
> Hello!
>
> I tried to use imap-hibernate.
>
> But errors in maillog:
>
> Oct 19 05:14:24 server dovecot:
> imap(em...@example.com)<67125>: Error:
On 18.10.2018 20.43, Joseph Harth wrote:
> I am trying to use dovecot without ssl in centos 7. It works with imap
> but I am not able to make it work with pop3. Pop3 only works with
> ssl=yes. I can use dovecot in centos 4 ok. I get the same error with
> thunderbird and outlook. But for some
I am trying to use dovecot without ssl in centos 7. It works with imap but I am
not able to make it work with pop3. Pop3 only works with ssl=yes. I can use
dovecot in centos 4 ok. I get the same error with thunderbird and outlook. But
for some reason it works when I telnet to port 110 and do
13 matches
Mail list logo
