On 15 Jul 2019, at 23.17, Ralf Hildebrandt via dovecot
wrote:
>
> * Ralf Hildebrandt via dovecot :
>> We're using dovecot (via LMTP) as a backup for all incoming mail.
>>
>> I upgraded from 2.3.6 to 2.3.7 on the 12th:
>> 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic
>> 2:2.3
I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server
Notice that some status responses are missing (For folders INBOX.Archive,
INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as expected
In rfc5819 there is this:
If the server runs into unexpected proble
On 15 Jul 2019, at 18:11, Trever L. Adams via dovecot
wrote:
> So, one of the problems I am seeing is that people are trying to fake
> users into revealing information by sending from an outside domain but
> with an internal reply to address and claiming to be administration, IT
> or what not.
Y
So, one of the problems I am seeing is that people are trying to fake
users into revealing information by sending from an outside domain but
with an internal reply to address and claiming to be administration, IT
or what not.
I can set up something that will reject if from is outside the domain by
Finally getting around to upgrading my setup to 2.3.x.
All of our front end proxies are fine on 2.3 connecting to a 2.2 backend
storage pair.
So the question is, if I stage the upgrade, will it break replication
between the two backend storage servers? My thought was to upgrade one to
2.3, and k
Hello,
Following on my last question about broken mdboxes, removing
dovecot.map.log and force-resync does work. My last problem now however
is that after doing this, messages which were 'deleted' previously, come
back in the inbox as new messages.
I have the original mailboxes and can subsc
* Ralf Hildebrandt via dovecot :
> We're using dovecot (via LMTP) as a backup for all incoming mail.
>
> I upgraded from 2.3.6 to 2.3.7 on the 12th:
> 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic
> 2:2.3.7-8~bionic
>
> and it seems that 2.3.7 is slower than 2.3.6 -- mail to t
Hello,
I was discussing weird response from Dovecot on Mailkit (this is client IMAP C#
library) github page. We concluded that this is a bug in Dovecot server but I
wanted to double check with you. Here are the details about the issue
https://github.com/jstedfast/MailKit/issues/879
Sent with O
Dovecot can do cached ldap queries too. NSS module isn't going to do a comeback, sorry.
Aki
On 15/07/2019 16:51 Eugene Bright wrote:
I use LDAP right now, but local cached sssd queries are much faster and reliable.
Il 11/07/19 23:31, Timo Sirainen ha scritto:
On 11 Jul 2019, at 10.13, Alessio Cecchi via dovecot
mailto:dovecot@dovecot.org>> wrote:
Hi,
I'm running some Dovecot servers configured with LVS + Director +
Backend + NFS and version 2.2.36.3 (a7d78f5a2).
In the last days I see an increased nu
I use LDAP right now, but local cached sssd queries are much faster and
reliable.
On July 15, 2019 6:49:18 AM GMT+03:00, Aki Tuomi
wrote:
>
>
>On 15/07/2019 02:54 Eugene via dovecot < dovecot@dovecot.org> wrote:
>
>
>
>Hello!
>
>
>Upgrading manual tells that authdb [NSS module was removed][1]
We're using dovecot (via LMTP) as a backup for all incoming mail.
I upgraded from 2.3.6 to 2.3.7 on the 12th:
2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic
2:2.3.7-8~bionic
and it seems that 2.3.7 is slower than 2.3.6 -- mail to the backup
IMAP box is suddenly taking quite som
Il 15/07/19 14:34, Gianluca Scaglia via dovecot ha scritto:
Hi there,
on my mail server (postfix, dovecot 2.2.27 in Debian 9) I have an
automatic forwarding (with sender_bcc_maps in Postfix) for all the
emails sent in smtp from the same server, that are then put in the
Sent folder with a sie
Hi there,
on my mail server (postfix, dovecot 2.2.27 in Debian 9) I have an automatic
forwarding (with sender_bcc_maps in Postfix) for all the emails sent in smtp
from the same server, that are then put in the Sent folder with a sieve
rule.
In this way, however, when a user sends an e-mail to
Hi,
> On 15. Jul 2019, at 10:59, Timo Sirainen wrote:
>
> On 15 Jul 2019, at 10.58, Paul Hecker via dovecot wrote:
>>
>> Hi,
>>
>> since upgrading to Dovecot 2.3.7 I get the following new errors:
>
> What was the old version? Did you upgrade your kernel as well?
It was 2.3.6. But you are tr
On 15 Jul 2019, at 10.58, Paul Hecker via dovecot wrote:
>
> Hi,
>
> since upgrading to Dovecot 2.3.7 I get the following new errors:
What was the old version? Did you upgrade your kernel as well?
> 2019-07-15 09:10:52 mail dovecot:
> imap(p...@iwascoding.com)<32484>: Error: file_lock_free()
Hi,
since upgrading to Dovecot 2.3.7 I get the following new errors:
2019-07-15 09:10:52 mail dovecot:
imap(p...@iwascoding.com)<32484>: Error: file_lock_free():
Unexpectedly failed to retry locking
/var/spool/mail/iwascoding/paul/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-vsize.lock:
fcntl(/
On 7/14/19 11:30 PM, Aki Tuomi via dovecot wrote:
>> Try with one mailbox first.
>>
>> Delete dovecot.index.map files and run force-resync.
>>
>> ---
>> Aki Tuomi
>
> Sorry I ment dovecot.map.index there
Hey, that seemed to work!
I'll need to do more testing because I still have those false md
18 matches
Mail list logo