#techsupport — Public Fediverse posts on home.social

Max @[email protected] · 2026-05-22 · 13:43 UTC

One of the biggest curses in #techsupport is that #microsoft called it WINDOWS Explorer and INTERNET explorer in #windows and 9/10 users don’t know what the windows explorer is (resp. don’t know its name) …

#WindowsExplorer #InternetExplorer

#techsupport #microsoft #windows #windowsexplorer #internetexplorer

Max @[email protected] · 2026-05-22 · 13:43 UTC

One of the biggest curses in #techsupport is that #microsoft called it WINDOWS Explorer and INTERNET explorer in #windows and 9/10 users don’t know what the windows explorer is (resp. don’t know its name) …

#WindowsExplorer #InternetExplorer

#techsupport #microsoft #windows #windowsexplorer #internetexplorer

Max @[email protected] · 2026-05-22 · 13:43 UTC

One of the biggest curses in #techsupport is that #microsoft called it WINDOWS Explorer and INTERNET explorer in #windows and 9/10 users don’t know what the windows explorer is (resp. don’t know its name) …

#WindowsExplorer #InternetExplorer

#techsupport #microsoft #windows #windowsexplorer #internetexplorer

Max @[email protected] · 2026-05-22 · 13:43 UTC

One of the biggest curses in #techsupport is that #microsoft called it WINDOWS Explorer and INTERNET explorer in #windows and 9/10 users don’t know what the windows explorer is (resp. don’t know its name) …

#WindowsExplorer #InternetExplorer

#internetexplorer #windowsexplorer #windows #microsoft #techsupport

Max @[email protected] · 2026-05-22 · 13:43 UTC

One of the biggest curses in #techsupport is that #microsoft called it WINDOWS Explorer and INTERNET explorer in #windows and 9/10 users don’t know what the windows explorer is (resp. don’t know its name) …

#WindowsExplorer #InternetExplorer

#techsupport #microsoft #windows #windowsexplorer #internetexplorer

Bob Young @[email protected] · 2026-05-21 · 17:02 UTC

Microsoft can still surprise us. Yesterday a client scheduled for a remote support call at 9am today. The problem was that he was receiving error messages from Microsoft saying that his mailbox was almost full. At the appointed time I connected remotely to his computer, and watched while he pulled up the message. It was an email, rather than an in-app Outlook message, so the first thing I did was examine the header to make sure it was real (it was).

Here’s the surprise: Microsoft’s “mailbox full” messages come from an email account that has no DKIM signature and no DMARC policy! This is a classic first-blush clue that an email may be either malicious or spam.

Next, I looked at File – Options, and the in-app message was there, too, so it was indeed legitimate.

I enabled autoarchive, with message deletion from the mailbox after archiving, to fix the problem. BTW, I did this as a two-step process. First, I verified that archiving was working, and the location of the archive file. With that assurance, I enabled deletion from the mailbox.

So the issue was easy enough to fix – a simple configuration error – but, Microsoft, why are you using any email accounts with no DKIM signature and no DMARC policy? Set a good example for us!

#CallMeIfYouNeedMe #FIFONetworks

#TechSupport #HelpDesk #ServiceCall #Email

Cybersecurity - Networks - Wireless – Telecom – VoIP

#callmeifyouneedme #fifonetworks #techsupport #helpdesk #servicecall #email

Bob Young @[email protected] · 2026-05-21 · 17:02 UTC

Microsoft can still surprise us. Yesterday a client scheduled for a remote support call at 9am today. The problem was that he was receiving error messages from Microsoft saying that his mailbox was almost full. At the appointed time I connected remotely to his computer, and watched while he pulled up the message. It was an email, rather than an in-app Outlook message, so the first thing I did was examine the header to make sure it was real (it was).

Here’s the surprise: Microsoft’s “mailbox full” messages come from an email account that has no DKIM signature and no DMARC policy! This is a classic first-blush clue that an email may be either malicious or spam.

Next, I looked at File – Options, and the in-app message was there, too, so it was indeed legitimate.

I enabled autoarchive, with message deletion from the mailbox after archiving, to fix the problem. BTW, I did this as a two-step process. First, I verified that archiving was working, and the location of the archive file. With that assurance, I enabled deletion from the mailbox.

So the issue was easy enough to fix – a simple configuration error – but, Microsoft, why are you using any email accounts with no DKIM signature and no DMARC policy? Set a good example for us!

