Courier to Dovecot migration
This week, I've managed to migrate from courier-imap to dovecot at work. I always had a good experience with dovecot, and I still have one.
This week, I’ve managed to migrate from courier-imap to dovecot at work. I always had a good experience with dovecot, and I still have one.
Dovecot performances are very good in comparison with courier. With that switch, we dropped the CPU usage of the server from 25 % to 10 %, and it’s damn faster now. I have no idea why, but I think that it’s better written looking at the code, and also that its usage of index files helps a lot.
We got no problem getting things work with public folders either, so the switch was almost painless.
The only problem we had is that Dovecot is too smart for some MUA. Consequently, we hit an 8 years old Mutt bug #969, which I also reported to the Debian BTS as #549204 with a not-well-tested-but-seems-to-work patch.
Thanks to Claws mail, we also found a bug in dovecot 1.2.5, which should be fixed soon. Dovecot upstream is very responsive and that’s always something nice to know when you use a free software.
Related posts
Sending Emails in Python — Tutorial with Code Examples
What do you need to send an email with Python? Some basic programming and web knowledge along with the elementary Python skills. I assume you’ve already had a web app built with this language and now
Read more →Handling multipart/form-data natively in Python
RFC7578 (who obsoletes RFC2388) defines the multipart/form-data type that is usually transported over HTTP when users submit forms on your Web page.
Read more →