1. Juan Pedro Sanz Diez
  2. PowerBuilder
  3. Friday, 5 November 2021 11:09 AM UTC

    Hello, friends.

    We are using pb2019 R3. Also, we are using using Rolands smtp code. they both work fine.

    But since this summer we are getting, sometimes, this error when sending emails. 

 

Command failed: 421 4.7.66 TLS 1.0 and 1.1 are not supported.
Pease upgrade/update your client to support TLS 1.2 Visit........

  I have seen in a microsoft page, that the server, gradually, would send back this message aleatory, for those request that are using 1.0 and 1.1, for warning.

 

In internet options I have unchecked "use TLS 1.0 and 1.1"  and keep checked "use TLS 1.2" 

 

Since we won't send a mass mailing until next month, we can't proof it.

 

The question is, is there someting to do in PB for this to work or it's just a OS problem? Do you have this problem? how did you solve this?

 

In any case, next month I will tell you if the solution proposed (unchecked "use TLS 1.0 and 1.1" ) works.

 

See the images bellow for error and configuration of TLS

 

Thanks in advance.

 

regards

 

Juan Pedro Sanz Díez

 

 

Attachments (2)
Who is viewing this page
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 3 February 2022 19:04 PM UTC
  2. PowerBuilder
  3. # 1

I'm not sure how to interpret this phrase:

"IMPORTANT: Beginning early 2022, we will selectively pick tenants and disable Basic Auth for all affected protocols except SMTP AUTH for a period of 12-48 hours. After this time, Basic Auth for these protocols will be re-enabled, if the tenant admin has not already re-enabled them using our self-service tools."
Does the "period of 12-48 hours" apply to smtp only, or to all the other protocols?

Anyway, this kind of indicates to me that Microsoft is doing "changes" in the way they allow us to authenticate, trying to push us away from 'legacy' authentication. There should be settings for adminstrators to re-enable these 'legacy' authentication methods. Have a read:

https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-september-2021-update/ba-p/2772210 

regards

Comment
There are no comments made yet.
Brad Howie Accepted Answer Pending Moderation
  1. Tuesday, 21 December 2021 18:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi everyone,

 

I'm just wondering if there's an accepted solution for this.  I too began experiencing the same issue as described by Juan in his original post, using Roland's original SMTP code.  I tried switching over to the code from PBNISMTP, but am still receiving the same error message about upgrading to TLS 1.2 .  I've attached the screenshot showing the error, as well as the SMTP settings, which match those in Miguel's post.  I tried multiple other configuration settings, but typically would then receive a generic '-4' error.

 

Next up, I'll try the Chilkat API as suggested by Chris, but was hoping for a non-paid solution.

 

Thanks in advance!

Brad

 

 

 

 

Attachments (2)
Comment
  1. Miguel Leeuwe
  2. Tuesday, 21 December 2021 20:09 PM UTC
Hi,

Just a tip: Have a look at 'mailkit'. That's an open source solution which is constantly being updated and improved by many developers. It might take away some of the headaches.
  1. Helpful
  1. Andres De la Ossa
  2. Thursday, 3 February 2022 18:16 PM UTC
Hi everyone!



I'm just having the same issue as Juan and Brad. I think it's sort of a MS thing with SMTP protocol because our provider told us XOauth2, shortly, will be the main authentication method. The thing is that, using PBNISMTP setting TLS 1.2 with AUTH LOGIN, sometimes works and others not and when it doesn't, throws -4 code.



I think it's not a matter of coding because I downloaded latest version of libraries Roland used and, with those, created an enhanced version of his project and I had the same behavior.



Is Chilkat a guaranteed solution to all this?



Thank you all.
  1. Helpful
  1. Brad Howie
  2. Thursday, 3 February 2022 19:42 PM UTC
Hi Andres,



After experimenting unsuccessfully with a few solutions, I made the decision to move to Chilkat. It's been working flawlessly for over a month without a single error reported. You can get a month free trial to make sure it meets your needs.



Brad
  1. Helpful 2
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 1 December 2021 17:55 PM UTC
  2. PowerBuilder
  3. # 3

