Bug#389446: evolution: fails to import IMAPv4 configs from version 2.6

2006-11-01 Thread Thijs Kinkhorst
Hi, IMAPv4 has been seriously broken for a good while. Actually it has never been anything but an experimental implementation. The project team hesitated to remove it since some people depended on it. It was always desirable to have a migration script in place for the removal, but none was

Bug#389446: [Evolution] Bug#389446: evolution: fails to import IMAPv4 configs from version 2.6

2006-11-01 Thread Loïc Minier
On Wed, Nov 01, 2006, Thijs Kinkhorst wrote: Wouldn't it be possible to add a (presumably simple) patch to Evolution that on startup does something like (if account has type IMAPv4, set it to IMAP, done). That would solve it transparantly for the user. Something approaching was done for the

Bug#389446: evolution: fails to import IMAPv4 configs from version 2.6

2006-09-25 Thread Goedson Teixeira Paixao
Package: evolution Version: 2.8.0-1 Severity: normal evolution 2.6 used to have two different type of server for recieving messages from an IMAP server, IMAP and IMAPv4. In my configuration to access my work email, I used the IMAPv4 type (IMAP did not work). Now, I've upgraded to evolution 2.8

Bug#389446: evolution: fails to import IMAPv4 configs from version 2.6

2006-09-25 Thread Øystein Gisnås
On 25/09/06, Goedson Teixeira Paixao [EMAIL PROTECTED] wrote: evolution 2.6 used to have two different type of server for recieving messages from an IMAP server, IMAP and IMAPv4. In my configuration to access my work email, I used the IMAPv4 type (IMAP did not work). Now, I've upgraded to