Ошибка lrt led fqdn ip - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

Remove From My Forums

Question
Hello,

I have a newly installed Exchange 2013 working just dandy, except that it cannot relay mail for two particular domains.

Problem domain # 1 gives me an NDR:

primary target IP address: «Failed to connect. Winsock error code: 10061,
Win32 error code: 10061.» Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all
alternate hosts. The last endpoint attempted was 72.52.10.14:25′

Problem domain # 2 gives me a useless NDR:

Remote Server returned ‘550 4.4.7 QUEUE.Expired; message expired'<u5:p></u5:p>

Tracking messages to both domains I get a common error:

Eastern Time (US & Canada) and generated the error ‘[{LRT=};{LED=};{FQDN=};{IP=}]’.

Here’s what I have done so far:

I can telnet to both problem domains on port 25 and get a 220
DNS resolves both mail server FQDN’s to the correct IP
Using NSLOOKUP I can see MX records for both domains
I have verified EDNS using OARC’s site

Currently I am stumped. Any suggestions or help would be greatly appreciated.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase

Answers

Hi ,

Is this issue is constantly existing on your side or this is the first time you are facing this issue?

Both the NDR will occur if there is a reachability problem between your smart host and the destination mail server.

To segregate this issue just do the following.

1.Instead of allowing the smarthost to do the dns lookup for those domains by using your dns servers.We make use of the etc host file on the smarthost by manually putting the host A records for those problematic domains.

Please reply me if anything is unclear.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  
  Tuesday, January 13, 2015 6:25 PM
Hi ,

we can enable the protocol logging on the send connectors and check the error occurred on the logs during the communication from your smart host to the server in the destination domain.

Most importantly we will face this error message only when the destination server in not available on the particular time when your smart host tries to connect it.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:16 PM
After some further investigation, I found that one DNS server had a forwarder to the local IP address of another internal DNS server, probably left over and taken from the NIC settings when I joined the secondary DC to the domain a few weeks
ago.

I change the DNS server’s NIC properties DNS settings to 127.0.0.1 and deleted the internal forwarder and email to the problem domain is working now.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:15 PM
Hi Miguel ,

Happy to hear the good news.

Thanks for the update.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:24 PM

Источник

Перейти к контенту

Remove From My Forums

Question
Hello,

I have a newly installed Exchange 2013 working just dandy, except that it cannot relay mail for two particular domains.

Problem domain # 1 gives me an NDR:

primary target IP address: «Failed to connect. Winsock error code: 10061,
Win32 error code: 10061.» Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all
alternate hosts. The last endpoint attempted was 72.52.10.14:25′

Problem domain # 2 gives me a useless NDR:

Remote Server returned ‘550 4.4.7 QUEUE.Expired; message expired'<u5:p></u5:p>

Tracking messages to both domains I get a common error:

Eastern Time (US & Canada) and generated the error ‘[{LRT=};{LED=};{FQDN=};{IP=}]’.

Here’s what I have done so far:

I can telnet to both problem domains on port 25 and get a 220
DNS resolves both mail server FQDN’s to the correct IP
Using NSLOOKUP I can see MX records for both domains
I have verified EDNS using OARC’s site

Currently I am stumped. Any suggestions or help would be greatly appreciated.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase

Answers

Hi ,

Is this issue is constantly existing on your side or this is the first time you are facing this issue?

Both the NDR will occur if there is a reachability problem between your smart host and the destination mail server.

To segregate this issue just do the following.

1.Instead of allowing the smarthost to do the dns lookup for those domains by using your dns servers.We make use of the etc host file on the smarthost by manually putting the host A records for those problematic domains.

Please reply me if anything is unclear.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  
  Tuesday, January 13, 2015 6:25 PM
Hi ,

we can enable the protocol logging on the send connectors and check the error occurred on the logs during the communication from your smart host to the server in the destination domain.

Most importantly we will face this error message only when the destination server in not available on the particular time when your smart host tries to connect it.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:16 PM
After some further investigation, I found that one DNS server had a forwarder to the local IP address of another internal DNS server, probably left over and taken from the NIC settings when I joined the secondary DC to the domain a few weeks
ago.

I change the DNS server’s NIC properties DNS settings to 127.0.0.1 and deleted the internal forwarder and email to the problem domain is working now.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:15 PM
Hi Miguel ,

Happy to hear the good news.

Thanks for the update.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:24 PM

Having trouble with a fresh install of Exchange 2013 on 2012 R2.

Exchange is installed and all the DNS and autodiscover etc seems to be working fine, as I can open outlook on a domain joined PC and it auto configures etc all good.

