Hello Dovecot users,
Here is the final 0.4.7 release. No changes were committed since the
last release candidate.
Changelog v0.4.7:
* editheader extension: Made protection against addition and deletion of
headers configurable separately. Also, the `Received' and
`Auto-Submitted' headers are
Steffen Kaiser writes:
e.g. put message-id into mail_always_cache_fields
- From http://dovecot.org/pipermail/dovecot-cvs/2013-May/023261.html
lib-storage: Allow mail_*cache_fields settings to specify any hdr.* fields
... but I belatedly wrote ...
Maybe you can even add these items into
On 03/18/2015 08:49 PM, Timo Sirainen wrote:
There's no reason why flow and pager should write headers to stderr because it would always result
only in a mess. But instead of changing table headers to write to stdout, I think a better fix
would be to make tab formatter write headers to stderr.
Hi all,
Today I can finally announce that Dovecot Oy company has merged with
Open-Xchange AG. This helps us to get more Dovecot developers, support people
and so on. Most importantly, eventually it should allow me to get back to doing
what I like the most: Designing new and interesting stuff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 19 Mar 2015, Gedalya wrote:
On 03/18/2015 08:49 PM, Timo Sirainen wrote:
There's no reason why flow and pager should write headers to stderr because
it would always result only in a mess. But instead of changing table
headers to write to
hello,
I've posted same question here months ago.
But obtaine no answer, even not a you question is stupid.
So I don't know what to think about that.
My goal is to be able to find mails quickly with doveadm search.
We are using dovecot in a corporate. And some managers, sometimes ask to delete
On 19-3-2015 9:30, Gedalya wrote:
On 03/18/2015 08:49 PM, Timo Sirainen wrote:
There's no reason why flow and pager should write headers to stderr
because it would always result only in a mess. But instead of changing
table headers to write to stdout, I think a better fix would be to
make tab
Hello Dovecot users,
Here is the final 0.4.7 release. No changes were committed since the
last release candidate.
Changelog v0.4.7:
* editheader extension: Made protection against addition and deletion of
headers configurable separately. Also, the `Received' and
`Auto-Submitted' headers are
Vu Ngoc VU v...@mcra.fr writes:
My goal is to be able to find mails quickly with doveadm search.
We are using dovecot in a corporate. And some managers, sometimes ask to delete
some messages.
These messages are unwanted ones: mistakenly sent, defamatory...
So, that situations appear rarely,
Am 19.03.2015 um 14:07 schrieb James:
There is some underlying problem with imap-login but in order to debug
it I'd like to see a core file. On error dovecot reports core not
dumped. If I put abort() in the code at the point it is reporting
then a core file is written, so there is no OS
Date: Thu, 19 Mar 2015 15:08:42
From: Steffen Kaiser skdove...@smail.inf.fh-brs.de
Reply-To: dovecot@dovecot.org
To: Vu Ngoc VU v...@mcra.fr
Cc: dovecot@dovecot.org
Subject: Re: fast doveadm search results
My goal is to be able to find mails quickly with doveadm search.
What information you
There is some underlying problem with imap-login but in order to debug
it I'd like to see a core file. On error dovecot reports core not
dumped. If I put abort() in the code at the point it is reporting
then a core file is written, so there is no OS reason why a core can not
be written. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 19 Mar 2015, Vu Ngoc VU wrote:
My goal is to be able to find mails quickly with doveadm search.
What information you are search for? Message-ID, subject, body text?
If your data is in the headers, check out:
doveconf -a|grep -i cache
On 19/03/2015 13:35, Markus Schönhaber wrote:
dumped. If I put abort() in the code at the point it is reporting
then a core file is written, so there is no OS reason why a core can not
be written. It appears to be dovecot's choice to control the child. In
an attempt to obtain a core file I
On 03/19/2015 02:53 PM, James wrote:
...
service imap-login {
chroot =
drop_priv_before_exec = yes
user = dovecot
}
How can I make imap-login to produce a core file?
...
I can create core dumps but not from imap-login, so it's not a general
system restriction. Adding
Hi,
Is there any way of making sure the anvil service, used to penalty
login fails, is working ? I dont see anything on the logs regarding it
neither have it configured. It's not on my configuration files, but it
can be seen on a 'dovecot -a' dump. Should it be logging something ?
16 matches
Mail list logo
