Re: [Dovecot] v1.0.14 released (managesieve updated)
Timo Sirainen wrote: http://dovecot.org/releases/1.0/dovecot-1.0.14.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.14.tar.gz.sig Refreshed ManageSieve patch for new Dovecot v1.0 release: http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.14-MANAGESIEVE-v9.3.diff.gz http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.14-MANAGESIEVE-v9.3.diff.gz.sig Regards, Stephan.
Re: [Dovecot] v1.0.14 released
Matthias Andree wrote: On Mon, 02 Jun 2008, Timo Sirainen wrote: - proxy: Login success reply was sent in two IP packets, which confused some IMAP/POP3 clients So? Fix the clients or have the kernel reassemble packets. They can't control who and when is fragmenting and why anyways. I'm not against the change, but it's not a solution. So include the work-around (that doesn't break anything) in Dovecot, and notify the maintainers of the broken clients to Get a clue(tm) :P It does improve login latency for everyone... sure, not by much for most, but hey... :P -- Curtis Maloney [EMAIL PROTECTED]
Re: [Dovecot] v1.0.14 released
On Mon, 02 Jun 2008, Timo Sirainen wrote: - proxy: Login success reply was sent in two IP packets, which confused some IMAP/POP3 clients So? Fix the clients or have the kernel reassemble packets. They can't control who and when is fragmenting and why anyways. I'm not against the change, but it's not a solution. -- Matthias Andree
Re: [Dovecot] v1.0.14 released
On Tue, 03 Jun 2008, Curtis Maloney wrote: Matthias Andree wrote: On Mon, 02 Jun 2008, Timo Sirainen wrote: - proxy: Login success reply was sent in two IP packets, which confused some IMAP/POP3 clients So? Fix the clients or have the kernel reassemble packets. They can't control who and when is fragmenting and why anyways. I'm not against the change, but it's not a solution. So include the work-around (that doesn't break anything) in Dovecot, and notify the maintainers of the broken clients to Get a clue(tm) :P Yup. Buffered reads are a virtue :-) It does improve login latency for everyone... sure, not by much for most, but hey... :P By how long? Generation time of the 2nd packet *header* providing it's not reassembled along the path? Wow, impressive. Not. Buys you some 300 bits, that's perhaps 70 µs on my DSL, as the 2nd packet would usually be within the TCP congestion window and be sent back to back to the 1st packet of the response, so no additional round trip delays. I'd be surprised if anyone noticed beyond my broken client got pampered up. OK, let's stop here and not be derisive or defaitist or otherwise destructive, it's a Pareto optimization and as such probably justified. -- Matthias Andree
Re: [Dovecot] v1.0.14 released
On Tue, 2008-06-03 at 10:55 -0700, Kenneth Porter wrote: --On Tuesday, June 03, 2008 5:56 PM +1000 Curtis Maloney [EMAIL PROTECTED] wrote: So include the work-around (that doesn't break anything) in Dovecot, and notify the maintainers of the broken clients to Get a clue(tm) :P Which clients/versions? Can we name names? http://dovecot.org/list/dovecot/2008-April/030245.html I also remember someone having a similar problem with Dovecot's old POP3 code which also sent CRLF separately, but don't remember what the client was. Mailing list archives could tell. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.0.14 released
--On Tuesday, June 03, 2008 5:56 PM +1000 Curtis Maloney [EMAIL PROTECTED] wrote: So include the work-around (that doesn't break anything) in Dovecot, and notify the maintainers of the broken clients to Get a clue(tm) :P Which clients/versions? Can we name names?
Re: [Dovecot] v1.0.14 released
--On Tuesday, June 03, 2008 8:58 PM +0300 Timo Sirainen [EMAIL PROTECTED] wrote: Which clients/versions? Can we name names? http://dovecot.org/list/dovecot/2008-April/030245.html Ah, a mobile phone. Which means a firmware upgrade, and a niche market, which means a client fix is less likely.
[Dovecot] v1.0.14 released
http://dovecot.org/releases/1.0/dovecot-1.0.14.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.14.tar.gz.sig Since v1.1.0 release is getting near, this could well be the last v1.0 release. I'll still fix important bugs, but if the bugfix is large or affects only few people it'll probably get fixed only in v1.1 releases. * mbox: Enable mail_privileged_group while creating INBOX. - IMAP: Fixed a rare crash in FETCH BODY/BODYSTRUCTURE - IMAP: If mailbox is selected with EXAMINE, ignore flag changes - proxy: Login success reply was sent in two IP packets, which confused some IMAP/POP3 clients - ACL plugin leaked memory a bit - dovecot-auth: allow_nets setting with network masks didn't work correctly with big endian machines. signature.asc Description: This is a digitally signed message part
