• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Mails not received from AOL accounts

Julkvesan

New Pleskian
Hi all,

We can not receive emails from AOL accounts (sending is not a problem).

I am a little desperate because I don't know where to look or what to do to solve this problem.

We have deactivate spamassasin, deactivated check incoming email, add to white list aol ips, etc.

Usually aol clients get this answer:

--

This is the mail system at host omr-m017e.mx.aol.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<[email protected]>: Host or domain name not found. Name service error for
name=xxx.es type=MX: Host not found, try again


Reporting-MTA: dns; omr-m017e.mx.aol.com
X-Outbound-Mail-Relay-Queue-ID: 1715D3800085
X-Outbound-Mail-Relay-Sender: rfc822; [email protected]
Arrival-Date: Fri, 2 Mar 2018 10:09:57 -0500 (EST)

Final-Recipient: rfc822; [email protected]
Original-Recipient: rfc822;[email protected]
Action: failed
Status: 4.4.3
Diagnostic-Code: X-Outbound-Mail-Relay; Host or domain name not found. Name
service error for name=xxx.es type=MX: Host not found, try again


Return-Path: <[email protected]>
Received: from mtaout-mce02.mx.aol.com (mtaout-mce02.mx.aol.com [172.29.27.206])
by omr-m017e.mx.aol.com (Outbound Mail Relay) with ESMTP id 1715D3800085
for <[email protected]>; Fri, 2 Mar 2018 10:09:57 -0500 (EST)
Received: from [192.168.1.113] (unknown [92.189.235.239])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mtaout-mce02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 9FE57380030B9
for <[email protected]>; Fri, 2 Mar 2018 10:09:56 -0500 (EST)
From: XXX <[email protected]>
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Fri, 2 Mar 2018 16:09:55 +0100
Subject: xxx xxx xxx xxx
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_74164_896277825.1520082404102"
X-MB-Message-Source: WebUI
X-MB-Message-Type: User
X-Mailer: JAS STD
X-Originating-IP: [92.189.235.239]
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com;
s=20150623; t=1520082406;
bh=64z0lR+vg13M98OtlsEka2nOCn/9hMYTOIFvlz3xdS8=;
h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type;
b=Hnj4DLRyvZGZzhIEqpBJQ/GuE97VUADzRjh9+CWMLXEENNvrXV7uW8k+14Of2t9Yz
TVGSzpvaO/1wT9rqQcn50LIfSZMvTE8r+3Vh9R+1xJZdBtsdO375ckX7lpSiqWM5Bk
Kq5OkTsSIbHpbQ8qUWoIkevFWYLYQS8R5yGu8gTI=
x-aol-sid: 3039ac1a32b05a9a9de66534

--

Thanks and regards.
 
Does your domain have an MX record? Sometimes this is omitted, and it usually works because SMTP servers will then use the wildcard A-record to deliver mail. But in some cases SMTP servers do not, and as your error message indicates in your case the *.es domain is not found - at least not as an MX record.
 
I don't understand anything...

After PTR configuration we have received one mail from an aol account into [email protected]

Second try sendind to [email protected] from aol account, same error:

--
This is the mail system at host omr-m008e.mx.aol.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<[email protected]>: Host or domain name not found. Name service error for
name=juvesa.es type=MX: Host not found, try again
--

:((((
 
Intermittent results would indicate a DNS related issue; possibly with the sender's DNS servers unable to resolve the domain. If you just added a PTR record, it could still be propagating.
 
Back
Top