eM Client emails being blocked by recipient!

Mail
1

This has recently started happening.

For the most part, when I send an email using eM Client that belongs to a web based email service like Outlook (Hotmail), Gmail, or Yahoo, it’s getting blocked/rejected. However, if I compose and send the email directly from the website eg Yahoo, Gmail, or Outlook, there is usually no issue. Below are some samples.

First email:

Unauthenticated email from yahoo.com is not accepted due to domain’s DMARC policy. Please contact the administrator of yahoo.com domain if this was a legitimate mail. To learn about the DMARC initiative, go to Control unauthenticated mail from your domain - Google Workspace Admin Help d9443c01a7336-1f855e6a7f3sor27322895ad.11 - gsmtp

Second email:

Your message couldn’t be delivered because the recipient’s email server (outside Office 365) rejected your message because it appears to violate a policy setting the recipient’s email admin has set up. Commonly this is because the email server suspected your message is spam, either because of its content or because email from your email domain (the text after the “@” symbol in your email address) is being blocked. To fix this, try to modify your message, or change how you’re sending the message, using the guidance in this article: E-mailing Best Practices for Senders.
*>
> Then resend your message. If you continue to experience the problem, contact the recipient by some other means (by phone, for example) and ask them to ask their email admin to help fix the issue. Ask them to add your email address or your domain name to their allowed senders list.
*>
> For Email Admins: When Office 365 tried to send the message to the recipient the external email server returned the error below. This indicates the sender’s message appears to violate a policy setting that the recipient’s email admin has set up.
*>
> A common reason for this is because the message was detected as spam because of its content, or because your domain is on their block list. If the sender isn’t able to fix the problem by modifying their message, contact the recipient’s email admin and give them the the error and the email server that returned the error to help them determine the cause of the rejection. Also ask them to add your domain name to their list of allowed senders. It’s likely that only the recipient’s email admin can fix this problem. Unfortunately, Office 365 support is unlikely to be able to help fix these kinds of externally reported errors.

1 Like
2

Was this ever resolved? I am have a similar problem.

3

Unauthenticated email from yahoo.com is not accepted due to domain’s DMARC policy. Please contact the administrator of yahoo.com domain if this was a legitimate mail. To learn about the DMARC initiative, go to Control unauthenticated mail from your domain - Google Workspace Admin Help 1 d9443c01a7336-1f855e6a7f3sor27322895ad.11 - gsmtp

This is not an eM Client issue.

This means your default smtp server domain address configured in eM Client" and/or “in your mailbox online”, hasn’t passed the DMARC authentication checks" so gets rejected sending mail. Here is a good article on what DMARC is.

For a Google Workspace sending rejected DMARC error, see the following Google support link for example how to verify your DMARC record etc for your Domain to fix the sending problem.

I saw this recently with a customer where they had an old ISP domain SMTP server address set as their default “in their Gmail account online” which “had been fine up to around a year or so ago”. Then when all the global major mail servers updated with the new strict DMARC sending policies to prevent spoofing & phishing etc, then this person started to get sending mail DMARC rejected errors returned back to their Inbox.

So the only way then to fix it was to either update their old ISP Domain name so it’s was DMARC compliant to then send ok, or change their SMTP server address in Gmail online back to the Gmail default SMTP server. In their case I changed it to send via Gmail SMTP server which then fixed it as was simpler for them than trying to update their old ISP domain name to be DMARC compliant due to access problems at their old Domain provider.

4

@daryn_reif I don’t believe it has. I stopped using composing and replying email via eM Client. I now only use it to view mail.

@cyberzork no, I disagree. Apples and oranges. I believe this is an eM client issue.

5

@LL7977

no, I disagree. Apples and oranges. I believe this is an eM client issue.

As far as DMARC rejected errors messages go if you don’t believe me, you can then “speak to your SMTP mail server technical support staff” and they will update you on that and advise how to fix it.

eM Client is “only showing you the rejected error message from the sending server”. It doesn’t have an SMTP server built-in and is just an interface to send mail via your SMTP mail server.

