[Bug 364031] Re: imap email read status not updated on server

2009-06-23 Thread dpatel
Sorry if this is not the correct place but I am running Ubuntu Jaunty and using Gmail, yet mine does not mark as read on the server until I exit Evolution. It is reproducible. -- imap email read status not updated on server https://bugs.launchpad.net/bugs/364031 You received this bug

Re: [Bug 364031] Re: imap email read status not updated on server

2009-04-28 Thread Riccardo
I previously wrote about how to reproduce the reported bug, now I tried on Jaunty (I've installed it): the bug is fixed! Il giorno lun, 20/04/2009 alle 12.41 +, Sebastien Bacher ha scritto: Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer

[Bug 364031] Re: imap email read status not updated on server

2009-04-28 Thread Sebastien Bacher
closing since that works now ** Changed in: evolution (Ubuntu) Status: Incomplete = Fix Released -- imap email read status not updated on server https://bugs.launchpad.net/bugs/364031 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug

Re: [Bug 364031] Re: imap email read status not updated on server

2009-04-21 Thread Riccardo
More informations about the reported bug, as required. 1 - Yes It's reproducible. I tried with different instances of Ubuntu 8.10 (32 and amd 64) and the bug It's always present. I thought the trick could be on the server dovecot and so I tried with gmail but It's just the same. 2- How to

[Bug 364031] Re: imap email read status not updated on server

2009-04-20 Thread Riccardo
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25781205/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/25781206/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/25781207/ProcStatus.txt -- imap email

[Bug 364031] Re: imap email read status not updated on server

2009-04-20 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? * Could you try on jaunty? This will help us to find and resolve the problem. **