• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Remote host said: 554 Message refused.

Z

zimre

Guest
In the process of moving to a new server... setup up domain on new server... created mail account that redirects to e-mail address of a different domain located on old server... however, I receive the following error when sending mail to that address:

Hi. This is the qmail-send program at myDomain.net.
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.

<myAddress@myOtherDomain.com>:
This address no longer accepts mail.

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

Return-Path: <anonymous@myDomain.net>
Received: (qmail 31848 invoked by uid 48); 11 Apr 2007 10:52:25 -0500
Date: 11 Apr 2007 10:52:25 -0500
Message-ID: <20070411155225.31847.qmail@myDomain.net>
To: myAddress@myOtherDomain.com
Subject: Testing new e-mail redirect
From: ME <myAddress@myOtherDomain.com>
Reply-To: ME <myAddress@myOtherDomain.com>

rest of the message follows.

here's another sample:

Hi. This is the qmail-send program at myDomain.net.
I tried to deliver a bounce message to this address, but the bounce bounced!

<myAddress@myOtherDomain.com>:
This address no longer accepts mail.

--- Below this line is the original bounce.

Return-Path: <>
Received: (qmail 24073 invoked for bounce); 11 Apr 2007 10:14:21 -0500
Date: 11 Apr 2007 10:14:21 -0500
From: MAILER-DAEMON@myDomain.net
To: myAddress@myOtherDomain.com
Subject: failure notice

Hi. This is the qmail-send program at myDomain.net.
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.

<myAddress@myOtherDomain.com>:
This address no longer accepts mail.

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

Return-Path: <myAddress@myOtherDomain.com>
Received: (qmail 24065 invoked by uid 2523); 11 Apr 2007 10:14:21 -0500
Date: 11 Apr 2007 10:14:21 -0500
Message-ID: <20070411151421.24064.qmail@myDomain.net>
To: myAddress@myOtherDomain.com
Subject: <myDomain.net> Notification of the domain creation.
From: ME <myAddress@myOtherDomain.com>
Reply-To: ME <myAddress@myOtherDomain.com>
Content-Transfer-Encoding: 8bit
X-Mailer: PHP/5.0.5
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8

followed by content of message.

The address on my other domain is still active and can except mail from other sources ... for some reason won't except mail from the new server... Any ideas?

------
zimre
 
The domain also uses a contact form... the form is set to send two messages... one to the webmaster and one to the person filling out the form... when testing the form, I noticed... the person filling out the form receives their copy... however... the webmaster does not receive a copy... instead I receive a mail delivery error message similar to the ones mentioned above.

Though this one says: "550 Sender verify failed"

Also spam messages sent to the domain in question are being delivered to my postmaster address with the error: "Remote host said: 554 Message refused."


Any ideas?
 
I have had issues like this before to. By adding and SPF record that helped but more importantly having your reverse DNS setup correctly fixed my problem. Are you running your server from home?
 
Back
Top