@travisdh1 thanks! 🙂

@scottalanmiller said in Does the end of O365 Basic Authentication mean no more app passwords:

@Pete-S said in Does the end of O365 Basic Authentication mean no more app passwords:

@JaredBusch said in Does the end of O365 Basic Authentication mean no more app passwords:

Customer has a LoB application called Enfocus Switch.

It has a mail retrieval function that connects via IMAP using an app password on a normal O365 email account with MFA enabled.

It stopped retrieving email on the morning of Wednesday October 12th.

Since Microsoft finally killed Basic Auth on Tuesday, I assume this is related, but I can find no information on this at all.

The vendor do what they do, but I noticed that most applications that need this kind of functionality uses mail forwards from customers mailboxes to their own IMAP mailboxes.

That can be a way to solve this when microsoft kills it. Redirect from customers O365 mailbox to another provider that supports IMAP with normal authentication. Have the LoB application use that inbox instead.

We have customers doing that. Setting up MailCow to get past all the primary vendor security systems.

That makes sense.

I think you could probably run a bare mailserver with just dovecot as well. Since it only needs to handle incoming email from Microsoft and be an IMAP server, there's a lot things that becomes irrelevant - like spam detection, ip reputation etc.

@scottalanmiller No example output? 🙂

@pete-s said in Email Send Error Research:

@dashrender said in Email Send Error Research:

@jaredbusch said in Email Send Error Research:

@wrcombs said in Email Send Error Research:

So would it likely to assume that Username and password are incorrect ?

If the computer receives email, then the username and password were likely correct. Outlook's account setup wizard will only ask for the information one time by default.

If this system has never been able to send email, what is likely incorrect is the email server configuration details.

If it once sent email, then mostlikely Outlook had a connection problem once and popped up the credentials box, then the user put in the wrong info.

This seems VERY likely at this point!

Probably entered the Windows password he uses to login.

Probably his personal email password from home.

Variation for Debian 10 + Dovecot 2.3.4.1:

cat /var/log/dovecot/dovecot.log | grep imap-login:\ Info:\ Login | sed -e 's/.*Login: user=<\(.*\)>, m ethod=.*/\1/g' | sort | uniq | wc -l

@scottalanmiller
Just found this thread. I love AquaMail. Been using it for years. It's worthy of mention!

Hi,

There should be a Data Migration option in the Google Apps Admin dashboard ...

@Ambarishrh said:

For postfix to work for this i need to have the full SMTP+IMAP configured

You are associating SMTP and IMAP. They are unrelated. Completely and totally unrelated.

Postfix is SMTP, it has no association with IMAP handling.

Just install Postfix and your sending is fixed. Just put in your IMAP details of your Gmail account and your IMAP is fixed because your application absolutely has a built in IMAP client, that's what those settings are for. Those settings cannot work unless it is a client.

@JaredBusch said:

@Dashrender said:

There are always fringe cases. but most of my users are not such cases.

My users either. Sadly two of those boxes are on premise still. One is Exchange 2007 and the other is Exchange 2010 and OWA sucks there.

I circle the O365 question back to the people involved every few months.

On premise at customer sites? Yeah mine too, and I'll be upgrading to Exchange 2016 very soon to give the better OWA experience before we move to O365.

@nadnerB

I have had great results with this and the other people in the thread I worked with reported similar results.