Fixing “Files in web page are not in the expected location”

Situation: When opening outlook, you may receive a popup “Files in web page are not in the expected location”.

Resolution 1: When Outlook opens, click the folder in the menu that appears. After selecting Properties, go to the Home Page tab. The web page that Outlook is attempting to display will be disabled if the box labeled “Show home page by default for this folder” is unchecked.

Resolution 2: Problem resolved! The user added a Signature File with an image and subsequently deleted the image from the original folder. We created a new Signature File and the problem immediately resolved itself.

Sending to Gmail and receiving an error code 550. 5.7.26

Situation: When sending email to Gmail address, the client receives Undeliverable return email with error code 550. 5.7.26.

Suggestion 1: Contact your domain name and DNS manage company and have them to add DMARC record…SPF Auth….

Suggestion 2: Check that your domain’s SPF record includes the SMTP server that you have put in the SMA setting.

Suggestion 3: If yourdomain.com has no SPF record.  Delivery from that domain will always be unreliable.

Suggestion 4: Domain name & server: land-com.net    email sent from a @deanland.com address

Earlier in the day I added the DNS TXT configuration to both land-com.net and deanland.com as a Google-suggested remedy for this problem. It worked, as Barracuda (security provider) let my email through after having bounced it before.
Domain fit-foxconn.com has an SPF record, but delivery will depend on what SMTP server the sender is using.

Suggestion 5: Domain deanland.com has two SPF records which will cause errors.  Please combine them unto one.

How does land-com.net relate to deanland.com?
If this is the server you are using to send messages as deanland.com, then the SPF record “v=spf1 ip4:108.161.133.200/32 include:spf.reachmail.net -all” authorises your messages, but “v=spf1 include:spf.reachmail.net include:aspmx.googlemail.com -all” does not.  It will be arbitrary as to which one is found by various receiving domains.
You do not need the Google include unless you need to use Google servers.  That would not be a recommended procedure for non-Google domains.
Suggestion 6: Your ERP server needs to be added to the SPF and/ or relay via your email server so that it authenticates for it.

Suggestion 7:Check your SPF here https://mxtoolbox.com/spf.aspx

Suggestion 8: There’s a help document here:

https://support.google.com/a/answer/178333?hl=en#zippy=%2Csender-policy-framework-spf%2Cdomain-key-s… 

If you follow the breadcrumbs back at the top of the help page you get a lot more help docs.

Seems like this would have come up before with ERP email system. If you want to do it the easy way, you might contact tech support for you ERP system, they’ve probably already figured this out.

Suggestion 7: I succeeded to fix this

