Hi Luka,
I found already the problem, its a bug in dbmail. It doesn't handle the
"store FLAGS.SLIENT" command correct.
I fixed (or better workaround) it locally but didn't deployed it.
Btw I think there is a logic error anyway in handling concurrent changes
in dbmail, but I'm not sure if I'm right or misinterpreted the RFC.
regards,
Harald
Am 22.09.2015 um 15:03 schrieb Jure Pečar:
On Fri, 18 Sep 2015 14:07:31 +0200
Harald Leithner <leith...@itronic.at> wrote:
The Problem seams to be syncing after reading a message, the message get
marked as read. Outlook starts syncing and after sync the message get
unread again. After changing folder (or restart outlook) the message is
marked as read. So it seams that the server gets the correct flag set
but is unable to tell outlook the new state and returns the unread flag.
This doesn't happen the other direct (read->unread) this works without a
problem...
I would like to know if anyone else has this problem with DBMail 3.2.4
and Outlook 2013.
This is from a coworker who has problems subscribing to the mailing list:
Hello Harald,
I have been dealing with the same issues you have described. The problem in my
opinion is that Outlook 2013 makes multiple simultaneous connections to the
imap server. I tested the same manualy, by making two connections and marking
mails as read on one. The other connection did not see the change. I also tried
Database debug log (511). I did see the SQL query that aplied changes which
succeeded, but i did not see any query when i listed the emails on the second
connection. Maybe there is some sort of caching involved?
Best regards,
--
Harald Leithner
ITronic
Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Mobil: +43-699-123 78 4 78
Mail: leith...@itronic.at | itronic.at
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
