+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: Users can send emails, but can't receive (/thread-15944.html)
Users can send emails, but can't receive - clemorphy - 03-23-2012 07:39 PM
Hello,
I have just installed ispCP on a VPS.
The installation was OK.
I have created a reseller, and then a user with a domain (mydomain.net)
On this domain I have created an email account (myemailaccount@mydomain.net)
With this email account, using the webmail, I can send emails which are successfully received.
But when I try to send emails to this account, for example from gmail, I get an error message from gmail which says :
Quote:Delivery to the following recipient failed permanently:
myemailaccount@mydomain.net
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 5.7.1 <myemailaccount@mydomain.net>: Relay access denied (state 14).
Any idea to solve the problem ?
RE: Users can send emails, but can't receive - joximu - 03-23-2012 08:28 PM
There are many possibilities why this can happen.
First I would look in the mail log files on the ispcp server.
Find the lines which correspond to the delivery report above (5.7.1 <myemailaccount@mydomain.net>: Relay access denied) - often there are more infos which can help finding the problem.
If there is nothing in the mail logs which fit to the receiving mails - then probably the problem is outside: DNS or other things...
/J
RE: Users can send emails, but can't receive - clemorphy - 03-24-2012 12:00 AM
Thanx for your answer.
While trying to send from another server, I got a more precise error.
My MX record was pointing at a wrong server ...
It is working fine now
RE: Users can send emails, but can't receive - joximu - 03-24-2012 12:05 AM
ah - so "the problem outside"... DNS
/Closing