Chodí info maily o nedoručení (vyřešeno)

vdstudio · 2020-02-03 15:07:55

Dobrý den, od 13:50 nám chodí na skola@sololang.com maily o nedoručení zpráv (Mail delivery failed apod.). Žádnou rozesílku neděláme, můžete prosím prověřit a zakázat toto rozesílání z naší adresy? Děkuji.

Upravil vdstudio (2020-02-06 11:20:36)

vdstudio · 2020-02-03 15:09:15

Příklad zprávy:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

kalen@fixandpaint.net
host fixandpaint-net.mail.protection.outlook.com [104.47.66.10]
SMTP error from remote mail server after RCPT TO:<kalen@fixandpaint.net>:
550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [MW2NAM12FT024.eop-nam12.prod.protection.outlook.com]
Reporting-MTA: dns; mail-smtp1.stable.cz

Action: failed
Final-Recipient: rfc822;kalen@fixandpaint.net
Status: 5.0.0
Remote-MTA: dns; fixandpaint-net.mail.protection.outlook.com
Diagnostic-Code: smtp; 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [MW2NAM12FT024.eop-nam12.prod.protection.outlook.com]
Předmět You have unread missed call on February 03, 2020
Odesílatel fixandpaint.net NoticeMail
Adresát kalen@fixandpaint.net
Datum Dnes 13:50
Priorita
Hi kalen,

A new VMessage was left on your device on February 03, 2020 GST

Listen Now

If you have any questions, please visit our online help center or contact customer support.

Thanks,
fixandpaint.net support
Thіs еmаіl wаs sеnt tо kalen@fixandpaint.net.

vdstudio · 2020-02-03 15:10:29

Nebo tato například:

Your message to rrussell@servproofmclean.com couldn't be delivered.
rrussell wasn't found at servproofmclean.com.
skola Office 365 rrussell
Action Required Recipient
Unknown To address

How to Fix It
The 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 Admins
Status 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.

Original Message Details
Created Date: 2/3/2020 12:52:13 PM
Sender Address: skola@sololang.com
Recipient Address: rrussell@servproofmclean.com
Subject: You have unread missed call on February 03, 2020

Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient rrussell@servproofmclean.com not found by SMTP address lookup
DSN generated by: CY4PR03MB2662.namprd03.prod.outlook.com
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 2/3/2020
12:52:15 PM [37.72.175.133] mail-smtp1.stable.cz esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.91) (envelope-from <skola@sololang.com>) 2 sec
2 2/3/2020
12:52:16 PM mail-smtp-out-04.stable.cz CY1NAM02FT037.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
3 2/3/2020
12:52:17 PM CY1NAM02FT037.eop-nam02.prod.protection.outlook.com MN2PR03CA0028.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
4 2/3/2020
12:52:17 PM MN2PR03CA0028.namprd03.prod.outlook.com CY4PR03MB2662.namprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
Original Message Headers

Received: from MN2PR03CA0028.namprd03.prod.outlook.com (2603:10b6:208:23a::33)
by CY4PR03MB2662.namprd03.prod.outlook.com (2603:10b6:903:71::8) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.27; Mon, 3 Feb
2020 12:52:17 +0000
Received: from CY1NAM02FT037.eop-nam02.prod.protection.outlook.com
(2a01:111:f400:7e45::204) by MN2PR03CA0028.outlook.office365.com
(2603:10b6:208:23a::33) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.29 via Frontend
Transport; Mon, 3 Feb 2020 12:52:17 +0000
Authentication-Results: spf=pass (sender IP is 213.109.164.21)
smtp.mailfrom=sololang.com; servproofmclean.com; dkim=test (signature was
verified) header.d=sololang.com;servproofmclean.com; dmarc=pass action=none
header.from=sololang.com;
Received-SPF: Pass (protection.outlook.com: domain of sololang.com designates
213.109.164.21 as permitted sender) receiver=protection.outlook.com;
client-ip=213.109.164.21; helo=mail-smtp-out-04.stable.cz;
Received: from mail-smtp-out-04.stable.cz (213.109.164.21) by
CY1NAM02FT037.mail.protection.outlook.com (10.152.75.77) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.2686.25 via Frontend Transport; Mon, 3 Feb 2020 12:52:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=sololang.com; s=2xx2y-okh7yoccr; h=Content-Type:Subject:Date:To:From:
MIME-Version:Message-ID:Sender:Reply-To:Cc:Content-Transfer-Encoding:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=1/YYa5JZoQvOvyVYt8m6y5CR4GWSjlgL5uT8IvhQqKw=; b=ULp8njBJi7pnmxiQQdHRrEvRz
dEWW1d2MpapF3GkvYUTNsCYsv3+mvox/GmUYILuN0yE3QbncDC3djs2uJE5as8jznkZArxbHiCPxz
vwyA0bGVZZmBon7dGlbGA9dNhh44OFChb9ZzbPpaCkOwI1d8kYY0JcH3VtHPf3/KBHNOkDgLenDrY
YE5DWMmEgL6bvUYMy3tZzhXderDQFLAmQltKr8zHrXArbs6uitADYkTV7AfVjBGUr4FiN3h3l9dJa
6pZ5Xx2Nu14L9sjdwL9YxSUFtwLu1gw3xagh9phLXNEjbylHLaE2NdAeiRhcjRuvpY/c6jbY3GqJF
iv/F8VFoA==;
Received: from [37.72.175.133] (port=55521 helo=WIN-25FFVSIPLS1)
by mail-smtp1.stable.cz with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256)
(Exim 4.91)
(envelope-from <skola@sololang.com>)
id 1iybD5-0005GX-1l
for rrussell@servproofmclean.com; Mon, 03 Feb 2020 13:52:15 +0100
Message-ID: <98a93471976fac0a19b5fad6b9b9e7aade3339b5f866666353930911cf5adf81@sololang.com>
MIME-Version: 1.0
From: "servproofmclean.com NoticeMail" <skola@sololang.com>
To: rrussell@servproofmclean.com
X-Priority: 1
Priority: urgent
Importance: high
Date: 3 Feb 2020 06:52:13 -0600
Subject: You have unread missed call on February 03, 2020
Content-Type: multipart/alternative;
boundary=--boundary_15178_c9ff5f5b-a55b-4d10-b7c5-8348736b7cee
Return-Path: skola@sololang.com
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: d7e6357d-7c8f-4def-bed2-bbcf6552072b:0
X-Forefront-Antispam-Report: CIP:213.109.164.21;IPV:;CTRY:CZ;EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f1b553f7-8478-4e54-0a0e-08d7a8a7e5da
X-MS-TrafficTypeDiagnostic: CY4PR03MB2662:
Reporting-MTA: dns;CY4PR03MB2662.namprd03.prod.outlook.com
Received-From-MTA: dns;mail-smtp-out-04.stable.cz
Arrival-Date: Mon, 3 Feb 2020 12:52:17 +0000

