MaxBulk newest plus Office365 not sending mails

bwiecha · Feb 23, 2022

Hello ,
I am trying to resolve issue with sending mails via office365.
during tests I got only:

[01] 2/23 09:50:39 ~ Opening connection for delivery...
[01] 2/23 09:50:39 ~ Connecting to smtp.office365.com Port:587
[01] 2/23 09:50:40 ~ Connected
[01] 2/23 09:50:40 220 FR3P281CA0001.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 23 Feb 2022 08:50:39 +0000
[01] 2/23 09:50:40 > EHLO [xxx.xxx.xxx.xxx]
[01] 2/23 09:50:40 250-FR3P281CA0001.outlook.office365.com Hello [xxx.xxx.xxx.xxx]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 2/23 09:50:40 > STARTTLS
[01] 2/23 09:50:40 220 2.0.0 SMTP server ready
[01] 2/23 09:50:40 ~ Connected
[01] 2/23 09:50:40 > EHLO [xxx.xxx.xxx.xxx]
[01] 2/23 09:50:40 250-FR3P281CA0001.outlook.office365.com Hello [xxx.xxx.xxx.xxx]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH LOGIN XOAUTH2
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 2/23 09:50:40 > AUTH LOGIN
[01] 2/23 09:50:40 334 VXNlcm5hbWU6
[01] 2/23 09:50:40 > [email protected]
[01] 2/23 09:50:40 334 UGFzc3dvcmQ6
[01] 2/23 09:50:40 > **************
[01] 2/23 09:50:40 421 4.7.66 TLS 1.0 and 1.1 are not supported. Please upgrade/update your client to support TLS 1.2. Visit https://aka.ms/smtp_auth_tls. [FR3P281CA0001.DEUP281.PROD.OUTLOOK.COM]
[01] 2/23 09:50:40 ~ Remote server has unexpectedly closed the connection (#102). Stage: -1
[00] 2/23 09:50:40 ~ [!]
[00] 2/23 09:50:50 ~ Delivery incomplete -> Sent (0) + Errors (0) < Total (2)
[00] 2/23 09:50:50 ~ Socket #1 Pointer: 1 Total: 2
[00] 2/23 09:50:50 ~ Reconnecting to smtp.office365.com Port:465
[01] 2/23 09:51:11 ~ The server smtp.office365.com doesn't respond. Trying on port #2525
[00] 2/23 09:51:28 ~ Canceling process...
[00] 2/23 09:51:28 ~ Asking socket #1 to QUIT...
[00] 2/23 09:51:28 ~ [!]
[00] 2/23 09:51:28 ~ Closing all streams
[00] 2/23 09:51:28 ~ Unlinking socket #1 port
[00] 2/23 09:51:28 ~ Creating report...
[00] 2/23 09:51:28 ~ Finishing...
[00] 2/23 09:51:28 ~ Finished.

-----------------------------------------------------------------------
MaxBulk Mailer Delivery Report [#60] - 23.02.2022
-----------------------------------------------------------------------

Mailer version: 8.8.1-US (4) 64bit Pro - Registered
Machine OS/speed: Windows 10 (Build 19042)/2.371Ghz

Streams: 1 [1 Used | 1 Dropped] Single Server
Delivery mode: Singly (Tag processing ON)

SMTP server address: smtp.office365.com [Port: 587] đź”’TLS v1.2 Exp
Authentication: ESMTP (Login) | [xxx.xxx.xxx.xxx]
Signature: No
Groups: 25 [Interval: 00:03:45]

Delivery start date: 23.02.2022 at 09:50:38
End date: 23.02.2022 at 09:51:28
Total duration: 50 second(s) (Cancelled by user)
Rate: 0,02 recipient(s)/second

to a total of: 2 recipient(s) [2/103]
List name: unknown
Sent: 0
Failed: 2 undelivered [Delivery cancelled by user]

Mail subject: [Info]
Mail priority: Normal
Reply To: [email protected] (Sender)
Errors: [email protected] (Sender)
Return receipt: No
Mail format: Styled Text | utf-8 | quoted-printable
Mail size: 0 Bytes (Doesn't include attachments)
Attachments: 1 (17 Bytes)
Encoding: Base64

MLM: Click-through tracking [Deactivated]

-----------------------------------------------------------------------

so all IP and mails are changed over here to random

Not receiving / connecting to host at all

Update:
https://www.maxprog.com/site/support/us/maxbulkmailer/how-to-send-bulk-email-with-office365.php did not worked. And via adding password app on ms site there as no way to add it (no password app on the ms list)

stanbusk · Feb 23, 2022

Are you using some kind of proxy? MaxBulk Mailer only uses TLSv1.2 however the server says a TLSv1.1 is being used.

bwiecha · Feb 24, 2022

stanbusk said:
Are you using some kind of proxy? MaxBulk Mailer only uses TLSv1.2 however the server says a TLSv1.1 is being used.

No , not at all. direct connection to smtp.office365.com

stanbusk · Mar 13, 2022

I found out that some accounts are returning that error. I really don't know why but it looks like a bug.

bwiecha · Mar 16, 2022

stanbusk said:
I found out that some accounts are returning that error. I really don't know why but it looks like a bug.

So that means it will not work at all on my setup ? (buggy software)

stanbusk · Mar 16, 2022

Exactly, buggy server software. Only office365 has this problem but not on all accounts. We have an office365 here and it works just fine.

Code:

[01] 3/16 06:06:39     ~ Opening connection for delivery...
[01] 3/16 06:06:39     ~ Connecting to smtp.office365.com Port:587
[01] 3/16 06:06:39     ~ Connected
[01] 3/16 06:06:39 220 BN9PR03CA0263.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 16 Mar 2022 12:06:39 +0000
[01] 3/16 06:06:39 > EHLO [192.168.100.82]
[01] 3/16 06:06:39 250-BN9PR03CA0263.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:39 > STARTTLS
[01] 3/16 06:06:40 220 2.0.0 SMTP server ready
[01] 3/16 06:06:40     ~ Connected
[01] 3/16 06:06:40 > EHLO [192.168.100.82]
[01] 3/16 06:06:40 250-BN9PR03CA0263.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH LOGIN XOAUTH2
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:40 > AUTH LOGIN
[01] 3/16 06:06:40 334 VXNlcm5hbWU6
[01] 3/16 06:06:40 > [email protected]
[01] 3/16 06:06:40 334 UGFzc3dvcmQ6
[01] 3/16 06:06:40 > ********************
[01] 3/16 06:06:43 235 2.7.0 Authentication successful
[01] 3/16 06:06:43 > MAIL FROM:<[email protected]>
[01] 3/16 06:06:43 250 2.1.0 Sender OK
[01] 3/16 06:06:43 > RCPT TO:<[email protected]> [1/1]
[01] 3/16 06:06:43 250 2.1.5 Recipient OK
[01] 3/16 06:06:43 > DATA
[01] 3/16 06:06:43 354 Start mail input; end with <CRLF>.<CRLF>
[01] 3/16 06:06:43     ~ Sending message
[01] 3/16 06:06:43     ~ with ID <[email protected]>
[01] 3/16 06:06:43     ~ To [email protected]
[01] 3/16 06:06:45 250 2.0.0 OK <AM0PR04MB69966A19746E6469F9526685B1119@AM0PR04MB6996.eurprd04.prod.outlook.com> [Hostname=AM0PR04MB6996.eurprd04.prod.outlook.com]
[01] 3/16 06:06:45     ~ Stage 3 dispatch done
[01] 3/16 06:06:45 > QUIT
[01] 3/16 06:06:45 221 2.0.0 Service closing transmission channel
[01] 3/16 06:06:45     ~ Stage 4 dispatch done
[00] 3/16 06:06:45     ~ [-????]
[00] 3/16 06:06:45     ~ Closing all streams
[00] 3/16 06:06:45     ~ Creating report...
[00] 3/16 06:06:45     ~ Sending report...
[01] 3/16 06:06:45     ~ Opening connection for delivery...
[01] 3/16 06:06:45     ~ Connecting to smtp.office365.com Port:587
[01] 3/16 06:06:45     ~ Connected
[01] 3/16 06:06:45 220 BN9PR03CA0253.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 16 Mar 2022 12:06:44 +0000
[01] 3/16 06:06:45 > EHLO [192.168.100.82]
[01] 3/16 06:06:45 250-BN9PR03CA0253.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:45 > STARTTLS
[01] 3/16 06:06:45 220 2.0.0 SMTP server ready
[01] 3/16 06:06:45     ~ Connected
[01] 3/16 06:06:45 > EHLO [192.168.100.82]
[01] 3/16 06:06:45 250-BN9PR03CA0253.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH LOGIN XOAUTH2
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:45 > AUTH LOGIN
[01] 3/16 06:06:45 334 VXNlcm5hbWU6
[01] 3/16 06:06:45 > [email protected]
[01] 3/16 06:06:45 334 UGFzc3dvcmQ6
[01] 3/16 06:06:45 > ********************
[01] 3/16 06:06:48 235 2.7.0 Authentication successful
[01] 3/16 06:06:48 > MAIL FROM:<[email protected]>
[01] 3/16 06:06:48 250 2.1.0 Sender OK
[01] 3/16 06:06:48 > RCPT TO:<[email protected]> [1/1]
[01] 3/16 06:06:48 250 2.1.5 Recipient OK
[01] 3/16 06:06:48 > DATA
[01] 3/16 06:06:48 354 Start mail input; end with <CRLF>.<CRLF>
[01] 3/16 06:06:48     ~ Preparing report delivery
[01] 3/16 06:06:48     ~ with ID <[email protected]>
[01] 3/16 06:06:48     ~ To [email protected]
[01] 3/16 06:06:49 250 2.0.0 OK <AM0PR04MB6996FBD6D8694DC317FB5483B1119@AM0PR04MB6996.eurprd04.prod.outlook.com> [Hostname=AM0PR04MB6996.eurprd04.prod.outlook.com]
[01] 3/16 06:06:49     ~ Stage 3 dispatch done
[01] 3/16 06:06:49 > QUIT
[01] 3/16 06:06:49 221 2.0.0 Service closing transmission channel
[01] 3/16 06:06:49     ~ Stage 4 dispatch done
[00] 3/16 06:06:49     ~ [-]
[00] 3/16 06:06:49     ~ Finishing...
[00] 3/16 06:06:49     ~ Finished.

-----------------------------------------------------------------------
MaxBulk Mailer Delivery Report [#3,779] - 3/16/22
-----------------------------------------------------------------------

      Mailer version: 8.8.1-US (2) 64bit Pro - Registered
    Machine OS/speed: Mac OS 12.2.1/0Mhz

             Streams: 5 [1 Used] Single Server
       Delivery mode: Singly (Tag processing ON)

 SMTP server address: smtp.office365.com [Port: 587] TLS v1.2 Exp
      Authentication: ESMTP (Login) | [192.168.100.82]
           Signature: No
              Groups: 25 [Interval: 00:03:45]

 Delivery start date: 3/16/22 at 06:06:37
            End date: 3/16/22 at 06:06:45
      Total duration: 8 second(s) - Retries: 0/10
                Rate: 0.25 recipient(s)/second

       to a total of: 1 recipient(s) [1/8]
           List name: [TEST] Stanley - 6 entries
                Sent: 1

        Mail subject: Test
       Mail priority: Normal
            Reply To: [email protected] (Sender)
              Errors: [email protected] (Sender)
      Return receipt: No
         Mail format: Styled Text | utf-8 | quoted-printable
           Mail size: 28 Bytes (Doesn't include attachments)
         Attachments: none

                 MLM: Click-through tracking [Activated]

-----------------------------------------------------------------------

bwiecha · Mar 16, 2022

stanbusk said:

Exactly, buggy server software. Only office365 has this problem but not on all accounts. We have an office365 here and it works just fine.

Code:

[01] 3/16 06:06:39     ~ Opening connection for delivery...
[01] 3/16 06:06:39     ~ Connecting to smtp.office365.com Port:587
[01] 3/16 06:06:39     ~ Connected
[01] 3/16 06:06:39 220 BN9PR03CA0263.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 16 Mar 2022 12:06:39 +0000
[01] 3/16 06:06:39 > EHLO [192.168.100.82]
[01] 3/16 06:06:39 250-BN9PR03CA0263.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:39 > STARTTLS
[01] 3/16 06:06:40 220 2.0.0 SMTP server ready
[01] 3/16 06:06:40     ~ Connected
[01] 3/16 06:06:40 > EHLO [192.168.100.82]
[01] 3/16 06:06:40 250-BN9PR03CA0263.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH LOGIN XOAUTH2
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:40 > AUTH LOGIN
[01] 3/16 06:06:40 334 VXNlcm5hbWU6
[01] 3/16 06:06:40 > [email protected]
[01] 3/16 06:06:40 334 UGFzc3dvcmQ6
[01] 3/16 06:06:40 > ********************
[01] 3/16 06:06:43 235 2.7.0 Authentication successful
[01] 3/16 06:06:43 > MAIL FROM:<[email protected]>
[01] 3/16 06:06:43 250 2.1.0 Sender OK
[01] 3/16 06:06:43 > RCPT TO:<[email protected]> [1/1]
[01] 3/16 06:06:43 250 2.1.5 Recipient OK
[01] 3/16 06:06:43 > DATA
[01] 3/16 06:06:43 354 Start mail input; end with <CRLF>.<CRLF>
[01] 3/16 06:06:43     ~ Sending message
[01] 3/16 06:06:43     ~ with ID <[email protected]>
[01] 3/16 06:06:43     ~ To [email protected]
[01] 3/16 06:06:45 250 2.0.0 OK <AM0PR04MB69966A19746E6469F9526685B1119@AM0PR04MB6996.eurprd04.prod.outlook.com> [Hostname=AM0PR04MB6996.eurprd04.prod.outlook.com]
[01] 3/16 06:06:45     ~ Stage 3 dispatch done
[01] 3/16 06:06:45 > QUIT
[01] 3/16 06:06:45 221 2.0.0 Service closing transmission channel
[01] 3/16 06:06:45     ~ Stage 4 dispatch done
[00] 3/16 06:06:45     ~ [-????]
[00] 3/16 06:06:45     ~ Closing all streams
[00] 3/16 06:06:45     ~ Creating report...
[00] 3/16 06:06:45     ~ Sending report...
[01] 3/16 06:06:45     ~ Opening connection for delivery...
[01] 3/16 06:06:45     ~ Connecting to smtp.office365.com Port:587
[01] 3/16 06:06:45     ~ Connected
[01] 3/16 06:06:45 220 BN9PR03CA0253.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 16 Mar 2022 12:06:44 +0000
[01] 3/16 06:06:45 > EHLO [192.168.100.82]
[01] 3/16 06:06:45 250-BN9PR03CA0253.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:45 > STARTTLS
[01] 3/16 06:06:45 220 2.0.0 SMTP server ready
[01] 3/16 06:06:45     ~ Connected
[01] 3/16 06:06:45 > EHLO [192.168.100.82]
[01] 3/16 06:06:45 250-BN9PR03CA0253.outlook.office365.com Hello [179.42.225.0]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH LOGIN XOAUTH2
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
[01] 3/16 06:06:45 > AUTH LOGIN
[01] 3/16 06:06:45 334 VXNlcm5hbWU6
[01] 3/16 06:06:45 > [email protected]
[01] 3/16 06:06:45 334 UGFzc3dvcmQ6
[01] 3/16 06:06:45 > ********************
[01] 3/16 06:06:48 235 2.7.0 Authentication successful
[01] 3/16 06:06:48 > MAIL FROM:<[email protected]>
[01] 3/16 06:06:48 250 2.1.0 Sender OK
[01] 3/16 06:06:48 > RCPT TO:<[email protected]> [1/1]
[01] 3/16 06:06:48 250 2.1.5 Recipient OK
[01] 3/16 06:06:48 > DATA
[01] 3/16 06:06:48 354 Start mail input; end with <CRLF>.<CRLF>
[01] 3/16 06:06:48     ~ Preparing report delivery
[01] 3/16 06:06:48     ~ with ID <[email protected]>
[01] 3/16 06:06:48     ~ To [email protected]
[01] 3/16 06:06:49 250 2.0.0 OK <AM0PR04MB6996FBD6D8694DC317FB5483B1119@AM0PR04MB6996.eurprd04.prod.outlook.com> [Hostname=AM0PR04MB6996.eurprd04.prod.outlook.com]
[01] 3/16 06:06:49     ~ Stage 3 dispatch done
[01] 3/16 06:06:49 > QUIT
[01] 3/16 06:06:49 221 2.0.0 Service closing transmission channel
[01] 3/16 06:06:49     ~ Stage 4 dispatch done
[00] 3/16 06:06:49     ~ [-]
[00] 3/16 06:06:49     ~ Finishing...
[00] 3/16 06:06:49     ~ Finished.

-----------------------------------------------------------------------
MaxBulk Mailer Delivery Report [#3,779] - 3/16/22
-----------------------------------------------------------------------

      Mailer version: 8.8.1-US (2) 64bit Pro - Registered
    Machine OS/speed: Mac OS 12.2.1/0Mhz

             Streams: 5 [1 Used] Single Server
       Delivery mode: Singly (Tag processing ON)

 SMTP server address: smtp.office365.com [Port: 587] TLS v1.2 Exp
      Authentication: ESMTP (Login) | [192.168.100.82]
           Signature: No
              Groups: 25 [Interval: 00:03:45]

 Delivery start date: 3/16/22 at 06:06:37
            End date: 3/16/22 at 06:06:45
      Total duration: 8 second(s) - Retries: 0/10
                Rate: 0.25 recipient(s)/second

       to a total of: 1 recipient(s) [1/8]
           List name: [TEST] Stanley - 6 entries
                Sent: 1

        Mail subject: Test
       Mail priority: Normal
            Reply To: [email protected] (Sender)
              Errors: [email protected] (Sender)
      Return receipt: No
         Mail format: Styled Text | utf-8 | quoted-printable
           Mail size: 28 Bytes (Doesn't include attachments)
         Attachments: none

                 MLM: Click-through tracking [Activated]

-----------------------------------------------------------------------

Then waiting For Your Company to fix Your code for Office365 to work on all corporate servers . Not only few of them. Also the one You are testing is a free outlook.com account , not a corpo/pay plan office365.com account.

stanbusk · Mar 16, 2022

Ask Office365 support to fix the problem, I can't do anything.

Juhn_Hoo · Mar 31, 2022

Good Morning,

I have exactly the same problem and it seems that we will all have it.

Microsoft is rolling out TLS 1.2 in a phased manner, so sooner or later MaxBulk software will fail everyone who uses Office365.
Please try to fix it.
The error received is that the server detects that it is not TLS1.2 even though I have selected TLS1.2 Exp.
Please upgrade/update your client to support TLS 1.2. Visit https://aka.ms/smtp_auth_tls. [LO4P123CA0013.GBRP123.PROD.OUTLOOK.COM]

Also a few months ago it didn't fail and now it does. It is very clear that Microsoft Office 365 has changed its security policy and MaxBulk Mailer is not adapted for that.

Thanks for all.

Juhn_Hoo

stanbusk · Mar 31, 2022

This is a bug and it doesn't affect all Office365 users. Unfortunately, there is absolutely nothing I can do. A solution is to use a real bulk SMTP server like Authsmtp, turboSMTP, Amazon SES, RealSender, SMTP.com, MailJet, SendGrid, SMTP2GO, Mandrill or purchase a web hosting package that provides some webspace to store your website (and message pictures) and a mail server.

Juhn_Hoo · Mar 31, 2022

Hello,

The idea is to use the account with the corporate domain to send personalized emails. In my case we use office365 accounts linked to the corresponding domain.

If MaxBulk should work with office 365, I understand that you should find a solution. MaxBulk is great because it's so easy to use... but if it doesn't work properly with office 365 and you need another SMTP... it's no longer easy to use.

Thanks for all.

stanbusk · Mar 31, 2022

Yes indeed but if the issue is on the Office365 server you should understand there is very little I can do. We own an Offfice365 account here and it just works. I have never been able to reproduce the problem. I already posted a log demonstrating that. Anyway it is something I guess Office365 administrators will fix soon or later.

bwiecha · Apr 1, 2022

So in this point You should make an upgrade or a notification that most of office365.com would not work at all.

Juhn_Hoo · Apr 1, 2022

Hi

If from Maxprog you are aware that many clients have this incident... you should proactively try to see the cases of office 365 that fail. In my case, I insist it is a corporate account, that is, it is linked to my domain controller... that is, my domain is not hotmail.com or hotmail.es, it is the domain of my company.... On the other hand, the error that it gives is that the server that is the same for all users in the world detects that the client is trying to communicate via TLS1.0 or TLS1.1 if the program is configured for TLS1.2 Exp this should not fail.

Something is wrong either with the configuration or with something else.

Thanks for all

bwiecha · Apr 1, 2022

In my office365 is same type. Not a free hotmail/outlook account . This is a corporate account with domain . Just like Juhn_Hoo. Looks like almost same type but different domain. So then You should add or do something with this BUG. At least add info on main site that Your software is not supporting office365 corporate version . Just works on free accounts.

stanbusk · Apr 1, 2022

Our account is not a free account and it simply works. Only a very few amount of people is having this issue. I believe nobody is reporting it to Microsoft.

Juhn_Hoo · Apr 4, 2022

stanbusk said:
Our account is not a free account and it simply works. Only a very few amount of people is having this issue. I believe nobody is reporting it to Microsoft.

Hi

My office 365 license provider tells me that Microsoft is detecting that the MaxBulk client is not using TLS1.2.

If Microsoft does not allow the use of lower TLS1.2. From there it's like nonsense to report the bug to Microsoft... either you use TLS1.2 or you can't use the service.

In this case, the logical thing is to talk to the provider of the messaging client, in this case you.

Thanks for all

stanbusk · Apr 14, 2022

I am already working on this but if people complain to Microsoft perhaps we will get that fixed faster. It is the very only server that gives that error.

stanbusk · Apr 26, 2022

MaxBulk Mailer switched from TLSv1.1 to TLSv1.2 about 4 years ago when Google and most servers asked developers to drop old TLS versions because they would no longer be supported. TLSv1.2 is the last SSL version used on all secure servers including HTTPS. For a reason that is yet to be clarified, every server on earth works well except for some Office365 accounts. They indeed return an error that TLSv1.1 is used and that it is no longer supported. As stated before we switched to TLSv1.2 about 4 years ago. By the way, during those 4 years, all Office365 accounts were working well as any others. Then all of a sudden, since last month, some users are getting this error. It is clear that there is an Office365 issue here but we are investigating a way to bypass that error.

stanbusk · May 11, 2022

A solution is on the way. I believe we will be able to release a MaxBulk Mailer version with the fix by the end of July. For those of you that can't wait you can get a bulk email account at smtp2go. We can't release a version earlier because the problem is not really MaxBulk Mailer but the OpenSSL libraries.

MaxBulk newest plus Office365 not sending mails

New Member

Attachments

Administrator

New Member

Administrator

New Member

Administrator

New Member

Administrator

New Member

Administrator

New Member

Administrator

New Member

New Member

New Member

Administrator

New Member

Administrator

Administrator

Administrator