As far as your other 2nd email sending rejected errors go, you will need to “contact the receiving mail server technical support” by phone or contact website form or community website if they have one, as to why your sent emails are getting rejected for “Policy reasons”.

The most common reason emails are rejected is due to eg: their mail server detects something in the sending mail “Header, or Subject or Body” of the email and blocks / rejects it.

Or it could be that receiving mail server only allows certain IP addresses & blocks everyone else like a University or Government organisation etc.

There can be many reasons why email gets rejected. So the receiving mail server technical support staff can advise why your emails are being rejected.

All I can suggest is eg: try sending a new “basic text only email” and see if it still gets rejected. If that works, then you know it’s something in the content of your original rejected messages.

Now if even a basic plain text message still gets rejected for Policy reasons from the same receiving mail server then you will definitely need to contact their technical support to see why.

6

DMARC is not a eM Client issue, DMARC is handled at the server side as @cyberzork says. So if it is reporting a DMARC error, then you should be contacting your email provider about this specific issue.

1 Like
7

I have no idea what you’re talking about — DMARC issue.

I pretty much stopped using eM Client for replying to emails now. The [widespread issue] is gone. I am now using Microsoft Outlook 2024 as my primary email client.

8

I am also having this issue.
If I send an email from my hotmail account using eM Client, the recipient’s server rejects my email. If i send the same email from the web based hotmail portal, the email goes through.
So, now I cannot trust sending emails from eM Client.
Makes eM Client more and more redundant.

9

@geeedeee

I am also having this issue.
If I send an email from my hotmail account using eM Client, the recipient’s server rejects my email. If i send the same email from the web based hotmail portal, the email goes through

Sending via webmail is different than sending via mail clients as it uses different ports etc. So you need to see why your being rejected.

Click the dropdown on the right of Refresh and click “Show Operations”. Then click the “Log tab” and look for obvious sending error messages and paste them in this thread. We might then be able to see why it’s being rejected.

10

This is what the log shows:
10:16:35 am xxxxxxxxxxxxxxxxxxxx AirSync Synchronizing folder ‘/Calendar’
10:16:37 am xxxxxxxxxxxxxxxxxxxx AirSync Synchronizing folder ‘/Contacts’
10:16:38 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder list
10:16:39 am xxxxxxxxxxxxxxxxxxxx AirSync Synchronizing folder ‘/Tasks’
10:16:43 am xxxxxxxxxxxxxxxxxxxx IMAP Downloading messages: For folder /Sent
10:16:43 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder ‘/2014 Emails’
10:17:08 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder ‘/Archive’

The “xxxxxxxxxxxxxxxxxxxx” is my email address (hidden for privacy)

11

I just replied to the email in question. My reply to this email is coming back as “undeliverable”.

Here is the log, copied, immediately after I hit the “reply” to this email.

6:15:21 am xxxxxxxxxxxxxxxxxxxx AirSync Synchronizing folder ‘/Contacts’
6:15:22 am xxxxxxxxxxxxxxxxxxxx AirSync Synchronizing folder ‘/Tasks’
6:15:25 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder ‘/2014 Emails’
6:15:50 am xxxxxxxxxxxxxxxxxxxx AirSync Synchronizing folder ‘/Contacts’
6:15:57 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder ‘/Archive’
6:16:04 am xxxxxxxxxxxxxxxxxxxx SMTP Connecting: To xxxxxxxxxxxxxxxxxxxx
6:16:07 am xxxxxxxxxxxxxxxxxxxx SMTP Connected: To xxxxxxxxxxxxxxxxxxxx
6:16:07 am xxxxxxxxxxxxxxxxxxxx SMTP Sending messages
6:16:10 am xxxxxxxxxxxxxxxxxxxx SMTP Disconnected: From xxxxxxxxxxxxxxxxxxxx
6:16:10 am xxxxxxxxxxxxxxxxxxxx SMTP Disconnected: Done
6:16:22 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder ‘/Inbox’
6:16:24 am xxxxxxxxxxxxxxxxxxxx IMAP Moving item(s) from folder ‘/Inbox’ to folder ‘/Junk Email’
6:16:25 am xxxxxxxxxxxxxxxxxxxx IMAP Synchronizing folder ‘/Archive’

