* Jakobus Sch?rz:> Does it matter, if the keyword-files do not match?Possibly. The keyword files define flag<->letter mappings. You have shown two files with mappings (let's call them A and B) with A being a subset of B. If a file is moved from A to B, all is fine. What happens if a file is moved from B to A is for Aki to know. ;-)> 0 $label3 > 1 NonJunk > 2 Junk > 3 redirected > 4 $label2 > 5 $label4 > 6 SeenThis does not look right to me. AFAIK, "Seen" should not appear in this list, because it is one of the predefined flags, but that is also a subject I'd like to hear the Dovecot authors talk about. -Ralph P.S.: Unrelated: Please do not top-post, and definitely do not quote the complete message history every time you reply. Thanks.
Am 05.12.18 um 22:19 schrieb Ralph Seichter:> * Jakobus Sch?rz: > >> Does it matter, if the keyword-files do not match? > Possibly. The keyword files define flag<->letter mappings. You have > shown two files with mappings (let's call them A and B) with A being a > subset of B. If a file is moved from A to B, all is fine. What happens > if a file is moved from B to A is for Aki to know. ;-) > >> 0 $label3 >> 1 NonJunk >> 2 Junk >> 3 redirected >> 4 $label2 >> 5 $label4 >> 6 Seen > This does not look right to me. AFAIK, "Seen" should not appear in this > list, because it is one of the predefined flags, but that is also a > subject I'd like to hear the Dovecot authors talk about. > > -Ralph > > P.S.: Unrelated: Please do not top-post, and definitely do not quote the > complete message history every time you reply. Thanks.Ok. I use dovecot as a service... i did nothing, which is not said in the official dovecot doku... so... Seen is in this file... Dovecot must write it down there... because i did it not... i work with thunderbird, gmail and horde... so dovecot must wrote it itself...
?On 12/5/18, 3:32 PM, "dovecot on behalf of Jakobus Sch?rz"
<dovecot-bounces at dovecot.org on behalf of wertstoffe at nurfuerspam.de>
wrote:
Ok. I use dovecot as a service... i did nothing, which is not said in
the official dovecot doku... so... Seen is in this file... Dovecot must
write it down there... because i did it not... i work with thunderbird,
gmail and horde... so dovecot must wrote it itself...
Your attitude is NOT helping you here. We're mostly volunteers and fellow
users here. We don't owe you a thing.
That said, hopefully Aki or one of the other folks (Stephan?) will jump in here.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 5 Dec 2018, Jakobus Sch?rz wrote:> Am 05.12.18 um 22:19 schrieb Ralph Seichter: >> * Jakobus Sch?rz: >> >>> Does it matter, if the keyword-files do not match?I think it does not matter.>>> 6 Seen >> This does not look right to me. AFAIK, "Seen" should not appear in this >> list, because it is one of the predefined flags, but that is also a> Ok. I use dovecot as a service... i did nothing, which is not said in > the official dovecot doku... so... Seen is in this file... Dovecot must > write it down there... because i did it not... i work with thunderbird, > gmail and horde... so dovecot must wrote it itself...Yes, Dovecot write it there, but a client instructed Dovecot to do so as keyword (tag or whatever it is named), maybe the Sieve script was it. Seen in this file is not the "seen" status of IMAP. To get deeper into the problem, I would: 1) edit the dovecot-keywords files to spell "Seen" as "XSeen", in order to make sure this setting (local keyword) does not interfere with \Seen (global IMAP flag) 2) change (I know it should not matter) addflag "Junk \\seen"; into addflag "Junk"; addflag "\\Seen"; 3) use a file dump tool to verify that "what you see is what you've typed", meaning that "\\Seen" is really ASCII \\Seen, e.g. in Linux: hd sieve-script - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBXAjx48QnQQNheMxiAQKaFgf+NLsYdX83pDDj0JDRjXzot/jGDWSEm3Ec IhCmFtaKf/nE2WQsgZct4pHPicGgjRX6BrLWbGlQepiQY3yMp5qlZYu6rk1wkk8q qtmkL5mgGL53KtaHPdHGBp20+ATGVF7eAQbnaNFBK3UEBddKbq/QNbeChrHtxXuF kbVLYN+6nyX9YGBayo1CT05jwhu77Taflx6jIxRXncY1kEYkdGz8E7K/AqSNkYBn KTHhYfuRUL69vJrJMUpzlnJWtV7H3BCv1yLxYMAOqJFFa4pAOcezGIh2mUIOFl2L wdzwOQ0LQKekdV5m36K2UrcxTJ94j22/g2N5H6OO3zLh0i/uXT3FNA==gt8A -----END PGP SIGNATURE-----