• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Using External Mail Servers

C

cmurphy@

Guest
Here is the plesk zone for this domain

Code:
n-e-s.net.	NS	ns.n-e-s.net.	
n-e-s.net.	A	65.254.59.157	
mssql.n-e-s.net.	A	65.254.59.157	
webmail.n-e-s.net.	A	65.254.59.157	
ns.n-e-s.net.	A	65.254.59.157	
mail.n-e-s.net.	A	216.168.230.166	
ftp.n-e-s.net.	CNAME	n-e-s.net.	
[url]www.n-e-s.net.	CNAME	n-e-s.net.	[/url]
n-e-s.net.	MX (0)	inbound.n-e-s.net.netsolmail.net.	
n-e-s.net.	MX (5)	outbound.n-e-s.net.netsolmail.net.	
65.254.59.157 / 24	PTR	n-e-s.net.


The problem is this:

Local domains on this box are unable to send mail to this domain.

A bounce occurs with the following information:

Code:
Hi. This is the qmail-send program at veglargh.hyperactivehosting.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.

<[email protected]>:
This address no longer accepts mail.

--- Below this line is a copy of the message.


I am assuming this is due to the redirect for the MX records not working and our server trying to deliver a local email to a local box which of course does not exist.

What do you think is wrong?
 
If you are using a mail server external to Plesk, simply click the "disable" button within the mail area for the domain name.
 
Back
Top