On Sun, 8 Dec 2019 10:30:33 -0500 (EST), Wietse Venema stated: >Gerard E. Seibert: >> Dec 8 09:42:30 scorpio postfix/smtp[87448]: 47W8Dj4Q1jz1xx1: SASL >> authentication failed; cannot authenticate to server >> smtp.office365.com[52.96.58.98]: invalid parameter supplied > >The "invalid parameter supplied" is a libsasl error message. > >According to posttls-finger (below my signature), they support two >SASL authentication methods: LOGIN and XOAUTH2. > >Let's get rid of XOAUTH2: > > # postconf -e "smtp_sasl_mechanism_filter = login" > # postfix reload > >and see if that makes a difference. > > Wietse > >% posttls-finger 52.96.58.98 >...plaintext handshake and tls handshake deleted... >posttls-finger: Untrusted TLS connection established to >52.96.58.98[52.96.58.98]:25: TLSv1.2 with cipher >ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) posttls-finger: > EHLO >tail.porcupine.org posttls-finger: < >250-MN2PR13CA0023.outlook.office365.com Hello [70.104.130.26] >posttls-finger: < 250-SIZE 157286400 posttls-finger: < 250-PIPELINING >posttls-finger: < 250-DSN posttls-finger: < 250-ENHANCEDSTATUSCODES >posttls-finger: < 250-AUTH LOGIN XOAUTH2 >posttls-finger: < 250-8BITMIME >posttls-finger: < 250-BINARYMIME >posttls-finger: < 250-CHUNKING >posttls-finger: < 250 SMTPUTF8 >posttls-finger: > QUIT >posttls-finger: < 221 2.0.0 Service closing transmission channel > > Wietse
Thank you for that quick and accurate answer. I was just wondering, is this a bug in 'libsasl' or is it due to a change in Outlook? My setup had been working for years without any errors. -- Gerard
