[Dovecot] 1.0-test68 released
Recommended update, has had a lot of testing today. No new big features.
Changes:
- LDAP authentication should work finally?
- Some header lookup fixes that should fix sort/threading issues
- Don't crash with 0-byte size mboxes
- Transaction log fixes. Also rotate .log file to .log.2 file, allowing more history and less "transaction log file lost" messages.
- SEARCHing multiple headers might have crashed
- mbox: When first message was expunged we might have gotten "uid-last unexpectedly lost" errors.
- recent flag counter wasn't updated in index file header always even if the recent flags were removed
- UIDVALIDITY changes are handled more transparently
- Added --rundir configure option (not actually tested, does it work? :)
- etc.
Hi Timo,
Has the exsits after expunge been fixed for OE yet? (haven't been paying much attention to the CVS list the last week or so).
Regards Andrew
On Saturday 23 April 2005 21:26, Timo Sirainen wrote:
Recommended update, has had a lot of testing today. No new big features.
Changes:
- LDAP authentication should work finally?
- Some header lookup fixes that should fix sort/threading issues
- Don't crash with 0-byte size mboxes
- Transaction log fixes. Also rotate .log file to .log.2 file, allowing more history and less "transaction log file lost" messages.
- SEARCHing multiple headers might have crashed
- mbox: When first message was expunged we might have gotten "uid-last unexpectedly lost" errors.
- recent flag counter wasn't updated in index file header always even if the recent flags were removed
- UIDVALIDITY changes are handled more transparently
- Added --rundir configure option (not actually tested, does it work? :)
- etc.
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Daemons did it
On 23.4.2005, at 23:37, Andrew Hutchings wrote:
Has the exsits after expunge been fixed for OE yet? (haven't been paying much attention to the CVS list the last week or so).
Oh, the delay-newmail workaround bug. I forgot that. Added on top of TODO now.
Also I seem to be having some problems with flags not being written into mbox for some messages. It did it with test67 too though.
Maybe test69 will come tomorrow then. :)
Hello Timo,
Saturday, April 23, 2005, 11:49:29 PM, you [TS] wrote:
TS> Maybe it's time to set up bugzilla?
Yep. I'd rather prefer Mantis bug tracking system, http://www.mantisbt.org, to Bugzilla.
-- Tero Ripattila
On Sunday 24 April 2005 12:12, Tero Ripattila wrote:
TS> Maybe it's time to set up bugzilla? Yep. I'd rather prefer Mantis bug tracking system, http://www.mantisbt.org, to Bugzilla.
Or Trac http://trac.edgewall.com/ My company has just migrated to Trac internally and it's really slick. I've used mantis in the past too and I would say that for projects under 50 developers (active ones) that with Mantis or Trac is much more sensible. Bugzilla is pretty high overhead for smaller projects...
Trac has the added advantage of tight subversion integration, built-in wiki, and milestone tracking.
Just my two cents, Patrick.
On Saturday 23 April 2005 21:46, Timo Sirainen wrote:
On 23.4.2005, at 23:37, Andrew Hutchings wrote:
Has the exsits after expunge been fixed for OE yet? (haven't been paying much attention to the CVS list the last week or so).
Oh, the delay-newmail workaround bug. I forgot that. Added on top of TODO now.
Also I seem to be having some problems with flags not being written into mbox for some messages. It did it with test67 too though.
Maybe test69 will come tomorrow then. :)
Ah cool. Thanks. Can't wait to try it out :) I'd write it myself but wasn't sure what angle you wanted to take on the fix (plus my code is always messy :) ) We have had 2 critical servers burn out (ones that don't have redundency yet) in the last week so I haven't had much time for development of our mailservers.
I agree with you about the bugzilla. At this rate you are going to have to get someone else in th project to do general admin :)
Regards Andrew
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Chewing gum on /dev/sd3c
Hi Timo/Guys, Suggested features (after we had a nasty NFS disk failure): the NFS started to fail it took a long time to access the mailboxes, average
- Have reject connections after load of X (like exim, sendmail, etc...), when
load on the dovecot servers was 30-40 (until the NFS turned the disk r/o and all connections were getting kicked out). 2. Have a dead server response setup. Freeserve/Wanadoo do this by setting a flag in their software which accepts all POP connections regards of user/pass and says there is no mail (users don't panic and flood the phones for a while then). Not sure how you would do this with IMAP though.
Maybe these to features could even be linked in some way. Anyway, I'll leave it to you to mull over, flame, etc...
Regards Andrew
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: All of the packets are empty.
Andrew Hutchings wrote:
- Have a dead server response setup. Freeserve/Wanadoo do this by setting a flag in their software which accepts all POP connections regards of user/pass and says there is no mail (users don't panic and flood the phones for a while then). Not sure how you would do this with IMAP though.
I'v been thinking the same thing. One issue that has crossed my mind is that how POP3 clients work in case like this when user leaves his/hers mail on the server.
-- Tomi Hakala
On Monday 25 April 2005 07:37, Tomi Hakala wrote:
Andrew Hutchings wrote:
- Have a dead server response setup. Freeserve/Wanadoo do this by setting a flag in their software which accepts all POP connections regards of user/pass and says there is no mail (users don't panic and flood the phones for a while then). Not sure how you would do this with IMAP though.
I'v been thinking the same thing. One issue that has crossed my mind is that how POP3 clients work in case like this when user leaves his/hers mail on the server.
Hmm...A read only mailbox maybe.
I know...a single mail that can be downloaded once by every user which says a
server status until system is fully online, could even be held in the config
file. A small DB in RAM or a file or something could state who has 'deleted'
the message so they don't download it twice.
Either that or give them a BOFH excuse when they phone :)
The phones went non-stop for 4 hours when our NFS failed, everyone but me was
at a trade show, and due to a bug in exchange a customer of a customer had
accidentally generated several million E-Mails over 24 hours with the bounces
pointed at us which filled the backup NFS server HDD so that wasn't reliable.
It would have been so much easier if I could have switched the phones off :)
I had a fun day :)
Regards Andrew
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Admin - North Wales Linux User Group - www.nwlug.org.uk Proprietor - A-Wing Internet Services - www.a-wing.co.uk Random BOFH excuse: working as designed
On Mon, Apr 25, 2005 at 09:37:47AM +0300, Tomi Hakala wrote:
Andrew Hutchings wrote:
- Have a dead server response setup. Freeserve/Wanadoo do this by setting a flag in their software which accepts all POP connections regards of user/pass and says there is no mail (users don't panic and flood the phones for a while then). Not sure how you would do this with IMAP though.
I'v been thinking the same thing. One issue that has crossed my mind is that how POP3 clients work in case like this when user leaves his/hers mail on the server.
Depends on the client. Quite frequently, the pop-client will get confused the next time it connects and gets the real mailbox, and will download everything that was still on the server.
Same thing may happen in the case of IMAP and 'disappearing' namespaces and subscriptions. I would personally not risk it, and instead have dovecot give a customized error message "ERR Sorry, due to an unforseen problem our mailservers are currently inaccessible. For more information, please see http://our-website.us.org/news/?item=115" or such :)
-- Thomas Wouters thomas@xs4all.net
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
On Monday 25 April 2005 09:44, Thomas Wouters wrote:
On Mon, Apr 25, 2005 at 09:37:47AM +0300, Tomi Hakala wrote:
Andrew Hutchings wrote:
- Have a dead server response setup. Freeserve/Wanadoo do this by setting a flag in their software which accepts all POP connections regards of user/pass and says there is no mail (users don't panic and flood the phones for a while then). Not sure how you would do this with IMAP though.
I'v been thinking the same thing. One issue that has crossed my mind is that how POP3 clients work in case like this when user leaves his/hers mail on the server.
Depends on the client. Quite frequently, the pop-client will get confused the next time it connects and gets the real mailbox, and will download everything that was still on the server.
Same thing may happen in the case of IMAP and 'disappearing' namespaces and subscriptions. I would personally not risk it, and instead have dovecot give a customized error message "ERR Sorry, due to an unforseen problem our mailservers are currently inaccessible. For more information, please see http://our-website.us.org/news/?item=115" or such :)
Ah, I see what you mean, didn't think of it like that. In that case a custom error message may be the best move and would work well in a high load situation (stopping new connections). Most pop clients tell you the server error message when one appears so it might work for that too.
Regards Andrew
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Admin - North Wales Linux User Group - www.nwlug.org.uk Proprietor - A-Wing Internet Services - www.a-wing.co.uk Random BOFH excuse: sounds like a Windows problem, try calling Microsoft support
On Mon, 2005-04-25 at 07:22 +0100, Andrew Hutchings wrote:
Suggested features (after we had a nasty NFS disk failure): the NFS started to fail it took a long time to access the mailboxes, average
- Have reject connections after load of X (like exim, sendmail, etc...), when
load on the dovecot servers was 30-40 (until the NFS turned the disk r/o and all connections were getting kicked out).
I think this should be a separate script which just notifies Dovecot to stop handling connections.
- Have a dead server response setup. Freeserve/Wanadoo do this by setting a flag in their software which accepts all POP connections regards of user/pass and says there is no mail (users don't panic and flood the phones for a while then). Not sure how you would do this with IMAP though.
Someone already mentioned the possibility of using -ERR (and IMAP can do it with "NO [ALERT]") which would show the error message to client. This could be useful I guess..
But how should this be configured? And should it happen only after successful login or should all login attempts be just failed with the error message?
Actually it's already possible I think.. If passdb returns:
nologin=yes reason=Sorry, server down
It won't let anyone log in and gives the error message as the reason. Although that doesn't set IMAP's [ALERT] tag.. Maybe another flag should be set for that.
So .. then what's needed is a way to make passdb return those settings. With SQL it's possible by changing Dovecot to use some alternate dovecot-sql-down.conf file and sending HUP to dovecot. Not exactly easy I guess..
Maybe some auth_failure_file-setting which points to a file. If the file exists, it overrides normal passdb handling and returns whatever settings that are set in it to clients?
participants (6)
-
Andrew Hutchings
-
Patrick Audley
-
Tero Ripattila
-
Thomas Wouters
-
Timo Sirainen
-
Tomi Hakala