On 7/29/21 07:33, Mart Pirita wrote:
This is very bad news.
I don't think that disto is old, if I can compile almost every software with it.
So at the moment I have two choices, newer upgrade Dovecot or rollback the
buffer_t changes and use latest version?
Just fyi, Centos provides an unusab
Hi all!
For a long time, I've been running this out of cron as user "perry":
/usr/bin/doveadm expunge -u perry mailbox SPAM not seen before 7d
After upgrading to 2.3.13 as a result of a debian upgrade, this broke. I
now am suddenly getting:
doveconf: Fatal: Error in configuration file /etc/d
On 8/18/21 12:31, Aki Tuomi wrote:
Hi!
this is a known issue, you can workaround it
Any ideas when it will be fixed?
Perry
__libc_start_main+0xe6) [0x7f55e00831a6] ->
/usr/local/libexec/dovecot/dovecot-lda [0x402819]
Ideas?
--
Perry E. Metzgerpe...@piermont.com
It appears that the lda + sieve does not respect the userdb_mail
setting, though the imap server does(!?). Is this expected behavior?
Perry
--
Perry E. Metzgerpe...@piermont.com
Timo Sirainen writes:
> On Wed, 2010-07-07 at 14:42 -0400, Perry E. Metzger wrote:
>> It appears that the lda + sieve does not respect the userdb_mail
>> setting, though the imap server does(!?). Is this expected behavior?
>
> Are you calling deliver with -d parameter? If
Timo Sirainen writes:
> On Wed, 2010-07-07 at 13:23 -0400, Perry E. Metzger wrote:
>> Jul 7 13:18:00 bellman dovecot: lda(perry): Panic: file
>> index-transaction.c: line 70 (index_transaction_init): assertion failed:
>> (box->opened)
>> Jul 7 13:18:00 bell
"Perry E. Metzger" writes:
> Timo Sirainen writes:
>> On Wed, 2010-07-07 at 14:42 -0400, Perry E. Metzger wrote:
>>> It appears that the lda + sieve does not respect the userdb_mail
>>> setting, though the imap server does(!?). Is this expected behavior?
Stephan Bosch writes:
> It is related to that change, yes. I fixed the problem, but I am still
> not entirely happy with the error handling of the store action.
It would be best, I think, if the system failed safe (i.e. if it did not
lose the user's mail in case of error, but rather stored it in
o have a
better facility.
BTW, none of this addresses my biggest concern about sieve in general,
which is its fragility. This is impossible to fix in the IMAP
server/sieve facility though -- it is really a client interface issue.
Perry
--
Perry E. Metzgerpe...@piermont.com
On Sat, 10 Jul 2010 19:38:34 +0200 "Leander S."
wrote:
> Hi,
>
> is there a possibility to give the if cases a AND / OR sensetivity?
You know about anyof/allof in the sieve language, yes?
--
Perry E. Metzgerpe...@piermont.com
ce in
performance can be quite remarkable.
--
Perry E. Metzgerpe...@piermont.com
12 matches
Mail list logo
