[Dovecot] THREAD REFERENCES bug
I found it on an ancient dovecot version, so it might be already fixed. Let's say I have a folder with 3 messages UIDSubject Date 12 One 2013-06-09 11 Testmail 2013-06-10 14 Subject 2013-06-11 C: A0003 UID THREAD REFERENCES US-ASCII ALL S: * THREAD (12)(11)(14) Now I received a message with today's date (2013-06-12) with subject "Testmail" (the same as message with uid=11. The new message has uid=16. C: A0003 UID THREAD REFERENCES US-ASCII ALL S: * THREAD (12)((11)(16))(14) I expected 16 (or more likely 11 and 16) to be at the end of the result, after 14, i.e. (12)(14)((11)(16)). The problem for a user is when he has more messages in a folder. When user receives a new message sometimes (on subject duplicate) he will not see it because it will be somewhere in the middle of the result, but should be on top. -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
Re: [Dovecot] Connection closed by foreign host.
(gdb) bt full #0 0x7fbbfe71a015 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x7fbbfe701da5 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #2 0x7fbbfe70212d in buffer_write () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x7fbbfe6efe9e in imap_utf8_to_utf7 () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x7fbbfe9df778 in mailbox_list_default_get_storage_name () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #5 0x7fbbfe9932df in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #6 0x7fbbfe9e1856 in mailbox_list_get_storage () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #7 0x7fbbfe993308 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #8 0x7fbbfe9e1856 in mailbox_list_get_storage () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. Zitat von Michael Cramer : i tried the latest dev version 2.2.2-0~auto54 for ubuntu and when i do some testing i got a connection closed. the commands are issued through telnet: root@i920:~# telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1 LOGIN t...@lokal.de 123456 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE NOTIFY COMPRESS=DEFLATE QUOTA ACL RIGHTS=texk] Logged in 2 LIST () "" (virtual/*) * LIST () "/" virtual/All * LIST () "/" virtual/Flagged * LIST (\UnMarked) "/" virtual/Flagged * LIST (\Marked) "/" virtual/All 2 OK List completed. 3 LIST () "" (*) Connection closed by foreign host. the command with number 3 results everytime in a connection closed. i turned on debug_log but nothing is shown there.
[Dovecot] Connection closed by foreign host.
i tried the latest dev version 2.2.2-0~auto54 for ubuntu and when i do some testing i got a connection closed. the commands are issued through telnet: root@i920:~# telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1 LOGIN t...@lokal.de 123456 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE NOTIFY COMPRESS=DEFLATE QUOTA ACL RIGHTS=texk] Logged in 2 LIST () "" (virtual/*) * LIST () "/" virtual/All * LIST () "/" virtual/Flagged * LIST (\UnMarked) "/" virtual/Flagged * LIST (\Marked) "/" virtual/All 2 OK List completed. 3 LIST () "" (*) Connection closed by foreign host. the command with number 3 results everytime in a connection closed. i turned on debug_log but nothing is shown there.
[Dovecot] Zlib plugin: changing compression save level
Hi, I have running dovecot 2.1.15 with zlib plugin enabled and "zlib_save_level = 6" since about 2 years now without any problems. What happens if I now change the zlib_save_level to 9? Should that work without any problems, or become the current saved "*.m" files incompatible or unreadable? Thanks Urban
Re: [Dovecot] Wait for interface to become available instead of dying?
Am 11.06.2013 09:24, schrieb Sebastian Arcus: > On 11/06/13 08:18, Robert Schetterer wrote: >> Am 11.06.2013 09:00, schrieb Sebastian Arcus: >>> At the moment, if one of the interfaces specified with "listen=" in >>> dovecot.conf is not up when Dovecot is started, >>> then Dovecot just refuses to start. Is there an option to make Dovecot >>> start anyway, and just use the interface >>> when it becomes available? It is inconvenient to have Dovecot refuse to >>> start during boot because some interface is >>> temporarily not available. >> >> try write some wrapper to the dovecot start script , checking your >> interfaces and perhaps echo some stuff in dovecot.conf, or simply use -c >> option for starting another dovecot.conf >> but i would not recommand this practises >> >> > Thanks Robert. That's an interesting idea. It probably isn't really > worth the hassle as the whole issue is not quite that important. I was > merely wondering if there is a configuration option for Dovecot to > ignore missing interfaces. > > Maybe coming from the other direction of the spectrum might also be a > good idea - something like a "nolisten" option - to prevent it from > listening on certain interfaces. That's the main reason I use the > "listen" option - to prevent Dovecot from ever listening on certain > interfaces, as an extra layer of protection in case the firewall ever > gets misconfigured. perhaps good idea , but i think it hasnt high prior, wait for Timos Statement Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: [Dovecot] Wait for interface to become available instead of dying?
On 11/06/13 08:18, Robert Schetterer wrote: Am 11.06.2013 09:00, schrieb Sebastian Arcus: At the moment, if one of the interfaces specified with "listen=" in dovecot.conf is not up when Dovecot is started, then Dovecot just refuses to start. Is there an option to make Dovecot start anyway, and just use the interface when it becomes available? It is inconvenient to have Dovecot refuse to start during boot because some interface is temporarily not available. try write some wrapper to the dovecot start script , checking your interfaces and perhaps echo some stuff in dovecot.conf, or simply use -c option for starting another dovecot.conf but i would not recommand this practises Thanks Robert. That's an interesting idea. It probably isn't really worth the hassle as the whole issue is not quite that important. I was merely wondering if there is a configuration option for Dovecot to ignore missing interfaces. Maybe coming from the other direction of the spectrum might also be a good idea - something like a "nolisten" option - to prevent it from listening on certain interfaces. That's the main reason I use the "listen" option - to prevent Dovecot from ever listening on certain interfaces, as an extra layer of protection in case the firewall ever gets misconfigured.
Re: [Dovecot] Wait for interface to become available instead of dying?
Am 11.06.2013 09:00, schrieb Sebastian Arcus: > At the moment, if one of the interfaces specified with "listen=" in > dovecot.conf is not up when Dovecot is started, > then Dovecot just refuses to start. Is there an option to make Dovecot > start anyway, and just use the interface > when it becomes available? It is inconvenient to have Dovecot refuse to > start during boot because some interface is > temporarily not available. try write some wrapper to the dovecot start script , checking your interfaces and perhaps echo some stuff in dovecot.conf, or simply use -c option for starting another dovecot.conf but i would not recommand this practises Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: [Dovecot] Wait for interface to become available instead of dying?
On 11/06/13 00:21, Reindl Harald wrote: Am 10.06.2013 21:04, schrieb Sebastian Arcus: On 10/06/13 13:14, Reindl Harald wrote: Am 10.06.2013 11:45, schrieb Sebastian Arcus: At the moment, if one of the interfaces specified with "listen=" in dovecot.conf is not up when Dovecot is started, then Dovecot just refuses to start. Is there an option to make Dovecot start anyway, and just use the interface when it becomes available? It is inconvenient to have Dovecot refuse to start during boot because some interface is temporarily not available. Then again, maybe there is some strong security reasoning behind the way Dovecot behaves at the moment? the main question is why do you not order the start of your services correctly how should a application bind to a specific interface if it is not up? The order of services is fine as it is. The problem is that if any of the interfaces Dovecot is supposed to be binding to is missing, Dovecot seems to refuse to start at all where i work and config servers *i want* the to fail if the config is wrong instead of just binding to what is available is not a predictable configuration if you specify ecplicit interfaces openvpn service for example might have been reconfigured on a different IP so why the hell to you not config dovecot with "address = *" if you want this Steady now. I was only asking a question. No need to burst a blood vessel over this. Some people prefer their systems to work slightly differently than others. It's the way of the world. Thank you for taking the time to answer.