“xxxxxxxxxxxxxxxxxxxx” = my email address

In my junk folder, I receive an email back saying my reply was undeliverable and this is the content of that email:

My reply is to an email on which there is one sender and two people copied.
Recipient 1 + Recipient 2 - have email addresses with the same domain name (it’s a corporation)

Recipient 3 = different domain name (it’s a corporation)

Diagnostic information for administrators:

Generating server: MW4PR14MB6141.namprd14.prod.outlook.com

“recipient 1 email address (hidden for privacy)”

Remote server returned ‘550 5.7.520 Message blocked because it contains content identified as spam. AS(4810)’

“recipient 2 email address (hidden for privacy)”

Remote server returned ‘550 5.7.520 Message blocked because it contains content identified as spam. AS(4810)’

“recipient 3 email address (hidden for privacy)”

Remote server returned ‘550 5.7.520 Message blocked because it contains content identified as spam. AS(4810)’

Original message headers:

Received: from SA1PR14MB5880.namprd14.prod.outlook.com (2603:10b6:806:25b::5)

by MW4PR14MB6141.namprd14.prod.outlook.com (2603:10b6:303:22f::6) with

Microsoft SMTP Server (version=TLS1_2,

cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9298.13; Sat, 8 Nov

2025 02:16:08 +0000

Received: from SA1PR14MB5880.namprd14.prod.outlook.com

([fe80::7ab0:7f53:96ef:40fb]) by SA1PR14MB5880.namprd14.prod.outlook.com

([fe80::7ab0:7f53:96ef:40fb%3]) with mapi id 15.20.9298.007; Sat, 8 Nov 2025

02:16:08 +0000

From: “my name" <

xxxxxxx>

To: “Recipient 1" <

“recipient 1 email address (hidden for privacy)”>

Subject: Re: Demolition prices

CC: “Recipient 2” <
“recipient 2 email address (hidden for privacy)”

, “Recipient 3”

<“recipient 3 email address (hidden for privacy)”

Date: Sat, 08 Nov 2025 02:16:01 +0000

Message-ID: <

SA1PR14MB588034132283FAD5CEDEEC86BDC0A@SA1PR14MB5880.namprd14.prod.outlook.com>

In-Reply-To: <

1131D3FD-129C-464B-B206-00FACE2F82A2@domain name of recipient 1>

References: <

1131D3FD-129C-464B-B206-00FACE2F82A2@domain name of recipient 2>

Reply-To: “my name" <

xxxxxxxxxxxxxxxxxxxx>

User-Agent: eM_Client/10.3.2622.0

Content-Type: multipart/related; boundary=“------=_MB8BD09BF6-A502-458F-86DF-68C56E894EAB”

X-ClientProxiedBy: TPYP295CA0008.TWNP295.PROD.OUTLOOK.COM (2603:1096:7d0:9::9)

To SA1PR14MB5880.namprd14.prod.outlook.com (2603:10b6:806:25b::5)

Return-Path:

xxxxxxxxxxxxxxxxxxxxx

X-Microsoft-Original-Message-ID: [email protected]

MIME-Version: 1.0

X-MS-Exchange-MessageSentRepresentingType: 1

X-MS-PublicTrafficType: Email

X-MS-TrafficTypeDiagnostic: SA1PR14MB5880:EE_|MW4PR14MB6141:EE_

X-MS-Office365-Filtering-Correlation-Id: bfaf1967-4f1f-4079-4a80-08de1e6cc64c

X-MS-Exchange-SLBlob-MailProps:

zZTkHIKWWP8CCgZrLw7ylW/h+dKRsHQunWh/mvP2WUT0D8ljMKE+mIrixDc565gBE18StJFq7qG5Jtc2LTtDz18IBjYzLkaLErErgcOoGZ+MXyMW4Asl0OAvIBUXHBXs0pgdw4eT/k7CJ7msFlDU3eigAB1tyWazH6gQ0dTVQHJp90j35q1FSjBRMKVTIb1rK/c0dT3BVnKxqyX3bRyHk3RjO7BYIxbhfzXb/w0PrrxyyO9fjstlTajAgRip7QaHBqL6DyUGVFyBlM1PlhXn0HMoFr/hTIWbRCp17Hx6lYEaeXxoLTYph4TGBZUaaZIVNBfvSqYJASec1Gvf06+du1OYKy8Rb6gLibhXlg4+eE9YFCksaN3IAW1uPircbBRm/gwLgIzcOToI+pte/c4aVdllm+Wx8FoL78hGQW31+OZwjDW5ceAJCsyv+JJrnst6ouQzxAWxh3R0AQD1/zCQ1tj3za1j0UcymA05HfvB7vlQf0owWe2+wkJ2+axdhKN4yYbyif3TBj0zMLDk2+vUdV84x1/ErT99gsySgUosCpfM74MViZ823Ln/6FUYRHuxdj5vXJitlELtX37t2Npx8KP0Idg/8UgZCPDDptQPxuGBROO7+MGsOH6ahSIIxhSR6UwLE1w01c9antk11PP2/coHuRgcPWe05YWGE0F26IAO2n7SL+iQVA==

X-Microsoft-Antispam:

BCL:0;ARA:14566002|9400799040|461199028|5072599009|6092099016|15080799012|8060799015|19110799012|12050799012|12121999013|23021999003|51005399006|3412199025|440099028|40105399003|6105599021;

X-Microsoft-Antispam-Message-Info:

=?us-ascii?Q?KormvgXYp1Z/X+2ns39f9PF7c71Xt2UcIeRK1iOcRRurX8MZhNiByQ6iXqzz?=

=?us-ascii?Q?F89I3wwLY5SNhIycbEJBpIzBy6/PLRZwR4GSMjUNoWY7LcmRzkCRvnhwyACb?=

=?us-ascii?Q?99ISxtpWwDlECc4Nzl08XVNdCwjjJFkwNMtxGUyrD13P4zFxbW5SPmyze1U0?=

=?us-ascii?Q?KrzX7N4EWmTkeLctaBKOnFcgACtB0m1pvF3LsxmydvG0h1hQABY1YSM7qyAx?=

=?us-ascii?Q?1xmXi7g3weFfQImYHj0PkKUZ4i61Cx7aemo/WDJqcNcLK0rdTkxD63dui3R3?=

=?us-ascii?Q?Huv43VmJC+X1cj4XM3tRF8bd5SK20KFlZ/efALZNvfk8JC3QrB0uHNvOKvkM?=

=?us-ascii?Q?TjQpNTvmlz7/VcDvAiazI0W+SntgnkMKxi9o+5Efnp5HONCx9GhMY+y8zG1S?=

=?us-ascii?Q?CssdWRHr7Kq866sfePXLYIaTTzZ9zE9snyIWT/BDr90KZmgI15OeCknJ9WkA?=

=?us-ascii?Q?M0SJOPyMgfODUhb7lTOxYTMiKNoFy5JbuJL4aS2RVR9mbibmrjn9sDhZZNWA?=

=?us-ascii?Q?PCpjQdxglwFypBHqo0Rc1Dn4dmPrhh4USW7ulnvh0hN3V/3Aq2G0qYFp4uqD?=

=?us-ascii?Q?8TuiUC1f2kgIERJEtgSjYMTFMpd4hyTTMJeg73ua+8NhLOsEZ06ZJjW4TdUx?=

=?us-ascii?Q?j74cOF64OKGKt1G8Tw+qfCANnGTQ6SM9h1YaVMpuWHhyEqQIxa1eIBBK/7JC?=

=?us-ascii?Q?MnEtz9Iy+zcTa7UP4/qe+nZTJtOi3bLJtbpi6WLKQnqHb9KXyTmvkmwqQXK3?=

=?us-ascii?Q?ru0Y2DDr9Fl0ldq4COepeBLhZg/Y5EYp4neZijdfLDu4tFdz8bzyv/SUUh0R?=

=?us-ascii?Q?ZZWeSUx20cKP940lQNMd7oBzqOZqoD2UlIFY1E/oW46PzpGl9/LL+UhXnNZb?=

=?us-ascii?Q?flhRSQphOFayDFKb8OIjuHDFQCdsGKyypxrGECictB1HyZDtJ3Wpe7eHd+OA?=

=?us-ascii?Q?9790qeH4DYNH0suLfPBtsyr73S+xJB0Az7lTw7nUuJUNA0OdFkwnHL2Q6HWp?=

=?us-ascii?Q?52nppv/G/cMPvsXbxj61kAfyByJEiAwakecNLyeYVtbWZZtaEYtGtiG1Rube?=

=?us-ascii?Q?3KxVjMA8WeU/Sw9uL5XAwjwBBcYknfHCICsu8QbAdRLrjx6iCA5ageFIoh1u?=

=?us-ascii?Q?gv/EXCU8Xgf7KXvEVEcP0fUQyM4omWqfaJDyQl9HkICWZL7sT0XWz1nLMMBD?=

=?us-ascii?Q?3GYG/LdWQv6LylFs+mtAgK8t9sIOKLezxba7x9DXSnrYmQwHXgHD0F6aRA4M?=

=?us-ascii?Q?E5RATgaInEU2npor/axQcFhfNAr9ivZ2ipXjdeXuGcKdf7XSGkSDcfWhfMCu?=

=?us-ascii?Q?ck+An901ZKK25++dT2018GQLQixJ1yNiX/cRe4aUIlQjpuII3LzYOORW33lL?=

=?us-ascii?Q?j9m7qTuklUiTDv0Kj/tZFDAlyAwqq0PaugEurIxJAl6r9M1FLngK8romvFUd?=

=?us-ascii?Q?MlkBOGkvqtoUpl8MhVacLxbpnFqE61cN+N3Ll6IG6XaMVP7HvmXFNWX+RKo5?=

=?us-ascii?Q?bW+pSyOgKHK+rApkTB+I1Qov3yh92+LU4n6HAQGrlfeCaSf5PaVnB3V+jtuZ?=

=?us-ascii?Q?Ws3vKFTefF4nGYIY5c38+2UxyANPDaHJ1H0QDISINbMEWpJDoJvfmBtuzNg7?=

=?us-ascii?Q?sQ=3D=3D?=

X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1

X-MS-Exchange-AntiSpam-MessageData-0:

=?us-ascii?Q?sgZ/DRuVF8RP8a92OTF5lz/A2DgiRv/YIsuZq2kZB8qjsF11eoxLcj85PorS?=

=?us-ascii?Q?0WxYZWz9+3Vo5Y50FEpziHhHB98OhlmD9YjXCiOvTUrZfRCu0Yi8r2Jmyirc?=

=?us-ascii?Q?poNZ7nLoncNf6w1zIlZOitZgY1Gdgl6f7c6VwMuS6wO3AyYqb0lKz85427WO?=

=?us-ascii?Q?oKQnY1oNlVfNBSmMHpKhB0pfXbDi+IgoUv4D54k4+yAkufYYDcvtwC3RX/gY?=

=?us-ascii?Q?lKFRftAJo2ByqyGQfooqxWSURGmHHI1b5EEDSKTrnAuG3ttLYCcc/R/fJ9Pr?=

=?us-ascii?Q?cajNLvXYS1rklHpbURPY30TOmH5fJ5NUBCKJpzjm52W36Hiv4bja21RcvBpA?=

=?us-ascii?Q?y+Q4xbER02d6jx/k2C2jQGzxdLQ0UPPTSnyroY0JaswCYflMNlBLIpJ59A+f?=

=?us-ascii?Q?Lg7DCTGM4zU7AAoSJdYpld/ZqBBtAaB81zz9br0bfUCvnPpRtDfI2CjEYFXJ?=

=?us-ascii?Q?FOz0PBhASeumvYBkxl+cSq/Hrrh8woUpYexy95ytJZ6Rjs6aD9mLpfnX14+k?=

=?us-ascii?Q?eHNx8i06Ml/tMM5XuJptOIDT1bPQqZSLVZbEN1z1PLgc3i2SzAIOF8cK/sTT?=

=?us-ascii?Q?4RPG3txGr21Ml39qb5uEnelIuyZc0XuNXs1Go9t2+IzDZHOOCpDkRSQyw3P5?=

=?us-ascii?Q?Me9LTMz7rAX/GqHVeXoq05Y9MBbGwzUldD9snyrySv0vYNIPnya3U2mEJc9N?=

=?us-ascii?Q?QfmFbsD4MmBuqRauT8iOBBKfOdBo2npa28Irv5zP+Uol7ApbA4h9L+BNM2jC?=

=?us-ascii?Q?K0J+dUDEgYpW5ZtRmNqV1QIZqonSvMZZUyjOcaDQXHJmWufs+thPdZTPtbIB?=

=?us-ascii?Q?DeUTWrpQiykulObJp+QnTC/xXiTYVAEbsJv83VWPBcxXxotKSwU7IGL275nR?=

=?us-ascii?Q?smgfBHGWXs2cPfnAJkNjtE5cItyYZQ8fxqOLQt+uIBjqleEWZj7zummgjkhX?=

=?us-ascii?Q?Ht/0zlq76eCliNsmAmCe94pdIDXj0fiMxQeBn+Rlc66TXuXGS7thYZkrFTKk?=

=?us-ascii?Q?iN8tpniS0IHIA75aV6WWGVc4uuR9Qr+VrZ67vXkM5l9Gh9X/aeib5SLIFjC5?=

=?us-ascii?Q?uTdyR3txFInUmBLaXUhRr+6315U7dyWPJPSh+qC21UK52DogDgEM3jaubZgF?=

=?us-ascii?Q?4/6FqvZxO25BopsBFhQQ/BeltyciTis2Nph/x2k068k+n6ayAJrZb7w0xavj?=

=?us-ascii?Q?okd5kd6hpcYaNAiK9TTmpBc0k2MkKnBI/9iuYL1YtmDORE5WrZk4sK7Y/8XX?=

=?us-ascii?Q?Rsh30R3tJ5zDMYaCN5XA?=

12

So thats explains why its being rejected. It contains content identified as spam. AS(4810)’ There is something in the content of your emails that is causing the recieving server to block your email when sending via your SMTP server.

This can sometimes happen if you are eg: replying or forwarding an mail from other people where sometimes it has content in it that is suspicious so gets blocked at the receiving end,

It can be something in the header, subject or body of the email or even in an attachment that the receiving server is rejecting due to its detecting spam in those emails. So not an eM Client issue but something within those emails that are causing them to be rejected.

1 Like
13

Thanks @cyberzork

I was replying to an email from the company..

my reply was only text, nothing else unusual.

I guess it’s something about the content of the original email from them that has something in it which is leading to their server to reject my reply.
Their original email has a footer with their website, physical address, phone numbers and some accreditation numbers related to their field of work. Maybe it’s that.

There is nothing else in the email such as links which may be construed as suspicious.

14

I’ve had this happen too, turns out my SPF record was missing some required info. Once I updated it to include my sending server, things went through fine again.

15

I had a similar problem before, and what helped was using an email warmup tool for a few weeks. It slowly built trust with email providers by gradually increasing sending volume and making sure my messages didn’t land in spam. I think this step made a big difference in how my emails were received afterward. Might be worth a try if nothing else is working.