Emails play a crucial role in online communication. Business orders to meeting invites, lost or delayed mails can end up creating disgruntled customers.
In our role as Website Support Specialists for online businesses, we resolve hundreds of mail issues every day. A commonly encountered email bounce error faced by web hosts, website owners and server owners is:
554 5.7.1 <email@example.com>: Relay access denied (more…)
Mail errors are commonly encountered issues in our role as Website support specialists. In Plesk Windows servers, the default mail server is MailEnable.
Plesk account owners sometimes report the MailEnable error ‘SMTP server response: 550 Requested action not taken: mailbox unavailable or not local’ when trying to send out mails or when managing their account functions through the Plesk panel. (more…)
Now almost every webmaster uses a mobile device to check and reply to their business mails, but the increased mobility presents an issue of mails going out of sync between the various devices they use.
Engineers in our help desk support team often receive requests to locate missing mails sent from mobile devices. This is mostly reported by iPhone and iPad users, and is caused by differing naming conventions for the “sent” mail folder in different mail clients.
SMTP error from remote mail server after RCPT TO:<firstname.lastname@example.org>:
host mx.server.com [xxx.xxx.xxx.xxx]: 550-Verification failed for <email@example.com>
550-The mail server could not deliver mail to firstname.lastname@example.org. The account ordomain may not exist, they may be blacklisted, or missing the proper dns entries.
550 Sender verify failed
If you are a Parallels Plesk web host, you would recognize this as one of the common errors reported by your customers.
Sender verify failed can be caused by issues ranging from improper file permissions to RFC non-compliance. Engineers at Bobcares help desk support services collect detailed information regarding the error through log analysis and engaging the customer. The following are the few of the common causes for this error. (more…)
The mail user reports the error:
Task email@example.com – Sending reported error (0x800CCC78): ‘Cannot send the
message. Verify the email address in your account properties. The server
responded: 550 Access denied – Invalid HELO name (See RFC2821 188.8.131.52)
Corresponding entry in Postfix logs say:
2014-09-12 12:19:45 H=isp-ip-rev-dns.net [xxx.xxx.xxx.xxx] rejected MAIL :
Access denied - Invalid HELO name (See RFC2821 184.108.40.206)
At Bobcares help desk support services, this is a common error we see in Parallels Plesk shared hosting servers. Strict anti-spam rules or lack of SMTP authentication usually cause this error. Given below are a few scenarios we’ve encountered, and the solutions we provided for them. (more…)
Task ‘firstname.lastname@example.org – Sending’ reported error (0x80042109) : ‘Outlook cannot connect to your outgoing (SMTP) e-mail server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).’
If you are a Parallels Plesk web host, this would be a common error reported by your customers who use Outlook.
A one-size-fit-all solution is not possible for this error as the issue might be in the PC/Laptop, at the ISP or even at your server.
Help desk support services at Bobcares engage each web master on a step-by-step trouble shooting process, which determines exactly where the issue is, and solves the specific issue that caused the error. Here’s a quick run down on the various issues that can cause Outlook error 0x80042109. (more…)