OK, last try.

Is it supposed to give the current time and date in the error message. I've no problem with it giving an "internal error" message to the client, but I am a little confused about the time being in there. That's all I'm asking about.

Mark Lidstone IT and Network Support Administrator

BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122
Fax: +44 (0)23 8063 5144

E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk

== Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited.

==

-----Original Message----- From: Andrew Boothman [mailto:andrew@mux.org.uk] Sent: 20 August 2004 18:09 To: Dovecot list Subject: Re: [Dovecot] Unusual behaviour

Mark Lidstone wrote:

I thought that Dovecot was supposed to handle that kind of thing? Reading from the website:

"Any kind of crash is considered as bug and will be fixed - even if it happens only by deliberately poking the index files."

I've done it in the past by just creating the bare folders - they appear in the IMAP folder list then when they're used Dovecot seems to

create the sub folders anyway.

The issue I'm asking about here is, should the error message say "Internal Error [date time]" rather than something useful?

Did Dovecot actually crash? Did it log a more sensible error message to syslog?

I think Dovecot quite often reports an "internal error" to the client but then writes a more sensible error message to syslog. Which is probably no bad thing as you may well not want clients to see detailed error messages - there's nothing they can do about it anyway.

Andrew