Note:
Mail server IP  is 000.000.000.000
ERP Server IP is 111.111.111.111
Shown reason for the issue:
550-5.7.26 Unauthenticated email from example.com is not accepted due to the domain’s DMARC policy
But the DKIM and DMARC are not the targets for fixing.
The root cause for the issue:
ERP fail as the domain of me@example.com designates 111.111.111.111 (ERP’s IP address) is not permitted, sender) smtp.mailfrom=me@example.comHow it solved:
1- Updated the code in ERP “send-email.php” file
$config = Array(
‘protocol’ => ‘smtp’,
‘smtp_host’ => ‘mail.example.com’,
‘smtp_port’ => 465,
‘smtp_user’ => ‘system-mail@example.com‘,
‘smtp_pass’ => ‘password’,
‘charset’=>’utf-8’,
‘validate’=>TRUE,
‘wordwrap’=> TRUE,
‘dkim_domain’ => ‘example.com’,
‘dkim_selector’ => ‘mail’,

2- Equipped the Mail service daemon on the ERP server with relay sending capabilities as shown in the below tutorial.
https://www.bonusbits.com/wiki/HowTo:Configure_SendMail_to_Use_SMTP_Relay 

4- Updated the DNS records in the hosting company Cpanel to fit the modifications that were made.
– In the TXT section updated:

Host Record: @
TXT Value: v=spf1 mx a ip4:000.000.000.000 ip4:111.111.111.111 ~all
And updated:
Host Record: mail
TXT Value: v=spf1 mx a ip4:000.000.000.000 ip4:111.111.111.111 -all

Fixing Problem scanning. something went wrong. please try again

Situation: The client installs canon MF4800 Printer/Fax/Scan. All work except scan with this error: Problem scanning. something went wrong. please try again.

Resolution 1: It may have a Windows update pending. Install it and restart the Windows.

Resolution 2: Run System File Checker (SFC), follow these steps:

  1. In the search box on the taskbar, type command prompt, press and hold (or right-click) Command Prompt, then select Run as administrator > Yes.
  2. At the command prompt, type sfc /scannow (note the space between sfc and the /). Scanning will take a few minutes.
  3. Do one of the following, depending on the results of the scan:
    • If SFC finds corrupted files and replaces them, restart your PC and check if the issue persists.
    • If SFC doesn’t find corrupted files or finds corrupted files but can’t replace them, try using the Deployment Image Service and Management Tool (DISM).

Resolution 3: Use the Deployment Image Service and Management Tool (DISM), follow these steps:

  1. In the search box on the taskbar, type command prompt, press and hold (or right-click) Command Prompt, and then select Run as administrator > Yes.
  2. At the command prompt, type dism.exe /Online /Cleanup-image /Restorehealth (note the space between dism.exe and / and each switch (/)).
  3. If DISM finds corrupted files and replaces them, restart your PC and check if the issue persists.

Note: You need to be connected to the Internet to use DISM, and it might take several minutes to finish.

Resolution 3: The process was somewhat different, because I have my printer installed as a wired network printer to facilitate its use across my home network. But I essentially did the same thing: I removed all traces I could find of the drivers, disconnected printer from network, rebooted, plugged printer back into network (I’m not using USB, learning from past mistakes, then reinstalled WIndows 8 drivers from website. They seem to work for both print and scan.

Resolution 4:

Media create tool receives this error code 0x80070003 – 0xA001B

 

  • Resolution1:If you are receiving this error message on your device when using the Media Creation tool, the only option available is to retry the process until it works (slim chance). The only other working solution that will solve this problem is to create your Windows installation media using a different computer.
  • Resolution2:Resetting the Windows Update Components to fix the error code 0x80070003 with the KB5007186 update.
  • Resolution 3:Suggests clearing storage space in C: Drive on your system to fix the issue.
  • Resolution 4: Resetting the entire Windows Update component if the error is due to corrupted Windows Update dependencies. If the Windows Update component is malfunctioning, quick fixes include using Microsoft Update Catalog, the Media Creation Tool, or the Windows Update Assistant.
  • Resolution 5: Disabling CSM and enabling Secure boot if not and trying again. Others suggest downloading an ISO file from Microsoft servers and using Rufus to create an Installation media.

Can’t setup email after tenant migration with AADST50020

Situation: After migrating Microsoft tenant, some users can’t setup their email with this message; Sorry, we’re having trouble signing you in. AADST50020…

Troubleshooting: It could be the cache issue.

Resolution 1: Clean the email account cache.

Resolution 2: Remove and re-add Outlook app.

Go to Settings>App>Outlook, tap

Uninstall

 

Fixing 550 5.7.64 TenantAttribution; Relay Access Denied

Situation: After migrating Micrsoft tenant using Quest-on-demand, the client can’t send email to gmail with this error message:

550 5.7.64 TenantAttribution; Relay Access Denied [ValidationStatus of ‘CN=chicagotech.net’ is CertificateExpired] [AM7EUR03FT021.eop-EUR03.prod.protection.outlook.com 2023-10-05T14:05:40.792Z 08DBC59CBFCC3CE2]

Troubleshooting: When migrating Tenant, the client creates temporary certificates for Quest-on-demand on their DNS record. 

chicagotech.net. 60 IN MX 0 bt-esg-uksouth-1-1.odmad.quest-on-demand.com.

chicagotech.net. 60 IN MX 0 bt-esg-uksouth-1-2.odmad.quest-on-demand.com.

We find the quest on demand server is on the relay outbound by going to Exhange admin center under Mail flow Connectors, 

The resolution is disabling BT-IntegrationPro-Out… in Rules whch fixes the problem.