#CallMeIfYouNeedMe #FIFONetworks

#TechSupport #HelpDesk #ServiceCall #Email

Cybersecurity - Networks - Wireless – Telecom – VoIP

#callmeifyouneedme #fifonetworks #techsupport #helpdesk #servicecall #email

Bob Young @[email protected] · 2026-05-21 · 17:02 UTC

Microsoft can still surprise us. Yesterday a client scheduled for a remote support call at 9am today. The problem was that he was receiving error messages from Microsoft saying that his mailbox was almost full. At the appointed time I connected remotely to his computer, and watched while he pulled up the message. It was an email, rather than an in-app Outlook message, so the first thing I did was examine the header to make sure it was real (it was).

Here’s the surprise: Microsoft’s “mailbox full” messages come from an email account that has no DKIM signature and no DMARC policy! This is a classic first-blush clue that an email may be either malicious or spam.

Next, I looked at File – Options, and the in-app message was there, too, so it was indeed legitimate.

I enabled autoarchive, with message deletion from the mailbox after archiving, to fix the problem. BTW, I did this as a two-step process. First, I verified that archiving was working, and the location of the archive file. With that assurance, I enabled deletion from the mailbox.

So the issue was easy enough to fix – a simple configuration error – but, Microsoft, why are you using any email accounts with no DKIM signature and no DMARC policy? Set a good example for us!

#CallMeIfYouNeedMe #FIFONetworks

#TechSupport #HelpDesk #ServiceCall #Email

Cybersecurity - Networks - Wireless – Telecom – VoIP

#callmeifyouneedme #fifonetworks #techsupport #helpdesk #servicecall #email

Bob Young @[email protected] · 2026-05-21 · 17:02 UTC

Microsoft can still surprise us. Yesterday a client scheduled for a remote support call at 9am today. The problem was that he was receiving error messages from Microsoft saying that his mailbox was almost full. At the appointed time I connected remotely to his computer, and watched while he pulled up the message. It was an email, rather than an in-app Outlook message, so the first thing I did was examine the header to make sure it was real (it was).

Here’s the surprise: Microsoft’s “mailbox full” messages come from an email account that has no DKIM signature and no DMARC policy! This is a classic first-blush clue that an email may be either malicious or spam.

Next, I looked at File – Options, and the in-app message was there, too, so it was indeed legitimate.

I enabled autoarchive, with message deletion from the mailbox after archiving, to fix the problem. BTW, I did this as a two-step process. First, I verified that archiving was working, and the location of the archive file. With that assurance, I enabled deletion from the mailbox.

So the issue was easy enough to fix – a simple configuration error – but, Microsoft, why are you using any email accounts with no DKIM signature and no DMARC policy? Set a good example for us!

#CallMeIfYouNeedMe #FIFONetworks

#TechSupport #HelpDesk #ServiceCall #Email

Cybersecurity - Networks - Wireless – Telecom – VoIP

#email #servicecall #helpdesk #techsupport #fifonetworks #callmeifyouneedme

Bob Young @[email protected] · 2026-05-21 · 17:02 UTC

Microsoft can still surprise us. Yesterday a client scheduled for a remote support call at 9am today. The problem was that he was receiving error messages from Microsoft saying that his mailbox was almost full. At the appointed time I connected remotely to his computer, and watched while he pulled up the message. It was an email, rather than an in-app Outlook message, so the first thing I did was examine the header to make sure it was real (it was).

Here’s the surprise: Microsoft’s “mailbox full” messages come from an email account that has no DKIM signature and no DMARC policy! This is a classic first-blush clue that an email may be either malicious or spam.

Next, I looked at File – Options, and the in-app message was there, too, so it was indeed legitimate.

I enabled autoarchive, with message deletion from the mailbox after archiving, to fix the problem. BTW, I did this as a two-step process. First, I verified that archiving was working, and the location of the archive file. With that assurance, I enabled deletion from the mailbox.

So the issue was easy enough to fix – a simple configuration error – but, Microsoft, why are you using any email accounts with no DKIM signature and no DMARC policy? Set a good example for us!

#CallMeIfYouNeedMe #FIFONetworks

#TechSupport #HelpDesk #ServiceCall #Email

Cybersecurity - Networks - Wireless – Telecom – VoIP

#callmeifyouneedme #fifonetworks #techsupport #helpdesk #servicecall #email