http://bugs.winehq.org/show_bug.cgi?id=14797
Summary: Setting up SSL Email access Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: msetzerii@gmail.com
Pegasus Mail is a critical program that I use on my only windows 98, and am looking to move to complete linux. The regular email via port 25 and 110 seem to work fine, but with accounts like gmail, one must use secure ports 995 and 465. Attempts to do this result in no trace file. I'm not clear if and how these ports need to be activated in wine, or if some dll needs to be added. There isn't any error message, it just fails with no trace information available.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2008-08-08 08:35:09 --- Please attach complete terminal output as a text file.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #2 from Juan Lang juan_lang@yahoo.com 2008-08-08 10:33:41 --- Which version of Pegasus Mail? Is there a download link available?
http://bugs.winehq.org/show_bug.cgi?id=14797
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.pmail.com/ Summary|Setting up SSL Email access |Setting up SSL Email access | |in Pegasus Mail
http://bugs.winehq.org/show_bug.cgi?id=14797
Michael Setzer II msetzerii@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |msetzerii@gmail.com
--- Comment #3 from Michael Setzer II msetzerii@gmail.com 2008-08-08 21:11:13 --- Pegasus 4.41
http://www.pmail.com/ http://www.pmail.com/downloads.htm
The program works normally if access is done with a standard port 25 / 110 email connections, but with gmail account it requires an SSL connection using port 995, and 465. It attempts to make the connection, and then no trace information found.
I am running the Pegasus with the -Z 160 (160 is 128 + 32) 32 Enter TCP/IP debugging mode 128 "Blind load" WINSOCK.DLL - do not attempt to locate it first.
Also the following options. -A (no parameter) Forces Pegasus Mail to run in standalone mode, ignoring any NetWare connection. -ROAM This option tells Pegasus Mail that it should ignore the configured drive letter when locating user mailboxes and mail files, and should instead use the drive letter of the drive from which WINPM-32.EXE was run. If Pegasus Mail and your mailbox directories are located on the same physical drive, you should always use this option. -ROAM greatly simplifies running the program on Peer-to-Peer and non-NetWare networks, because it allows the same copy of the program to be run no matter what drive letter mappings exist on the particular workstation where it runs. This switch also allows you to install a complete, working copy of Pegasus Mail, complete with mailboxes, onto a memory stick, and to use that memory stick in any computer where it is subsequently plugged. You must not use this switch if Pegasus Mail and your mailbox directories cannot be accessed using the same drive letter. This switch is ignored and has no effect in either Novell NetWare operating mode.
All those option were set at install, but the -Z was just 128, I added the 32 to get the debugging file. Which did produce some extra data that I didn't notice before since the error was saying no trace data.
Debug File contains this. --- Fri, 08 Aug 2008 15:58:18 --- Connect to 'smtp.gmail.com' port 465, timeout 60. 15:58:19.389 [*] Connection established to 209.85.201.111 15:58:20.901 22: Error -14 activating SSL session (locus 6014, type 4, code 0, '') 15:58:20.901 --- Connection closed normally at Fri, 08 Aug 2008 15:58:20. ---\0A\0A
So, it is making a connection, but not sure what the Error -14 is caused by.
It works with the standard ports, so is it a missing DLL or configuration setting? The Linux is Fedora 8.
http://bugs.winehq.org/show_bug.cgi?id=14797
Kai Blin kai.blin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |secur32
--- Comment #4 from Kai Blin kai.blin@gmail.com 2008-08-10 03:29:45 --- I guess it's trying to load the schannel provider from sspi.
Can you provide a WINEDEBUG=+secur32 wine app.exe log?
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #5 from Michael Setzer II msetzerii@gmail.com 2008-08-10 20:14:09 --- an you provide a WINEDEBUG=+secur32 wine app.exe log?
I tried adding the WINEDEBUG=+secur32 to the launcher if I put the log at the end of the line, it doesn't run. With the line below it does run, bur produces the same error, and I don't see were it creates the log file if any.
env WINDEBUG=+secur32 WINPREFIX="/home/msetzerii/.wine" wine "C:\PMAIL\Programs\WINPM-32.EXE" -roam -A -Z 160
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #6 from Juan Lang juan_lang@yahoo.com 2008-08-11 12:28:27 --- (In reply to comment #5)
env WINDEBUG=+secur32 WINPREFIX="/home/msetzerii/.wine" wine "C:\PMAIL\Programs\WINPM-32.EXE" -roam -A -Z 160
That's got a couple of typos, you want WINEDEBUG rather than WINDEBUG, and WINEPREFIX rather than WINPREFIX.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #7 from Juan Lang juan_lang@yahoo.com 2008-08-11 12:32:18 --- (In reply to comment #5)
With the line below it does run, bur produces the same error, and I don't see were it creates the log file if any.
It'll just sent the output to the console, whatever that is. You don't want to use a launcher for this, you want to run it from the command prompt, and redirect the output to a log file. Something like the following should work: cd ~/.wine/drive_c/PMAIL/Programs WINEDEBUG=+secur32 wine "C:\PMAIL\Programs\WINPM-32.EXE" -roam -A -Z 160 >& console.txt
Then attach console.txt here.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #8 from Michael Setzer II msetzerii@gmail.com 2008-08-11 13:33:05 --- Created an attachment (id=15381) --> (http://bugs.winehq.org/attachment.cgi?id=15381) Output of Winedebug with Pegasus Mail secure connection
This is the console.txt file produced by using the WINEDEBUG line recommended, and running the Pegasus program. Then just attempted to do a secure email connection with gmail. File is about 102K in size.
In contrast, just opening and exiting the program resulted in these lines only. ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: Permission denied fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:storage:StgCreateDocfile Transacted mode not implemented.
http://bugs.winehq.org/show_bug.cgi?id=14797
Edward Hasbrouck edward@hasbrouck.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |edward@hasbrouck.org
--- Comment #9 from Edward Hasbrouck edward@hasbrouck.org 2008-10-04 17:23:23 --- I experience what I think is the same bug, using Pegasus Mail 4.41, Wine 1.1.5, and Ubuntu 8.04. There are other reports that may correspond to the same bug in the comments on Pegasus Mail 4.4.1 in the Wine AppDB. I think this bug should be linked to the Wine AppDB, and the status changed to confirmed, but I don't know how to do that.
I'm a fairly advnaced Pmail user, but a Linux newbie. If there is anything I can do to assist in investigating this bug, please let me know.
http://bugs.winehq.org/show_bug.cgi?id=14797
Thomas Stephenson admin@linux-tstephenson.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |admin@linux-tstephenson.com
--- Comment #10 from Thomas Stephenson admin@linux-tstephenson.com 2008-10-14 11:56:31 --- Pegasus Mail uses Peter Gutmann's crypylib to do SSL/TLS http://www.cs.auckland.ac.nz/~pgut001/cryptlib/index.html
I've talked to him about the problem and he does not know why it does not work.
http://bugs.winehq.org/show_bug.cgi?id=14797
Geoff Lane bunsen@tesco.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bunsen@tesco.net
--- Comment #11 from Geoff Lane bunsen@tesco.net 2009-02-20 12:45:58 --- (In reply to comment #9)
I experience what I think is the same bug, using Pegasus Mail 4.41, Wine 1.1.5, and Ubuntu 8.04.
I've got exactly the same setup (assuming typo with Wine should read 1.1.15)
I have contributed to Bug #10213 for over a year now, this too relates to Pegasus.
I am also unable to receive SSL mail from my gmail account, it reports << No trace information available >>
Geoff Lane
http://bugs.winehq.org/show_bug.cgi?id=14797
Dr. Werner Furlan furlan@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #12 from Dr. Werner Furlan furlan@gmx.net 2009-02-20 16:45:16 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #13 from Thomas Stephenson admin@linux-tstephenson.com 2009-02-20 23:23:53 --- (In reply to comment #12)
*** This bug has been confirmed by popular vote. ***
Conimed by popular vote???? I hope it was confirmed by testing. ;-)
http://bugs.winehq.org/show_bug.cgi?id=14797
sebas sbstst@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sbstst@yahoo.com
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #14 from Edward Hasbrouck edward@hasbrouck.org 2009-03-04 23:36:57 --- Using pmail 4.41, ubuntu 8.04. Upgraded wine to 1.1.16. Bug 9735 (entire pmail app closes when sub-window is closed) no longer occurs -- THANK YOU!!!!
But Bug 14797 (encypted SMTP fails) is still present.
http://bugs.winehq.org/show_bug.cgi?id=14797
Dr. Werner Furlan furlan@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |furlan@gmx.net
--- Comment #15 from Dr. Werner Furlan furlan@gmx.net 2009-03-15 04:37:14 --- (In reply to comment #14)
Using pmail 4.41, ubuntu 8.04. Upgraded wine to 1.1.16. Bug 9735 (entire pmail app closes when sub-window is closed) no longer occurs -- THANK YOU!!!!
But Bug 14797 (encypted SMTP fails) is still present.
(In reply to comment #13)
(In reply to comment #12)
*** This bug has been confirmed by popular vote. ***
Conimed by popular vote???? I hope it was confirmed by testing. ;-)
of course I tested it. It is the last problem I have with Pegasus Mail (4.41) and Ubuntu Intrepid. The problem will make Pegasus Mail virtually unusable for me under Linux because my Email provider GMX will change the allowed Login method from Plain text to SSL - so I will not be able to download my mail from tomorrow the 16th of march.
http://bugs.winehq.org/show_bug.cgi?id=14797
Michael Setzer II mikes@kuentos.guam.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mikes@kuentos.guam.net
--- Comment #16 from Michael Setzer II mikes@kuentos.guam.net 2009-06-04 06:57:47 --- Have gotten Pegasus to work using stunnel instead of build-in ssl. With Fedora 10 I was able to use the Lnux Stunnel with the following stunnel.conf
client = yes
[gmailpop] accept = 20995 connect = pop.gmail.com:995
[gmailsmtp] accept = 20465 connect = smtp.gmail.com:465
[gmailimap] accept = 20993 connect = imap.gmail.com:993
In Pegasus, setup the gmail account to use 127.0.0.1 and ports 20xxx ports.
With Unbuntu, this didn't work, but installing the windows stunnel under wine, and using the same stunnel.conf would allow Pegasus to work. First run stunnel, then Pegasus.
http://bugs.winehq.org/show_bug.cgi?id=14797
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|secur32 |-unknown
--- Comment #17 from Juan Lang juan_lang@yahoo.com 2009-08-07 18:14:45 --- Based on the logs, and the fact that this is using Peter Gutman's cryptlib, I'm going to say this isn't a secur32 bug. The log is mostly lines like the following:
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION fixme:ntdll:NtQuerySystemInformation (0x00000004,0x1407fc0,0x00008000,0x7ec6b8f4) stub fixme:ntdll:NtQuerySystemInformation (0x00000006,0x1407fc0,0x00008000,0x7ec6b8f4) stub fixme:ntdll:NtQuerySystemInformation (0x00000007,0x1407fc0,0x00008000,0x7ec6b8f4) stub fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PROCESSOR_PERFORMANCE_INFORMATION fixme:ntdll:NtQuerySystemInformation (0x00000009,0x1407fc0,0x00008000,0x7ec6b8f4) stub fixme:ntdll:NtQuerySystemInformation (0x0000000a,0x1407fc0,0x00008000,0x7ec6b8f4) stub fixme:ntdll:NtQuerySystemInformation (0x0000000c,0x1407fc0,0x00008000,0x7ec6b8f4) stub fixme:ntdll:NtQuerySystemInformation (0x0000000d,0x1407fc0,0x00008000,0x7ec6b8f4) stub
That is, it's calling NtQuerySystemInformation with an incrementing value of SystemInformationClass, the first parameter. I'll guess that cryptlib is attempting to fill an entropy pool with random data. The code that's likely being executed is something like that here: http://src.gnu-darwin.org/ports/security/cryptlib/work/random/win32.c
I'm guessing we don't handle enough of these queries to provide enough entropy for cryptlib, and therefore cryptlib refused to initialize.
http://bugs.winehq.org/show_bug.cgi?id=14797
David turbolad995@hotmail.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |turbolad995@hotmail.co.uk
--- Comment #18 from David turbolad995@hotmail.co.uk 2010-05-01 17:31:53 --- I can confirm this is still a problem when using Pegasus Mail under version 1.1.42 of Wine.
You cannot use SSL for POP or SMTP in Pegasus Mail alone when running it under Wine.
http://bugs.winehq.org/show_bug.cgi?id=14797
Rob Hills rhills@medimorphosis.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rhills@medimorphosis.com.au
--- Comment #19 from Rob Hills rhills@medimorphosis.com.au 2010-07-08 08:05:54 --- I also confirm that this remains a problem for Pegasus Mail 4.52 and Wine 1.1.42 on Ubuntu 10.04. It's a show stopper for me sadly as my ISP only provides encrypted access to their mail server so I have to use ports 993 and 465.
I can use Thunderbird without any problem with those ports, how do they work around this issue?
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #20 from Thomas Stephenson admin@linux-tstephenson.com 2010-07-08 10:05:20 --- (In reply to comment #19)
I also confirm that this remains a problem for Pegasus Mail 4.52 and Wine 1.1.42 on Ubuntu 10.04. It's a show stopper for me sadly as my ISP only provides encrypted access to their mail server so I have to use ports 993 and 465.
I can use Thunderbird without any problem with those ports, how do they work around this issue?
Use STunnel for Windows to do the SSL, the Ubuntu STunnel for Linux did not work for me but I have not tried it recently. I use WinPMail with both Mercury and GMail hosts using SSL with no problems. Here's what I use in the client configuration.
[GMail IMAP4] accept = 20993 connect = imap.gmail.com:993
[GMail POP3] accept = 20995 connect = pop.gmail.com:995
[GMail SMTP] accept = 20465 connect = smtp.gmail.com:465
[tstephenson SMTP] accept = 10587 connect = 192.168.1.2:465
[tstephenson POP3] Accept = 10110 Connect = 192.168.1.2:995
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #21 from Rob Hills rhills@medimorphosis.com.au 2010-07-08 11:00:47 --- Thanks for the suggestion Thomas. I've actually now got it working using the Linux stunnel:
Thanks to Michael Setzer's comment #16, I've now got Pegasus Mail working in Ubuntu 10.04 with the help of Linux Stunnel4. Unlike Michael's experience, I've found that the current version of Linux Stunnel for ubuntu works. Briefly I did the following:
1. Installed stunnel: sudo apt-get install stunnel
2. Modified the stunnel configuration file: sudo gedit /etc/stunnel/stunnel.conf
The changes I made were: - commented out the "cert = " line - this is not needed in our case - UNcommented the "client = yes" line - commented out all of the existing sections for pop3s, imaps, ssmtp etc - these sections start with the section name in square brackets (eg [pop3s]) - Added my own sections for [imap] and [smtp] as detailed by Michael in comment #16 (with some tweaks for my own mail provider, Webfaction).
3. Start the stunnel daemon: sudo service stunnel4 start
5. Configured Pegasus Mail as detailed in comment #16
A bit of a fiddle, but its a workaround. And I have one less reason to drop back to Windoze.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #22 from Michael Setzer II mikes@kuentos.guam.net 2010-07-08 13:03:09 --- Glad to hear you got it working. It has always worked with the Fedora that I mainly use thru all the versions. With the Ubuntu the linux stunnel didn't work, but installing the windows stunnel did. Don't have much work on Ubuntu, so it may have been any number of things.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #23 from Juan Lang juan_lang@yahoo.com 2010-07-09 11:45:59 --- (In reply to comment #19)
I can use Thunderbird without any problem with those ports, how do they work around this issue?
Thunderbird doesn't use the same crypto library. I already described where I think the problem is likely to be in Wine, and it hasn't received any attention since then, so this bug will likely remain open for a while.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #24 from David turbolad995@hotmail.co.uk 2010-07-15 20:33:06 --- Still not working in Wine 1.2-rc7 despite all settings for POP3 and SMTP being correct in order to use SSL.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #25 from Michael Setzer II mikes@kuentos.guam.net 2010-07-15 20:44:42 --- Are you referring to it not working with the built in SSL configuration or with using the Stunnel solution?
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #26 from David turbolad995@hotmail.co.uk 2010-09-04 11:28:21 CDT --- (In reply to comment #25)
Are you referring to it not working with the built in SSL configuration or with using the Stunnel solution?
I believe this problem is caused by a bug in Wine - the built-in SSL uses Peter Gutmann's cryptlib and this seems to be what Wine can't handle.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #27 from David turbolad995@hotmail.co.uk 2010-12-06 05:39:57 CST --- (In reply to comment #26)
(In reply to comment #25)
Are you referring to it not working with the built in SSL configuration or with using the Stunnel solution?
I believe this problem is caused by a bug in Wine - the built-in SSL uses Peter Gutmann's cryptlib and this seems to be what Wine can't handle.
I have confirmation it is the cryptlib component itself that does not work in Wine, which is why Pegasus Mail in Wine will not work with SSL connections. I'm using Wine version 1.3.8 and it's only this bug that stops Pegasus Mail getting a "Platinum" rating in the AppDB, as everything else in Pegasus Mail works perfectly.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #28 from Michael Setzer II mikes@kuentos.guam.net 2010-12-06 06:28:43 CST --- I've been using Pegasus with Stunnel setup for some time to get around this issue when accessing gmail account.
Thanks for the info.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #29 from David turbolad995@hotmail.co.uk 2010-12-11 14:50:22 CST --- (In reply to comment #28)
I've been using Pegasus with Stunnel setup for some time to get around this issue when accessing gmail account.
Thanks for the info.
Please could someone post a link on how to use "Stunnel setup" in Pegasus Mail using Wine? That could be a workaround until this bug is fixed.
Once Wine is fixed to allow Pegasus Mail to access POP3 and SMTP using SSL (via the cryptlib component), I will very happy to award Pegasus Mail a "Platinum" rating in AppDB. :)
Note: if this helps, you could contact the developers of Pegasus Mail here: http://www.pmail.com/contacts.htm
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #30 from Michael Setzer II mikes@kuentos.guam.net 2010-12-11 16:24:10 CST --- http://bugs.winehq.org/show_bug.cgi?id=14797
Shows the whole list of comments on this, and comments 16 and 20 are the main ones that explain the setup. Just install stunnel, and setup the stunnel.conf file to map the local ports to gmail. Then setup pegasus to use those local ports to connect to sites.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #31 from David turbolad995@hotmail.co.uk 2010-12-12 06:38:30 CST --- (In reply to comment #30)
http://bugs.winehq.org/show_bug.cgi?id=14797
Shows the whole list of comments on this, and comments 16 and 20 are the main ones that explain the setup. Just install stunnel, and setup the stunnel.conf file to map the local ports to gmail. Then setup pegasus to use those local ports to connect to sites.
Thanks.
Does this only work for GMail? I used to be able to use Pegasus Mail in Windows to send/retrieve e-mail from my Yahoo account using the SSL settings within Pegasus Mail.
When this bug is fixed, it should allow Pegasus Mail to use SSL to send and receive e-mails, even those with attachments, HTML e-mail etc. It could also fix any other Windows programs' which use Peter Gutmann's cryptlib via Wine. Then I can award Pegasus Mail a "Platinum" rating in AppDB and suggest to David Harris (the creator of Pegasus Mail) that future releases of Pegasus Mail are tested in Wine, so the same Windows binary can work in Linux without any extra work on his part.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #32 from Michael Setzer II mikes@kuentos.guam.net 2010-12-12 07:14:03 CST --- Don't know about yahoo. Long ago, I had used it with pop/smtp before they dropped that support for the free accounts, and then I dropped it completely. I did use it with my local ISP. When I was in the states for the summer, they don't allow non-local access to the smtp, so setup the access with the same setup.
I use Fedora Linux, and Thomas uses Ubuntu..
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #33 from Rob Hills rhills@medimorphosis.com.au 2010-12-12 09:17:36 CST --- (In reply to comment #31)
(In reply to comment #30)
<..>
When this bug is fixed, it should allow Pegasus Mail to use SSL to send and receive e-mails, even those with attachments, HTML e-mail etc. It could also fix any other Windows programs' which use Peter Gutmann's cryptlib via Wine. Then I can award Pegasus Mail a "Platinum" rating in AppDB and suggest to David Harris (the creator of Pegasus Mail) that future releases of Pegasus Mail are tested in Wine, so the same Windows binary can work in Linux without any extra work on his part.
Sadly, I see much bigger problems on the horizon for the upcoming version 5 of Pegasus Mail. Looking at David's developer blog at http://www.pmail.com/devnews.htm, he talks about using Internet Explorer to render HTML within Pegasus Mail and an "SQL-based backend" to store contacts and mail data. While he doesn't say so explicitly I strongly suspect he's talking about the embedded version of SQL Server that M$ makes available free these days.
I hope I'm being unnecessarily pessimistic, but it seems to me that the future of Pegasus Mail and Wine is not looking rosy.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #34 from Thomas Stephenson admin@linux-tstephenson.com 2010-12-12 13:49:51 CST --- (In reply to comment #33)
(In reply to comment #31)
(In reply to comment #30)
<..>
<snip a lot>
Sadly, I see much bigger problems on the horizon for the upcoming version 5 of Pegasus Mail. Looking at David's developer blog at http://www.pmail.com/devnews.htm, he talks about using Internet Explorer to render HTML within Pegasus Mail and an "SQL-based backend" to store contacts and mail data. While he doesn't say so explicitly I strongly suspect he's talking about the embedded version of SQL Server that M$ makes available free these days.
The IERenderer will be an option as well as the current BearHTML. The MSIE stuff definitely does not work in Linux, BearHTML does. As for the SQL, you are already using it if you use Spamhalter with WinPMail. He's definitely not going to be using MS SQL for this.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #35 from David turbolad995@hotmail.co.uk 2011-04-05 17:00:17 CDT --- This bug still exists in Wine version 1.3.17 AND the latest version of Pegasus Mail (4.61 as of this writing) with SSL enabled for POP3 and SMTP.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #36 from Rob Hills rhills@medimorphosis.com.au 2011-04-05 19:46:45 CDT --- (In reply to comment #35)
This bug still exists in Wine version 1.3.17 AND the latest version of Pegasus Mail (4.61 as of this writing) with SSL enabled for POP3 and SMTP.
I have regretfully given away Pegasus and moved across to Thunderbird. Using some solutions available online together with some Python code I wrote myself, I have been able to migrate most of my 20+ year-old Pegasus Mailbox and its multi-level folder structure across. With a couple of addons to Thunderbird I have been able to replicate most of the functionality I used in Pegasus.
I made that decision because it seems to me that with each new version Pegasus Mail is being locked in to the Windows OS and I just don't have the time to jump through the hoops trying to make it work in Linux. It's a shame that when David Harris dropped Borland C not so long ago, he elected to go with the M$ option rather than an open-source, multi-platform option like gcc.
Cheers, Rob Hills
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #37 from David turbolad995@hotmail.co.uk 2011-04-08 15:02:42 CDT --- Please don't give up on this bug. Pegasus Mail is only one step away from being awarded “Platinum” in the AppDB, once this bug is fixed. It's a good challenge for any programmer with access to Wine's code to fix this bug and make Pegasus Mail work flawlessly in Wine. Who's up for the challenge? ;)
@Rob Hills - as for Pegasus Mail becoming locked into Windows - it's one of the reasons why Linux users' need Wine to run their Windows programs needed for productivity. The more bugs that are reported AND fixed (especially this one, which can make Pegasus Mail work 100%) the closer we come to helping newcomers migrate to Linux without having to dual-boot with Windows or use Windows in a virtual machine etc just to run critical Windows programs.
I will update this bug report from time to time when I test Pegasus Mail with newer versions of Wine. Everything else I've tested in Pegasus Mail seems to be working properly in Wine. Thank you.
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #38 from David turbolad995@hotmail.co.uk 2011-04-10 16:51:24 CDT --- OpenSSL may be used soon and this bug may change:
http://www.pmail.com/devnews.htm
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #39 from David turbolad995@hotmail.co.uk 2011-06-02 19:10:57 CDT --- I have received this e-mail reply from the developer of Pegasus Mail, David Harris, which includes his responses to the comments above:
__
I've now read through the thread on WineHQ.
I've been aware of this problem for quite a while, but because it's entirely an issue inside Cryptlib, there's been nothing I can do about it - I freely admit that I am not a cryptographer, and believe I am wise enough to know that I should not be attempting to make changes to a large, complex cryptographic library without about 1000x more knowledge and experience than I currently have.
What I *can* tell you is that I'm currently migrating from cryptlib to OpenSSL, and am well down the track to making the migration. I don't know how OpenSSL fares under Wine, but I'd guess there must a fair chance that it will integrate better. The only gotcha is that OpenSSL also has severe problems with entropy gathering (you may recall the Debian OpenSSL debacle of a few years back), so in my code I currently use some very basic calls to WinCrypt routines (most specifically CryptGenRandom()) to gather entropy with which I can seed OpenSSL's PRNG. If this causes a problem and you are able to do so, please put me in touch with someone inside Wine who might be able to advise on alternative ways of gathering entropy in that environment and I'll do my best to accommodate them.
In general, in fact, I am entirely happy to co-operate with the people involved in Wine at any time - all they need to do is approach me with any reasonable request for coding changes and I'll bend over backwards to try and accommodate it. The simple fact, though, is that in all these years, to the best of my knowledge nobody officially associated with the project has ever been in touch with me. Any changes I've made for the benefit of Wine (and there are a few) are solely because one of my beta testers regularly uses the environment.
With regard to the man who was sad that I chose MSVC instead of GCC, well, I'm afraid that was simple pragmatism: GCC simply isn't a good enough for my Windows development needs at this point. Even with that said, though, the choice of compiler has almost no bearing on whether or not an application can be ported between environments - issues of UI, resource management, target environments, processor and data formats are far more significant. In the event that a genuine linux port of WinPMail was ever going to surface, it would of necessity involve a near-total rewrite, so the compiler is really a non-issue. It's the enormity of the rewrite required that has primarily made it impractical for me to consider doing such a port myself - my days are so full just doing what I am already doing that there is no imaginable way I could consider taking on such a huge project. Since I know that statement slides towards an inevitable segue into issues of Open Source, I'll simply say now that that is a discussion for another time and another forum.
I don't have a WineHQ account, so I'd be grateful if you wouldn't mind reposting this within the thread so people realize that I am aware of the problem and am, with lucking, moving towards a solution.
Cheers!
-- David --
__
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #40 from Juan Lang juan_lang@yahoo.com 2011-06-03 14:22:39 CDT --- Thanks for following through with that, Michael. In fact, CryptGenRandom should work well for generating entropy: it just reads /dev/urandom. As far as I know, OpenSSL works reasonably well on Wine. (And as a former user of PMail for DOS back in the NetWare days, I feel compelled to say: thanks, David!)
http://bugs.winehq.org/show_bug.cgi?id=14797
Jonas Svensson jonass@lysator.liu.se changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonass@lysator.liu.se
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #41 from David turbolad995@hotmail.co.uk 2011-12-10 09:25:17 CST --- As this bug has not been fixed since it was reported in August 2008, I'm wondering if you would consider putting this on the list of bugs to fix for the 1.4 Wine version milestone?
Once this bug has been fixed, Pegasus Mail would run perfectly in Wine and be rated "Platinum" in AppDB. :)
http://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #42 from Dave Rove drove1640@bobmail.info 2012-01-28 09:16:20 CST --- This bug is still valid for Ubuntu-11.10 with Wine-1.3.28. It also applies to the SSL email in the Forte Agent usenet/email client.
Thanks to Michael Setzer's comment #16 and Rob Hills' comment #21, I've used the "stunnel" workaround which works fine for Forte Agent as well.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #43 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #44 from Edward Hasbrouck edward@hasbrouck.org --- (In reply to Austin English from comment #43)
This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine?
The problem may have been resolved by evolution of pmail, rather than by wine.
Starting with Pegasus Mail v. 4.7 (released February 2014), pmail has switched to openssl from the previous crypto library for these functions.
pmail 4.7 (and presumably subsequent versions, assuming openssl is retained in pmail) does not have this problem under wine. pmail 4.7 runs under wine and connects to secure SMTP servers without needing the "stunnel" workaround.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #45 from Austin English austinenglish@gmail.com --- (In reply to Edward Hasbrouck from comment #44)
(In reply to Austin English from comment #43)
This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine?
The problem may have been resolved by evolution of pmail, rather than by wine.
Starting with Pegasus Mail v. 4.7 (released February 2014), pmail has switched to openssl from the previous crypto library for these functions.
pmail 4.7 (and presumably subsequent versions, assuming openssl is retained in pmail) does not have this problem under wine. pmail 4.7 runs under wine and connects to secure SMTP servers without needing the "stunnel" workaround.
Do you still have access to earlier versions / are they still affected?
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #46 from Edward Hasbrouck edward@hasbrouck.org --- Yes, previous versions of Pegasus Mail (through v 4.63) are still in wide use, and are still affected. pmail v. 4.70 is the first not affected.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #47 from Austin English austinenglish@gmail.com --- (In reply to Edward Hasbrouck from comment #46)
Yes, previous versions of Pegasus Mail (through v 4.63) are still in wide use, and are still affected. pmail v. 4.70 is the first not affected.
Thanks. Could you attach the terminal output from 1.7.16 please?
https://bugs.winehq.org/show_bug.cgi?id=14797
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download CC| |focht@gmx.net Summary|Setting up SSL Email access |Pegasus Mail 4.4 to 4.6 SSL |in Pegasus Mail |enabled POP3 and SMTP | |doesn't work
--- Comment #48 from Anastasius Focht focht@gmx.net --- Hello folks,
please retest with recent Wine 1.7.x version, preferably 1.7.33/34
Regards
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #49 from Jonas Svensson jonass@lysator.liu.se --- Created attachment 50460 --> https://bugs.winehq.org/attachment.cgi?id=50460 Tested with wine-1.7.33 (from Ubuntu repository)
Added a log from using wine 1.7.33 and to me it looks the same as before, ie the problem is still there.
However it gets harder to test this as more and more mail servers turn off old insecure protocols like SSL.
https://bugs.winehq.org/show_bug.cgi?id=14797
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #50 from joaopa jeremielapuree@yahoo.fr --- Is still a bug in current wine (3.20)?
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #51 from Michael Setzer II mikes@kuentos.guam.net --- (In reply to joaopa from comment #50)
Is still a bug in current wine (3.20)?
Pegasus mail came out with a new version that used openssl, and that resolved the issue. Believe that was version 4.70, and current version is 4.72, and it works fine directly. Before had to use stunnel to run the connection thru. So, not sure if the original code would work with the newer wine, but using the latest version of Pegasus with the openssl has no issues.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #52 from joaopa jeremielapuree@yahoo.fr --- Following the last comment, this bug should be close as ABANDONED probably. Can an administrator close this bug as ABANDONED?
https://bugs.winehq.org/show_bug.cgi?id=14797
Dave daveypy@outlook.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |daveypy@outlook.com
--- Comment #53 from Dave daveypy@outlook.com --- (In reply to joaopa from comment #52)
Following the last comment, this bug should be close as ABANDONED probably. Can an administrator close this bug as ABANDONED?
The problem with abandoning this bug is that older (Windows) software may be left permanently broken. Each time a bug like this one is fixed, other Windows programs benefit and it makes Wine more complete.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #54 from Zebediah Figura z.figura12@gmail.com --- (In reply to Dave from comment #53)
(In reply to joaopa from comment #52)
Following the last comment, this bug should be close as ABANDONED probably. Can an administrator close this bug as ABANDONED?
The problem with abandoning this bug is that older (Windows) software may be left permanently broken. Each time a bug like this one is fixed, other Windows programs benefit and it makes Wine more complete.
While that's certainly true, if it's no longer possible to reproduce the bug by virtue of not having the old software, then there's not much point keeping the bug open.
Unless someone can still reproduce the bug?
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #55 from Michael Setzer II mikes@kuentos.guam.net --- (In reply to Zebediah Figura from comment #54)
(In reply to Dave from comment #53)
(In reply to joaopa from comment #52)
Following the last comment, this bug should be close as ABANDONED probably. Can an administrator close this bug as ABANDONED?
The problem with abandoning this bug is that older (Windows) software may be left permanently broken. Each time a bug like this one is fixed, other Windows programs benefit and it makes Wine more complete.
While that's certainly true, if it's no longer possible to reproduce the bug by virtue of not having the old software, then there's not much point keeping the bug open.
Unless someone can still reproduce the bug?
I believe with version 4.7x Pegasus moved to openssl and the built in ssl connection works with no problems, so that resolved the issue with Pegasus email and wine. So, the issue is resolved with later versions of Pegasus, so it can be closed, but not sure what that best method would be to state this status.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #56 from Austin English austinenglish@gmail.com --- Are old versions usable in general (i.e. updates aren't forced)? If so, and someone had a copy that can test, it should stay open.
https://bugs.winehq.org/show_bug.cgi?id=14797
Jonas winehq@jonass.user.lysator.liu.se changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@jonass.user.lysator. | |liu.se
--- Comment #57 from Jonas winehq@jonass.user.lysator.liu.se --- Old versions of this is usable in the sense that updates aren't forced. But old versions are not available from authors website, only current version is.
https://bugs.winehq.org/show_bug.cgi?id=14797
Edward Hasbrouck edward@hasbrouck.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|edward@hasbrouck.org |
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #58 from Michael Setzer II mikes@kuentos.guam.net --- Just to note: Pegasus 4.73 and 4.80 have worked fine with wine up to version 7.10 of the Fedora wine build. With the update to 7.12 of Fedora's something caused a spinning wheel icon to happen at some point (view a new message) that make program unresponsive. No error shows up on screen, and top and ps -ef show no issues...
Doing a dnf downgrade wine fixes the problem, but takes the wine installation back to version 6.16...
Regular dnf upgrade attempts to reinstall the wine 7.12 version. The 7.10 version does exist on koji server, but would require downloading the many individual 7.10 rpm files and installing the group.
Went to winehq and downloaded and installed the latest winehq-devel (also did winehq-stable and winehq-stagging on other machines but results seem to be same) Was at version 7.13, but just had main machine upgrade to 7.14, but same issue. Nothing on what 7.14 does on site yet.
The 7.13 and 7.14 versions both fix the spinning wheel problem, but had 2 other minor issues pop up. One was easy to solve. Fedora 35 would no longer run exe files directly from command line. Turned out during the upgrade wine-systemd was removed?? But just reinstalling it fixed that.
The new issues is that the scroll bars do not always work using mouse buttons. With the Fedora versions of wine all the scroll bars work with mouse buttons on up/down and moving the slider. With the winehq versions 7.13 and 7.14 all scroll bars seem to work fine with the mouse wheel, but was very slow used imwheel to increase sensitivity to 10 to get that.
Example: Primary View window has 3 panels. Left side has folder lists, scroll bar works with scroll wheel, but nothing happens with mouse clicks on up/down and nothing happens with slider. With scroll wheel the slider moves correctly. On the right side are a top and bottom panel. Top panel lists messages in folder selected in left panel. Scroll wheel control moves to other panels as point enters them fine. Top right panels scroll bar does nothing with mouse controlls. The bottom right panel works fine with both scroll wheel or mouse buttons as it should?.
Other windows is folder list view that only has one scroll bar, and it doesn't respond with mouse, but fine with wheel?
Distribution list window has two panels. Left one doesn't work with mouse, but right one does? See no messages in wine output.
So, not sure why sometimes the scroll bar options work with mouse, and sometimes not. With the 7.12 version of Fedora's wine. the scroll bars work fine with wheel or mouse controls.
Am use to using mouse controls more than scroll wheel, so would be nice to get both working. Thanks.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #59 from Jonas winehq@jonass.user.lysator.liu.se --- (In reply to Michael Setzer II from comment #58)
Just to note: Pegasus 4.73 and 4.80 have worked fine with wine up to version 7.10 of the Fedora wine build.
Michael, your comment seems to be unrelated to this bug? This bug is about encryption on old version of Pegasus Mail.
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #60 from Jonas winehq@jonass.user.lysator.liu.se --- (In reply to Jonas from comment #57)
But old versions are not available from authors website, only current version is.
Correction: Old versions are not exposed/advertised. But they are still there and can be found using archive.org. I have updated the URL for this bug to the last version affected of this bug (to the best of my knowledge).
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #61 from Jonas winehq@jonass.user.lysator.liu.se --- (In reply to Jonas from comment #60)
I have updated the URL for this bug to the last version affected of this bug (to the best of my knowledge).
I were not allowed to change the URL. The correct one should be:
download-us.pmail.com/w32-463.exe
https://bugs.winehq.org/show_bug.cgi?id=14797
--- Comment #62 from Michael Setzer II mikes@kuentos.guam.net --- (In reply to Jonas from comment #60)
(In reply to Jonas from comment #57)
But old versions are not available from authors website, only current version is.
Correction: Old versions are not exposed/advertised. But they are still there and can be found using archive.org. I have updated the URL for this bug to the last version affected of this bug (to the best of my knowledge).
I had gotten a email that referenced this bug report as well as the new ones I posted about the bug that isn't about an issue with pegasus, but with updates in the Fedora 7.12 version of wine and the winehq 7.13 and 7.14 versions. Thought it best to put the information in all linked bug reports.
The openssl issue has been fixed long ago 4.73 of Pegasus had and updated openssl, and 4.80 has an even newer version. Since I use it with wine under linux, I switch to using stunnel to handle the ssl connection, which has even an newer version of openssl and is using the 64 bit version, whereas the Pegasus email program is still 32 bit at momment. There is a 4.81 version that is waiting for Google approval of its auth2 support, but they have no ideal when google will handle that. The 4.73 and 4.80 work fine with Fedora wine before 7.12, the works fine with 7.13 and 7.14 versions of winehq wine except for the scroll bar with mouse. Seems other program also have this issue.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla