Ecelerity

dynaco120 · 26 Jan 2024, 12:05 PM

Users of a regional ISP that use their ISP’s email server are receiving rejection notices when they send emails to users on my email server. The error message sent back to the ISP user indicates “the address failed”, “550 5.0.0 Access denied“ but a check of my logs indicate that the ISP’s email server did not even make an attempt to deliver the mail.

The only thing that might suggest what is going on is that the error message appears to be created by “ecelerity” which I assume is some sort of commercial filtering software.

Does anyone know if ecelerity tends to block for some period of time, as some DNSBLs do, or if it is a permanent block?

It really has me baffled. I could see if it blocked email “from” my server if it thought it was spam etc., but why would it block “inbound” email to my server? Why would it care what email my email server accepts?

All email from other sources arrives without a problem.

Thanks

n5bb · 27 Jan 2024, 06:22 AM

Unfortunately, many SMTP error messages are generic and don’t let you know the root cause. Are these send attempts all directed at the same domain, which resolves to your server? It appears to me that the ISP is not allowing the SMTP transaction to even start. This might be due to a malformed email address at your domain, or the ISP system not properly discovering your DNS record, resolving your MX record properly, or not reaching your server MX IP address due to a routing problem.

Is there only one domain whose MX record points to your server? If there was another domain whose email is being delivered to your server, someone could test to see if that other domain works.

Of course, it’s also possible there is some other reason involving spam control. Do you have SPF records set up for the domain which is supposed to be receiving the messages?

Bill

26 Jan 2024, 12:05 PM	#1
dynaco120 Junior Member Join Date: Dec 2010 Posts: 9	Ecelerity Users of a regional ISP that use their ISP’s email server are receiving rejection notices when they send emails to users on my email server. The error message sent back to the ISP user indicates “the address failed”, “550 5.0.0 Access denied“ but a check of my logs indicate that the ISP’s email server did not even make an attempt to deliver the mail. The only thing that might suggest what is going on is that the error message appears to be created by “ecelerity” which I assume is some sort of commercial filtering software. Does anyone know if ecelerity tends to block for some period of time, as some DNSBLs do, or if it is a permanent block? It really has me baffled. I could see if it blocked email “from” my server if it thought it was spam etc., but why would it block “inbound” email to my server? Why would it care what email my email server accepts? All email from other sources arrives without a problem. Thanks

27 Jan 2024, 06:22 AM	#2
n5bb Intergalactic Postmaster Join Date: May 2004 Location: Irving, Texas Posts: 9,031	Unfortunately, many SMTP error messages are generic and don’t let you know the root cause. Are these send attempts all directed at the same domain, which resolves to your server? It appears to me that the ISP is not allowing the SMTP transaction to even start. This might be due to a malformed email address at your domain, or the ISP system not properly discovering your DNS record, resolving your MX record properly, or not reaching your server MX IP address due to a routing problem. Is there only one domain whose MX record points to your server? If there was another domain whose email is being delivered to your server, someone could test to see if that other domain works. Of course, it’s also possible there is some other reason involving spam control. Do you have SPF records set up for the domain which is supposed to be receiving the messages? Bill