When I try to send an email to an external address, it sits in the outbox for ages…. then hours later goes. then it seems to free up and i can send as many emails as I want to the external address.

If i try to send an email to myself or any other internal address, it goes nowhere… it goes into sent items but never comes back into my inbox.

Any tips would be greatly appreciated… after many hours of googling I am stuck.

check
Best Answer

Hi James,

What is your outlook anywhere settings? How do you have the security on this set? I recently installed exchange server 2013 and found that a lot of what should be default settings, were not default settings.

Another thing to check is your queue messages. But it sounds more like the connection between outlook and the server which is having the issue seeing that they are stuck in the outbox.

Another thing to note that if this is exchange server with no SPs applied, there could be a bug causing the issue. I had major issues with users who had shared mailboxes or had another user mailbox open, whereby the emails sat in the outbox for hours before being sent.

Or it simply could be your DNS records are incorrect. I hope you get it sorted. Mail servers are fickle beasts.

Was this post helpful?
thumb_up
thumb_down

View Best Answer in replies below

Read these next…

IT Adventures: Episode Three — Danger

Holidays

Tell a Story day is coming up on April 27th, and were working on an interactive story for it. Here’s the idea. Below, there will be a story prompt which is sort of like a Choose Your Own Adventure, except that the rest of it isn’t written. …
How to virtualize a physical server with multiple drives

Virtualization

Hey Spiceheads! We need to take a (Windows) server that has three physical drives and virtualize it into Hyper-V. What is the best practice for this? I’ve read Virtual Machine Manager is the way to go, but this is a first for me and we’re open to suggesti…
Launching Chrome and Default Apps window opens up??

Windows

Each time I launch Chrome the Windows 11 Default Apps window pops up. I can’t figure out why exactly.
Snap! — Lunar Lawyers, Digital Dog Spike, On Demand Meteor Showers, Pixel Pants

Spiceworks Originals

Your daily dose of tech news, in brief.

Welcome to the Snap!

Flashback: April 12, 1976: Ronald Wayne cashes out, selling 10% of Apple for $800. (Read more HERE.)

