[quote user="Tom Barkas"] I've done that and sent it in.

Using the debugger makes pegasus insist on closing down[/quote]

Thanks for feedback, Tom!

v4.52 In the last few days, it has become impossible to reply to an email by clicking on Reply. It puts up the Options  then goes to an hourglass and at best does nothing, but usually gives a Not responding. Running an Update install doesn't change anything. Any ideas?

Sorry - wrong information. It's only certain emails it does this with, some of the ones I get from Taiwan. Don't know if it helps, but these are the headers of a problem one:
Return-Path:
X-Original-To: tom@bark.eclipse.co.uk
Delivered-To: tom@bark.eclipse.co.uk
Received: from mxa02css.ch.as12513.net (mxa-cluster.ch.as12513.net [82.153.251.80])
 by mda02.lois.eclipse.net.uk (Postfix) with ESMTP id C59631E02A1
 for ; Sun, 22 May 2011 15:49:44 +0100 (BST)
Received: from earth.karoo.kcom.com (earth.karoo.kcom.com [212.50.160.55])
 by mxa02css.ch.as12513.net (Postfix) with ESMTP id 506887BF96
 for ; Sun, 22 May 2011 15:49:43 +0100 (BST)
X-IronPort-AV: E=Sophos;i="4.65,251,1304290800";
   d="xml'?docx'72,32,150,48?emf'72,32,150,48?scan'72,32,150,48,32,208,72,48,150,217?rels'72,32,150,48,32,208,72,48,150,217?png'72,32,150,48,32,208,72,48,150,217,150";a="1098633612"
Received: from moutng.kundenserver.de ([212.227.126.171])
  by earth.eclipse.kcom.com with ESMTP; 22 May 2011 15:49:45 +0100
Received-SPF: pass (mxeu0: domain of ntu.edu.tw designates 140.112.2.142 as permitted sender) client-ip=140.112.2.142; envelope-from=huangcs@ntu.edu.tw; helo=smtps.ntu.edu.tw;
Received: from smtps.ntu.edu.tw (smtps.ntu.edu.tw [140.112.2.142])
 by mx.kundenserver.de (node=mxeu0) with ESMTP (Nemesis)
 id 0MNaBi-1QI8Mr39ru-007UOu for tom@barkas.co.uk; Sun, 22 May 2011 16:49:43 +0200
Received: from TOSHIBAPC (111-248-8-109.dynamic.hinet.net [111.248.8.109])
 (using TLSv1 with cipher AES128-SHA (128/128 bits))
 (No client certificate requested)
 by smtps.ntu.edu.tw (Postfix) with ESMTP id C78FB106855
 for ; Sun, 22 May 2011 22:49:32 +0800 (CST)
From: "Huang Chiun-Sheng"
To:
Subject: FW: manuscript of Dr. Lo and Dr. Huang
Date: Sun, 22 May 2011 22:49:32 +0800
Message-ID:
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="----=_NextPart_000_0041_01CC18D2.84E6AA90"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcwWPyn7fCK43DA0TIepByMcJH8zVACT7rPw
Content-Language: zh-tw
X-Antivirus: avast! (VPS 110522-0, 22/05/2011), Inbound message
X-Antivirus-Status: Clean
X-PMFLAGS: 570970240 0 1 P7UISK88.CNM       

Update to 4.61 which has fixes to cure problems with messages with long lines in them. It has other benefits also.

[quote user="Tom Barkas"]v4.52 In the last few days, it has become impossible to reply to an email by clicking on Reply. It puts up the Options  then goes to an hourglass and at best does nothing, but usually gives a Not responding. Running an Update install doesn't change anything.[/quote]

I'm a bit confused about the version you're using: Did you update 4.52 or what else does update install mean? If you're still using 4.52 I would support Jerry's recommendation and add: Don't forget to update IERenderer after doing so at least if you're running a system with IE 9 installed. If you still get these "unresponsive" situations you should also install the MiniDump extension: The next time Pegasus Mail appears to hang please go to MiniDump's Start menu group (provided you allowed one to be created) and click the PMDebug Snapshot shortcut to be sent to the beta-reports account after restarting Pegasus Mail (I assume you have to force its termination). For details please read MiniDump's ReadMe file.

What I meant by Update install was I reinstalled 4.52 using the Update option. I've also updated to 4.61 - if I try to reply to the same problem messages in 4.61, it freaks out with a message "Run-Time check failure #2 -stack around the variable 'tface' was corrupted". Choosing the option Ignore seems to work.

[quote user="Tom Barkas"]Run-Time check failure #2 -stack around the variable 'tface' was corrupted". Choosing the option Ignore seems to work.[/quote]

This is a "debug error" pointing to potentially serious issues: In this case it would also be helpful if you could provide us with a dump created by MiniDump: It should get created after installing the extension if you click "Retry" in the above mentioned dialog. If you don't get a reporting dialog when doing this (see the ReadMe file for details) it might be required to restart Pegasus Mail via MiniDump's Start menu group entry called "Pegasus Mail Debugger" and trying the "Reply" button again. But sometimes using the debugger may

even

prevent the error from reoccurring at all ...

Hi, Michael,

 I've done that and sent it in.

Using the debugger makes pegasus insist on closing down