Issues migrating away from Indy

[Jan Breukelman 0]

Hi, We are trying to migrate away from Indy because of the lack of modern OpenSSL dll's and no OAuth support

Now we implemented the first part: Moving from TIdSMTP to TSslSmtpCli.

At first it looked fine, but at the moment we went to production a lot of SSL errors occurred: SSL handshake failed - No error returned, connection closed unexpectedly, but not all the time.

Out application is a ISAPI module, with datasnap,  where multiple clients can give the server the order to send emails. Some of these need to be send asynchrone, some synchrone.

I came across the following topic and if there is any application which runs completely in thread, it is an isapi module.

 How should the sending of email be implemented in such a case?

 

Thanx in advance,

Jan

[Angus Robertson 625]

ICS has a specific component for sending email, TIcsMailQueue, it uses a thread with a TSslSmtpCli component to send email previously saved in EML files, using multiple servers and retries over many hours to ensure email is sent.  It handles all the SSL stuff for you.  

 

The main sample is OverbyteIcsMailQu which has OAuth2, but the component is also used in several server samples.

 

Haven't written an ISAPI for many years, but the component should run in a DLL easily.

 

Angus

 

 

 

 

[Remy Lebeau 1542]

6 hours ago, Jan Breukelman said:

Hi, We are trying to migrate away from Indy because of the lack of modern OpenSSL dll's

Just because modern OpenSSL is not directly in Indy itself yet does not mean there are no options for it at all.  For example:

https://github.com/JPeterMugaas/TaurusTLS

6 hours ago, Jan Breukelman said:

and no OAuth support

Did you see this?

https://www.indyproject.org/2024/10/20/sasl-oauth-support-finally-added-to-master/

[Jan Breukelman 0]

Thanks @Remy Lebeau 
This is much safer than migrating to a new component.