During a cloud migration from a on-premise Exchange server behind a commercial firewall to a full Office365 Exchange we noticed the amount of spam that was getting through. Here is an example of the email.
The phishing email looks very genuine, but isn’t. We hope you find this information prior to an incident at your facility and it helps you thwart any attempt at gaining access to your facilities network.
We noticed users were having issues opening Office documents like a Word or Excel file that was sent to them via email. Everything looks normal, but when they click on the file to open it they get the following error.
The fix is really easy.
Save the file to your machine
Right-click on the file and go down to “Properties“.
On the General Tab, check “Unblock” and click okay. This may be on the Security tab.
We upgraded a Windows 7 machine to Windows 10 via the Media Creation Tool. Once the upgrade was finished Outlook wouldn’t run. We got the following error.
We uninstalled and re-installed the Office program but this didn’t solve the issue. We ran a repair from the “uninstall Program” but choosing “repair”. This time I start to check Office by opening Word and not Outlook. Word opened fine and so did all the rest of the Office suite. Outlook opened like it should.
Had a user who started to get this message. “Your message couldn’t be delivered because you weren’t recognized as a valid sender”. Logged into their Office 365 Admin account and went to Protection >> Action Center. Saw the user there and clicked “unblock” them. It took a minute, and came back with the user still in the list. I tried to send an email at the user and got the same error. In the Admin panel >> Action Center the user was still listed. I clicked “unblock” again and this time the user wasn’t listed. I tried to send another email, and got the same error again. I see a alert on the Action Center page to go to the new “Restricted Users page“. This page didn’t show the user being blocked.
I looked at the error in the Non-Deliverable Report in the returned email. The error in the message is “550 5.1.8 Access denied, bad outbound sender“.
This page was a help to let me know it could take a few hours for the email to resume.
We recently had to move a domain from Wild West Domains to another Godaddy Reseller hosting account. This was able to be done in just a few minutes where a domain transfer usually takes a week to complete. We ran into issue when Godaddy moved the DNS in the background and then asked me what the MX record was. They didn’t explain to me that that we should have written it down, so now we had to start from scratch.
I logged into their Office 365 account as the Admin and went to Setup >> Domains. We could see there were issues with the various records.
We clicked on the domain name with the issue and it lead us to some screens to fix the issue.
We clicked on the “click here to view”.
Clicking on “Fix my Records” took me to a Godaddy Login where it asked for authorization and then it would fix my records; however, I had already went in and manually updated the records. Their page gave me good instructions on what records to add. It was broken up in sections and those sections had titles. Those title were the type of record I needed to add. In the image above you will see “MX Records” and CName Records”.
A customer called in because the hard drive in their copier died and was replaced. Since it was replaced the settings were never the same and their “Scan-to-folder” and “scan-to-email” was no longer working.
I could see there was an attempt by someone to get this set up; however, they would get an error about failing to send because of SMTP authentication. In the web interface of the printer which I reached by typing the IP address of the printer into the browser window and supplying the default credentials of “admin” and password “1111”.
Go to the “Properties” tab and in the Menu on the left under “Services” go to “Email” and then “Setup”. Go to the “Required Information” tab. This group is using Office 365 to handle their email, so I needed the following settings:
SMTP Server: smtp.office365.com
Host Name: check this box.
Device Email Address: I had to add a valid email address and password.
While still in the “SMTP (Email)” section go to the “SMTP Authentication” tab. Here is what we needed fixed. It should look like the following:
You can use the “test configuration” button to make sure it is working properly.
This YouTube video did help me get the connection to Active Directory working correctly.
Here is a link to Xerox’s support for the copier I was working on.