Hi all,
after upgrade from Dovecot 2.2 to 2.3 I started to see that emails from
Trash folder are automatically deleted after ~7 days. Email clients are
not configured to automatically expunge or empty trash on log out (I
see this behavior for multiple mailboxes, with different clients).
With
Hello, any news about the attached error?
I'm preparing the 2.2 to 2.3 upgrade and having the same error.
We have the mail stores in an NFS filer.
Regards
On 19.01.2018 11:55, Søren Skou wrote:
Hiya all,
I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on
my testbed. The
This fix is part of next release.
---Aki TuomiDovecot oy
Original message From: "Juan C. Blanco"
Date: 30/05/2018 19:31 (GMT+02:00) To: Dovecot Mailing List
Subject: Re: Fatal: nfs flush requires mail_fsync=always
Hello, any news about the attached error?
I'm preparing
Hi!
On Thu, 31 May 2018 00:44:58 +0900,
A. Schulze wrote:
> When running multiple instances of dovecot on the same host (or running
> multiple docker container),
> it is hard to distinguish logs from different processes: the syslog entries
> are all prefixed with the same identifier "dovecot"
>
Hello,
When running multiple instances of dovecot on the same host (or running
multiple docker container),
it is hard to distinguish logs from different processes: the syslog entries are
all prefixed with the same identifier "dovecot"
It is hardcoded here:
Thanks for that. Turns out it was an issue with exim stripping the local part
suffix from the envelope before passing over lmtp to dovecot. Fixed in the exim
router config!
Although if you turn on trace with spamtest it does result in a crash during
mail receipt:
lmtp(t...@test.net)<7988>:
On 30/05/2018 18:50, Aki Tuomi wrote:
This fix is part of next release.
OK, thanks!
---
Aki Tuomi
Dovecot oy
Original message
From: "Juan C. Blanco"
Date: 30/05/2018 19:31 (GMT+02:00)
To: Dovecot Mailing List
Subject: Re: Fatal: nfs flush requires mail_fsync=always
Am 30.05.2018 um 18:08 schrieb SATOH Fumiyasu:
> Hi!
>
> On Thu, 31 May 2018 00:44:58 +0900,
> A. Schulze wrote:
>> When running multiple instances of dovecot on the same host (or running
>> multiple docker container),
>> it is hard to distinguish logs from different processes: the syslog
Op 30/05/2018 om 17:08 schreef Peter Schiffer:
Hi all,
after upgrade from Dovecot 2.2 to 2.3 I started to see that emails from
Trash folder are automatically deleted after ~7 days. Email clients are
not configured to automatically expunge or empty trash on log out (I
see this behavior for
Setting up postfix/dovecot on a clean FreeBSD cloud server, and have discovered
a strange problem resulting from the interaction of Mac OS X Mail and dovecot
(using the Maildir file structure). Essentially, under very specific
circumstances, Mail somehow tells dovecot that a new incoming
On 30.05.2018 01:46, DevOps wrote:
> All,
>
> We currently use a proxy configuration with an sql query to authenticate
> and discover which backend server an address belongs to and proxy the
> connection to that host to authenticate and retrieve mail. We are
> looking to move to OAUTH2 for
Op 28-5-2018 om 14:18 schreef daniel_1...@protonmail.com:
Dear list,
I want to define two concurrent rules :
1. I want to flag an e-mail containing the word "cloud" in the body
2. I want to move mail sent explicitly to me (as opposed to mail sent to an alias I am
part of) going to "INOBX.I
Aki Tuomi:
There is already ssl_client_ca, for verifying clients. ssl_ca verifies
certs when dovecot is connecting somewhere.
For clarification:
there is a third use case an admin may need intermediate certificates:
And that's where dovecot act as server providing imap/pop3/lmtp/sieve
Hi,
Can you send me that script?
Regards,
Stephan.
Op 28-5-2018 om 13:07 schreef Thorsten Hater:
Dear all,
I stumbled upon the following behaviour of Pigeonhole, which I consider
to be problematic. A user deployed a Sieve script similar to the
following snippet
if not anyof (address :is
‐‐‐ Original Message ‐‐‐
On May 30, 2018 9:08 AM, Stephan Bosch wrote:
> Performing an addflag will not affect fileinto actions that were
>
> executed before; it will only affect fileinto (and keep) executed
>
> thereafter. That is why the order is so important in your script.
>
>
Hi,
Im on Manjaro linux fully up to date running
dovecot 2.3.1-2
pigeonhole 0.5.1-2
All is running well except I am having problems with fileinto - it refuses to
use variables, and mailboxexists is also failing for me.
Im just dealing with plus addressing - should be simple but the behaviour
Hi,
Checking in - this is still an issue with 2.3-master as of today
(2.3.devel (3a6537d59)).
I haven't been able to narrow the problem down to a specific commit.
The best I have been able to get to is that this commit is relatively
good (not perfect but good enough):
Op 30-5-2018 om 14:01 schreef Barry Pearce:
Hi,
Im on Manjaro linux fully up to date running
dovecot 2.3.1-2
pigeonhole 0.5.1-2
All is running well except I am having problems with fileinto - it
refuses to use variables, and mailboxexists is also failing for me.
Im just dealing
Hello,
Am 29.05.2018 um 11:30 schrieb Gerald Galster:
Am 29.05.2018 um 11:00 schrieb Aki Tuomi :
On 29.05.2018 11:35, Hajo Locke wrote:
Hello,
Am 29.05.2018 um 09:22 schrieb Aki Tuomi:
On 29.05.2018 09:54, Hajo Locke wrote:
Hello List,
i use dovecot 2.2.22 and have the same problem
I have a large mail backup folder backup@backup.invalid; I'm cleaning
up daily like this:
infimum=`date -d "-4 day" +"%Y-%m-%d"`
doveadm expunge -u backup@backup.invalid mailbox INBOX SAVEDBEFORE $infimum
doveadm purge -u backup@backup.invalid
yet I see this:
# find attachments/ -type f
20 matches
Mail list logo
