Remy Lebeau

I like using "Auto Mark as Read". It goes inline with how other email readers work. But I don't want to use "Mark messages as read when leaving the group...

If I am reading a message, and it gets marked as read, I don't want the message to become hidden while I am still reading it because "Hide Read Messages"...

I thought the whole purpose of `(package_)compiler_...` was to prevent this kind of thing from happening? If the `min/max` is set to 10.2, then the package shouldn't be made available...

> but failed on the Indy part Can you be more specific? Was it a due to a problem with how Indy handles an `SSLIOHandler` server-side, or was it due...

The problem appears to be in `TIdSSLIOHandlerSocketSChannel.Clone()`, which `TIdFTP` calls when setting up a new data connection. `TIdFTP` clones the `SSLIOHandler` of the control connection, expecting the clone to reuse...

> what it the purpose of the Clone method ? To create a new `SSLIOHandler` object that shares a TLS session with an existing `SSLIOHandler` object. > the TLS session...

The change you propose for `IdSASLCollection.pas` really belongs in `IdSASLLogin.pas` instead, as such prompt handling is specific to the `AUTH LOGIN` command and not to other SASLs. However, better handling...

@MWASoftware (and anyone else who is interested in contributing to this effort) - there is a new joint initiative with Embarcadero and some other 3rd party devs to get Indy...

> Remy, Did you get the message I sent you via the contact page on indyproject.org? I saw your comment on the recent blog post. I replied to you privately.

Indy natively supports OpenSSL only up to 1.0.2u (see IndySockets/IndyTLS-OpenSSL#10). Chances are that `libcrypto.so` and `libssl.so` on your Linux machine are symlinks to a newer OpenSSL version. If so, Indy...