Bonus Flashback: April 12, 1981: First Space Shuttle Launch (Read more HERE….
Need new storage hardware!

Windows

Currently I have some backups going to this device, some to another, and then all of it going to the cloud. I would like to consolidate all of the backups to one device, shoot it to the cloud from the new device, and then create a copy on USB periodically…

Remove From My Forums

Question
Hello,

I have a newly installed Exchange 2013 working just dandy, except that it cannot relay mail for two particular domains.

Problem domain # 1 gives me an NDR:

primary target IP address: «Failed to connect. Winsock error code: 10061,
Win32 error code: 10061.» Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all
alternate hosts. The last endpoint attempted was 72.52.10.14:25′

Problem domain # 2 gives me a useless NDR:

Remote Server returned ‘550 4.4.7 QUEUE.Expired; message expired'<u5:p></u5:p>

Tracking messages to both domains I get a common error:

Eastern Time (US & Canada) and generated the error ‘[{LRT=};{LED=};{FQDN=};{IP=}]’.

Here’s what I have done so far:

I can telnet to both problem domains on port 25 and get a 220
DNS resolves both mail server FQDN’s to the correct IP
Using NSLOOKUP I can see MX records for both domains
I have verified EDNS using OARC’s site

Currently I am stumped. Any suggestions or help would be greatly appreciated.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase

Answers

Hi ,

Is this issue is constantly existing on your side or this is the first time you are facing this issue?

Both the NDR will occur if there is a reachability problem between your smart host and the destination mail server.

To segregate this issue just do the following.

1.Instead of allowing the smarthost to do the dns lookup for those domains by using your dns servers.We make use of the etc host file on the smarthost by manually putting the host A records for those problematic domains.

Please reply me if anything is unclear.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  
  Tuesday, January 13, 2015 6:25 PM
Hi ,

we can enable the protocol logging on the send connectors and check the error occurred on the logs during the communication from your smart host to the server in the destination domain.

Most importantly we will face this error message only when the destination server in not available on the particular time when your smart host tries to connect it.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:16 PM
After some further investigation, I found that one DNS server had a forwarder to the local IP address of another internal DNS server, probably left over and taken from the NIC settings when I joined the secondary DC to the domain a few weeks
ago.

I change the DNS server’s NIC properties DNS settings to 127.0.0.1 and deleted the internal forwarder and email to the problem domain is working now.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:15 PM
Hi Miguel ,

Happy to hear the good news.

Thanks for the update.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:24 PM

I came across this error after recently migrating a user mailbox — I was told by the user that they had sent an email to another couple of users and one specific user did not receive the email. What added to the perplexity of the situation was that there was no NDR generated by Exchange to the sender either.

So I decided to hit up the mail logs with Get-MessagingTrackingLog:
Get-MessageTrackingLog -Server MS02 -Start «03/26/2015 06:00:00» -End «03/26/2015 08:00:00» -Sender «user@domain.com» -MessageSubject «Your subject title» | FL

and was interested to find out that there was a ROUTE event that had a status of ‘FAIL’:

In the end it was only by chance I stumbled upon the issue — it was in fact that when a user is migrated (even from one mailbox to another to another environment / domain) there X400 address changes — the problem lies in the fact that this X400 (or X500, X800) data is held within a users NK2 data and because it does not automatically update with the new X400 address (coupled with the fact that Outlook uses the X400 address to route mail by default — not the SMTP address!) the mail was being sent to the users old x400 address!

In order to resolve this you can manually modify all of the end user’s NK2 files (yikes) or alternatively add the old x400 address under the mailbox properties. In order to do the latter you will firslty need to get hold of the old X400 address — fortunately when you migrate a mailbox from one DB to another the original DB retains the mailbox (for 30 days by default) in a disconnected state — so we need to run the following command on the mailbox database with the original (now disconnected) mailbox on:

or if you have access to the original mailbox still you can use:

Get-Mailbox <user-mailbox> | fl LegacyExchangeDN

I have also encountered this issue where the migration process has stripped the X400 address from the mailboxes email addresses.

We finally add the additional X400 (or X500, X800) address to the user’s email addresses in ECP > Recipients > Properties > Email Addresses > Add.

The X400 (or X500, X800) address should look something like:
/o=org/ou=Exchange Administrative Group/cn=Recipients/cn=Joe Bloggs

Источник

Remove From My Forums

Question
Hello,

I have a newly installed Exchange 2013 working just dandy, except that it cannot relay mail for two particular domains.

Problem domain # 1 gives me an NDR:

primary target IP address: «Failed to connect. Winsock error code: 10061,
Win32 error code: 10061.» Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all
alternate hosts. The last endpoint attempted was 72.52.10.14:25′

Problem domain # 2 gives me a useless NDR:

Remote Server returned ‘550 4.4.7 QUEUE.Expired; message expired'<u5:p></u5:p>

Tracking messages to both domains I get a common error:

Eastern Time (US & Canada) and generated the error ‘[{LRT=};{LED=};{FQDN=};{IP=}]’.

Here’s what I have done so far:

I can telnet to both problem domains on port 25 and get a 220
DNS resolves both mail server FQDN’s to the correct IP
Using NSLOOKUP I can see MX records for both domains
I have verified EDNS using OARC’s site

Currently I am stumped. Any suggestions or help would be greatly appreciated.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase

Answers

Hi ,

Is this issue is constantly existing on your side or this is the first time you are facing this issue?

Both the NDR will occur if there is a reachability problem between your smart host and the destination mail server.

To segregate this issue just do the following.

1.Instead of allowing the smarthost to do the dns lookup for those domains by using your dns servers.We make use of the etc host file on the smarthost by manually putting the host A records for those problematic domains.

Please reply me if anything is unclear.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  
  Tuesday, January 13, 2015 6:25 PM
Hi ,

we can enable the protocol logging on the send connectors and check the error occurred on the logs during the communication from your smart host to the server in the destination domain.

Most importantly we will face this error message only when the destination server in not available on the particular time when your smart host tries to connect it.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:16 PM
After some further investigation, I found that one DNS server had a forwarder to the local IP address of another internal DNS server, probably left over and taken from the NIC settings when I joined the secondary DC to the domain a few weeks
ago.

I change the DNS server’s NIC properties DNS settings to 127.0.0.1 and deleted the internal forwarder and email to the problem domain is working now.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:15 PM
Hi Miguel ,

Happy to hear the good news.

Thanks for the update.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:24 PM

Источник

Remove From My Forums

Question
Hello,

I have a newly installed Exchange 2013 working just dandy, except that it cannot relay mail for two particular domains.

Problem domain # 1 gives me an NDR:

primary target IP address: «Failed to connect. Winsock error code: 10061,
Win32 error code: 10061.» Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all
alternate hosts. The last endpoint attempted was 72.52.10.14:25′

Problem domain # 2 gives me a useless NDR:

Remote Server returned ‘550 4.4.7 QUEUE.Expired; message expired'<u5:p></u5:p>

Tracking messages to both domains I get a common error:

Eastern Time (US & Canada) and generated the error ‘[{LRT=};{LED=};{FQDN=};{IP=}]’.

Here’s what I have done so far:

I can telnet to both problem domains on port 25 and get a 220
DNS resolves both mail server FQDN’s to the correct IP
Using NSLOOKUP I can see MX records for both domains
I have verified EDNS using OARC’s site

Currently I am stumped. Any suggestions or help would be greatly appreciated.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase

Answers

Hi ,

Is this issue is constantly existing on your side or this is the first time you are facing this issue?

Both the NDR will occur if there is a reachability problem between your smart host and the destination mail server.

To segregate this issue just do the following.

1.Instead of allowing the smarthost to do the dns lookup for those domains by using your dns servers.We make use of the etc host file on the smarthost by manually putting the host A records for those problematic domains.

Please reply me if anything is unclear.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  
  Tuesday, January 13, 2015 6:25 PM
Hi ,

we can enable the protocol logging on the send connectors and check the error occurred on the logs during the communication from your smart host to the server in the destination domain.

Most importantly we will face this error message only when the destination server in not available on the particular time when your smart host tries to connect it.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:16 PM
After some further investigation, I found that one DNS server had a forwarder to the local IP address of another internal DNS server, probably left over and taken from the NIC settings when I joined the secondary DC to the domain a few weeks
ago.

I change the DNS server’s NIC properties DNS settings to 127.0.0.1 and deleted the internal forwarder and email to the problem domain is working now.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:15 PM
Hi Miguel ,

Happy to hear the good news.

Thanks for the update.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:24 PM

Remove From My Forums

Question
Hello,

I have a newly installed Exchange 2013 working just dandy, except that it cannot relay mail for two particular domains.

Problem domain # 1 gives me an NDR:

primary target IP address: «Failed to connect. Winsock error code: 10061,
Win32 error code: 10061.» Attempted failover to alternate host, but that
did not succeed. Either there are no alternate hosts, or delivery failed to all
alternate hosts. The last endpoint attempted was 72.52.10.14:25′

Problem domain # 2 gives me a useless NDR:

Remote Server returned ‘550 4.4.7 QUEUE.Expired; message expired'<u5:p></u5:p>

Tracking messages to both domains I get a common error:

Eastern Time (US & Canada) and generated the error ‘[{LRT=};{LED=};{FQDN=};{IP=}]’.

Here’s what I have done so far:

I can telnet to both problem domains on port 25 and get a 220
DNS resolves both mail server FQDN’s to the correct IP
Using NSLOOKUP I can see MX records for both domains
I have verified EDNS using OARC’s site

Currently I am stumped. Any suggestions or help would be greatly appreciated.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase

Answers

Hi ,

Is this issue is constantly existing on your side or this is the first time you are facing this issue?

Both the NDR will occur if there is a reachability problem between your smart host and the destination mail server.

To segregate this issue just do the following.

1.Instead of allowing the smarthost to do the dns lookup for those domains by using your dns servers.We make use of the etc host file on the smarthost by manually putting the host A records for those problematic domains.

Please reply me if anything is unclear.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  
  Tuesday, January 13, 2015 6:25 PM
Hi ,

we can enable the protocol logging on the send connectors and check the error occurred on the logs during the communication from your smart host to the server in the destination domain.

Most importantly we will face this error message only when the destination server in not available on the particular time when your smart host tries to connect it.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:16 PM
After some further investigation, I found that one DNS server had a forwarder to the local IP address of another internal DNS server, probably left over and taken from the NIC settings when I joined the secondary DC to the domain a few weeks
ago.

I change the DNS server’s NIC properties DNS settings to 127.0.0.1 and deleted the internal forwarder and email to the problem domain is working now.

Miguel Fra | Falcon IT Services, Miami, FL
SharePoint Site |
Joomla Site | Knowledgebase
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:15 PM
Hi Miguel ,

Happy to hear the good news.

Thanks for the update.

Thanks & Regards S.Nithyanandham
- Marked as answer by
  Miguel Fra
  Tuesday, January 13, 2015 6:24 PM

Having trouble with a fresh install of Exchange 2013 on 2012 R2.

Exchange is installed and all the DNS and autodiscover etc seems to be working fine, as I can open outlook on a domain joined PC and it auto configures etc all good.

When I try to send an email to an external address, it sits in the outbox for ages…. then hours later goes. then it seems to free up and i can send as many emails as I want to the external address.

If i try to send an email to myself or any other internal address, it goes nowhere… it goes into sent items but never comes back into my inbox.

Any tips would be greatly appreciated… after many hours of googling I am stuck.

check
Best Answer

Hi James,

Another thing to check is your queue messages. But it sounds more like the connection between outlook and the server which is having the issue seeing that they are stuck in the outbox.

Or it simply could be your DNS records are incorrect. I hope you get it sorted. Mail servers are fickle beasts.

Was this post helpful?
thumb_up
thumb_down

View Best Answer in replies below

Read these next…

Where are they in Windows 11?

Windows

Quick and I hope easy question, I have figured out ways to do this in W11 but just wondering if there is an easier way.Where are the following in «Windows 11″1. Map Network Drive2. Add PC to a Domain3. This PC (Option)Thank you.
Tape library

Data Storage, Backup & Recovery

HI I am trying to learn my self how to connect a Dell R720 server with a LTO 7 tape library. Can someone advise and guide me with the best practice? because to begin with I have these questions.1. Can I connect the tape Libary directly to the server? if …
Raspberry Pi uses? As a desktop?

Hardware

I saw this post:https://twitter.com/mysterybiscuit5/status/1663271923063685121I like the form factor. Got me thinking — are any of the Raspberry Pi offerings a viable replacement for a windows 10 PC? For general work — surfing, document writing? spreadsh…
Spark! Pro series – 2nd June 2023

Spiceworks Originals

Today in History marks the Passing of Lou Gehrig who died of
ALS or Lou Gehrig’s Disease. I have a
friend suffering from this affliction, so this hits close to home. If you get the opportunity, or are feeling
g…
Snap! — AI Camera, Android Malware, Space, and more Space

Spiceworks Originals

Your daily dose of tech news, in brief.

Welcome to the Snap!

Flashback: June 2, 1966: The US «Soft Lands» on Moon (Read more HERE.)

Bonus Flashback: June 2, 1961: IBM Releases 1301 Disk Storage System (Read more HERE.)

You need to hear…

Go to exchangeserver

Mail flow from EX2010 to EX2016

I’m in the process of migrating from Ex2010 to EX2016, but I’m having problems when a mailbox on EX2010 tries to send an email to one on EX2016. The reverse order works fine, EX2016 can send to EX2010 though. The message leaves the EX2010 server, and I can confirm that EX2016 receives it correctly using the SmtpReceive logs so there is no TLS issue that I’m aware of, but then the message ends up in the «SMTP Deliver to mailbox» queue (next hop domain = db01), with the following error:

——————————————————-

Last Error: 421 4.4.2 Connection dropped due to SocketError

Queue ID: EX201619

Recipients: tctest@mydomain.com;2;3;[{LED=421 4.4.2 Connection dropped due to SocketError};{MSG=};{FQDN=};{IP=};{LRT=}];0;CN=DB01,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxx,DC=xxx,DC=xxx,DC=xxx;0

——————————————————-

Any advice on what might be the cause of this, please?

Источник

On #Exchange2013 I am getting the error message as follows,

generated the error ‘[{LRT=};{LED=450 4.7.25 Client host rejected: cannot find your hostname, [xxx.xxx.xxx.130]};{FQDN=};{IP=}]’.

I am getting this error message only when the user sends email to a particular domain.

I have recently configured SPF, DKIM, DMARC records on DNS Level by requesting the ISP.

FQDN which I am using for sending emails is mx1.xyz.com.ab which is associated with the public IP — xxx.xxx.xxx.131

I have checked the PTR records for the IP ending with .131 on mxtoolbox.com, they do exist. I have also checked the PTR records for the IP which is mentioned in the error message, i.e. .130. Also for this IP they PTR records exist.
I have verified the PTR records through nslookup also and the results are all same as shown in mxtoolbox.com.

Further information, I have configured the SPF Record as follows,

xyz.com.ab. IN TXT «v=spf1 mx a ptr ip4:xxx.xxx.xxx.131 ip4:xxx.xxx.xxx.130 ~all»

The mails are getting delivered to Gmail, Hotmail, and other domains. Only to a particular domain, users are not able to send the emails.

Any help would be much appreciated because this issue is now eating up my brains.

Thanks.

Faraz.

Источник

Question

Answers

Question

Answers

Read these next…

IT Adventures: Episode Three — Danger

How to virtualize a physical server with multiple drives

Launching Chrome and Default Apps window opens up??

Snap! — Lunar Lawyers, Digital Dog Spike, On Demand Meteor Showers, Pixel Pants

Need new storage hardware!

Question

Answers

Question

Answers

Question

Answers

Question

Answers

Read these next…

Where are they in Windows 11?

Tape library

Raspberry Pi uses? As a desktop?

Spark! Pro series – 2nd June 2023

Snap! — AI Camera, Android Malware, Space, and more Space