Re: [MlMt] Markdown formatting
On 11 Nov 2021, at 2:08 EAT, Randall Gellens wrote: > On 9 Nov 2021, at 9:52, Steve Hodgson wrote: > >> I’m running Version 1.14 (5843). Seems ok today. > > I'm still on 1.13.2, since I'm not on OS 11 yet and I believe 1.13.2 is the > latest for 10.anything. I find lots of formatting problems in markdown, > including the need to add extra blank lines to get one to show up. I’m on OS X 10.14.6 and currently on MailMate Version 1.14 (5820). Option + clicking on “check for update” in the MailMate menu offers me version 5845 which I’ll download shortly. I can see in the release notes for 5845 the following under “Coding/Bulding related changes”: “Requires macOS 10.12 (previously public release required 10.10).” -- patrick ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Exchange: How to add another account with same credentials as the main account
Moin, On 7 Nov 2021, at 20:00, Mike Brasch wrote: Access another user mailbox: Either set base IMAP path in client settings to /users/otheru...@company.com or use the following username: domain\user\otheru...@company.com where otheru...@company.com it target mailbox name. The username way does not work. I only get a "wrong passwod". Where can I set the base IMAP path for the other variant? Where I can specify the base IMAP path. Is there a file I can edit? PLEASE HELP!!! Outlook is driving my crazy. :) -- Best regards Mike___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Markdown formatting
On 10 Nov 2021, at 15:30, Bill Cole wrote: On 2021-11-10 at 18:08:27 UTC-0500 (Wed, 10 Nov 2021 15:08:27 -0800) Randall Gellens is rumored to have said: I believe 1.13.2 is the latest for 10.anything. Nope. The test versions through the current r5844 have all run on Mojave (10.14.) No major issues and Benny cheerfully accepts bug reports for them on Mojave. Good to know. I'm actually still on 10.13 (High Sierra). I tried 10.14 on another machine cloned from my usual one, and MailMate kept locking up, presumably due to an OS issue accessing the address book or something, so I'm waiting on newer OSes until I can find time to clone my system again and try it out safely. --Randall ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Markdown formatting
On 12 Nov 2021, at 5:09, Patrick Okui wrote: On 11 Nov 2021, at 2:08 EAT, Randall Gellens wrote: On 9 Nov 2021, at 9:52, Steve Hodgson wrote: I’m running Version 1.14 (5843). Seems ok today. I'm still on 1.13.2, since I'm not on OS 11 yet and I believe 1.13.2 is the latest for 10.anything. I find lots of formatting problems in markdown, including the need to add extra blank lines to get one to show up. I’m on OS X 10.14.6 and currently on MailMate Version 1.14 (5820). Option + clicking on “check for update” in the MailMate menu offers me version 5845 which I’ll download shortly. I can see in the release notes for 5845 the following under “Coding/Bulding related changes”: “Requires macOS 10.12 (previously public release required 10.10).” I just tried to check for an update but received the error "SSL certificate problem: certificate has expired", which might explain why I wasn't aware there was anything newer. --Randall ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Exchange: How to add another account with same credentials as the main account
On 2021-11-12 at 11:55:04 UTC-0500 (Fri, 12 Nov 2021 17:55:04 +0100) Mike Brasch is rumored to have said: Moin, On 7 Nov 2021, at 20:00, Mike Brasch wrote: Access another user mailbox: Either set base IMAP path in client settings to /users/otheru...@company.com or use the following username: domain\user\otheru...@company.com where otheru...@company.com it target mailbox name. The username way does not work. I only get a "wrong passwod". Where can I set the base IMAP path for the other variant? Where I can specify the base IMAP path. Is there a file I can edit? Not in MM. I don't think MM supports specifying a base path for a source account. This may be something you must do in DavMail? PLEASE HELP!!! Outlook is driving my crazy. :) It tends to do that... -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] Markdown formatting
On 2021-11-12 at 13:34:46 UTC-0500 (Fri, 12 Nov 2021 10:34:46 -0800)
Randall Gellens
is rumored to have said:
I just tried to check for an update but received the error "SSL
certificate problem: certificate has expired", which might explain why
I wasn't aware there was anything newer.
That's probably a consequence of the recent expiration of the root CA
cert ("DST Root CA X3") on a secondary validation path for Let's Encrypt
certificates. Sites serve the full trust chain of certs needed for all
of their trust paths except for the root to all clients and many are
still serving both the valid trust path and the one that relies on an
expired root. There's actually no consensus on whether server and
intermediate certs that were issued when a CA cert was valid should be
considered invalid when the CA expires but the issued cert is still
nominally valid.
The fixes for that base problem vary between systems and can be
confusing because an app can use the OS's security layer and its
keychains of trusted CA certs or the Apple-distributed antique OpenSSL
with a PEM bundle of CA certs in /etc/ssl/cert.pem or the MacPorts
OpenSSL with the 'curl-ca-bundle' package that puts a link at
/opt/local/etc/openssl/cert.pem which points to
/opt/local/share/curl/curl-ca-bundle.crt. Or if you use Homebrew, you
might have something in /usr/local/etc. Some apps may even bundle their
own SSL libraries to do self-updates. I'm pretty sure MM just uses the
system facilities, but if you have similar problems with other tools
If Keychain Access will let you do so, you should remove "DST Root CA
X3" from your System Roots keychain. On recent systems with SPI enabled,
you can't do that so you can work around the problem by changing its
Trust Settings to "Always Trust." You also should check your keychains
for multiple versions of the "ISRG Root X1" certificate, which SHOULD be
a self-signed root CA cert in SystemRoots. However, you may also have
another version in the System or login keychains which is NOT actually a
root CA cert but rather is issued by that expired root CA cert. If you
do have one of those, they need to go. If you are unable to remove
non-root versions of the "ISRG Root X1" cert or do not have the root
version in SystemRoots, you can get the current version from
http://x1.i.lencr.org/ and import it into your System keychain. (imports
into SystemRoots don't work.)
Ideally, the fix is server-side. Servers like updates.mailmate-app.com
should be reconfigured to send only the server certificate and its
immediate issuer cert as the server's trust chain, NOT including the
version of "ISRG Root X1" which is signed by the expired cert. That
would break a DIFFERENT subset of older clients (which don't trust the
ISRG root by default) which is probably why even Let's Encrypt's own
servers are still sending the quasi-bogus cert.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
___
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
