"Verify AppleID before we closed your account" ...

[yellowtriumph]

Originally Posted by Peter47

I recently got two bounced e-mails - postmaster@..... which I am sure that I have not sent (although I have been sending a lot of e-mails recently).

Is the scam that you click on the original message and infect your computer (the first) one or follow instructions to resend the message (second one, see below, but please DON'T click on link) or that my machine has been sending out messages that I am not aware of? I don't have Office 365 and use windows live mail which makes me suspicious.

If you do inadvertently open a file will a full antivirus scan make you safe or is it too late?
__________________________________________________________

Your message to zzzzz couldn't be delivered.
zzzzz wasn't found at zzzz.com.
petersgordon Office 365 kharrison Action Required Recipient Unknown To address
How to Fix ItThe address may be misspelled or may not exist. Try one or more of the following:

• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
• Contact the recipient (by phone, for example) to check that the address exists and is correct.
• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsoft.
More Info for Email AdminsStatus code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365. (Don't click on this!)

Original Message DetailsCreated Date:4/14/2017 6:12:58 AMSender Address:zzzzzzzzzRecipient Address:yyyyyyyySubject:You have notifications pending
Error DetailsReported error:550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup DSN generated by:CY1PR15MB0329.namprd15.prod.outlook.com

Message HopsHOPTIME (UTC)FROMTOWITHRELAY TIME14/14/2017
10:15:46 AMskunkworx.t2hadvertising.comBY2NAM03FT040.mail.protection. outlook.comMicrosoft SMTP Server4 hr, 2 min, 48 sec24/14/2017
10:15:47 AMBY2NAM03FT040.eop-NAM03.prod.protection.outlook.comBN6PR15CA0014.outlook.offic e365.comMicrosoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256)1 sec34/14/2017
10:15:48 AMBN6PR15CA0014.namprd15.prod.outlook.comCY1PR15MB0329.nampr d15.prod.outlook.comMicrosoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256)1 sec

I think you are suffering form 'spoofing'. This means that someone has gotten hold of the name of your email account domain and they are sending out emails 'all over the world' that look as though they have come from you. Apparently it is very easy to do. If the receiving account does not receive your email (or rejects it) then a 'message undeliverable email' is sent back to the sender of the email - which is you - even though you didn't send it originally!


A while back I was plagued with dozens of these undeliverable emails every day. I waited to see if it would calm down or go away of its own accord but it never did, in fact the volume of the emails increased to the hundreds per day and our email accounts were unmanageable in the end.


Now, we have our own web domain (let's call it www.1234.com) and the emails are handled through this domain. So when I send an email it is sent from [email protected] to the email receiver. We have several email addresses ([email protected], [email protected]) and they are all handled by our domain in the same way. All of these addresses were being spoofed.


In the end I contacted the domain administrator (fasthosts.co.uk) and had a livechat with them, they explained what was going on - they also confirmed 'spoofing' is very difficult to stop. I've posted below part of the livechat cobversation:


I'mafraid this is the part wherein spoofing is gets a bit hard to stop as we can'tcontrol the server that is doing this and sending out mail making it look likeit is coming from you. I can add an SPF record to your domain name, SPF recordsadds an identity line to the mail headers that would allow the valid server ormail host to send out emails using mail address - this stops the spoofing -however the SPF records takes a full 24 hours to take effect. SPF is 'Sender Policy Framework'.


So, I asked the chap to go ahead and do this which he did. It stopped the problem dead in it's tracks and I have not had any of these undeliverable emails since.


I hope this is of some help to you.