Final-Recipient: rfc822;rrussell@servproofmclean.com
Action: failed
Status: 5.1.10
Diagnostic-Code: smtp;550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient rrussell@servproofmclean.com not found by SMTP address lookup

Předmět You have unread missed call on February 03, 2020
Odesílatel servproofmclean.com NoticeMail
Adresát rrussell@servproofmclean.com
Datum Dnes 13:52
Priorita
Hi rrussell,

A new VMessage was left on your device on February 03, 2020 GST

Listen Now

If you have any questions, please visit our online help center or contact customer support.

Thanks,
servproofmclean.com support
Thіs еmаіl wаs sеnt tо rrussell@servproofmclean.com.

vdstudio · 2020-02-03 15:15:16

Prozatím jsem změnil ve webadminu heslo ke schránce, nevím ale, jestli to pomůže...

vdstudio · 2020-02-03 15:24:49

Vypadá to, že buď pomohla změna hesla, nebo se ten SPAM už rozeslal na všechny zadané kontakty. Poslední mail s chybou o nedoručení přišel ve 14:07 a celkem přišlo 40 takových mailů. Lze se prosím nějak zabezpečit proti takovým rozesílkám? Děkuji.

JF · 2020-02-03 20:24:28

Dobrý den, dle uvedených zpráv posíláte emaily na neexistující emailové schránky, proto se vám tyto informace vracejí.

vdstudio · 2020-02-03 21:34:42

Dobrý den, děkuji za odpověď. To já samozřejmě vím, co znamenají ty maily. Jde o to, že my tyto maily neposíláme! Posílá je někdo jiný, ale z naší emailové adresy a přes servery stable.cz. Dorazilo mi během 20 minut 40 notifikací o nedoručení a předpokládám, že dalších X mailů normálně odešlo na správné e-mail adresy... Nevím úplně jak je tohle možné, proto jsem se obrátil na vás. Napadlo mě jedině změnit heslo, jinak do toho nevidím. Dnes kolem 17:30 nám nešel z prostředí webmailu odeslat mail, hlásilo to vyčerpání 24 hodinového limitu pro odesílání zpráv (teď už to zase jde). Dokážete prosím poznat z nějakých logů odkud to ti spameři posílají a můžete mi poradit, jak jim v tom zabránit? Nevím co mám dělat a nechci, aby se naše adresa dostala do black listů. Děkuji.

TomasEndora · 2020-02-04 09:53:38

Dobrý den,

podle hlaviček někdo rozesílal z Vaší schránky z 37.72.175.133 (dle geoip USA).. Na 99% šlo o uhádnutí hesla (na schránce skola@ bylo slabé heslo). Náš server má limit 200 e-mailů/4 hodiny. Proto byla poté rozesílka blokována. Upravte si u schránky heslo na nové bezpečné. Poté by mělo být vše nadále v pořádku jako doposud.

Hezký den

vdstudio · 2020-02-06 11:20:00

Děkuji. Vyřešeno tedy.

#1 2020-02-03 15:07:55

Chodí info maily o nedoručení (vyřešeno)

#2 2020-02-03 15:09:15

Re: Chodí info maily o nedoručení (vyřešeno)

#3 2020-02-03 15:10:29

Re: Chodí info maily o nedoručení (vyřešeno)

#4 2020-02-03 15:15:16

Re: Chodí info maily o nedoručení (vyřešeno)

#5 2020-02-03 15:24:49

Re: Chodí info maily o nedoručení (vyřešeno)

#6 2020-02-03 20:24:28

Re: Chodí info maily o nedoručení (vyřešeno)

#7 2020-02-03 21:34:42

Re: Chodí info maily o nedoručení (vyřešeno)

#8 2020-02-04 09:53:38

Re: Chodí info maily o nedoručení (vyřešeno)

#9 2020-02-06 11:20:00

Re: Chodí info maily o nedoručení (vyřešeno)

Zápatí