jholzhey_bu · Technical Administrator, Bruin Support Services · ✭✭✭✭✭

LOL @ "defiantly." That's absolutely right!! OK, I'll report it. Thanks again, P!!

[View:/cfs-file/__key/communityserver-discussions-components-files/38/Email-Template-Demo.mp4:800:407] Sorry, didn't have time to shrink it down.

Let me try recording a screen video. I'll try getting it posted within the hour.

Yes, but I was wondering about that. Years ago, we had to generate and add a password to all new accounts. When we integrated with our SSO solution (OKTA), I stopped doing that. So OLDER accounts have a password, new accounts do not, and it's the older accounts that have problems. So I wondered if migrate.bat had anything…

NULLing out the hashed PW field in the TECH table did not fix the issue. So it's gotta be saved somewhere else, too. Any chance someone knows where?

Can anyone verify that they're having the same problem? Or perhaps that I'm just doing something wrong?

Update! Pretty sure the problem is related to the older accounts that I had to manually add passwords to when they removed LDAP auth support for Techs. For new accounts, I don't have to set a password, because I have PW settings hidden, and new accounts are not having this problem at all. So now I have to see if there's a…

Excellent! Finally, some good news!

"Office 365 access token reauthorization is now improved for incoming mail account" WHD 12.8.7 release notes I'll be updating my Test env ASAP and start testing.

Here's the most recent message I got from Danica on 6/30/25: "Our engineering and dev teams are still monitoring the WHD environments where they deployed the DB. So far, they have not yet received reports about email issues with Microsoft 365 recurring, such as losing reauthorization. Based on the previous findings,…

Ah! I've never heard that term ever. I guess I've always thought of that as just testing in general.

Uh...BD? I'm guessing it's something super simple that I'm too stupid to figure out? 

MS Graph. That was a whole thing when we first couldn't get Outbound mail working. However, Danica contacted me last night and said it's definitely still broke in 12.8.6, but we may be able to use our test environment as a guinea pig. For what, I'm not sure.

Premature celebration. It's still a problem. However, there is some good news about the upgrade. Our deleted messages are finally being moved to the Deleted Items folder, like they're supposed to be. That's been a problem since moving to 12.8.

Upgraded our Test environment to 12.6.x. It's only been about 20 hours so far, but no auth errors yet. They obviously messed around with the function in order to add support for Gmail, so I'm hoping it's finally fixed. Not sure how long to wait to do prod. I may just do it tonight, since it's definitely not getting worse.…

OH!! Was that just a 12.8.5 thing? I never made the connection.

She already tried NP++. It has a 2GB limit. Regardless, it's a good idea. Lemme try to split it in half.

Ah, OK. Latest update for me is Danica having trouble opening my 3.62 GB log file. 

Do you have a ticket # I can reference for them?

Wait, are you me from a slightly different timeline, because yeah...samesies. Again.

Well here's something interesting. This morning, my test system started failing for the very 1st time. I changed nothing. 

I was just about to post this exact same message. Including the brain part.

I've gotten that same response, weeks ago. My ticket for it is actually on hold or whatever it is.

We have a scheduled task to create a ticket and auto-assign to either me or my backup every 80 days, since the auth expires at 90. We got to ignore the ticket this last time because we've been doing it daily for weeks now. I need to set up another task for the "24-month" exp. for the secret. Point is, yes, this can…

Perfect! You're (still) awesome!

Well, here's a kicker. I just now noticed that we had one mailbox (out of 6) that started failing yesterday just after 2PM, and 14 & 1/2 hours later, decided to start working again at 4:30 AM. All on its own. No reauth.

Oh, definitely! This is why I'm so worried about going back for this security update. We're backed into a corner.