To be honest, I was running the bugGenie using outlook for sending emails and it stopped working somewhere in October. I think Microsoft has changed its policy for authentication and now you have to use a token instead of a password (or something like that). I simply stopped using Outlook and used gmail instead.

Apart from all that: I think your smtp setting might be incorrect. 

From https://www.gmass.co/blog/outlook-smtp/ :

Outlook SMTP Settings

When you need to add your Outlook.com account (or Microsoft account / Hotmail account / Live.com account / MSN account) to another mail app (like Gmail), you’ll need to use the following SMTP settings:

  • SMTP Server Name: smtp.office365.com
  • SMTP Port Number: 587
  • SMTP Encryption Method: STARTTLS

Once you add these SMTP settings, you should be able to use another mail app to send emails from your Outlook account.

But how do you receive incoming emails?
To receive incoming emails, you’ll need to configure the IMAP settings or POP settings of the mail app you’ll be using.

Here are the IMAP settings for Outlook:

  • IMAP Server Name: outlook.office365.com
  • IMAP Port: 993
  • IMAP Encryption Method: TLS

And here are the POP settings for Outlook:

  • POP Server Name: outlook.office365.com
  • POP Port: 995
  • POP Encryption Method: TLS

However, to use POP, you’ll need to enable its access in Outlook.

Comment
  1. Juan Pedro Sanz Diez
  2. Friday, 3 December 2021 13:53 PM UTC
Thanks you Miguel. With the SMTP (smtp.office365.com) it works Fine!!!
  1. Helpful
  1. Miguel Leeuwe
  2. Friday, 3 December 2021 13:59 PM UTC
YW
  1. Helpful
There are no comments made yet.
Juan Pedro Sanz Diez Accepted Answer Pending Moderation
  1. Wednesday, 1 December 2021 10:31 AM UTC
  2. PowerBuilder
  3. # 4

 

Hello Roland

 

 Finally the solution unchecked "use TLS 1.0 and 1.1" hasn't worked, so I have tried with the new version in  https://www.topwizprogramming.com/pbnismtp.html

but I have not had any success....

Bellow , I have attached the snapshots. With the early versión it works fine, but with the new one it seems not to work. I have randomize the values of Connection Type, Auth Method an character Set values without any success....

 

Also, the message seems to be generic, where can I find out what the - 4 could mean?

Any idea to find a solution?

 

Thanks,

Juan Pedro Sanz Díez

 

Attachments (4)
Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 5 November 2021 18:36 PM UTC
  2. PowerBuilder
  3. # 5

I removed that SMTP example from my website due to the security library I used being out of date.

Try this one instead:

https://www.topwizprogramming.com/pbnismtp.html

It has a bulk mailer capability. The program connects to the server once, does multiple sends, and then disconnects. This makes it much faster than if it had to connect and disconnect for every send.

 

Comment
  1. Miguel Alzate
  2. Thursday, 26 May 2022 16:03 PM UTC
Hi, Roland. Is it possible to know the C code of your PBNISMTP.PBX extension?
  1. Helpful
  1. Roland Smith
  2. Thursday, 26 May 2022 16:23 PM UTC
The VS 2019 solution is available to download on the same page:

https://www.topwizprogramming.com/pbnismtp.html
  1. Helpful
  1. Miguel Alzate
  2. Thursday, 26 May 2022 20:28 PM UTC
Oh, fine! Thank you, Roland.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 5 November 2021 14:56 PM UTC
  2. PowerBuilder
  3. # 6

Hi Juan;

  I would suggest trying another SMTP inteface. For example, this one already supports TLS 1.2 & 1.3 as well  ...

https://www.example-code.com/powerbuilder/smtp_enable_tls_1_3.asp

HTH

Regards ... Chris

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Friday, 5 November 2021 13:04 PM UTC
  2. PowerBuilder
  3. # 7

Hi.

Maybe you should contact Roland Smith. Anyway, in his source I see some checks for TLSv1, TLSv1_1, TLSv1_2 and even AnyTLS, so I guess that his library is compatible with TLS 1.2. Cannot help more than that. I'm not a c++ expert.

Andreas.

Comment
  1. Juan Pedro Sanz Diez
  2. Friday, 5 November 2021 14:53 PM UTC
thanks.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.