550 Relay Not Permitted
Here are some of the most common ones:
1. You're trying to send mail through our mail servers without authentication.
2. Your ISP has blocked the port you're sending mail on.
3. The domain you're sending mail to doesn't have the correct mailservers listed.
4. The DNS records for the domain you're sending mail to have recently been updated.
5. There is a forwarder on the receiving end of the e-mail address you are sending to that forwards to another e-mail address that forwards back to the initial e-mail address, creating an infinite loop.
These are the most common reasons above for seeing this error. Read below to see how to address each issue.
Here is the list of solutions you'll need in the event of seeing this error and one of the above reasons being the cause:
1. In order to send mail through a mail server, your email client must be configured to use SMTP Authentication. That is, our mail servers needs to be logged into with a username and password. Common email clients include a tickbox in the account configuration with the label "This server requires authentication". That box should be ticked, otherwise look for a setting on the outgoing server settings that refers to authentication and set it to use the same username and password for the incoming server.
If there's not an option to use the same credentials as the incoming mail server, you should set your full e-mail address as the username, and then add your mailbox password to the password field.
2. Some ISPs, such as AOL, block sending mail on port 25. If this is the case for your ISP, setting SMTP to port 587 will in almost all circumstances be a working alternative.
3. Our mailservers won't accept mail for domains that don't have our mail servers as the primary MX records (i.e. the records with the lowest priority number set). If you get a 550 error when sending to our servers, and they aren't the primary records, you'll need to raise the priority of the MX records that point to our mail servers by setting them with the lowest number of the existing records.
4. You may also see this error shortly after a DNS change has been made. If a domain's DNS cache has not yet updated to reflect recent changes, you may face 550 errors. Waiting will resolve the matter in this instance.
5. This is simply a case of removing the forwarder that completes the loop. Remember that you can set forwarders on auto-responders, so if this forwards back to the e-mail address the auto-responder is for, this will need to be changed or removed.
If you continue to receive the error, please contact Pebble support, we will be able to assist you further.