<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 3/29/10 2:21 AM, Mark Banner wrote:
<blockquote cite="mid:4BB07132.6000104@mozillamessaging.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 22/03/2010 22:41, Mark Banner wrote:
<blockquote cite="mid:4BA7F203.7040203@mozillamessaging.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
A couple of days ago over irc, timeless suggested a solution to
fix <a moz-do-not-send="true"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=123440">Bug
123440</a> -
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span id="summary_alias_container"><span
id="short_desc_nonedit_display">Stop that annoying modal
dialog when mail can't connect to the mail server from
connection time out error.<br>
<br>
The basic idea is that all Mailnews modal dialogs go to the
alerts service. I think this would mean they would appear in
the same location as the new mail alert - certainly on Linux
& Mac (not quite so sure about Windows, but probably!).</span></span><br>
</blockquote>
Did anyone actually give these builds a try? If I've not heard
anything in about 24 hours, I'll push the patch forward and we can
expose it in beta 2 for some wider feedback.<br>
</blockquote>
I've tried them on and off, but I don't think I've hit the problem,
because it's no longer trivial to reproduce by just turning off
network access.<br>
<br>
For people who want to test, intentionally misconfiguring a server
or edit /etc/hosts may be the easiest way...<br>
<br>
Dan<br>
<br>
</body>
</html>