You finish a quotation, press Send and get an error. Your inbox still receives messages, so the connection appears to be working. What should you check next?
Start with the exact error and a simple comparison with webmail. Sending uses an outgoing service called SMTP, while reading messages commonly uses IMAP. One can work while the other needs attention.
This guide is for a business mailbox on your own domain. If your email is provided by Google Workspace, Microsoft 365 or another service, follow that provider’s account and connection instructions.
1 Save the error before changing anything
Keep a copy of the message in Drafts and capture the complete error. If you received an “Undelivered Mail” or delivery-failure notice, preserve its technical details, including the server response and any message or queue ID.
Note whether the message stayed in Outbox, failed immediately or produced a bounce later. Also record the sending address, recipient, app and attempt time. These details help support find the relevant server log.
For a fictional example, imagine a stationery supplier in Tamale trying to send a quotation from orders@example.com to accounts@example.org. Record “23 October, 10:15 GMT” alongside the error. Both addresses are reserved examples; use your own details only in your private support request.
Avoid repeatedly pressing Send while you investigate. First check whether the message is waiting in Outbox or whether the recipient already received it, so you can avoid duplicate quotations.
2 Compare the app with webmail
Open the webmail link provided for your service. Nakroteck’s webmail guide explains how Plesk customers can open Mail and use the webmail icon beside the mailbox. Sign in with the full email address and mailbox password.
If the error reports a sending limit or a policy block, keep that error and go to the relevant check below. Otherwise, send one short test through webmail to a different address you control. Use a harmless subject and no attachment, then check the destination’s Inbox and Spam folders.
- If the test arrives, compare the app’s outgoing settings with the current settings for your own service.
- If webmail also rejects sending, save its error too. The problem needs investigation beyond that app’s setup.
- If the webmail page itself times out, record the full URL and try loading it once on another connection, such as mobile data. Tell support which connection failed.
A message appearing in Sent is useful evidence, but confirm receipt at the destination before concluding that delivery worked. Email can pass through several servers, and a failure notice can arrive after the first server accepts it. The SMTP standard explains that handover.
3 Match the response to the next check
Read the words beside the code. A short code alone rarely identifies the complete cause.
| Error or symptom | What it points towards | What to do next |
|---|---|---|
535 5.7.8 or an authentication failure |
The outgoing server did not accept the login credentials. | Check the full username, current mailbox password and outgoing server settings. |
550 5.7.1 with policy or authorisation wording |
A server refused the message under an access or filtering rule. | Preserve the full response and the name of the rejecting server for support. |
| “Sending limit exceeded” or similar wording | An allowance may have been reached. | Pause sending and check which mailbox or shared allowance applies. |
| Connection timeout or certificate warning | The connection or server identity needs checking. | Verify the supplied hostname and encryption settings; report the exact warning. |
The SMTP authentication specification defines 535 5.7.8 as a credentials failure. The enhanced status-code standard describes 5.7.1 as an authorisation refusal. A policy rejection can come from your sending provider, an intermediate relay or the recipient’s system; the complete bounce helps identify which one.
SMTP responses beginning with 4 generally indicate a temporary failure. Those beginning with 5 indicate a failure that needs review before repeating the same request. “Permanent” describes that failed request; it does not mean the mailbox can never work again. These categories come from the SMTP reply rules.
For a login problem, compare the outgoing hostname, port, encryption and authentication with the settings supplied for your mailbox. Nakroteck’s email-app setup guide provides the Plesk setup reference. Keep encryption and certificate checks enabled. If your password has changed, update the saved login in each app or integration that uses that mailbox.
4 Check the shared sending allowance
On Plesk hosting, outgoing limits can apply to a mailbox, a domain and the hosting subscription. The domain allowance is shared across its mailboxes. A subscription can also cover more than one domain.
This means a mailbox can be limited even when its own recent sending is low: another mailbox or an application may have used the shared allowance. Plesk documents how these limits interact.
Ask which allowance was reached, how recipients are counted and when sending can resume. Follow any retry time given in the error. A figure quoted for another business or hosting service may not apply to yours.
Pause a newsletter, automated notification job or other known source of repeated sending while the usage is reviewed. Switching between webmail and a phone does not create a separate allowance for the same mailbox. If the recorded volume is unexpected, ask support to investigate possible misuse before increasing a limit.
5 Give support the details needed to trace the failure
For a policy rejection, ask your provider to identify the rejecting system and review the specific rule. Keep spam filtering and sending limits active while the cause is checked.
If the rejection explicitly mentions SPF, DKIM or DMARC, include that wording. These records help servers check a sending domain’s identity; Google’s sender guidelines explain their use for Gmail. Follow your actual email provider’s instructions for any record changes. A login or allowance error by itself is not a reason to replace your DNS records.
Send support this information in a private ticket:
- Your domain, sending address and affected recipient address.
- The complete error or bounce, including a message or queue ID if present.
- The date, exact time and time zone of the attempt.
- The app and device, plus the result of the webmail comparison.
- For a timeout, the URL or server hostname and your public IP on the affected connection.
Keep passwords, recovery codes and private message contents out of screenshots. If receiving mail is also affected, use the separate incoming-email checklist.
Your next step: if sending still fails after these checks, contact Nakroteck support with the error and attempt details above. Ask for the specific cause to be checked before changing your settings again.
Need help choosing the right setup?
Talk to Nakroteck before you buy hosting, domains, SSL, or website services. We will help you choose the right option for your business.