I've configured several email addresses using the built-in CPanel email utility, and they're all able to successfully send outgoing mail. Incoming mail however is bounced back, with one of the following two errors:
Address not found:
The response from the remote server was:
550 5.1.1 <email#domain.com> Recipient not found.
Message not delivered:
The response from the remote server was:
550 5.4.1 [nathan#fortunesfavored.com]: Recipient address rejected: Access denied
I believe that these error codes (550 5.4.1 and 550 5.1.1) are Exchange server errors, meaning that incoming mail is being directed to the wrong server. (I'm hosting on a GoDaddy service). Is that correct? If so, is this an issue that I would solve in my DNS settings under the MX entry? Here's what I have now:
Priority Host Points to TTL
10 # mailstore1.secureserver.net 1 Hour
0 # smtp.secureserver.net 1 Hour
yes you have to edit your MX entries.
Login to you cpanel account.
under emails click on MX entries.
if there is no MX entry then add a MX entry.
mail.yourdomainname.com and set priority 10
Related
I am trying to send a mail from centos machine, but I came to a problem. I have installed "mail" and ssmtp inside my linux machine and I got this response when I try to send a mail.
ssmtp: 550 invalid DNS MX or A/AAAA resource record
FromLineOverride=YES
mailhub=smtp.1und1.de:587
UseSTARTTLS=YES
Of course, with the correct password and user.
I have tried already couple of users and everybody are returning the same.
I have tried even with my own user and the password that I have, but it won't work.
If you have any other approaches to this problem let me know also.
What am I doing wrong ?
The problem seems to be the FROM address for the SMTP envelope. Some SMTP servers will ignore an invalid value like Gmail for example (that's why it worked for me with Gmail) but if you're using 1und1 SMTP-Server you have to override the domain if it's not the same as the mail domain (e.g. if you're on a local test server).
You can override the domain in the /etc/ssmtp/ssmtp.conf:
Assuming your email is: my#yourdomain.de
rewriteDomain=yourdomain.de
when im trying to send email from my domain to polish email providers onet.pl and gazeta.pl im getting bounce back message:
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
XXX#gazeta.pl
SMTP error from remote mail server after HELO mydomain.com:
host mx.poczta.gazeta.pl [1.1.1.1]: 503 5.7.0 Error:
access denied for unknown[2.2.2.2]
I have configured ptr and mx record. Please help.
There are so many possibilities for the mail denied. Please check :
1) Your mail server IP address should not be blacklisted anywhere. You can check it from http://multirbl.valli.org/lookup/
2) Make sure that the recipient mail server listen on the port which you are using i.e. Port 25. Please check if the port 587 works. You can also try port 465 with TLS.
3) Check if any Antivirus application installed on your side causes the issue.
I've been trying to install a Postfix server for handling mail for my domain. I found some nice tutorial and I was able to create email address and server responds correctly with telnet (imap and pop3 included, I also charge the config in Gmail and works correctly).
To handle POP3 and IMAP I have installed Courier
The problem comes when I try to send e-mails to myself (with external email address), I receive the following error code:
Action: failed
Status: 5.4.6
Diagnostic-Code: X-Postfix; mail for (servername) loops back to
myself
I reviewed my postfix mail.conf config, as in many webs they said that it could be because mydestination was not corectly configured. I have included the domain configuration and I still get the same error. (/etc/postfix/main.cf)
mydestination = mail.mydomain.com, domain.com, localhost
This is in a VPS, so the hostname is different to the domain name, I'm not sure if this can have any influence on the handling mail error.
Could someone help me to find where can the error be?
Thanks for your attention and your answers
You're probably sending mail to a recipient, with an email address in a zone which has an MX record, with its value a hostname, which resolves to the ip address of your mailserver, while this your server hasn't been told in its main.cf config file (behind mydestination), that it is referring to itself.
Therefore, your server is wondering why an attempt to send mail to - as it believes - another server results in finding that the ip address of that another server is its own ip address.
Update mydestination accordingly.
It helps to use the same hostname for MX record, for all zones your mailserver handles incoming mail for, as that keeps your mydestination manageable.
I have a problem with SMTP configuration.
I use Gmail with my domain for ex. www.mydomain.com. When I try to send email from server under that domain to mailbox#mydomain.com I get fail report
Final-Recipient: rfc822;mailbox#mydomain.com
Action: failed
Status: 5.3.5
MX records are as in Google configuration wizard. Why is the mail looping?
10 alt2.aspmx.l.google.com
10 aspmx.l.google.com.mydomain.com
10 alt1.aspmx.l.google.com
20 aspmx2.googlemail.com
20 aspmx3.googlemail.com
My server is IIS 7, with default SMTP service.
Thank you for any help.
If someone will find this question, problem was with DNS MX records:
aspmx.l.google.com.mydomain.com
but it should be
aspmx.l.google.com
Apparently this was causing the loop.
I have two websites, we'll call them a.com and b.com. I already have a mail server running on b.com. What I would like to do is have any email sent to #a.com to be automatically forwarded to b.com. I edited the only MX record in the a.com DNS settings to be...
Priority: 10
Host: #
Points To: b.com
After setting this up and giving it time to propagate, mail sent to a.com does not go through and I get a "Message not delivered" response from my email client.
Thanks for any help!
The MX-Record does only tell the webserver where to deliver mail for that specific domain. So any mail sent to user#a.com will be sent to the mailserver at b.com, that does not mean that they get forwarded to user#b.com. You will have to configure your mailserver at b.com to accept mails for the a.com domain.