http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #25 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-12 15:57:24 --- (In reply to comment #24)
(In reply to comment #23)
This is not much help to me. I tried doing regression testing for days and never was sure I got it right since there was never any change to the way Wine worked with Pegasus Mail. That's the primary reason no one had done regression testing since we were not at all clear as to how to do this.
My Wine is now in two different directories. ~.wine and ~\wine I was hoping there would be some simple way to build the wine package by running something like wineinstall that is in the ~\wine\tools directory.
E-mail me privately, and I'll try to help. This sort of thing doesn't belong on bugzilla.
Agreed, it should not be in bugzilla but it's also obvious that this is way beyond my skill set. I've worked with Windows, VM, VMS, Netware and a bit of UNIX but it's not at all clear to me as to how to get rid of the patch. I'm too much of a Linux/Wine nubie.
It appears that you have found the reason through regression testing of why the Wine closes Pegasus Mail when it sends a close to the editor. I really want to thank you for your effort. I would have expected some sort of response from the developer of the patch that broke this in the first place but that does not appear to be the case.
I hope one of these days this fix will show up in a released version.