Re: History mails are stored in the tmp/ directory

On 20.07.20 10:19, lty wrote: >>> On 20/07/2020 10:37 lty wrote: >>> We found that there are historically corrupted mails in the tmp/ >>> directory, >>> For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists. >>> We suspect that it may be caused by network transmission, or the user >>> interrup

Re: Questions about Dovecot push notifications

I managed to figure out some of my questions and answer them here I case someone else runs into them: Am 16.07.20 um 09:39 schrieb Ralf Becker: > I read the docu available under: > https://doc.dovecot.org/configuration_manual/push_notification/ > > I'm using Dovecot 2.2.36.4 with directors and a r

Sieve and OX push_notification_drive seem to not work together

While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script moves the message on arrival to an other folder, neither in INBOX were it original arrives by LMTP, nor in the folder Sieve moves the message. Is that a misc

Re: Sieve and OX push_notification_drive seem to not work together

  On 21/07/2020 13:35 Ralf Becker wrote:     While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script

Re: Sieve and OX push_notification_drive seem to not work together

Hi Aki, Am 21.07.20 um 15:07 schrieb Aki Tuomi: >> On 21/07/2020 13:35 Ralf Becker > > wrote: >>   >>   >> While it's documented that the OX push_notification_driver only supports >> MessageNew events, it does NOT generate any event if a Sieve script >> moves the messag

Re: To field was not correct indexed by FTS

On Tue, Jul 21, 2020 at 08:18:21 +0900, TACHIBANA Masashi wrote: > Hi, > > Thank you for your reply. > > I hope this bug to be fixed soon. :) It is a tricky one because as far as I can tell, the From header is invalid. So, we have to figure out the best way to handle such input. The input is in

ports with different crypto settings

    Hello Everyone,     Is it possible, with latest dovecot, to have different crypto settings on different pop/imap ports? Basically i'm looking to have one port with TLSv1 enabled, which will be exposed to internal networks only, and other ports with TLSv1.2+ only, which will be exposed to