Menu
▾
▴
hermesmail-discuss
You can subscribe to this list here.
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(11) |
| 2021 |
Jan
(13) |
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Butch K. <bu...@ke...> - 2022-08-19 04:33:29
|
At 01:25 PM 8/18/2022 -0700, Will Daly via Hermesmail-discuss, wrote: > >unsubscribe Click on this link to send a message to unsubscribe from the list: mailto:her...@li...?subject=unsubscribe Butch |
|
From: Will D. <wil...@me...> - 2022-08-18 20:25:28
|
unsubscribe On Thu, 13 May 2021 at 17:25, Braxton Neate <bra...@gm...> wrote: > Hello, > > I was wondering how I can support the HERMES Mail project in an > ongoing way? I know there has been a few fundraising campaigns and > there has now been a breakthrough getting the code to compile. I > really hope it is possible to add UTF-8 support to Eudora, I don't > have much to offer but would like to support the project to continue if I > can. > > I am stubbornly using Eudora despite and needing to communicate in > Japanese for which I can't use Eudora. I don't even have a long > history with Eudora, but it really is the best email client there is. > > Regards, > Braxton Neate > > > > _______________________________________________ > Hermesmail-discuss mailing list > Her...@li... > https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > |
|
From: John B. <jba...@tw...> - 2022-01-07 00:33:14
|
I get the following error message when trying to install the hermesmail program. "Installation of Microsoft visual C++ 2015 Redistributable package (X86) appears to have failed" "Do you want to continue". What is happening and how do I fix it? Also is this program workable on a windows 10, 64 bit system? John Barron |
|
From: Braxton N. <bra...@gm...> - 2021-05-14 00:23:36
|
Hello, I was wondering how I can support the HERMES Mail project in an ongoing way? I know there has been a few fundraising campaigns and there has now been a breakthrough getting the code to compile. I really hope it is possible to add UTF-8 support to Eudora, I don't have much to offer but would like to support the project to continue if I can. I am stubbornly using Eudora despite and needing to communicate in Japanese for which I can't use Eudora. I don't even have a long history with Eudora, but it really is the best email client there is. Regards, Braxton Neate |
|
From: Michael O. <ref...@ou...> - 2021-02-18 23:52:06
|
<html> <body> <br><br> BTW, I did try Pandora email client and it does not have this issue. SO it appears likely the source of the problem is somewhere in Hermes SSL code.<br><br> At 04:41 PM 2/18/2021, Michael Oujesky wrote:<br><br> <blockquote type=cite class=cite cite="">Thank you for the suggestion. I tried "never" and the send fails immediately with SSL required.<br><br> I sent out a couple of emails today that failed on the initial attempt, but then succeeded getting out on the second or third retry. I rather expect it is a timing issue in OpenSSL, but don't know if it is on my side or theirs. With Hermesmal SSL being a couple of years old now, I am wondering if a refresh of Hermes SSL support with a later version of OpenSSL might help resolve my issue.<br><br> However, I could still use documentation on settings for Eudora.ini SSL send option to test with.<br><br> Michael<br><br> At 01:51 PM 2/18/2021, Steven Zegas wrote:<br> <blockquote type=cite class=cite cite="">PS: I read the OP more carefully, and yes, it's related. I also thought about tweaking the .ini to solve this 'send' problem. Somewhere, some time, I had some documentation on the .ini. I thought I could just experiment. ... My guess? There is some new SMTP standard being implemented and TLS may be deprecated? Wild guess. <br><br> I am not sure if this is related. I have two discrete instances of Hermes installed in separate folders (with local .ini files; not reliant on the registry.) Both have used the same settings. I have separate email accounts with NetAddress (USA.net) and my clients have worked just fine with both, send/receive. Suddenly, send no longer worked (last week) - with unable to connect SMTP. Tech support insisted that they had no server-side changes ('please contact the support team for your email client.') All along, I used alternate submission port (587). I tried 465 at their request; didn't work. 25, default; didn't work. I cycled through secure sockets settings, which was working fine with 'required, STARTTLS', and finally, the one that worked is 'never'. ... In the tech all, they referred to Outlook incessantly, and the option to change or enforce PW. I'm not sure which. <br><br> Do this relate to the current email? <br> Helpful? Interesting?<br><br> <br><br> At 01:13 AM 02/18/2021, Ronald van Ginkel wrote:<br><br> <blockquote type=cite class=cite cite="">Hi Michael.<br><br> You can trace the source code to find references to it and try to understand how they work.<br><br> By example, this are some code snipets with some of those parameters:<br><br> <font face="Courier, Courier"><x-tab> </x-tab> m_pSSLReference->m_CertificateInfo.m_bIgnoreExpired<x-tab> </x-tab>= pSettings->m_nSSLReceiveIgnoreExpiredCerts;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_AllowSSL_2_0 = pSettings->m_nSSLReceiveAllowVersion2;<br> <x-tab> </x-tab> m_pSSLReference->m_SSLLogSession = pSettings->m_SSLReceiveLogSession;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_AllowRegExp = pSettings->m_SSLReceiveAllowRegExp;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_CipherSuite = pSettings->m_SSLReceiveCipherSuite;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_MinEncryption = pSettings->m_SSLReceiveMinEncryption;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_MinKeyExchangeLength = pSettings->m_SSLReceiveMinKeyExchangeLength;<br> <x-tab> </x-tab> m_pSSLReference->m_CertificateInfo.m_csPrivateKey = pSettings->m_SSLReceivePrivateKey;<br> <x-tab> </x-tab> m_pSSLReference->m_CertificateInfo.m_csPassPhrase= pSettings->m_SSLReceivePrivateKeyPassword;<br><br> </font>And here they manage one of the (MinEncryption):<br><br> <font face="Courier, Courier">[...]<br> <x-tab> </x-tab> IDS_ERR_MINENCRYPTIONNONO "You have configured this personality/protocol to reject encryption levels below %ld.,\r\n But the negotiated encryption level is %ld\r\n Hence this established secure channel is unacceptable. Connection will be dropped."<br> [...]<x-tab> </x-tab><x-tab> </x-tab><br> <x-tab> </x-tab><x-tab> </x-tab><x-tab> </x-tab>// No easy way to determine this under SSL Plus 4.X.<br> <x-tab> </x-tab>if (pConnectionInfo->m_CipherKeyBits < pSSLReference->m_ProtocolInfo.m_MinEncryption)<br> <x-tab> </x-tab>{<br> <x-tab> </x-tab><x-tab> </x-tab>CString csError;<br> <x-tab> </x-tab><x-tab> </x-tab> csError.Format(CResString(IDS_ERR_MINENCRYPTIONNONO), pSSLReference->m_ProtocolInfo.m_MinEncryption, pConnectionInfo->m_CipherKeyBits);<br> <x-tab> </x-tab><x-tab> </x-tab> pConnectionInfo->m_Outcome.AddErrors(csError);<br> <x-tab> </x-tab><x-tab> </x-tab> pConnectionInfo->m_Outcome.m_Outcome = SSLOutcome::SSLREJECTED;<br> <x-tab> </x-tab>}<br> [...]<br><br> <br> </font>Of course, get some kind of documentation should be a lot easier ;-)<br><br> Regards!<br><br> ______________________________________________________________________________________________________________________________________<br> <br> I have been getting 10054 errors while sending email. No issues receiving mail, just sending. Sometime merely retrying the send works for smaller message, but if there are embedded images or attachments that doesn't work. My email provider provided the following from one of the failures <dl> <dd>Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 947731 mail.warning] warning: TLS library problem: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac:s3_pkt.c:535: 2:49 <dd>Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 197553 mail.info] lost connection after DATA (5739 bytes) from unknown[x.x.x.x] </dl>I have tried another email app (Pandors) and it does not have the same issue. So, I am looking to tweak the SSLSend options in Eudora.ini to see if I can resolve this issus with OpenSSL. However, I have been able to find any detail explanations of the following settings and the Eudora/Hermes pop-up for the option is singularly un-enlightening. <dl> <dd>< <a href="x-eudora-option:SSLSendAllowRegExp" eudora="autourl"> X-Eudora-Option:SSLSendAllowRegExp</a>> <dd>< <a href="x-eudora-option:SSLSendAllowVersion2" eudora="autourl"> X-Eudora-Option:SSLSendAllowVersion2</a>> <dd>< <a href="x-eudora-option:SSLSendCipherSuite" eudora="autourl"> X-Eudora-Option:SSLSendCipherSuite</a>> <dd>< <a href="x-eudora-option:SSLSendClientCertsFile" eudora="autourl"> X-Eudora-Option:SSLSendClientCertsFile</a>> <dd>< <a href="x-eudora-option:SSLSendClientCertsInfo" eudora="autourl"> X-Eudora-Option:SSLSendClientCertsInfo</a>> <dd>< <a href="x-eudora-option:SSLSendIgnoreExpCert" eudora="autourl"> X-Eudora-Option:SSLSendIgnoreExpCert</a>> <dd>< <a href="x-eudora-option:SSLSendLogSession" eudora="autourl"> X-Eudora-Option:SSLSendLogSession</a>> <dd>< <a href="x-eudora-option:SSLSendMinEncryption" eudora="autourl"> X-Eudora-Option:SSLSendMinEncryption</a>> <dd>< <a href="x-eudora-option:SSLSendMinKeyExchangeLength" eudora="autourl"> X-Eudora-Option:SSLSendMinKeyExchangeLength</a>> <dd>< <a href="x-eudora-option:SSLSendPrivateKey" eudora="autourl"> x-Eudora-option:SSLSendPrivateKey</a>> <dd>< <a href="x-eudora-option:SSLSendPrivateKeyPassword" eudora="autourl"> x-Eudora-option:SSLSendPrivateKeyPassword</a>> <dd>< <a href="x-eudora-option:SSLSendUse" eudora="autourl"> X-Eudora-Option:SSLSendUse</a>> <dd>< <a href="x-eudora-option:SSLSendVersion" eudora="autourl"> X-Eudora-Option:SSLSendVersion</a>> <dd>< <a href="x-eudora-option:SSLSendVersion3" eudora="autourl"> X-Eudora-Option:SSLSendVersion3</a>> </dl>Might someone be able to direct me to where I might find the details on these option settings?<br><br> Thank you in advance.<br><br> <br><br> <br><br> <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a><br> <br> ______________________________________________________________________________________________________________________________________ <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a> </blockquote></blockquote></blockquote></body> <br> </html> |
|
From: Michael O. <ref...@ou...> - 2021-02-18 22:42:13
|
<html> <body> <br> Thank you for the suggestion. I tried "never" and the send fails immediately with SSL required.<br><br> I sent out a couple of emails today that failed on the initial attempt, but then succeeded getting out on the second or third retry. I rather expect it is a timing issue in OpenSSL, but don't know if it is on my side or theirs. With Hermesmal SSL being a couple of years old now, I am wondering if a refresh of Hermes SSL support with a later version of OpenSSL might help resolve my issue.<br><br> However, I could still use documentation on settings for Eudora.ini SSL send option to test with.<br><br> Michael<br><br> At 01:51 PM 2/18/2021, Steven Zegas wrote:<br> <blockquote type=cite class=cite cite="">PS: I read the OP more carefully, and yes, it's related. I also thought about tweaking the .ini to solve this 'send' problem. Somewhere, some time, I had some documentation on the .ini. I thought I could just experiment. ... My guess? There is some new SMTP standard being implemented and TLS may be deprecated? Wild guess. <br><br> I am not sure if this is related. I have two discrete instances of Hermes installed in separate folders (with local .ini files; not reliant on the registry.) Both have used the same settings. I have separate email accounts with NetAddress (USA.net) and my clients have worked just fine with both, send/receive. Suddenly, send no longer worked (last week) - with unable to connect SMTP. Tech support insisted that they had no server-side changes ('please contact the support team for your email client.') All along, I used alternate submission port (587). I tried 465 at their request; didn't work. 25, default; didn't work. I cycled through secure sockets settings, which was working fine with 'required, STARTTLS', and finally, the one that worked is 'never'. ... In the tech all, they referred to Outlook incessantly, and the option to change or enforce PW. I'm not sure which. <br><br> Do this relate to the current email? <br> Helpful? Interesting?<br><br> <br><br> At 01:13 AM 02/18/2021, Ronald van Ginkel wrote:<br><br> <blockquote type=cite class=cite cite="">Hi Michael.<br><br> You can trace the source code to find references to it and try to understand how they work.<br><br> By example, this are some code snipets with some of those parameters:<br><br> <font face="Courier, Courier"><x-tab> </x-tab> m_pSSLReference->m_CertificateInfo.m_bIgnoreExpired<x-tab> </x-tab>= pSettings->m_nSSLReceiveIgnoreExpiredCerts;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_AllowSSL_2_0 = pSettings->m_nSSLReceiveAllowVersion2;<br> <x-tab> </x-tab> m_pSSLReference->m_SSLLogSession = pSettings->m_SSLReceiveLogSession;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_AllowRegExp = pSettings->m_SSLReceiveAllowRegExp;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_CipherSuite = pSettings->m_SSLReceiveCipherSuite;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_MinEncryption = pSettings->m_SSLReceiveMinEncryption;<br> <x-tab> </x-tab> m_pSSLReference->m_ProtocolInfo.m_MinKeyExchangeLength = pSettings->m_SSLReceiveMinKeyExchangeLength;<br> <x-tab> </x-tab> m_pSSLReference->m_CertificateInfo.m_csPrivateKey = pSettings->m_SSLReceivePrivateKey;<br> <x-tab> </x-tab> m_pSSLReference->m_CertificateInfo.m_csPassPhrase= pSettings->m_SSLReceivePrivateKeyPassword;<br><br> </font>And here they manage one of the (MinEncryption):<br><br> <font face="Courier, Courier">[...]<br> <x-tab> </x-tab> IDS_ERR_MINENCRYPTIONNONO "You have configured this personality/protocol to reject encryption levels below %ld.,\r\n But the negotiated encryption level is %ld\r\n Hence this established secure channel is unacceptable. Connection will be dropped."<br> [...]<x-tab> </x-tab><x-tab> </x-tab><br> <x-tab> </x-tab><x-tab> </x-tab><x-tab> </x-tab>// No easy way to determine this under SSL Plus 4.X.<br> <x-tab> </x-tab>if (pConnectionInfo->m_CipherKeyBits < pSSLReference->m_ProtocolInfo.m_MinEncryption)<br> <x-tab> </x-tab>{<br> <x-tab> </x-tab><x-tab> </x-tab>CString csError;<br> <x-tab> </x-tab><x-tab> </x-tab> csError.Format(CResString(IDS_ERR_MINENCRYPTIONNONO), pSSLReference->m_ProtocolInfo.m_MinEncryption, pConnectionInfo->m_CipherKeyBits);<br> <x-tab> </x-tab><x-tab> </x-tab> pConnectionInfo->m_Outcome.AddErrors(csError);<br> <x-tab> </x-tab><x-tab> </x-tab> pConnectionInfo->m_Outcome.m_Outcome = SSLOutcome::SSLREJECTED;<br> <x-tab> </x-tab>}<br> [...]<br><br> <br> </font>Of course, get some kind of documentation should be a lot easier ;-)<br><br> Regards!<br><br> ______________________________________________________________________________________________________________________________________<br> <br> I have been getting 10054 errors while sending email. No issues receiving mail, just sending. Sometime merely retrying the send works for smaller message, but if there are embedded images or attachments that doesn't work. My email provider provided the following from one of the failures <dl> <dd>Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 947731 mail.warning] warning: TLS library problem: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac:s3_pkt.c:535: 2:49 <dd>Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 197553 mail.info] lost connection after DATA (5739 bytes) from unknown[x.x.x.x] </dl>I have tried another email app (Pandors) and it does not have the same issue. So, I am looking to tweak the SSLSend options in Eudora.ini to see if I can resolve this issus with OpenSSL. However, I have been able to find any detail explanations of the following settings and the Eudora/Hermes pop-up for the option is singularly un-enlightening. <dl> <dd>< <a href="x-eudora-option:SSLSendAllowRegExp" eudora="autourl"> X-Eudora-Option:SSLSendAllowRegExp</a>> <dd>< <a href="x-eudora-option:SSLSendAllowVersion2" eudora="autourl"> X-Eudora-Option:SSLSendAllowVersion2</a>> <dd>< <a href="x-eudora-option:SSLSendCipherSuite" eudora="autourl"> X-Eudora-Option:SSLSendCipherSuite</a>> <dd>< <a href="x-eudora-option:SSLSendClientCertsFile" eudora="autourl"> X-Eudora-Option:SSLSendClientCertsFile</a>> <dd>< <a href="x-eudora-option:SSLSendClientCertsInfo" eudora="autourl"> X-Eudora-Option:SSLSendClientCertsInfo</a>> <dd>< <a href="x-eudora-option:SSLSendIgnoreExpCert" eudora="autourl"> X-Eudora-Option:SSLSendIgnoreExpCert</a>> <dd>< <a href="x-eudora-option:SSLSendLogSession" eudora="autourl"> X-Eudora-Option:SSLSendLogSession</a>> <dd>< <a href="x-eudora-option:SSLSendMinEncryption" eudora="autourl"> X-Eudora-Option:SSLSendMinEncryption</a>> <dd>< <a href="x-eudora-option:SSLSendMinKeyExchangeLength" eudora="autourl"> X-Eudora-Option:SSLSendMinKeyExchangeLength</a>> <dd>< <a href="x-eudora-option:SSLSendPrivateKey" eudora="autourl"> x-Eudora-option:SSLSendPrivateKey</a>> <dd>< <a href="x-eudora-option:SSLSendPrivateKeyPassword" eudora="autourl"> x-Eudora-option:SSLSendPrivateKeyPassword</a>> <dd>< <a href="x-eudora-option:SSLSendUse" eudora="autourl"> X-Eudora-Option:SSLSendUse</a>> <dd>< <a href="x-eudora-option:SSLSendVersion" eudora="autourl"> X-Eudora-Option:SSLSendVersion</a>> <dd>< <a href="x-eudora-option:SSLSendVersion3" eudora="autourl"> X-Eudora-Option:SSLSendVersion3</a>> </dl>Might someone be able to direct me to where I might find the details on these option settings?<br><br> Thank you in advance.<br><br> <br><br> <br><br> <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a><br> <br> ______________________________________________________________________________________________________________________________________ <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a> </blockquote></blockquote></body> <br> </html> |
|
From: Ronald v. G. <ro...@t-...> - 2021-02-18 09:25:19
|
Hi Michael.
You can trace the source code to find references to it and try to
understand how they work.
By example, this are some code snipets with some of those parameters:
m_pSSLReference->m_CertificateInfo.m_bIgnoreExpired =
pSettings->m_nSSLReceiveIgnoreExpiredCerts;
m_pSSLReference->m_ProtocolInfo.m_AllowSSL_2_0 =
pSettings->m_nSSLReceiveAllowVersion2;
m_pSSLReference->m_SSLLogSession = pSettings->m_SSLReceiveLogSession;
m_pSSLReference->m_ProtocolInfo.m_AllowRegExp =
pSettings->m_SSLReceiveAllowRegExp;
m_pSSLReference->m_ProtocolInfo.m_CipherSuite =
pSettings->m_SSLReceiveCipherSuite;
m_pSSLReference->m_ProtocolInfo.m_MinEncryption =
pSettings->m_SSLReceiveMinEncryption;
m_pSSLReference->m_ProtocolInfo.m_MinKeyExchangeLength =
pSettings->m_SSLReceiveMinKeyExchangeLength;
m_pSSLReference->m_CertificateInfo.m_csPrivateKey =
pSettings->m_SSLReceivePrivateKey;
m_pSSLReference->m_CertificateInfo.m_csPassPhrase=
pSettings->m_SSLReceivePrivateKeyPassword;
And here they manage one of the (MinEncryption):
[...]
IDS_ERR_MINENCRYPTIONNONO "You have configured this
personality/protocol to reject encryption levels below %ld.,\r\n But
the negotiated encryption level is %ld\r\n Hence this established
secure channel is unacceptable. Connection will be dropped."
[...]
// No easy way to determine this under SSL Plus 4.X.
if (pConnectionInfo->m_CipherKeyBits <
pSSLReference->m_ProtocolInfo.m_MinEncryption)
{
CString csError;
csError.Format(CResString(IDS_ERR_MINENCRYPTIONNONO),
pSSLReference->m_ProtocolInfo.m_MinEncryption,
pConnectionInfo->m_CipherKeyBits);
pConnectionInfo->m_Outcome.AddErrors(csError);
pConnectionInfo->m_Outcome.m_Outcome =
SSLOutcome::SSLREJECTED;
}
[...]
Of course, get some kind of documentation should be a lot easier ;-)
Regards!
______________________________________________________________________________________________________________________________________
I have been getting 10054 errors while sending email. No issues
receiving mail, just sending. Sometime merely retrying the send
works for smaller message, but if there are embedded images or
attachments that doesn't work. My email provider provided the
following from one of the failures
Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 947731
mail.warning] warning: TLS library problem: error:1408F119:SSL
routines:SSL3_GET_RECORD:decryption failed or bad record
mac:s3_pkt.c:535: 2:49
Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 197553
mail.info] lost connection after DATA (5739 bytes) from unknown[x.x.x.x]
I have tried another email app (Pandors) and it does not have the
same issue. So, I am looking to tweak the SSLSend options in
Eudora.ini to see if I can resolve this issus with OpenSSL. However,
I have been able to find any detail explanations of the
following settings and the Eudora/Hermes pop-up for the option is
singularly un-enlightening.
< X-Eudora-Option:SSLSendAllowRegExp>
< X-Eudora-Option:SSLSendAllowVersion2>
< X-Eudora-Option:SSLSendCipherSuite>
< X-Eudora-Option:SSLSendClientCertsFile>
< X-Eudora-Option:SSLSendClientCertsInfo>
< X-Eudora-Option:SSLSendIgnoreExpCert>
< X-Eudora-Option:SSLSendLogSession>
< X-Eudora-Option:SSLSendMinEncryption>
< X-Eudora-Option:SSLSendMinKeyExchangeLength>
< x-Eudora-option:SSLSendPrivateKey>
< x-Eudora-option:SSLSendPrivateKeyPassword>
< X-Eudora-Option:SSLSendUse>
< X-Eudora-Option:SSLSendVersion>
< X-Eudora-Option:SSLSendVersion3>
Might someone be able to direct me to where I might find the details
on these option settings?
Thank you in advance.
_______________________________________________
Hermesmail-discuss mailing list
Her...@li...
https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss
______________________________________________________________________________________________________________________________________ |
|
From: Michael O. <ref...@ou...> - 2021-02-17 19:09:22
|
<html> <body> <br> I have been getting 10054 errors while sending email. No issues receiving mail, just sending. Sometime merely retrying the send works for smaller message, but if there are embedded images or attachments that doesn't work. My email provider provided the following from one of the failures <dl> <dd>Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 947731 mail.warning] warning: TLS library problem: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac:s3_pkt.c:535: 2:49 <dd>Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 197553 mail.info] lost connection after DATA (5739 bytes) from unknown[x.x.x.x] </dl>I have tried another email app (Pandors) and it does not have the same issue. So, I am looking to tweak the SSLSend options in Eudora.ini to see if I can resolve this issus with OpenSSL. However, I have been able to find any detail explanations of the following settings and the Eudora/Hermes pop-up for the option is singularly un-enlightening.<br><br> <dl> <dd><<a href="x-eudora-option:SSLSendAllowRegExp" eudora="autourl"> X-Eudora-Option:SSLSendAllowRegExp</a>> <dd><<a href="x-eudora-option:SSLSendAllowVersion2" eudora="autourl"> X-Eudora-Option:SSLSendAllowVersion2</a>> <dd><<a href="x-eudora-option:SSLSendCipherSuite" eudora="autourl"> X-Eudora-Option:SSLSendCipherSuite</a>> <dd><<a href="x-eudora-option:SSLSendClientCertsFile" eudora="autourl"> X-Eudora-Option:SSLSendClientCertsFile</a>> <dd><<a href="x-eudora-option:SSLSendClientCertsInfo" eudora="autourl"> X-Eudora-Option:SSLSendClientCertsInfo</a>> <dd><<a href="x-eudora-option:SSLSendIgnoreExpCert" eudora="autourl"> X-Eudora-Option:SSLSendIgnoreExpCert</a>> <dd><<a href="x-eudora-option:SSLSendLogSession" eudora="autourl"> X-Eudora-Option:SSLSendLogSession</a>> <dd><<a href="x-eudora-option:SSLSendMinEncryption" eudora="autourl"> X-Eudora-Option:SSLSendMinEncryption</a>> <dd> <<a href="x-eudora-option:SSLSendMinKeyExchangeLength" eudora="autourl"> X-Eudora-Option:SSLSendMinKeyExchangeLength</a>> <dd><<a href="x-eudora-option:SSLSendPrivateKey" eudora="autourl"> x-Eudora-option:SSLSendPrivateKey</a>> <dd> <<a href="x-eudora-option:SSLSendPrivateKeyPassword" eudora="autourl"> x-Eudora-option:SSLSendPrivateKeyPassword</a>> <dd><<a href="x-eudora-option:SSLSendUse" eudora="autourl"> X-Eudora-Option:SSLSendUse</a>> <dd><<a href="x-eudora-option:SSLSendVersion" eudora="autourl"> X-Eudora-Option:SSLSendVersion</a>> <dd><<a href="x-eudora-option:SSLSendVersion3" eudora="autourl"> X-Eudora-Option:SSLSendVersion3</a>> </dl>Might someone be able to direct me to where I might find the details on these option settings?<br><br> Thank you in advance.<br><br> <br><br> <br> </body> <br> </html> |
|
From: Curtis M. <cm...@db...> - 2021-01-14 21:42:56
|
Hi Ronald, I have a no longer-used licensed copy of Wintertree (Dec 2004) that I can provide with a license key, along with US-English, German and Finnish dictionaries. -Curtis At 02:08 PM 1/14/2021, Ronald van Ginkel wrote: >Hi guys. > >This is how things are actually: > >I have contacted Leon Shustek from The Computer >History Museum, who is the one who got the >source code from Qualcomm. He has treated me >very kindly and provided very useful information: > >- In the version published by the museum, 5 files are missing: > >Spell checker (Wintertree-software): >spell.cpp >scce.h (I have found it on the internet and added to the project) > >Combobox for embedding in a SECCustomToolBar (Stingray): >TBarBmpCombo.cpp >TBarStatic.cpp >TBarEdit.cpp > >- Wintertree also required to change the prefix >of the SCCE_ * functions to SpellCheck_ *, which >generated a lot of compilation errors. I have >undone the change and these errors are gone. > >- I keep trying to compile the original project >(the museum version) in Visual Studio 2017. >There are more than 1,000 errors, but most of >them are repetitive. I´m solving the most obvious and easy ones. >One of these errors (which generates 440 errors) >I have posted on StackOverflow for help as it is >beyond my knowledge. If anyone in this group >knows how to solve it, I would be very grateful. > >https://stackoverflow.com/questions/65718797/a-bit-complex-c2102-requires-l-value-error/65718881#65718881 > >I think the goal of compiling a version of >Eudora without the spell checker and without the >Combobox control seems quite accessible. > >I will continue to move forward with the idea of minimizing errors. > >Keep in touch > >Ronald > >______________________________________________________________________________________________________________________________________ > >Hi Curtis. > >Thank you for your clarifyng answer. > >Pete explained Stingray issue two week ago. It >seems there's not an easy solution cause Eudora >is using a custom Stingray library. > >Anyway, I shall contact Perforce to see if we can move forward. > >I shall keep you informed. > >Regards! > >Ronald > >______________________________________________________________________________________________________________________________________ >Hi Pete, >I think Ron is asking whether anybody has >successfully assembled an environment in which >Eudora can be compiled from source code released >by the museum. I suspect that the answer is no, >given the Stingray obstacle. The spell checker >should be no big deal - there are quite a few at >Nuget with an Apache license. For Stingray, it >might be a good idea to open a dialog with >Perforce - >https://www.perforce.com/products/stingray. They >do not provide pricing information - >https://www.perforce.com/how-buy - which >suggests that it is quite pricey. But it is also >possible that they might be willing to cooperate >with an open-source product in exchange for free >advertising, esp. given that most of us still >using Eudora (and those who wish they could use >it again) -- are software developers or in a >related profession. Those that are not still >tend to be scientists or researchers at academic institutions. > >Currently the biggest problem with Eudora is the >character encoding issue. Daniel Kuhn has >created a semi-effective Delphi plug-in ( >http://www.windharp.de/software/utf8iso.htm) but >lost the source code. Surely that he could >outline its operation. A plug-in just has to >compile to a Win-32 DLL so it's >language-agnostic. Another minor problem is the >mailbox limit of 2GB, but I can live with that. >HTML rendering is another, but lesser issue, >along with inability to decode some types of embedded images. > >I still use Eudora on my 8 or 10 email accounts >- with some mailboxes dating back to 1996 or so. >Occasionally I have to log into a websmail >service or gmail to deal with particularly >recalcitrant messages. With the TLS changes >already done, a good UTF8 plugin would be a huge >step forward, pending the more difficult issue >of actually getting the ^&#&$ thing to compile! >Curtis > > > >At 03:35 PM 1/9/2021, Pete Maclean wrote: >>Ron, >> >>>- Is there any source code that can be compiled in anyway ? >> >>I do not understand this question. >> >>>- If it is not: >>> >>> - What source code and environment >>> are the best to begin to fight with ? >> >>I recommend starting with the raw code that was >>published as open source rather than the Hermes repository. >> >>> - Is there an unavoidable obstacle >>> that prevents compiling the source code? >> >>Yes. The main obstacle is the Stingray >>library. It is an obstacle in several ways >>especially in that Eudora was built using a >>customized version of it and we do not have >>documentation on those customizations. Another >>minor obstacle is that Eudora uses a spell >>checker that is a commercial product. >> >>Pete Maclean >> >>At 07:28 AM 1/9/2021, Ronald van Ginkel wrote: >> >>>Hi Curtis. >>> >>>Yes, I'm afraid all of us are short of time, >>>but for me, Eudora is my main tool for my >>>work, so I wanna invest some time and resources on it. >>> >>>Thank you for your offer, but I also have all >>>VS versions (I'm Microsoft Silver Partner), >>>but I need to know what is the first step. >>> >>>As I see, Eudora 'museum' code needs VS 2003: >>> >>>>Eudora.vcproj >>> >>>><VisualStudioProject >>>> ProjectType="Visual C++" >>>> Version="7.10" >>> >>> >>>But Hermes code needs VS 2015: >>> >>>>Eudora.vcxproj >>> >>>><Project DefaultTargets="Build" ToolsVersion="15.0" >>> >>> >>>And as I see, Hermes installer's eudora.exe is >>>the original one, so it seems it's no been compiled recently. >>> >>> >>>So, my point is: >>> >>>- Is there any source code that can be compiled in anyway ? >>> >>>- If it is not: >>> >>> - What source code and environment >>> are the best to begin to fight with ? >>> >>> - Is there an unavoidable obstacle >>> that prevents compiling the source code? >>> >>>Regards! >>> >>>Ronald >>> >>>______________________________________________________________________________________________________________________________________ >>>Hi Ronald, >>>If you would like to give it a go I have VS >>>2005 Pro. I can send an ISO image and license key. Wish I had more time! >>>Regards, >>>Curtis Meadow >>> >>>At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: >>> >>>>Hi Steve. >>>> >>>>Thank you for your answer, but the only thing >>>>I need to know is if it is possible to >>>>compile the source code of Eudora or Hermes >>>>and what is the necessary environment to do it. >>>> >>>> From here I will be able to understand where >>>> the project is standing and see if I can help in any way. >>>> >>>>Regards! >>>> >>>>Ronald >>>>______________________________________________________________________________________________________________________________________ >>>>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >>>> >>>>>Hi Steve. >>>>> >>>>>I took a way, but I finally could setup a >>>>>Virtual Machine with Windows XP 32 Bits >>>>>(Visual Studio 2002 cannot be installed on a >>>>>64 bits OS), installed VS2002 and imported Hermes project. >>>>> >>>>>... but it cannot been compiled. >>>>> >>>>>As I see, project file needs at least 2010 version. >>>>> >>>>>I've installed a VS2010 and tried to >>>>>compiled, but I get a lot of errors, most of >>>>>them due to the use of 'noexcept' expression >>>>>that it's only supported at VS 2015 or >>>>>above, and with VS2015 I get tons of errors trying to compile. >>>>> >>>>>Can anyone tell me is there a way to compile the source code ? >>>>> >>>>>Thank you in advance. >>>>> >>>>>Ronald >>>> >>>>Ronald, >>>> >>>>My main development machine keeps changing, >>>>and I have changed motherboards 1-2 times in >>>>recent years, so the environment I first >>>>tested the Eudora source code in no longer >>>>exists. This pre-dated the 'Hermes' project >>>>by several months at least. I don't have the >>>>'Hermes Project' files. I have the files >>>>that were released from the Computer Museum that Qualcomm authorized. >>>> >>>>A little common sense: VS2010 didn't exist >>>>at the time of the final release of Eudora, >>>>so it couldn't have been the required version. >>>> >>>>When a newer version of Visual Studio tries >>>>to open a project from a previous version of >>>>Visual Studio, it will convert the old >>>>project file to the new project file. It >>>>also shows a warning box on the screen when >>>>it does this, and gives you the option to >>>>save the old version unmodified but you have >>>>to enter a new name for the old file to >>>>use. So if you had initially tried to >>>>compile the source code with VS2010, the project file was converted. >>>> >>>>I don't presently have Visual Studio 2002 >>>>installed. I did have it installed in a >>>>64-bit Windows 7 environment. As I recall, >>>>it wasn't easy to install. I just finished a >>>>search, and I found some install instructions >>>>which say that to install it, you need to not >>>>already have newer versions of Visual Studio >>>>on the system, and there were a couple of >>>>specific items you need to check-off and not install, for it to work. >>>> >>>>Use of Windows XP to make a compiling >>>>environment is a common work around for these >>>>kinds of problems. I recently (recent defined >>>>as within the past 2 years) had to run a >>>>16-bit program that was compiled using >>>>QuickBasic. I had to do the same thing, as >>>>Windows XP could run 16-bit programs. I soon >>>>went to some trouble to write a replacement >>>>program that runs in a 64-bit environment. >>>> >>>>I don't know anything about this 'noexcept' >>>>expression you are talking about, and >>>>anything I say is going to be speculation. I >>>>generally do most of my work in older versions of Visual Studio. >>>> >>>>Steve >>>> >>>> >>>>_______________________________________________ >>>>Hermesmail-discuss mailing list >>>>Her...@li... >>>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>>> >>>> >>>>______________________________________________________________________________________________________________________________________ >>>> >>>>_______________________________________________ >>>>Hermesmail-discuss mailing list >>>>Her...@li... >>>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>> >>> >>> >>>______________________________________________________________________________________________________________________________________ >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > > > >______________________________________________________________________________________________________________________________________ > >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > >______________________________________________________________________________________________________________________________________ > |
|
From: Ronald v. G. <ro...@t-...> - 2021-01-14 19:12:09
|
Hi guys. This is how things are actually: I have contacted Leon Shustek from The Computer History Museum, who is the one who got the source code from Qualcomm. He has treated me very kindly and provided very useful information: - In the version published by the museum, 5 files are missing: Spell checker (Wintertree-software): spell.cpp scce.h (I have found it on the internet and added to the project) Combobox for embedding in a SECCustomToolBar (Stingray): TBarBmpCombo.cpp TBarStatic.cpp TBarEdit.cpp - Wintertree also required to change the prefix of the SCCE_ * functions to SpellCheck_ *, which generated a lot of compilation errors. I have undone the change and these errors are gone. - I keep trying to compile the original project (the museum version) in Visual Studio 2017. There are more than 1,000 errors, but most of them are repetitive. I´m solving the most obvious and easy ones. One of these errors (which generates 440 errors) I have posted on StackOverflow for help as it is beyond my knowledge. If anyone in this group knows how to solve it, I would be very grateful. https://stackoverflow.com/questions/65718797/a-bit-complex-c2102-requires-l-value-error/65718881#65718881 I think the goal of compiling a version of Eudora without the spell checker and without the Combobox control seems quite accessible. I will continue to move forward with the idea of minimizing errors. Keep in touch Ronald ______________________________________________________________________________________________________________________________________ Hi Curtis. Thank you for your clarifyng answer. Pete explained Stingray issue two week ago. It seems there's not an easy solution cause Eudora is using a custom Stingray library. Anyway, I shall contact Perforce to see if we can move forward. I shall keep you informed. Regards! Ronald ______________________________________________________________________________________________________________________________________ Hi Pete, I think Ron is asking whether anybody has successfully assembled an environment in which Eudora can be compiled from source code released by the museum. I suspect that the answer is no, given the Stingray obstacle. The spell checker should be no big deal - there are quite a few at Nuget with an Apache license. For Stingray, it might be a good idea to open a dialog with Perforce - https://www.perforce.com/products/stingray. They do not provide pricing information - https://www.perforce.com/how-buy - which suggests that it is quite pricey. But it is also possible that they might be willing to cooperate with an open-source product in exchange for free advertising, esp. given that most of us still using Eudora (and those who wish they could use it again) -- are software developers or in a related profession. Those that are not still tend to be scientists or researchers at academic institutions. Currently the biggest problem with Eudora is the character encoding issue. Daniel Kuhn has created a semi-effective Delphi plug-in ( http://www.windharp.de/software/utf8iso.htm) but lost the source code. Surely that he could outline its operation. A plug-in just has to compile to a Win-32 DLL so it's language-agnostic. Another minor problem is the mailbox limit of 2GB, but I can live with that. HTML rendering is another, but lesser issue, along with inability to decode some types of embedded images. I still use Eudora on my 8 or 10 email accounts - with some mailboxes dating back to 1996 or so. Occasionally I have to log into a websmail service or gmail to deal with particularly recalcitrant messages. With the TLS changes already done, a good UTF8 plugin would be a huge step forward, pending the more difficult issue of actually getting the ^&#&$ thing to compile! Curtis At 03:35 PM 1/9/2021, Pete Maclean wrote: >Ron, > >>- Is there any source code that can be compiled in anyway ? > >I do not understand this question. > >>- If it is not: >> >> - What source code and environment are >> the best to begin to fight with ? > >I recommend starting with the raw code that was >published as open source rather than the Hermes repository. > >> - Is there an unavoidable obstacle >> that prevents compiling the source code? > >Yes. The main obstacle is the Stingray >library. It is an obstacle in several ways >especially in that Eudora was built using a >customized version of it and we do not have >documentation on those customizations. Another >minor obstacle is that Eudora uses a spell >checker that is a commercial product. > >Pete Maclean > >At 07:28 AM 1/9/2021, Ronald van Ginkel wrote: > >>Hi Curtis. >> >>Yes, I'm afraid all of us are short of time, >>but for me, Eudora is my main tool for my work, >>so I wanna invest some time and resources on it. >> >>Thank you for your offer, but I also have all >>VS versions (I'm Microsoft Silver Partner), but >>I need to know what is the first step. >> >>As I see, Eudora 'museum' code needs VS 2003: >> >>>Eudora.vcproj >> >>><VisualStudioProject >>> ProjectType="Visual C++" >>> Version="7.10" >> >> >>But Hermes code needs VS 2015: >> >>>Eudora.vcxproj >> >>><Project DefaultTargets="Build" ToolsVersion="15.0" >> >> >>And as I see, Hermes installer's eudora.exe is >>the original one, so it seems it's no been compiled recently. >> >> >>So, my point is: >> >>- Is there any source code that can be compiled in anyway ? >> >>- If it is not: >> >> - What source code and environment are >> the best to begin to fight with ? >> >> - Is there an unavoidable obstacle >> that prevents compiling the source code? >> >>Regards! >> >>Ronald >> >>______________________________________________________________________________________________________________________________________ >>Hi Ronald, >>If you would like to give it a go I have VS >>2005 Pro. I can send an ISO image and license key. Wish I had more time! >>Regards, >>Curtis Meadow >> >>At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: >> >>>Hi Steve. >>> >>>Thank you for your answer, but the only thing >>>I need to know is if it is possible to compile >>>the source code of Eudora or Hermes and what >>>is the necessary environment to do it. >>> >>> From here I will be able to understand where >>> the project is standing and see if I can help in any way. >>> >>>Regards! >>> >>>Ronald >>>______________________________________________________________________________________________________________________________________ >>>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >>> >>>>Hi Steve. >>>> >>>>I took a way, but I finally could setup a >>>>Virtual Machine with Windows XP 32 Bits >>>>(Visual Studio 2002 cannot be installed on a >>>>64 bits OS), installed VS2002 and imported Hermes project. >>>> >>>>... but it cannot been compiled. >>>> >>>>As I see, project file needs at least 2010 version. >>>> >>>>I've installed a VS2010 and tried to >>>>compiled, but I get a lot of errors, most of >>>>them due to the use of 'noexcept' expression >>>>that it's only supported at VS 2015 or above, >>>>and with VS2015 I get tons of errors trying to compile. >>>> >>>>Can anyone tell me is there a way to compile the source code ? >>>> >>>>Thank you in advance. >>>> >>>>Ronald >>> >>>Ronald, >>> >>>My main development machine keeps changing, >>>and I have changed motherboards 1-2 times in >>>recent years, so the environment I first >>>tested the Eudora source code in no longer >>>exists. This pre-dated the 'Hermes' project >>>by several months at least. I don't have the >>>'Hermes Project' files. I have the files that >>>were released from the Computer Museum that Qualcomm authorized. >>> >>>A little common sense: VS2010 didn't exist at >>>the time of the final release of Eudora, so it >>>couldn't have been the required version. >>> >>>When a newer version of Visual Studio tries to >>>open a project from a previous version of >>>Visual Studio, it will convert the old project >>>file to the new project file. It also shows a >>>warning box on the screen when it does this, >>>and gives you the option to save the old >>>version unmodified but you have to enter a new >>>name for the old file to use. So if you had >>>initially tried to compile the source code >>>with VS2010, the project file was converted. >>> >>>I don't presently have Visual Studio 2002 >>>installed. I did have it installed in a >>>64-bit Windows 7 environment. As I recall, it >>>wasn't easy to install. I just finished a >>>search, and I found some install instructions >>>which say that to install it, you need to not >>>already have newer versions of Visual Studio >>>on the system, and there were a couple of >>>specific items you need to check-off and not install, for it to work. >>> >>>Use of Windows XP to make a compiling >>>environment is a common work around for these >>>kinds of problems. I recently (recent defined >>>as within the past 2 years) had to run a >>>16-bit program that was compiled using >>>QuickBasic. I had to do the same thing, as >>>Windows XP could run 16-bit programs. I soon >>>went to some trouble to write a replacement >>>program that runs in a 64-bit environment. >>> >>>I don't know anything about this 'noexcept' >>>expression you are talking about, and anything >>>I say is going to be speculation. I generally >>>do most of my work in older versions of Visual Studio. >>> >>>Steve >>> >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>> >>> >>>______________________________________________________________________________________________________________________________________ >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> >> >> >>______________________________________________________________________________________________________________________________________ >> >>_______________________________________________ >>Hermesmail-discuss mailing list >>Her...@li... >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss ______________________________________________________________________________________________________________________________________ _______________________________________________ Hermesmail-discuss mailing list Her...@li... https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss ______________________________________________________________________________________________________________________________________ |
|
From: Ronald v. G. <ro...@t-...> - 2021-01-11 14:00:13
|
Hi Curtis. Thank you for your clarifyng answer. Pete explained Stingray issue two week ago. It seems there's not an easy solution cause Eudora is using a custom Stingray library. Anyway, I shall contact Perforce to see if we can move forward. I shall keep you informed. Regards! Ronald ______________________________________________________________________________________________________________________________________ Hi Pete, I think Ron is asking whether anybody has successfully assembled an environment in which Eudora can be compiled from source code released by the museum. I suspect that the answer is no, given the Stingray obstacle. The spell checker should be no big deal - there are quite a few at Nuget with an Apache license. For Stingray, it might be a good idea to open a dialog with Perforce - https://www.perforce.com/products/stingray. They do not provide pricing information - https://www.perforce.com/how-buy - which suggests that it is quite pricey. But it is also possible that they might be willing to cooperate with an open-source product in exchange for free advertising, esp. given that most of us still using Eudora (and those who wish they could use it again) -- are software developers or in a related profession. Those that are not still tend to be scientists or researchers at academic institutions. Currently the biggest problem with Eudora is the character encoding issue. Daniel Kuhn has created a semi-effective Delphi plug-in (http://www.windharp.de/software/utf8iso.htm) but lost the source code. Surely that he could outline its operation. A plug-in just has to compile to a Win-32 DLL so it's language-agnostic. Another minor problem is the mailbox limit of 2GB, but I can live with that. HTML rendering is another, but lesser issue, along with inability to decode some types of embedded images. I still use Eudora on my 8 or 10 email accounts - with some mailboxes dating back to 1996 or so. Occasionally I have to log into a websmail service or gmail to deal with particularly recalcitrant messages. With the TLS changes already done, a good UTF8 plugin would be a huge step forward, pending the more difficult issue of actually getting the ^&#&$ thing to compile! Curtis At 03:35 PM 1/9/2021, Pete Maclean wrote: >Ron, > >>- Is there any source code that can be compiled in anyway ? > >I do not understand this question. > >>- If it is not: >> >> - What source code and environment are the best to begin >> to fight with ? > >I recommend starting with the raw code that was published as open >source rather than the Hermes repository. > >> - Is there an unavoidable obstacle that prevents compiling >> the source code? > >Yes. The main obstacle is the Stingray library. It is an obstacle >in several ways especially in that Eudora was built using a >customized version of it and we do not have documentation on those >customizations. Another minor obstacle is that Eudora uses a spell >checker that is a commercial product. > >Pete Maclean > >At 07:28 AM 1/9/2021, Ronald van Ginkel wrote: > >>Hi Curtis. >> >>Yes, I'm afraid all of us are short of time, but for me, Eudora is >>my main tool for my work, so I wanna invest some time and resources on it. >> >>Thank you for your offer, but I also have all VS versions (I'm >>Microsoft Silver Partner), but I need to know what is the first step. >> >>As I see, Eudora 'museum' code needs VS 2003: >> >>>Eudora.vcproj >> >>><VisualStudioProject >>> ProjectType="Visual C++" >>> Version="7.10" >> >> >>But Hermes code needs VS 2015: >> >>>Eudora.vcxproj >> >>><Project DefaultTargets="Build" ToolsVersion="15.0" >> >> >>And as I see, Hermes installer's eudora.exe is the original one, so >>it seems it's no been compiled recently. >> >> >>So, my point is: >> >>- Is there any source code that can be compiled in anyway ? >> >>- If it is not: >> >> - What source code and environment are the best to begin >> to fight with ? >> >> - Is there an unavoidable obstacle that prevents compiling >> the source code? >> >>Regards! >> >>Ronald >> >>______________________________________________________________________________________________________________________________________ >>Hi Ronald, >>If you would like to give it a go I have VS 2005 Pro. I can send an >>ISO image and license key. Wish I had more time! >>Regards, >>Curtis Meadow >> >>At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: >> >>>Hi Steve. >>> >>>Thank you for your answer, but the only thing I need to know is if >>>it is possible to compile the source code of Eudora or Hermes and >>>what is the necessary environment to do it. >>> >>> From here I will be able to understand where the project is >>> standing and see if I can help in any way. >>> >>>Regards! >>> >>>Ronald >>>______________________________________________________________________________________________________________________________________ >>>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >>> >>>>Hi Steve. >>>> >>>>I took a way, but I finally could setup a Virtual Machine with >>>>Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a >>>>64 bits OS), installed VS2002 and imported Hermes project. >>>> >>>>... but it cannot been compiled. >>>> >>>>As I see, project file needs at least 2010 version. >>>> >>>>I've installed a VS2010 and tried to compiled, but I get a lot of >>>>errors, most of them due to the use of 'noexcept' expression that >>>>it's only supported at VS 2015 or above, and with VS2015 I get >>>>tons of errors trying to compile. >>>> >>>>Can anyone tell me is there a way to compile the source code ? >>>> >>>>Thank you in advance. >>>> >>>>Ronald >>> >>>Ronald, >>> >>>My main development machine keeps changing, and I have changed >>>motherboards 1-2 times in recent years, so the environment I first >>>tested the Eudora source code in no longer exists. This pre-dated >>>the 'Hermes' project by several months at least. I don't have the >>>'Hermes Project' files. I have the files that were released from >>>the Computer Museum that Qualcomm authorized. >>> >>>A little common sense: VS2010 didn't exist at the time of the >>>final release of Eudora, so it couldn't have been the required version. >>> >>>When a newer version of Visual Studio tries to open a project from >>>a previous version of Visual Studio, it will convert the old >>>project file to the new project file. It also shows a warning box >>>on the screen when it does this, and gives you the option to save >>>the old version unmodified but you have to enter a new name for >>>the old file to use. So if you had initially tried to compile the >>>source code with VS2010, the project file was converted. >>> >>>I don't presently have Visual Studio 2002 installed. I did have >>>it installed in a 64-bit Windows 7 environment. As I recall, it >>>wasn't easy to install. I just finished a search, and I found >>>some install instructions which say that to install it, you need >>>to not already have newer versions of Visual Studio on the system, >>>and there were a couple of specific items you need to check-off >>>and not install, for it to work. >>> >>>Use of Windows XP to make a compiling environment is a common work >>>around for these kinds of problems. I recently (recent defined as >>>within the past 2 years) had to run a 16-bit program that was >>>compiled using QuickBasic. I had to do the same thing, as Windows >>>XP could run 16-bit programs. I soon went to some trouble to >>>write a replacement program that runs in a 64-bit environment. >>> >>>I don't know anything about this 'noexcept' expression you are >>>talking about, and anything I say is going to be speculation. I >>>generally do most of my work in older versions of Visual Studio. >>> >>>Steve >>> >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>> >>> >>>______________________________________________________________________________________________________________________________________ >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> >> >> >>______________________________________________________________________________________________________________________________________ >> >>_______________________________________________ >>Hermesmail-discuss mailing list >>Her...@li... >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss ______________________________________________________________________________________________________________________________________ |
|
From: Jason S. <ja...@sh...> - 2021-01-10 02:18:55
|
Hello whoever you are. Rest assured, the issue you're seeing is not one related to Hermes or Eudora per se. Instead, it's a general issue as seen from time to time by many users of OpenSSL. OpenSSL is the software on your provider's server that is responsible for the encryption element of a TLS mail exchange session. In particular, that error can show up in log entries on the server side of a TLS connection. What it means is that there was a problem keeping the encryption stream stable between the two endpoints. This is normally due to intermittent network problems (perhaps lost/dropped packs or TCP issues) which affect the message authentication context (mac) of the TLS session. It can also be caused by any software or processes that scan TLS sessions such as anti-virus or organization-wide network security appliances that attempt to decode TLS sessions in real time. The problem is likely somewhere in the network layer. You should definitely run some network integrity checks between you and your provider. Jason At 05:11 PM 09/01/2021, you wrote: >My provider has provided a couple of log entries relating to my >issue. Has anyone seen this type of problem? > >Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 947731 >mail.warning] warning: TLS library problem: error:1408F119:SSL >routines:SSL3_GET_RECORD:decryption failed or bad record mac:s3_pkt.c:535: 2:49 >Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 197553 >mail.info] lost connection after DATA (5739 bytes) from unknown[x.x.x.x] |
|
From: Curtis M. <cm...@db...> - 2021-01-10 01:52:03
|
Hi Pete, I think Ron is asking whether anybody has successfully assembled an environment in which Eudora can be compiled from source code released by the museum. I suspect that the answer is no, given the Stingray obstacle. The spell checker should be no big deal - there are quite a few at Nuget with an Apache license. For Stingray, it might be a good idea to open a dialog with Perforce - https://www.perforce.com/products/stingray. They do not provide pricing information - https://www.perforce.com/how-buy - which suggests that it is quite pricey. But it is also possible that they might be willing to cooperate with an open-source product in exchange for free advertising, esp. given that most of us still using Eudora (and those who wish they could use it again) -- are software developers or in a related profession. Those that are not still tend to be scientists or researchers at academic institutions. Currently the biggest problem with Eudora is the character encoding issue. Daniel Kuhn has created a semi-effective Delphi plug-in (http://www.windharp.de/software/utf8iso.htm) but lost the source code. Surely that he could outline its operation. A plug-in just has to compile to a Win-32 DLL so it's language-agnostic. Another minor problem is the mailbox limit of 2GB, but I can live with that. HTML rendering is another, but lesser issue, along with inability to decode some types of embedded images. I still use Eudora on my 8 or 10 email accounts - with some mailboxes dating back to 1996 or so. Occasionally I have to log into a websmail service or gmail to deal with particularly recalcitrant messages. With the TLS changes already done, a good UTF8 plugin would be a huge step forward, pending the more difficult issue of actually getting the ^&#&$ thing to compile! Curtis At 03:35 PM 1/9/2021, Pete Maclean wrote: >Ron, > >>- Is there any source code that can be compiled in anyway ? > >I do not understand this question. > >>- If it is not: >> >> - What source code and environment are the best to begin >> to fight with ? > >I recommend starting with the raw code that was published as open >source rather than the Hermes repository. > >> - Is there an unavoidable obstacle that prevents compiling >> the source code? > >Yes. The main obstacle is the Stingray library. It is an obstacle >in several ways especially in that Eudora was built using a >customized version of it and we do not have documentation on those >customizations. Another minor obstacle is that Eudora uses a spell >checker that is a commercial product. > >Pete Maclean > >At 07:28 AM 1/9/2021, Ronald van Ginkel wrote: > >>Hi Curtis. >> >>Yes, I'm afraid all of us are short of time, but for me, Eudora is >>my main tool for my work, so I wanna invest some time and resources on it. >> >>Thank you for your offer, but I also have all VS versions (I'm >>Microsoft Silver Partner), but I need to know what is the first step. >> >>As I see, Eudora 'museum' code needs VS 2003: >> >>>Eudora.vcproj >> >>><VisualStudioProject >>> ProjectType="Visual C++" >>> Version="7.10" >> >> >>But Hermes code needs VS 2015: >> >>>Eudora.vcxproj >> >>><Project DefaultTargets="Build" ToolsVersion="15.0" >> >> >>And as I see, Hermes installer's eudora.exe is the original one, so >>it seems it's no been compiled recently. >> >> >>So, my point is: >> >>- Is there any source code that can be compiled in anyway ? >> >>- If it is not: >> >> - What source code and environment are the best to begin >> to fight with ? >> >> - Is there an unavoidable obstacle that prevents compiling >> the source code? >> >>Regards! >> >>Ronald >> >>______________________________________________________________________________________________________________________________________ >>Hi Ronald, >>If you would like to give it a go I have VS 2005 Pro. I can send an >>ISO image and license key. Wish I had more time! >>Regards, >>Curtis Meadow >> >>At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: >> >>>Hi Steve. >>> >>>Thank you for your answer, but the only thing I need to know is if >>>it is possible to compile the source code of Eudora or Hermes and >>>what is the necessary environment to do it. >>> >>> From here I will be able to understand where the project is >>> standing and see if I can help in any way. >>> >>>Regards! >>> >>>Ronald >>>______________________________________________________________________________________________________________________________________ >>>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >>> >>>>Hi Steve. >>>> >>>>I took a way, but I finally could setup a Virtual Machine with >>>>Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a >>>>64 bits OS), installed VS2002 and imported Hermes project. >>>> >>>>... but it cannot been compiled. >>>> >>>>As I see, project file needs at least 2010 version. >>>> >>>>I've installed a VS2010 and tried to compiled, but I get a lot of >>>>errors, most of them due to the use of 'noexcept' expression that >>>>it's only supported at VS 2015 or above, and with VS2015 I get >>>>tons of errors trying to compile. >>>> >>>>Can anyone tell me is there a way to compile the source code ? >>>> >>>>Thank you in advance. >>>> >>>>Ronald >>> >>>Ronald, >>> >>>My main development machine keeps changing, and I have changed >>>motherboards 1-2 times in recent years, so the environment I first >>>tested the Eudora source code in no longer exists. This pre-dated >>>the 'Hermes' project by several months at least. I don't have the >>>'Hermes Project' files. I have the files that were released from >>>the Computer Museum that Qualcomm authorized. >>> >>>A little common sense: VS2010 didn't exist at the time of the >>>final release of Eudora, so it couldn't have been the required version. >>> >>>When a newer version of Visual Studio tries to open a project from >>>a previous version of Visual Studio, it will convert the old >>>project file to the new project file. It also shows a warning box >>>on the screen when it does this, and gives you the option to save >>>the old version unmodified but you have to enter a new name for >>>the old file to use. So if you had initially tried to compile the >>>source code with VS2010, the project file was converted. >>> >>>I don't presently have Visual Studio 2002 installed. I did have >>>it installed in a 64-bit Windows 7 environment. As I recall, it >>>wasn't easy to install. I just finished a search, and I found >>>some install instructions which say that to install it, you need >>>to not already have newer versions of Visual Studio on the system, >>>and there were a couple of specific items you need to check-off >>>and not install, for it to work. >>> >>>Use of Windows XP to make a compiling environment is a common work >>>around for these kinds of problems. I recently (recent defined as >>>within the past 2 years) had to run a 16-bit program that was >>>compiled using QuickBasic. I had to do the same thing, as Windows >>>XP could run 16-bit programs. I soon went to some trouble to >>>write a replacement program that runs in a 64-bit environment. >>> >>>I don't know anything about this 'noexcept' expression you are >>>talking about, and anything I say is going to be speculation. I >>>generally do most of my work in older versions of Visual Studio. >>> >>>Steve >>> >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >>> >>> >>>______________________________________________________________________________________________________________________________________ >>> >>>_______________________________________________ >>>Hermesmail-discuss mailing list >>>Her...@li... >>>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> >> >> >>______________________________________________________________________________________________________________________________________ >> >>_______________________________________________ >>Hermesmail-discuss mailing list >>Her...@li... >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss |
|
From: <ref...@ou...> - 2021-01-09 22:12:10
|
My provider has provided a couple of log entries relating to my issue. Has anyone seen this type of problem? Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 947731 mail.warning] warning: TLS library problem: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac:s3_pkt.c:535: 2:49 Dec 17 20:28:24 pb-smtp21 postfix-sasl-smtpd[80996]: [ID 197553 mail.info] lost connection after DATA (5739 bytes) from unknown[x.x.x.x] |
|
From: Pete M. <gr...@ma...> - 2021-01-09 20:36:49
|
<html> <body> <font size=3>Ron,<br><br> <blockquote type=cite class=cite cite="">- Is there any source code that can be compiled in anyway ?</font></blockquote><br> I do not understand this question.<br><br> <blockquote type=cite class=cite cite=""><font size=3>- If it is not:<br><br> <x-tab> </x-tab>- What source code and environment are the best to begin to fight with ?</font></blockquote><br> I recommend starting with the raw code that was published as open source rather than the Hermes repository.<br><br> <blockquote type=cite class=cite cite=""><font size=3><x-tab> </x-tab>- Is there an unavoidable obstacle that prevents compiling the source code?</font></blockquote><br> Yes. The main obstacle is the Stingray library. It is an obstacle in several ways especially in that Eudora was built using a customized version of it and we do not have documentation on those customizations. Another minor obstacle is that Eudora uses a spell checker that is a commercial product.<br><br> <font size=3>Pete Maclean<br><br> At 07:28 AM 1/9/2021, Ronald van Ginkel wrote:<br><br> <blockquote type=cite class=cite cite="">Hi Curtis.<br><br> Yes, I'm afraid all of us are short of time, but for me, Eudora is my main tool for my work, so I wanna invest some time and resources on it.<br><br> Thank you for your offer, but I also have all VS versions (I'm Microsoft Silver Partner), but I need to know what is the first step.<br><br> As I see, Eudora 'museum' code needs VS 2003:<br><br> <blockquote type=cite class=cite cite="">Eudora.vcproj</blockquote><br> <blockquote type=cite class=cite cite=""><VisualStudioProject<br> <x-tab> </x-tab> ProjectType="Visual C++"<br> <x-tab> </x-tab> Version="7.10"</blockquote><br><br> But Hermes code needs VS 2015:<br><br> <blockquote type=cite class=cite cite="">Eudora.vcxproj</blockquote><br> <blockquote type=cite class=cite cite=""><Project DefaultTargets="Build" ToolsVersion="15.0" </blockquote><br><br> And as I see, Hermes installer's eudora.exe is the original one, so it seems it's no been compiled recently.<br><br> <br> So, my point is:<br><br> - Is there any source code that can be compiled in anyway ?<br><br> - If it is not:<br><br> <x-tab> </x-tab>- What source code and environment are the best to begin to fight with ?<br><br> <x-tab> </x-tab>- Is there an unavoidable obstacle that prevents compiling the source code?<br><br> Regards!<br><br> Ronald<br><br> ______________________________________________________________________________________________________________________________________<br> Hi Ronald,<br> If you would like to give it a go I have VS 2005 Pro. I can send an ISO image and license key. Wish I had more time!<br> Regards,<br> Curtis Meadow<br><br> At 12:33 PM 1/8/2021, Ronald van Ginkel wrote:<br><br> <blockquote type=cite class=cite cite="">Hi Steve.<br><br> Thank you for your answer, but the only thing I need to know is if it is possible to compile the source code of Eudora or Hermes and what is the necessary environment to do it.<br><br> From here I will be able to understand where the project is standing and see if I can help in any way.<br><br> Regards!<br><br> Ronald<br> ______________________________________________________________________________________________________________________________________<br> At 06:48 AM 1/8/2021, Ronald van Ginkel wrote:<br><br> <blockquote type=cite class=cite cite="">Hi Steve.<br><br> I took a way, but I finally could setup a Virtual Machine with Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 bits OS), installed VS2002 and imported Hermes project.<br><br> ... but it cannot been compiled.<br><br> As I see, project file needs at least 2010 version.<br><br> I've installed a VS2010 and tried to compiled, but I get a lot of errors, most of them due to the use of 'noexcept' expression that it's only supported at VS 2015 or above, and with VS2015 I get tons of errors trying to compile.<br><br> Can anyone tell me is there a way to compile the source code ?<br><br> Thank you in advance.<br><br> Ronald</blockquote><br> Ronald,<br><br> My main development machine keeps changing, and I have changed motherboards 1-2 times in recent years, so the environment I first tested the Eudora source code in no longer exists. This pre-dated the 'Hermes' project by several months at least. I don't have the 'Hermes Project' files. I have the files that were released from the Computer Museum that Qualcomm authorized.<br><br> A little common sense: VS2010 didn't exist at the time of the final release of Eudora, so it couldn't have been the required version.<br><br> When a newer version of Visual Studio tries to open a project from a previous version of Visual Studio, it will convert the old project file to the new project file. It also shows a warning box on the screen when it does this, and gives you the option to save the old version unmodified but you have to enter a new name for the old file to use. So if you had initially tried to compile the source code with VS2010, the project file was converted.<br><br> I don't presently have Visual Studio 2002 installed. I did have it installed in a 64-bit Windows 7 environment. As I recall, it wasn't easy to install. I just finished a search, and I found some install instructions which say that to install it, you need to not already have newer versions of Visual Studio on the system, and there were a couple of specific items you need to check-off and not install, for it to work.<br><br> Use of Windows XP to make a compiling environment is a common work around for these kinds of problems. I recently (recent defined as within the past 2 years) had to run a 16-bit program that was compiled using QuickBasic. I had to do the same thing, as Windows XP could run 16-bit programs. I soon went to some trouble to write a replacement program that runs in a 64-bit environment.<br><br> I don't know anything about this 'noexcept' expression you are talking about, and anything I say is going to be speculation. I generally do most of my work in older versions of Visual Studio.<br><br> Steve<br><br> <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a><br> <br> <br> ______________________________________________________________________________________________________________________________________ <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a> </blockquote><br><br> <br> ______________________________________________________________________________________________________________________________________ <br> _______________________________________________<br> Hermesmail-discuss mailing list<br> Her...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss" eudora="autourl"> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss</a></font> </blockquote></body> </html> |
|
From: Ronald v. G. <ro...@t-...> - 2021-01-09 12:39:18
|
Hi Curtis.
Yes, I'm afraid all of us are short of time, but for me, Eudora is my
main tool for my work, so I wanna invest some time and resources on it.
Thank you for your offer, but I also have all VS versions (I'm
Microsoft Silver Partner), but I need to know what is the first step.
As I see, Eudora 'museum' code needs VS 2003:
>Eudora.vcproj
><VisualStudioProject
> ProjectType="Visual C++"
> Version="7.10"
But Hermes code needs VS 2015:
>Eudora.vcxproj
><Project DefaultTargets="Build" ToolsVersion="15.0"
And as I see, Hermes installer's eudora.exe is the original one, so
it seems it's no been compiled recently.
So, my point is:
- Is there any source code that can be compiled in anyway ?
- If it is not:
- What source code and environment are the best to begin to
fight with ?
- Is there an unavoidable obstacle that prevents compiling
the source code?
Regards!
Ronald
______________________________________________________________________________________________________________________________________
Hi Ronald,
If you would like to give it a go I have VS 2005 Pro. I can send an
ISO image and license key. Wish I had more time!
Regards,
Curtis Meadow
At 12:33 PM 1/8/2021, Ronald van Ginkel wrote:
>Hi Steve.
>
>Thank you for your answer, but the only thing I need to know is if
>it is possible to compile the source code of Eudora or Hermes and
>what is the necessary environment to do it.
>
> From here I will be able to understand where the project is
> standing and see if I can help in any way.
>
>Regards!
>
>Ronald
>______________________________________________________________________________________________________________________________________
>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote:
>
>>Hi Steve.
>>
>>I took a way, but I finally could setup a Virtual Machine with
>>Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64
>>bits OS), installed VS2002 and imported Hermes project.
>>
>>... but it cannot been compiled.
>>
>>As I see, project file needs at least 2010 version.
>>
>>I've installed a VS2010 and tried to compiled, but I get a lot of
>>errors, most of them due to the use of 'noexcept' expression that
>>it's only supported at VS 2015 or above, and with VS2015 I get tons
>>of errors trying to compile.
>>
>>Can anyone tell me is there a way to compile the source code ?
>>
>>Thank you in advance.
>>
>>Ronald
>
>Ronald,
>
>My main development machine keeps changing, and I have changed
>motherboards 1-2 times in recent years, so the environment I first
>tested the Eudora source code in no longer exists. This pre-dated
>the 'Hermes' project by several months at least. I don't have the
>'Hermes Project' files. I have the files that were released from
>the Computer Museum that Qualcomm authorized.
>
>A little common sense: VS2010 didn't exist at the time of the final
>release of Eudora, so it couldn't have been the required version.
>
>When a newer version of Visual Studio tries to open a project from a
>previous version of Visual Studio, it will convert the old project
>file to the new project file. It also shows a warning box on the
>screen when it does this, and gives you the option to save the old
>version unmodified but you have to enter a new name for the old file
>to use. So if you had initially tried to compile the source code
>with VS2010, the project file was converted.
>
>I don't presently have Visual Studio 2002 installed. I did have it
>installed in a 64-bit Windows 7 environment. As I recall, it wasn't
>easy to install. I just finished a search, and I found some install
>instructions which say that to install it, you need to not already
>have newer versions of Visual Studio on the system, and there were a
>couple of specific items you need to check-off and not install, for it to work.
>
>Use of Windows XP to make a compiling environment is a common work
>around for these kinds of problems. I recently (recent defined as
>within the past 2 years) had to run a 16-bit program that was
>compiled using QuickBasic. I had to do the same thing, as Windows
>XP could run 16-bit programs. I soon went to some trouble to write
>a replacement program that runs in a 64-bit environment.
>
>I don't know anything about this 'noexcept' expression you are
>talking about, and anything I say is going to be speculation. I
>generally do most of my work in older versions of Visual Studio.
>
>Steve
>
>
>_______________________________________________
>Hermesmail-discuss mailing list
>Her...@li...
>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss
>
>
>______________________________________________________________________________________________________________________________________
>
>_______________________________________________
>Hermesmail-discuss mailing list
>Her...@li...
>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss
______________________________________________________________________________________________________________________________________ |
|
From: Steven Z. <oak...@us...> - 2021-01-08 23:11:40
|
A shout out to everyone working on this -- I appreciate it. I am using Hermes with TSL 1.2 and it works for POP and IMAP. I have two instances installed, in separate folders for separate accounts. I don't code but I'm a technical writer, so maybe I can lend a hand with some documentation (I'm not your SDK or API guy.) In any case keep up the effort. Steven At 02:40 PM 01/08/2021, Curtis Meadow wrote: >Hi Ronald, >If you would like to give it a go I have VS 2005 Pro. I can send an >ISO image and license key. Wish I had more time! >Regards, >Curtis Meadow > >At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: > >>Hi Steve. >> >>Thank you for your answer, but the only thing I need to know is if >>it is possible to compile the source code of Eudora or Hermes and >>what is the necessary environment to do it. >> >> From here I will be able to understand where the project is >> standing and see if I can help in any way. >> >>Regards! >> >>Ronald >>______________________________________________________________________________________________________________________________________ >>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >> >>>Hi Steve. >>> >>>I took a way, but I finally could setup a Virtual Machine with >>>Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 >>>bits OS), installed VS2002 and imported Hermes project. >>> >>>... but it cannot been compiled. >>> >>>As I see, project file needs at least 2010 version. >>> >>>I've installed a VS2010 and tried to compiled, but I get a lot of >>>errors, most of them due to the use of 'noexcept' expression that >>>it's only supported at VS 2015 or above, and with VS2015 I get >>>tons of errors trying to compile. >>> >>>Can anyone tell me is there a way to compile the source code ? >>> >>>Thank you in advance. >>> >>>Ronald >> >>Ronald, >> >>My main development machine keeps changing, and I have changed >>motherboards 1-2 times in recent years, so the environment I first >>tested the Eudora source code in no longer exists. This pre-dated >>the 'Hermes' project by several months at least. I don't have the >>'Hermes Project' files. I have the files that were released from >>the Computer Museum that Qualcomm authorized. >> >>A little common sense: VS2010 didn't exist at the time of the >>final release of Eudora, so it couldn't have been the required version. >> >>When a newer version of Visual Studio tries to open a project from >>a previous version of Visual Studio, it will convert the old >>project file to the new project file. It also shows a warning box >>on the screen when it does this, and gives you the option to save >>the old version unmodified but you have to enter a new name for the >>old file to use. So if you had initially tried to compile the >>source code with VS2010, the project file was converted. >> >>I don't presently have Visual Studio 2002 installed. I did have it >>installed in a 64-bit Windows 7 environment. As I recall, it >>wasn't easy to install. I just finished a search, and I found some >>install instructions which say that to install it, you need to not >>already have newer versions of Visual Studio on the system, and >>there were a couple of specific items you need to check-off and not >>install, for it to work. >> >>Use of Windows XP to make a compiling environment is a common work >>around for these kinds of problems. I recently (recent defined as >>within the past 2 years) had to run a 16-bit program that was >>compiled using QuickBasic. I had to do the same thing, as Windows >>XP could run 16-bit programs. I soon went to some trouble to write >>a replacement program that runs in a 64-bit environment. >> >>I don't know anything about this 'noexcept' expression you are >>talking about, and anything I say is going to be speculation. I >>generally do most of my work in older versions of Visual Studio. >> >>Steve >> >> >>_______________________________________________ >>Hermesmail-discuss mailing list >>Her...@li... >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> >> >>______________________________________________________________________________________________________________________________________ >> >>_______________________________________________ >>Hermesmail-discuss mailing list >>Her...@li... >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > > > >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss |
|
From: Curtis M. <cm...@db...> - 2021-01-08 22:56:47
|
Hi Ronald, If you would like to give it a go I have VS 2005 Pro. I can send an ISO image and license key. Wish I had more time! Regards, Curtis Meadow At 12:33 PM 1/8/2021, Ronald van Ginkel wrote: >Hi Steve. > >Thank you for your answer, but the only thing I need to know is if >it is possible to compile the source code of Eudora or Hermes and >what is the necessary environment to do it. > > From here I will be able to understand where the project is > standing and see if I can help in any way. > >Regards! > >Ronald >______________________________________________________________________________________________________________________________________ >At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: > >>Hi Steve. >> >>I took a way, but I finally could setup a Virtual Machine with >>Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 >>bits OS), installed VS2002 and imported Hermes project. >> >>... but it cannot been compiled. >> >>As I see, project file needs at least 2010 version. >> >>I've installed a VS2010 and tried to compiled, but I get a lot of >>errors, most of them due to the use of 'noexcept' expression that >>it's only supported at VS 2015 or above, and with VS2015 I get tons >>of errors trying to compile. >> >>Can anyone tell me is there a way to compile the source code ? >> >>Thank you in advance. >> >>Ronald > >Ronald, > >My main development machine keeps changing, and I have changed >motherboards 1-2 times in recent years, so the environment I first >tested the Eudora source code in no longer exists. This pre-dated >the 'Hermes' project by several months at least. I don't have the >'Hermes Project' files. I have the files that were released from >the Computer Museum that Qualcomm authorized. > >A little common sense: VS2010 didn't exist at the time of the final >release of Eudora, so it couldn't have been the required version. > >When a newer version of Visual Studio tries to open a project from a >previous version of Visual Studio, it will convert the old project >file to the new project file. It also shows a warning box on the >screen when it does this, and gives you the option to save the old >version unmodified but you have to enter a new name for the old file >to use. So if you had initially tried to compile the source code >with VS2010, the project file was converted. > >I don't presently have Visual Studio 2002 installed. I did have it >installed in a 64-bit Windows 7 environment. As I recall, it wasn't >easy to install. I just finished a search, and I found some install >instructions which say that to install it, you need to not already >have newer versions of Visual Studio on the system, and there were a >couple of specific items you need to check-off and not install, for it to work. > >Use of Windows XP to make a compiling environment is a common work >around for these kinds of problems. I recently (recent defined as >within the past 2 years) had to run a 16-bit program that was >compiled using QuickBasic. I had to do the same thing, as Windows >XP could run 16-bit programs. I soon went to some trouble to write >a replacement program that runs in a 64-bit environment. > >I don't know anything about this 'noexcept' expression you are >talking about, and anything I say is going to be speculation. I >generally do most of my work in older versions of Visual Studio. > >Steve > > >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > > >______________________________________________________________________________________________________________________________________ > >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss |
|
From: Ronald v. G. <ro...@t-...> - 2021-01-08 17:33:48
|
Hi Steve. Thank you for your answer, but the only thing I need to know is if it is possible to compile the source code of Eudora or Hermes and what is the necessary environment to do it. From here I will be able to understand where the project is standing and see if I can help in any way. Regards! Ronald ______________________________________________________________________________________________________________________________________ At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >Hi Steve. > >I took a way, but I finally could setup a Virtual Machine with >Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 >bits OS), installed VS2002 and imported Hermes project. > >... but it cannot been compiled. > >As I see, project file needs at least 2010 version. > >I've installed a VS2010 and tried to compiled, but I get a lot of >errors, most of them due to the use of 'noexcept' expression that >it's only supported at VS 2015 or above, and with VS2015 I get tons >of errors trying to compile. > >Can anyone tell me is there a way to compile the source code ? > >Thank you in advance. > >Ronald Ronald, My main development machine keeps changing, and I have changed motherboards 1-2 times in recent years, so the environment I first tested the Eudora source code in no longer exists. This pre-dated the 'Hermes' project by several months at least. I don't have the 'Hermes Project' files. I have the files that were released from the Computer Museum that Qualcomm authorized. A little common sense: VS2010 didn't exist at the time of the final release of Eudora, so it couldn't have been the required version. When a newer version of Visual Studio tries to open a project from a previous version of Visual Studio, it will convert the old project file to the new project file. It also shows a warning box on the screen when it does this, and gives you the option to save the old version unmodified but you have to enter a new name for the old file to use. So if you had initially tried to compile the source code with VS2010, the project file was converted. I don't presently have Visual Studio 2002 installed. I did have it installed in a 64-bit Windows 7 environment. As I recall, it wasn't easy to install. I just finished a search, and I found some install instructions which say that to install it, you need to not already have newer versions of Visual Studio on the system, and there were a couple of specific items you need to check-off and not install, for it to work. Use of Windows XP to make a compiling environment is a common work around for these kinds of problems. I recently (recent defined as within the past 2 years) had to run a 16-bit program that was compiled using QuickBasic. I had to do the same thing, as Windows XP could run 16-bit programs. I soon went to some trouble to write a replacement program that runs in a 64-bit environment. I don't know anything about this 'noexcept' expression you are talking about, and anything I say is going to be speculation. I generally do most of my work in older versions of Visual Studio. Steve _______________________________________________ Hermesmail-discuss mailing list Her...@li... https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss ______________________________________________________________________________________________________________________________________ |
|
From: SRTabler <srt...@gm...> - 2021-01-08 16:34:08
|
At 06:48 AM 1/8/2021, Ronald van Ginkel wrote: >Hi Steve. > >I took a way, but I finally could setup a Virtual Machine with >Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 >bits OS), installed VS2002 and imported Hermes project. > >... but it cannot been compiled. > >As I see, project file needs at least 2010 version. > >I've installed a VS2010 and tried to compiled, but I get a lot of >errors, most of them due to the use of 'noexcept' expression that >it's only supported at VS 2015 or above, and with VS2015 I get tons >of errors trying to compile. > >Can anyone tell me is there a way to compile the source code ? > >Thank you in advance. > >Ronald Ronald, My main development machine keeps changing, and I have changed motherboards 1-2 times in recent years, so the environment I first tested the Eudora source code in no longer exists. This pre-dated the 'Hermes' project by several months at least. I don't have the 'Hermes Project' files. I have the files that were released from the Computer Museum that Qualcomm authorized. A little common sense: VS2010 didn't exist at the time of the final release of Eudora, so it couldn't have been the required version. When a newer version of Visual Studio tries to open a project from a previous version of Visual Studio, it will convert the old project file to the new project file. It also shows a warning box on the screen when it does this, and gives you the option to save the old version unmodified but you have to enter a new name for the old file to use. So if you had initially tried to compile the source code with VS2010, the project file was converted. I don't presently have Visual Studio 2002 installed. I did have it installed in a 64-bit Windows 7 environment. As I recall, it wasn't easy to install. I just finished a search, and I found some install instructions which say that to install it, you need to not already have newer versions of Visual Studio on the system, and there were a couple of specific items you need to check-off and not install, for it to work. Use of Windows XP to make a compiling environment is a common work around for these kinds of problems. I recently (recent defined as within the past 2 years) had to run a 16-bit program that was compiled using QuickBasic. I had to do the same thing, as Windows XP could run 16-bit programs. I soon went to some trouble to write a replacement program that runs in a 64-bit environment. I don't know anything about this 'noexcept' expression you are talking about, and anything I say is going to be speculation. I generally do most of my work in older versions of Visual Studio. Steve |
|
From: Ronald v. G. <ro...@t-...> - 2021-01-08 12:00:25
|
Hi Steve. I took a way, but I finally could setup a Virtual Machine with Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 bits OS), installed VS2002 and imported Hermes project. ... but it cannot been compiled. As I see, project file needs at least 2010 version. I've installed a VS2010 and tried to compiled, but I get a lot of errors, most of them due to the use of 'noexcept' expression that it's only supported at VS 2015 or above, and with VS2015 I get tons of errors trying to compile. Can anyone tell me is there a way to compile the source code ? Thank you in advance. Ronald ______________________________________________________________________________________________________________________________________ At 11:26 AM 12/30/2020, you wrote: >Hi Darrel. > >Thank you for your words. > >I've downloaded Hermes Project from Sourceforge to get more info. > >For me, the key point is compile a working eudora.exe using this >source code. If we get this done, we can begin to improve it. > >Actually, it cannot be compiled using Visual Studio (4032 errors, >uf), but it seems it can be compiled through older IDEs. > >I've readed on some post that a exe was build, but it crashes on >open it. I have not info if we can get a functional exe through this >compilation. > >a) If we can compile a working Eudora through an older IDE, I think >the next approach would be do a software refactorization (the >masterplan file name it 'Brentford') so we can work on it using >Visual Studio. This is a project we can hire to a external developer >(using freelancer or similar). The VS solution file that came from the publicly released code seems to work with VS2002. There are some error messages that come up, though, while compiling, due to the absence of the stingray material. I've never come across stingray before seeing it referenced in the Eudora source code. Steve ______________________________________________________________________________________________________________________________________ |
|
From: Ronald v. G. <ro...@t-...> - 2020-12-30 16:26:48
|
Hi Darrel. Thank you for your words. I've downloaded Hermes Project from Sourceforge to get more info. For me, the key point is compile a working eudora.exe using this source code. If we get this done, we can begin to improve it. Actually, it cannot be compiled using Visual Studio (4032 errors, uf), but it seems it can be compiled through older IDEs. I've readed on some post that a exe was build, but it crashes on open it. I have not info if we can get a functional exe through this compilation. a) If we can compile a working Eudora through an older IDE, I think the next approach would be do a software refactorization (the masterplan file name it 'Brentford') so we can work on it using Visual Studio. This is a project we can hire to a external developer (using freelancer or similar). b) If we cannot compile a working Eudora in anyway, we must be realistic and know if this is possible or not. If it is possible, what are the steps and resources needed to achieve it. I'm sure that having a easily compilable project (Visual Studio shall be really nice), more people shall help to develope it. Sorry if I am telling things that are too obvious or without sufficient knowledge, it is not easy for me to understand the current situation of the project with the published information. Regards! Ronald ______________________________________________________________________________________________________________________________________ Hi All, Ronald makes some interesting points, Pete though has been under the hood with Eudora for at least a decade or 2 so also need to consider his viewpoint as well. It is item number 2) from Ronald that catches my attention. Particularly the paragraph stating an *"analysis of the functionalities that Eudora needs from Stingray". * A question that jumps to mind is how many of those functionalities might be within libraries easier to negotiate that Stingray, such as GTK or perhaps even Java? There is a Japanese developer who has built what looks like a Eudora clone. Sylpheed is very basic (with far less of the functionality of Eudora) called Sylpheed using GTK (SEE: https://sylpheed.sraoss.jp/en/). While Sylpheed has less functionality it demonstrates what can be done with GTK in at least matching the appearance of Eudora. Anyhow all of the above may be naive. Although I don't use Eudora myself -- I do though know people who are still using it on a daily basis, thanks to the patch on the Hermes site. I miss Eudora's ease of use, due to though frequently communicating in various languages I find Eudora impractical outside of English. Best Regards - Darrell On 12/29/2020 11:26 AM, Ronald van Ginkel wrote: >Hi Pete. > >First of all, thank you for the effort you are >making to keep this project alive. > > >I think ISO-8859-1 issue can be worked in two ways: > >*1)* Obtain the modified Stingray library: >Perhaps it is just an intellectual property >issue that can be negotiated in some way. I >supose we have some contact with Qualcomm and I >see Stingray owner is now Perforce: >https://www.perforce.com/products/stingray ><https://www.perforce.com/products/stingray>. > >I understand that these steps have already been >taken, but it is important to know if this >possibility has been ruled out and for what reason. > > >*2)* Reverse engineering to adapt Eudora back to >Stingray (assuming this is the most optimal >solution as opposed to integrating it with a different library). > >In this case, I think the first step would be to >have an analysis of the functionalities that >Eudora needs from Stingray to be able to size the project. > >A limited scope of the project is probably something that money can fix. > > >As most of you, Eudora is for me an >indispensable tool and currently irreplaceable. >More than 22 years of emails and 60Gb of >information that I can manage with agility >thanks to the X1 search engine that Eudora >incorporates and because of Eudora's own >functionality, so I am more than willing to >collaborate with the project (financially and >with my time and knowledge). The only thing is >that the campaigns to contribute funds are closed :-( > >Best regards! > >Ronald > >______________________________________________________________________________________________________________________________________ >Hi Darrell, > >It is indeed the case that there is no ETA for >iso-8859-1 compliance. Actually it is looking >more and more like that will never happen. > >I have posted about this before but I think it >would be useful to describe again why supporting >iso-8859-1 is such a big deal. It is because a >lack of iso-8859-1 capability in Eudora/Hermes >is not actually the problem. The Eudora that >most or all of us are using knows about >iso-8859-1 and has an appropriate amount of >support for it. The real problem is that Eudora >does not support display of Unicode >characters. I don't want to make a fuss about >how we refer to the problem -- we all now know >too well what we mean when we talk about the >"lack of iso-8859-1 support" so I think it's >okay to go on referring to it in this way. But >the real issue is larger and much deeper. If >Eudora was capable of displaying Unicode but >lacked support for iso-8859-1 (which would be >rather odd, but possible) the fix would be very >easy, maybe even something that could be done >with a patch to the existing binary. As things >are, it means changing a very large number of >calls to a particular third-party library called >Stingray that renders text for Eudora. We have >precious few volunteers on the project to begin >with and none who has experience with >Stingray. I believe we have a connection to one >contractor who does have some Stingray expertise >but we have negligible funds to pay him. What >is more, working with this library is formidably >difficult in one way: the Eudora developers >customized it and we do not have any good >records of these customizations. For this >reason and others we are not even able to rebuild Eudora in its original form. > >As far as I know, I am the only person on the >project who actually uses Eudora and who has any >real passion for the project. But I cannot do >it alone. When I was younger I might have taken >it on but now I am old, slower than I used to >be, and just not up to it. I have heard nothing >from the project leader in several months, no >progress is being made that I am aware of and I >fear the whole thing has effectively ground to a halt. > >Pete Maclean > >At 05:09 AM 12/28/2020, Darrell Jonsson wrote: >>Hi John, Others can correct me if I'm wrong. >>UTF compliance turned out to be a major >>non-trivial hurdle in Hermes development. So >>far as I understand it so far there is no >>timeline/ETA for UTF 8 compliance. Technical >>reasons for this complication were explained >>earlier in this list, as I remember it involves >>some deep global changes to the software's >>libraries. Perhaps others can explain more >>clearly. Best regards - Darrell On 12/25/2020 >>7:30 AM, John B. Lisle wrote: > Jason et >>al, > > Thanks for the insight on the two >>options. I'll try the easy option tomorrow. > > >>What additional features does one get with the >>full version? In particular, does it solve the >>UTF8 problem? > > I have a very large email >>database. I do have attachments in a separate >>directory. I didn't know you could also have >>the mail boxes and folders in a separate >>directory. Can you share how that is done? > > >>Thanks, > John. > > Sent from my iPhone > >> On >>Dec 25, 2020, at 12:04 AM, Jason Shoup >><ja...@sh...> wrote: >> >> Hi John and >>Happy Holidays. >> >> If you're already using a >>working copy of Eudora, then there's absolutely >>no need to install the full Hermes Mail >>package. At the present time, Hermes Mail is >>basically just Eudora 7.1.0.9 but with some >>TLS/SSL updates already included in the >>installation files. >> >> If you're using the >>stock version of Eudora 7.1.0.9, then you'll >>probably only need to update Eudora's TLS/SSL >>libraries to get TLS working again. It's a >>quick fix that works great on existing >>installations. >> >> Please download the >>HermSSL.zip file from Source Forge at >>https://sourceforge.net/projects/hermesmail/files/ >><https://sourceforge.net/projects/hermesmail/files/> >> >> >> Unzip the file and follow the >>instructions in the readme.txt file. It >>involves replacing a few of Eudora's files with >>new ones from the Hermes Mail project. >> >> >>After updating, you'll find your Eudora can now >>negotiate TLS1.2 when receiving email via POP >>and IMAP. When sending mail via SMTP, I've only >>been able to negotiate up to TLS1.0, but >>luckily it's still widely supported amongst >>many providers. >> >> Please note however that >>the files included in the HermSSL.zip file will >>only address the TLS/SSL issue. Eudora will >>still continue to suffer from the lack of >>iso-8859-1 support. That's what causes those >>strange characters to appear in messages >>received from those who send mail using the >>iso-8859-1 character set. >> >> It's always a >>good idea to backup Eudora's data directories >>before making any changes. In my case, where >>Eudora is installed and where I have it keep my >>email are in two separate locations. >> >> Good >>luck with the update. I'm sure you'll be happy >>to know you can keep using Eudora for a little >>while longer yet. It's still my primary email >>client too. This message having been proudly >>sent by Eudora. >> >> Have a wonderful holiday >>season. Stay safe and well amidst the pandemic. >>Cheers, >> >> Jason >> >> >> >> >> At 06:20 PM >>24/12/2020, you wrote: >>> Hi, >>> >>> I have >>been using Eudora since the early 1990s. I am >>having the "usual" problems with hosting >>company wanting to eliminate obsolete TLS >>support so I am having issues with my email >>accounts with them. They mentioned that Hermes >>Mail might be a solution. >>> >>> I am running >>Win 7 64 bit with Eudora 7.1.0.9 >>> >>> My >>question is simply "How do I install it"? Is it >>possible to try it and then back it out if it >>does not work -- most of my email accounts, >>including gmail, are fine with it; it is just >>the email accounts from a single hosting >>service that seem to have an issue. >>> >>> >>Thanks, >>> john. >> >> >> >> >>_______________________________________________ >> >> Hermesmail-discuss mailing list >> >>Her...@li... >> >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >><https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> >> > > >>_______________________________________________ >> > Hermesmail-discuss mailing list > >>Her...@li... > >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >><https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> >>_______________________________________________ >>Hermesmail-discuss mailing list >>Her...@li... >>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >><https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> </x-flowed> > >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > ><https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> >______________________________________________________________________________________________________________________________________ > ______________________________________________________________________________________________________________________________________ |
|
From: Darrell J. <jo...@we...> - 2020-12-29 20:52:39
|
Hi All, Ronald makes some interesting points, Pete though has been under the hood with Eudora for at least a decade or 2 so also need to consider his viewpoint as well. It is item number 2) from Ronald that catches my attention. Particularly the paragraph stating an *"analysis of the functionalities that Eudora needs from Stingray". * A question that jumps to mind is how many of those functionalities might be within libraries easier to negotiate that Stingray, such as GTK or perhaps even Java? There is a Japanese developer who has built what looks like a Eudora clone. Sylpheed is very basic (with far less of the functionality of Eudora) called Sylpheed using GTK (SEE: https://sylpheed.sraoss.jp/en/). While Sylpheed has less functionality it demonstrates what can be done with GTK in at least matching the appearance of Eudora. Anyhow all of the above may be naive. Although I don't use Eudora myself -- I do though know people who are still using it on a daily basis, thanks to the patch on the Hermes site. I miss Eudora's ease of use, due to though frequently communicating in various languages I find Eudora impractical outside of English. Best Regards - Darrell On 12/29/2020 11:26 AM, Ronald van Ginkel wrote: > > Hi Pete. > > First of all, thank you for the effort you are making to keep this > project alive. > > > I think ISO-8859-1 issue can be worked in two ways: > > *1)* Obtain the modified Stingray library: Perhaps it is just an > intellectual property issue that can be negotiated in some way. I > supose we have some contact with Qualcomm and I see Stingray owner is > now Perforce: https://www.perforce.com/products/stingray > <https://www.perforce.com/products/stingray>. > > I understand that these steps have already been taken, but it is > important to know if this possibility has been ruled out and for what > reason. > > > *2)* Reverse engineering to adapt Eudora back to Stingray (assuming > this is the most optimal solution as opposed to integrating it with a > different library). > > In this case, I think the first step would be to have an analysis of > the functionalities that Eudora needs from Stingray to be able to size > the project. > > A limited scope of the project is probably something that money can fix. > > > As most of you, Eudora is for me an indispensable tool and currently > irreplaceable. More than 22 years of emails and 60Gb of information > that I can manage with agility thanks to the X1 search engine that > Eudora incorporates and because of Eudora's own functionality, so I am > more than willing to collaborate with the project (financially and > with my time and knowledge). The only thing is that the campaigns to > contribute funds are closed :-( > > Best regards! > > Ronald > > ______________________________________________________________________________________________________________________________________ > Hi Darrell, > > It is indeed the case that there is no ETA for iso-8859-1 compliance. > Actually it is looking more and more like that will never happen. > > I have posted about this before but I think it would be useful to > describe again why supporting iso-8859-1 is such a big deal. It is > because a lack of iso-8859-1 capability in Eudora/Hermes is not > actually the problem. The Eudora that most or all of us are using > knows about iso-8859-1 and has an appropriate amount of support for > it. The real problem is that Eudora does not support display of > Unicode characters. I don't want to make a fuss about how we refer to > the problem -- we all now know too well what we mean when we talk > about the "lack of iso-8859-1 support" so I think it's okay to go on > referring to it in this way. But the real issue is larger and much > deeper. If Eudora was capable of displaying Unicode but lacked > support for iso-8859-1 (which would be rather odd, but possible) the > fix would be very easy, maybe even something that could be done with a > patch to the existing binary. As things are, it means changing a very > large number of calls to a particular third-party library called > Stingray that renders text for Eudora. We have precious few > volunteers on the project to begin with and none who has experience > with Stingray. I believe we have a connection to one contractor who > does have some Stingray expertise but we have negligible funds to pay > him. What is more, working with this library is formidably difficult > in one way: the Eudora developers customized it and we do not have > any good records of these customizations. For this reason and others > we are not even able to rebuild Eudora in its original form. > > As far as I know, I am the only person on the project who actually > uses Eudora and who has any real passion for the project. But I > cannot do it alone. When I was younger I might have taken it on but > now I am old, slower than I used to be, and just not up to it. I have > heard nothing from the project leader in several months, no progress > is being made that I am aware of and I fear the whole thing has > effectively ground to a halt. > > Pete Maclean > > At 05:09 AM 12/28/2020, Darrell Jonsson wrote: >> Hi John, Others can correct me if I'm wrong. UTF compliance turned >> out to be a major non-trivial hurdle in Hermes development. So far as >> I understand it so far there is no timeline/ETA for UTF 8 compliance. >> Technical reasons for this complication were explained earlier in >> this list, as I remember it involves some deep global changes to the >> software's libraries. Perhaps others can explain more clearly. Best >> regards - Darrell On 12/25/2020 7:30 AM, John B. Lisle wrote: > Jason >> et al, > > Thanks for the insight on the two options. I'll try the >> easy option tomorrow. > > What additional features does one get with >> the full version? In particular, does it solve the UTF8 problem? > > >> I have a very large email database. I do have attachments in a >> separate directory. I didn't know you could also have the mail boxes >> and folders in a separate directory. Can you share how that is done? >> > > Thanks, > John. > > Sent from my iPhone > >> On Dec 25, 2020, at >> 12:04 AM, Jason Shoup <ja...@sh...> wrote: >> >> Hi John and >> Happy Holidays. >> >> If you're already using a working copy of >> Eudora, then there's absolutely no need to install the full Hermes >> Mail package. At the present time, Hermes Mail is basically just >> Eudora 7.1.0.9 but with some TLS/SSL updates already included in the >> installation files. >> >> If you're using the stock version of Eudora >> 7.1.0.9, then you'll probably only need to update Eudora's TLS/SSL >> libraries to get TLS working again. It's a quick fix that works great >> on existing installations. >> >> Please download the HermSSL.zip file >> from Source Forge at >> https://sourceforge.net/projects/hermesmail/files/ >> <https://sourceforge.net/projects/hermesmail/files/> >> >> Unzip the >> file and follow the instructions in the readme.txt file. It involves >> replacing a few of Eudora's files with new ones from the Hermes Mail >> project. >> >> After updating, you'll find your Eudora can now >> negotiate TLS1.2 when receiving email via POP and IMAP. When sending >> mail via SMTP, I've only been able to negotiate up to TLS1.0, but >> luckily it's still widely supported amongst many providers. >> >> >> Please note however that the files included in the HermSSL.zip file >> will only address the TLS/SSL issue. Eudora will still continue to >> suffer from the lack of iso-8859-1 support. That's what causes those >> strange characters to appear in messages received from those who send >> mail using the iso-8859-1 character set. >> >> It's always a good >> idea to backup Eudora's data directories before making any changes. >> In my case, where Eudora is installed and where I have it keep my >> email are in two separate locations. >> >> Good luck with the update. >> I'm sure you'll be happy to know you can keep using Eudora for a >> little while longer yet. It's still my primary email client too. This >> message having been proudly sent by Eudora. >> >> Have a wonderful >> holiday season. Stay safe and well amidst the pandemic. Cheers, >> >> >> Jason >> >> >> >> >> At 06:20 PM 24/12/2020, you wrote: >>> Hi, >>> >> >>> I have been using Eudora since the early 1990s. I am having the >> "usual" problems with hosting company wanting to eliminate obsolete >> TLS support so I am having issues with my email accounts with them. >> They mentioned that Hermes Mail might be a solution. >>> >>> I am >> running Win 7 64 bit with Eudora 7.1.0.9 >>> >>> My question is >> simply "How do I install it"? Is it possible to try it and then back >> it out if it does not work -- most of my email accounts, including >> gmail, are fine with it; it is just the email accounts from a single >> hosting service that seem to have an issue. >>> >>> Thanks, >>> john. >> >> >> >> >> _______________________________________________ >> >> Hermesmail-discuss mailing list >> >> Her...@li... >> >> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> <https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> > > >> _______________________________________________ > Hermesmail-discuss >> mailing list > Her...@li... > >> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> <https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> >> _______________________________________________ Hermesmail-discuss >> mailing list Her...@li... >> https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >> <https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> >> </x-flowed> > > _______________________________________________ > Hermesmail-discuss mailing list > Her...@li... > https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > > <https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss> > ______________________________________________________________________________________________________________________________________ |
|
From: Ronald v. G. <ro...@t-...> - 2020-12-29 10:43:15
|
Hi Pete. First of all, thank you for the effort you are making to keep this project alive. I think ISO-8859-1 issue can be worked in two ways: 1) Obtain the modified Stingray library: Perhaps it is just an intellectual property issue that can be negotiated in some way. I supose we have some contact with Qualcomm and I see Stingray owner is now Perforce: https://www.perforce.com/products/stingray. I understand that these steps have already been taken, but it is important to know if this possibility has been ruled out and for what reason. 2) Reverse engineering to adapt Eudora back to Stingray (assuming this is the most optimal solution as opposed to integrating it with a different library). In this case, I think the first step would be to have an analysis of the functionalities that Eudora needs from Stingray to be able to size the project. A limited scope of the project is probably something that money can fix. As most of you, Eudora is for me an indispensable tool and currently irreplaceable. More than 22 years of emails and 60Gb of information that I can manage with agility thanks to the X1 search engine that Eudora incorporates and because of Eudora's own functionality, so I am more than willing to collaborate with the project (financially and with my time and knowledge). The only thing is that the campaigns to contribute funds are closed :-( Best regards! Ronald ______________________________________________________________________________________________________________________________________ Hi Darrell, It is indeed the case that there is no ETA for iso-8859-1 compliance. Actually it is looking more and more like that will never happen. I have posted about this before but I think it would be useful to describe again why supporting iso-8859-1 is such a big deal. It is because a lack of iso-8859-1 capability in Eudora/Hermes is not actually the problem. The Eudora that most or all of us are using knows about iso-8859-1 and has an appropriate amount of support for it. The real problem is that Eudora does not support display of Unicode characters. I don't want to make a fuss about how we refer to the problem -- we all now know too well what we mean when we talk about the "lack of iso-8859-1 support" so I think it's okay to go on referring to it in this way. But the real issue is larger and much deeper. If Eudora was capable of displaying Unicode but lacked support for iso-8859-1 (which would be rather odd, but possible) the fix would be very easy, maybe even something that could be done with a patch to the existing binary. As things are, it means changing a very large number of calls to a particular third-party library called Stingray that renders text for Eudora. We have precious few volunteers on the project to begin with and none who has experience with Stingray. I believe we have a connection to one contractor who does have some Stingray expertise but we have negligible funds to pay him. What is more, working with this library is formidably difficult in one way: the Eudora developers customized it and we do not have any good records of these customizations. For this reason and others we are not even able to rebuild Eudora in its original form. As far as I know, I am the only person on the project who actually uses Eudora and who has any real passion for the project. But I cannot do it alone. When I was younger I might have taken it on but now I am old, slower than I used to be, and just not up to it. I have heard nothing from the project leader in several months, no progress is being made that I am aware of and I fear the whole thing has effectively ground to a halt. Pete Maclean At 05:09 AM 12/28/2020, Darrell Jonsson wrote: >Hi John, Others can correct me if I'm wrong. UTF >compliance turned out to be a major non-trivial >hurdle in Hermes development. So far as I >understand it so far there is no timeline/ETA >for UTF 8 compliance. Technical reasons for this >complication were explained earlier in this >list, as I remember it involves some deep global >changes to the software's libraries. Perhaps >others can explain more clearly. Best regards - >Darrell On 12/25/2020 7:30 AM, John B. Lisle >wrote: > Jason et al, > > Thanks for the insight >on the two options. I'll try the easy option >tomorrow. > > What additional features does one >get with the full version? In particular, does >it solve the UTF8 problem? > > I have a very >large email database. I do have attachments in a >separate directory. I didn't know you could also >have the mail boxes and folders in a separate >directory. Can you share how that is done? > > >Thanks, > John. > > Sent from my iPhone > >> On >Dec 25, 2020, at 12:04 AM, Jason Shoup ><ja...@sh...> wrote: >> >> Hi John and >Happy Holidays. >> >> If you're already using a >working copy of Eudora, then there's absolutely >no need to install the full Hermes Mail package. >At the present time, Hermes Mail is basically >just Eudora 7.1.0.9 but with some TLS/SSL >updates already included in the installation >files. >> >> If you're using the stock version >of Eudora 7.1.0.9, then you'll probably only >need to update Eudora's TLS/SSL libraries to get >TLS working again. It's a quick fix that works >great on existing installations. >> >> Please >download the HermSSL.zip file from Source Forge >at >https://sourceforge.net/projects/hermesmail/files/ > >> >> Unzip the file and follow the >instructions in the readme.txt file. It involves >replacing a few of Eudora's files with new ones >from the Hermes Mail project. >> >> After >updating, you'll find your Eudora can now >negotiate TLS1.2 when receiving email via POP >and IMAP. When sending mail via SMTP, I've only >been able to negotiate up to TLS1.0, but luckily >it's still widely supported amongst many >providers. >> >> Please note however that the >files included in the HermSSL.zip file will only >address the TLS/SSL issue. Eudora will still >continue to suffer from the lack of iso-8859-1 >support. That's what causes those strange >characters to appear in messages received from >those who send mail using the iso-8859-1 >character set. >> >> It's always a good idea to >backup Eudora's data directories before making >any changes. In my case, where Eudora is >installed and where I have it keep my email are >in two separate locations. >> >> Good luck with >the update. I'm sure you'll be happy to know you >can keep using Eudora for a little while longer >yet. It's still my primary email client too. >This message having been proudly sent by >Eudora. >> >> Have a wonderful holiday season. >Stay safe and well amidst the pandemic. >Cheers, >> >> Jason >> >> >> >> >> At 06:20 PM >24/12/2020, you wrote: >>> Hi, >>> >>> I have >been using Eudora since the early 1990s. I am >having the "usual" problems with hosting company >wanting to eliminate obsolete TLS support so I >am having issues with my email accounts with >them. They mentioned that Hermes Mail might be a >solution. >>> >>> I am running Win 7 64 bit with >Eudora 7.1.0.9 >>> >>> My question is simply >"How do I install it"? Is it possible to try it >and then back it out if it does not work -- most >of my email accounts, including gmail, are fine >with it; it is just the email accounts from a >single hosting service that seem to have an >issue. >>> >>> Thanks, >>> john. >> >> >> >> >_______________________________________________ > > > Hermesmail-discuss mailing list >> >Her...@li... >> >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss > > > >_______________________________________________ > > Hermesmail-discuss mailing list > >Her...@li... > >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss >_______________________________________________ >Hermesmail-discuss mailing list >Her...@li... >https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss </x-flowed> _______________________________________________ Hermesmail-discuss mailing list Her...@li... https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss ______________________________________________________________________________________________________________________________________ |
|
From: Butch K. <bu...@ke...> - 2020-12-29 07:02:52
|
At 05:16 PM 12/28/2020 -0500, Pete Maclean wrote:
>>Hi Darrell,
>>
>>It is indeed the case that there is no ETA for UTF-8 compliance. Actually
>it is looking more and more like that will never happen.
>>
>>I have posted about this before but I think it would be useful to describe
>again why supporting UTF-8 is such a big deal. It is because a lack of
>UTF-8 capability in Eudora/Hermes is not actually the problem. The Eudora
>that most or all of us are using knows about UTF-8 and has an appropriate
>amount of support for it. The real problem is that Eudora does not support
>display of Unicode characters. I don't want to make a fuss about how we
>refer to the problem -- we all now know too well what we mean when we talk
>about the "lack of UTF-8 support" so I think it's okay to go on referring
>to it in this way. But the real issue is larger and much deeper. If
>Eudora was capable of displaying Unicode but lacked support for UTF-8
>(which would be rather odd, but possible) the fix would be very easy, maybe
>even something that could be done with a patch to the existing binary. As
>things are, it means changing a very large number of calls to a particular
>third-party library called Stingray that renders text for Eudora. We have
>precious few volunteers on the project to begin with and none who has
>experience with Stingray. I believe we have a connection to one contractor
>who does have some Stingray expertise but we have negligible funds to pay
>him. What is more, working with this library is formidably difficult in
>one way: the Eudora developers customized it and we do not have any good
>records of these customizations. For this reason and others we are not
>even able to rebuild Eudora in its original form.
>>
>>As far as I know, I am the only person on the project who actually uses
>Eudora and who has any real passion for the project. But I cannot do it
>alone. When I was younger I might have taken it on but now I am old,
>slower than I used to be, and just not up to it. I have heard nothing from
>the project leader in several months, no progress is being made that I am
>aware of and I fear the whole thing has effectively ground to a halt.
>>
>>Pete Maclean
>
Pete,
Your last paragraph fairly sums up what I have thought for a long time and I am not close to or part of the Hermes Project. The release of Eudora Source Code created many unrealizable expectations both inside the project and outside in the potential user community. Reality has finaly arrived and I do not think the Hermes project will ever generate anything useful beyond the TLS extensions for Eudora.
However, there is a very successful product available that advances the "Eudora Look and Feel" into a modern email client - Pandora which is found at:
http://www.drivehq.com/web/brana/pandora.htm
I abandoned Eudora; switched to Pandora two years ago; and found Pandora meets my needs. Occasionally something goes bump and Brana is responsive to either correct a false understanding of what should happen; explain what I should have done; or accept a bug report.
Now the Pandora Project from what I understand is a "one man band and show" and not Brana's primary source of income. We need to determine how we can best assist the project to move forward. I tried to work on the HELP documentation but was unable to create the drive and passion necessary to make a meaningful contribution. Someone else may have better results. Now, I monitor the Forum and offer assistance when possible.
I think the best way now to assist Brana is to purchase a Pandora license. Keeping in mind the license cost is small and depending on your location, it is less than a good burger for lunch. Then install Pandora and give it a good evaluation. When something does not work as expected, use the Pandora Forum or submit a bug report.
There are some people that cannot make the change because Pandora does not have some feature or function they need. However, there are many Eudora shortcomings that are solved such as UTF-8, OAUTH2 authorization, TLS, attachments stored as files or as MIME embedded entities inside the messages; and until a evaluation is attempted people will never know if they can switch or not.
Enough ranting on my part. May you be blessed in the coming New Year and may the Covid-19 vaccine be rapidly deployed and prove successful.
Regards,
Butch
There’s no escaping the fact that you are what you think.
You can’t change anything if you can’t change your thinking.
-Angel Chernoff |
