Posted by Leroy Zurovec on October 28, 2021 at 06:42:04:
We have recently begun experiencing a communication error when trying to send emails via Comet to O365. The message "unexpected error 29 encountered" displays. After acknowledging the message several times, the email(s) are sent. Is this due to a change made by Microsoft to O365.
Email Log:
Signature Systems Email Printer Started Thu, 28 Oct 2021 06:22:20 -0600 +0100
GMT time will be used for the date
>c>WEOL 1
+OK CRLF will be appended to each print
>c>CONNECT smtp.office365.com 587
+OK Connected to smtp.office365.com on port 587
>c>TIMEOUT 30
+OK Timeout set
220 CH2PR02CA0016.outlook.office365.com Microsoft ESMTP MAIL Service ready at Thu, 28 Oct 2021 11:24:38 +0000
>>>EHLO smtp.office365.com
250-CH2PR02CA0016.outlook.office365.com Hello [12.87.131.74]
250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
>>>STARTTLS
220 2.0.0 SMTP server ready
>c>SSL-ENABLE
-ERR SSL renegotiation failed
SSL Enabled for TLS re-negotiation
>>>EHLO signature.net
Unexpected error 29 encountered.
Email.ini:
server = smtp.office365.com 587
user = billing@metroelectricsupply.com
password = M*********
tls=true
Also, I have been notified by the company that provides our email support that within the next 9 to 12 months Microsoft will switch from legacy authentication to modern authentication for all devices. Does anyone know if Comet will handle this?
Thanks
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.