Communication Support send not the Email

questions
1

I have a problem with the communication support. Maybe you can help me with this. I have correctly installed the template and entered all the parameters correctly. But whenever I press the email button, I get the error message which I have uploaded in the picture. What’s wrong thank you for helping Walter
image

2

Hi Walter,
the smtp-implementation in Clarion is useless since TLS > 1.1 is mandantory on almost every well configured smtp-server.

The Communication-Support even nowadays in Clarion V11 is not able to support TLS 1.2 and so no mail sending can be done with clarion.
A pain in the ass.
Before 2018 it was no problem at all!

You may find some add ons, some external expensive tools like mail.dll or better use calls via run to Outlook or Thunderbird.

If you re interested in further details on sending with external Mail clients, fell free to let me know.

best regards from Hamburg, Germany

Ralph Rathmann

3

I thought I’d heard that there was an updated ClaRunEx DLL that you could get from support@softvelocity, with updated TLS. But I might not be remembering correctly.

4

Hi Jeff,
thanks for this information.

I am part of the C11 EE CSP, but havent got any information about that.
So i will give it a try.

regards
Ralph

Update: just wrote a mail to support…

5

Hallo Ralph vielen Dank für Deine Antwort die hat mir sehr geholfen, den vorher hat es funktioniert - wie Sie beschrieben haben.
Danke für Ihre Antwort und schön jemanden aus Deutschland hier zu treffen. Liebe Grüße Walter

6

Hello Ralph,

The following is some code I have using Mike Douglas’s LibCur that works against Microsoft servers correctly.
I hope this can help you.

! send_mail(),long

send_mail   procedure()!,long
curl        TCurlMailClass
res         CURLcode
is_ok       long
i           long
strTo       cstring(255)
add_to      long
    code
    is_ok = true
    curl.Init()

    curl.Server( gMail.server, gMail.port )
    curl.Account( gMail.user, gMail.passwd )
    curl.From( sFrom )

    add_to = 0
    strTo = ''
    !message(sTo)
    loop i = 0 to 9
        strTo = ItemS( sTo, i, ' ,;' )
        if clip(strTo) <> ''
            curl.AddRecipient( strTo ) !to/cc/bcc
            !message( strTo )
            add_to = add_to + 1
        else
            break
        end !* if *
    end !* loop *

    curl.UseSSL( CURLUSESSL_ALL )
    curl.SetSSLVerifyPeer( false )  !curl --insecure

    curl.Subject( _subject )
    curl.Body( _body )
    curl.AddAttachment( _attach )

    curl.SetOpt( CURLOPT_CONNECTTIMEOUT, 45 ) !connection timeout (seconds)

    res = curl.Send()
    if res = CURLE_OK
        sStatus = 'Mail enviado correctamente.'
    else
        sStatus = curl.StrError(res)
        is_ok = false
    end !* if *
    return is_ok

!* end *
1 Like
7

Hi Gustavo,

thank you, this looks very interesting and i will this give a try at first.

The Clarion support at [email protected] suggested another approach, but i only try that one, when i am really not successful after all.

Ralph

Hello Tim,

thank you for this reply.

In the meantime Gustavo Saracca posted on clarionhub an interesting reply, that uses libcurl .

As curl (my Version is 8.9.1 ) supports many protocols, i will give this a try at first.

best regards from Germany

Ralph Rathmann

Am 08.11.2024 um 17:37 schrieb [email protected]:
> Ralph,
>
> As far as I know TLS 1.2 is supported (and has been for a while). I will ask the Dev Team for details about how to enable it but it may be that it has to be specifically enabled on the OS (for at least some versions/installs of Windows)
>
> Here is a post/thread from a while back. It is specific to MSSQL but some of the implementation details may apply.
>
> Robert(Support)
>
> > changing the MSSQL protocol from TLS 1.0 and TLS 1.1 up to TLS 1.2. They are experiencing problems and the
> > Clarion app can’t establish a connection with MSSQL.
> —
> I had a similar problem with a new installation of a SQL Server 2019, and at that time noticed that Bruce J had described that issue as well on Clarionhub.com at
> Bug in ODBC SQL Server and OLEDB driver on Windows server 2016 when connecting to SQL Server 2019 running on Windows Server 2022 Error 772 or 18 SSL Security Error
>
> Bruce solved it by re-enabling TLS 1.0; however, I resolved the issue by installing the latest Microsoft SQL Native Driver on the client servers running our application. Although our app wasn’t using the actual native driver in the connection string, the update still fixed the connectivity for OLEDB.
> You can download the driver here_
> https://www.microsoft.com/en-us/download/details.aspx?id=50402 .
>
> Of course the client will still need to have TLS 1.2 enabled on the OS level. By default, that should be the case in any of the currently supported Windows OS versions. On the Window Server, you can check it with Nartac Software’s IIS Crypto tool → Client Protocols ( these settings are just the registry values).

8

Hallo Walter.

Ich verwende aufgrund des TLS-Zeugs seit Jahren “einfach” NetTalk,