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 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 and is not even on the wiki or man page yet.
Perhaps in the future doveadm save can provide this as output, but until then, if you have some good known criteria about the message you have just saved, such as Message-Id you can use that in doveadm search, combined with savedsince, this might be reliable enough for your needs.
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 ..." 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 and is not even on the wiki or man page yet.
Perhaps in the future doveadm save can provide this as output, but until then, if you have some good known criteria about the message you have just saved, such as Message-Id you can use that in doveadm search, combined with savedsince, this might be reliable enough for your needs.
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 project. I guess someone will say "contributions are welcome". There has also been some general discussion about organizing the documentation differently, making it more comprehensive and perhaps verbose, and my own personal impression that every line on the wiki seems to assume you already know everything there is no know about dovecot, except the line you're reading right now ;-) But I must say the documentation is still quite helpful, in its own way. And nothing will change unless people get into a practical discussion about organizing an effort to improve the documentation.
I've also looked at the source code. But my attempt to output the UID fails because of the error message: doveadm-mail save.c: 62: 36: error: dereferencing pointer to incomplete type in the line: printf("uid =%s\n", dec2str(save_ctx->dest_mail->uid));
Am 11.04.2015 um 08:46 schrieb Gedalya:
Unfortunately this is not unique. Dovecot's documentation is at all times significantly lagging behind the code, this is the MO for this project. I guess someone will say "contributions are welcome". There has also been some general discussion about organizing the documentation differently, making it more comprehensive and perhaps verbose, and my own personal impression that every line on the wiki seems to assume you already know everything there is no know about dovecot, except the line you're reading right now ;-) But I must say the documentation is still quite helpful, in its own way. And nothing will change unless people get into a practical discussion about organizing an effort to improve the documentation.
On 11 Apr 2015, at 10:48, Hardy Flor <HFlor@gmx.de> wrote:
I've also looked at the source code. But my attempt to output the UID fails because of the error message: doveadm-mail save.c: 62: 36: error: dereferencing pointer to incomplete type in the line: printf("uid =%s\n", dec2str(save_ctx->dest_mail->uid));
The UID isn't actually assigned at that point yet - it's only after transaction has been committed. See imap/cmd-append.c how it does it. Outputting the guid + uidvalidity + uid automatically would be useful I guess (for getting the GUID I think you'd need to create yet another transaction + mail_alloc() + mail_set_uid() + mail_get_special(MAIL_FETCH_GUID) - so maybe not worth the trouble since with the UID you can already do another doveadm fetch for the GUID).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 10 Apr 2015, Hardy Flor wrote:
Subject: Why are here ignore a simple question?
do you have a support contract with somebody, that covers Dovecot?
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
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBVSvCC3z1H7kL/d9rAQKlKAgAgFBpZH/LLi2nDX/wqOMV3cBr2Oon0/bA SIlDrYPiaWSBsabw3AsZPyemfFIeOlae0NpiGVKpLi/o1xzDUJrMhTc+WLI8PsgR mu81sBjh/E7UyjPEwiIq6XJPi5x6f+Y+IuYz4sTQolguNSH8tnWXRYso0v2p711B 2ny5m8vsihlCydSIP+5lulVWQ/aRAIU+Rh0VaelSqdEWM5pOV0ySKjf3yffwl2Fe zxkUvFn4c9sjzDfoj9KOHdeSFmypVo6OTPyrLI1pkDX48hiR0sirSPnszVqQvtkL zhFqK7ujXOzPGzbHDWUhvfi8l8oHGVGP4fnhxcpPeqVtFJ/PkzCbxg== =Nhwg -----END PGP SIGNATURE-----
participants (4)
-
Gedalya
-
Hardy Flor
-
Steffen Kaiser
-
Timo Sirainen