On 14-10-2020 14:54, webad...@exalt.com.au wrote:
I am investigating whether dovecot(https://github.com/dovecot/core/)
handles
case insensitive Message-ID headers as per RFC.
Again, Dovecot has nothing to do with this in the context. Fix your SMTP
client and the problem will go away.
And
On Wed, 14 Oct 2020, Maciej Milaszewski wrote:
On 14.10.2020 16:28, Adrian Minta wrote:
$DOVEADM expunge -A mailbox Trash savedbefore 30d
$DOVEADM expunge -A mailbox Spam savedbefore 30d
You might as we save yourself an invocation by doing
$DOVEADM expunge -A \( mailbox Trash OR
> On 14 Oct 2020, at 10:58, Graham Leggett wrote:
>
> Hi all,
>
> I want to enable trace debugging for sieve. Most specifically, I want to know
> what sieve scripts are running, and whether they’re doing anything.
This is what I have:
plugin {
sieve_trace_dir = ~/.trace
On 14 Oct 2020, at 12:37, @lbutlr wrote:
> jeorachu
I swear I typed hierarchy.
--
"A synonym is a word you use when you can't spell the word you first
thought of." - Burt Bacharach
On 14 Oct 2020, at 05:39, Sami Ketola wrote:
>> On 14. Oct 2020, at 14.20, @lbutlr wrote:
>>
>> On 14 Oct 2020, at 04:24, Sami Ketola wrote:
>>> On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
Those Mac clients who do not use nested folders do not seem to be
affected. That is, I've
On 14 Oct 2020, at 19:15, wrote:
> nice, thats my question :D
>
> If I remember correctly a log was created, but not under var/log but in the
> home directory of the mail user. For example /var/mail/user1/sieve.
I haven't been able to make any sieve logging appear anywhere. Does anyone
On 14.10.20 15:02, Victor Sudakov wrote:
I was asking because the section "Hierarchy separators" in
https://doc.dovecot.org/configuration_manual/namespace/ somewhat implies
that
However, changing the separator doesn’t change the on-disk “layout separator”.
That's why I thought that the
Hey,
nice, thats my question :D
If I remember correctly a log was created, but not under var/log but in the
home directory of the mail user. For example /var/mail/user1/sieve.
And not everything was logged, only serious errors. But I can not remember
exactly what happened...
we have solved
Hi all,
I want to enable trace debugging for sieve. Most specifically, I want to know
what sieve scripts are running, and whether they’re doing anything.
I cannot get anything other than dead silence from dovecot with respect to
sieve.
I have tried the same as asked in this question:
On 14/10/2020 09:11, J. de Meijer wrote:
Hi,
Not sure if this is it, but I used to have the same error when I started
with dovecot.
Aki's response was the following (and solved my problem).
-
Hi!
You can't set
service imap {
service_count = 256
}
if you are using multiple
14. 10. 2020 v 13:39, Sami Ketola :
>
>> On 14. Oct 2020, at 14.20, @lbutlr wrote:
>>
>> On 14 Oct 2020, at 04:24, Sami Ketola wrote:
>>> On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
Those Mac clients who do not use nested folders do not seem to be
affected. That is, I've
Hi
But if you have more users (200K) that is a problem with that scripts
On 14.10.2020 16:28, Adrian Minta wrote:
> The cron option is the safest.
>
> Run each night something like this:
>
> #!/bin/bash
>
> DOVEADM="/usr/bin/doveadm";
>
> $DOVEADM expunge -A mailbox Trash savedbefore 30d
>
14. 10. 2020 v 12:24, Sami Ketola :
>
>> On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
>>
>> Those Mac clients who do not use nested folders do not seem to be
>> affected. That is, I've already suggested to the Mac Mail user that he
>> start Thunderbird, move all his mailboxes into the IMAP
Hi all
I have dovecot-lda set up to run as vmail:vmail, with some sieve scripts in
/var/lib/dovecot/sieve.
The sieve scripts fail to be found with the following (detailed and very
helpful) error message:
Oct 14 16:13:33 gatekeeper dovecot[8109]:
lda(minf...@example.com)<8109>: Error: sieve:
The cron option is the safest.
Run each night something like this:
#!/bin/bash
DOVEADM="/usr/bin/doveadm";
$DOVEADM expunge -A mailbox Trash savedbefore 30d
$DOVEADM expunge -A mailbox Spam savedbefore 30d
On 10/13/20 10:27 PM, @lbutlr wrote:
When using autoexpunge = 14 days in, for
@lbutlr wrote:
> On 13 Oct 2020, at 20:36, Victor Sudakov wrote:
> > I am using Dovecot 2.3.4.1 with maildirs. Just found out that MacOS Mail
> > clients cannot work with nested folders, presumably because the MacOS
> > Mail does not understand "." as the IMAP separator.
>
> This is not correct.
@lbutlr wrote:
> On 14 Oct 2020, at 04:24, Sami Ketola wrote:
> > On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
> >> Those Mac clients who do not use nested folders do not seem to be
> >> affected. That is, I've already suggested to the Mac Mail user that he
> >> start Thunderbird, move all
Filip Hajný wrote:
> 14. 10. 2020 v 11:51, Victor Sudakov :
> >
> >> I had to do it with 10-20 live users and it went fine, nobody noticed
> >> anything (I made the change in the night hours just to be sure
> >> though). I had to go down and fix some erratic folder names that
> >> resulted from
> On 14. Oct 2020, at 14.20, @lbutlr wrote:
>
> On 14 Oct 2020, at 04:24, Sami Ketola wrote:
>> On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
>>> Those Mac clients who do not use nested folders do not seem to be
>>> affected. That is, I've already suggested to the Mac Mail user that he
On 14 Oct 2020, at 04:24, Sami Ketola wrote:
> On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
>> Those Mac clients who do not use nested folders do not seem to be
>> affected. That is, I've already suggested to the Mac Mail user that he
>> start Thunderbird, move all his mailboxes into the
On 13 Oct 2020, at 20:36, Victor Sudakov wrote:
> I am using Dovecot 2.3.4.1 with maildirs. Just found out that MacOS Mail
> clients cannot work with nested folders, presumably because the MacOS
> Mail does not understand "." as the IMAP separator.
This is not correct. Mac Mail has no problems
On 13 Oct 2020, at 21:54, webad...@exalt.com.au wrote:
> I am investigating whether dovecot(https://github.com/dovecot/core/) handles
> case insensitive Message-ID headers as per RFC.
What do you mean by "handles"? Dovecot is an LDA, it has no interaction with
the Message-ID headers.
You've
On 14.10.20 11:57, Victor Sudakov wrote:
Besides that: changing the hierarchy separator is generally possible. But
you schould try and check that with a test system to prevent problems with
your productive environment and all the other users.
I was hoping someone had already done that and I
Hi Victor,
On 14.10.20 11:51, Victor Sudakov wrote:
Did it change anything on Dovecot disk/storage or is the IMAP separator just
"virtual" - ephemeral ?
just for the for the sake of completeness: there is a difference between
the hierarchy separator (for the mailbox name) and the layout
> On 14. Oct 2020, at 12.51, Victor Sudakov wrote:
>
> Those Mac clients who do not use nested folders do not seem to be
> affected. That is, I've already suggested to the Mac Mail user that he
> start Thunderbird, move all his mailboxes into the IMAP root folder, and
> then go on using Mac
Filip Hajný wrote:
> >
> >> I had to do it with 10-20 live users and it went fine, nobody noticed
> >> anything (I made the change in the night hours just to be sure
> >> though). I had to go down and fix some erratic folder names that
> >> resulted from the botched separator handling on some
Markus Winkler wrote:
>
> On 14.10.20 04:36, Victor Sudakov wrote:
> > Do you think I can change the hierarchy separator in the "inbox"
> > namespace without breaking other clients and the mail layout on disk,
> > losing mail etc?
>
> I personally would try to avoid such a change (really IMHO),
14. 10. 2020 v 11:51, Victor Sudakov :
>
>> I had to do it with 10-20 live users and it went fine, nobody noticed
>> anything (I made the change in the night hours just to be sure
>> though). I had to go down and fix some erratic folder names that
>> resulted from the botched separator handling
Filip Hajný wrote:
> >
> > On 14.10.20 04:36, Victor Sudakov wrote:
> >> Do you think I can change the hierarchy separator in the "inbox"
> >> namespace without breaking other clients and the mail layout on disk,
> >> losing mail etc?
> >
> > I personally would try to avoid such a change (really
14. 10. 2020 v 11:28, Markus Winkler :
>
> Hi Victor,
>
> On 14.10.20 04:36, Victor Sudakov wrote:
>> Do you think I can change the hierarchy separator in the "inbox"
>> namespace without breaking other clients and the mail layout on disk,
>> losing mail etc?
>
> I personally would try to avoid
Hi Victor,
On 14.10.20 04:36, Victor Sudakov wrote:
Do you think I can change the hierarchy separator in the "inbox"
namespace without breaking other clients and the mail layout on disk,
losing mail etc?
I personally would try to avoid such a change (really IMHO), especially if
it's "only":
On 2020-09-10, Timo Sirainen wrote:
> We had a bunch of tests, but this required a large input buffer to be =
> feeded to the zstd compression code, which didn't happen all that =
> easily. I only accidentally caught it with the same test as I wrote for =
> reproducing the xz bug.
>
> Here's the
Hi,
Not sure if this is it, but I used to have the same error when I started
with dovecot.
Aki's response was the following (and solved my problem).
-
Hi!
You can't set
service imap {
service_count = 256
}
if you are using multiple system UIDs. See
On 14/10/2020 4:23 am, Dan Egli wrote:
> How can I explain to rspamd and/or sieve that a message that
> was delivered, but marked as spam is in fact NOT spam?
Perhaps you're after a fully automated solution but you might try this.
- Set up folders in your account or accounts who you want to be
34 matches
Mail list logo
