On 04/11/2015 02:39 AM, Hardy Flor wrote:
I had been on 3/12/2015 pointed to the lack of documentation of "doveadm
save". It was in the changelog of 2.2.16.
Unfortunately this is not unique. Dovecot's documentation is at all
times significantly lagging behind the code, this is the MO for this
I had been on 3/12/2015 pointed to the lack of documentation of "doveadm
save". It was in the changelog of 2.2.16.
Am 10.04.2015 um 23:39 schrieb Gedalya:
> On 04/10/2015 05:10 PM, Hardy Flor wrote:
>>
>> Am 06.04.2015 um 09:36 schrieb Hardy Flor:
>>> Hello,
>>>
>>> when I have with "doveadm save
On 04/10/2015 05:10 PM, Hardy Flor wrote:
Am 06.04.2015 um 09:36 schrieb Hardy Flor:
Hello,
when I have with "doveadm save ..." store a message, how do I get the
guid or uid of this message for the setthe flags?
Hardy
Maybe the feature is just not there? This command has just been added
a
Am 06.04.2015 um 09:36 schrieb Hardy Flor:
> Hello,
>
> when I have with "doveadm save ..." store a message, how do I get the
> guid or uid of this message for the setthe flags?
>
> Hardy
On Apr 10, 2015, at 12:14 AM, Steffen Kaiser
wrote:
> pass"word
>
> is no atom and Dovecot should reject it.
No, not passwords should be rejected.
> Maybe the former version did not checked the atoms 100% RFC conform.
Where is the definition that passwords have to be atomic? And if it is ther
On 4/8/2015 4:53 PM, Patrick Lion wrote:
> Hey folks,
>
> ive already made a bug report in the gentoo bugtracker last year. In the
> meantime after some releases the error persists with the current dovecot
> and pigeonhole versions.
>
> Please see my bug report at gentoo mailinglist:
>
> https://bu
