Fixing Common Email Problems: Can't Send, Receive or Log In

Fixing Common Email Problems: Can't Send, Receive or Log In

Email issues are frustrating, but most of them trace back to a small number of causes — wrong settings, a full mailbox, or an authentication hiccup. This guide walks you through the most common problems Momo Cloud customers encounter, with clear steps to fix each one.

Quick First-Check: Confirm Your Mail Settings

Before diving into specific problems, verify that your email client (Outlook, Thunderbird, Apple Mail, or your phone's mail app) is configured with the exact Momo Cloud settings below. A single wrong value — even one digit in a port number — can stop email from working entirely.

Tip: If you are unsure which settings your email client currently uses, look under Account Settings or Server Settings in your mail app. Compare every field against the table above before moving on.

Problem: Cannot Log In / Password Rejected

Symptom

Your email client shows an error such as "incorrect password," "authentication failed," or "invalid credentials."

Common Causes and Fixes

Wrong password. Passwords are case-sensitive. If you recently changed your cPanel or email account password, update it in your mail client too.

1. Log in to your cPanel account at your hosting control panel URL.
2. Go to Email Accounts and find the affected address.
3. Click Manage, then set a new password under Security.
4. Update the same password in your email client's account settings.

Username is not the full email address. Momo Cloud requires your complete email address as the username — for example sales@yourdomain.com, not just sales. Entering only the part before the @ sign will always fail.

1. Open your mail client's account or server settings.
2. Find the Username or Account Name field.
3. Replace any partial name with your full email address.
4. Save and try connecting again.

Tip: After three or more failed login attempts your IP address may be temporarily blocked by the server's brute-force protection. Wait five to ten minutes before trying again, or use Webmail (see below) to confirm the password works.

Problem: Cannot Send Email

Symptom

Incoming email works but messages sit in your Outbox, or you see errors like "relay denied," "authentication required," or "connection refused."

Common Causes and Fixes

SMTP authentication is not enabled. Momo Cloud's outgoing server requires you to log in before sending. Most email clients have a separate checkbox or option for this.

1. Open your outgoing server (SMTP) settings in your email client.
2. Enable SMTP Authentication or Outgoing Server Requires Authentication.
3. Set the username to your full email address and enter your password.
4. Save and try sending a test message.

Wrong outgoing port. Use port 465 with SSL/TLS, or port 587 with STARTTLS. Never use port 25 — most internet service providers (ISPs) and mobile networks block it, and Momo Cloud does not support it for authenticated client sending.

1. In your SMTP settings, change the port to 587 and set encryption to STARTTLS.
2. If that does not work, try port 465 with SSL/TLS instead.
3. Remove or change any setting that says port 25.

ISP is blocking outbound connections. Some internet providers in Tanzania and elsewhere block outbound SMTP traffic on all ports as an anti-spam measure. If you are on mobile data or a shared network, try switching between port 465 and 587. Using Webmail (which sends through the server directly) is a reliable workaround when your ISP is the cause.

Problem: Cannot Receive Email

Symptom

Senders report your address is unreachable, or you know emails should have arrived but your inbox is empty.

Common Causes and Fixes

Mailbox is full (over quota). When a mailbox reaches its storage limit, new messages bounce back to the sender. You will usually receive a quota warning email before this happens.

1. Log in to cPanel and go to Email Accounts.
2. Check the Storage Used column for your address.
3. If it is at or near 100%, log in to Webmail and delete old messages, large attachments, or empty the Trash and Spam folders.
4. To increase your quota, contact Momo Cloud support or adjust the limit in Email Accounts if your plan allows it.

Emails going to your Spam or Junk folder. Check Spam/Junk in both your email client and in Webmail. If legitimate messages land there, mark them as "Not Spam" to train the filter, and add the sender to your contacts or safe-senders list.

MX records are incorrect. If your domain's MX records do not point to mail.momo.tz, email sent to your address will be delivered to the wrong server or bounce entirely. This can happen after a domain transfer or DNS change.

1. Log in to cPanel and go to Zone Editor (or DNS Zone Editor).
2. Look for MX records for your domain.
3. The MX record should point to mail.momo.tz with a priority of 0 or 10.
4. If it is wrong, update it. DNS changes can take up to 24 hours to propagate worldwide.

Problem: Emails You Send Are Not Arriving at Recipients

Symptom

You can send without errors, but recipients say they never received your message — or it arrived in their spam.

Common Causes and Fixes

SPF and DKIM records are missing or misconfigured. These DNS records prove to other mail servers that your email is genuine. Without them, your messages are likely to be flagged as spam or rejected outright.

1. Log in to cPanel and open Email Deliverability.
2. Review the status of SPF, DKIM, and DMARC for your domain.
3. Click Repair next to any record shown as invalid or missing — cPanel will generate the correct values automatically.
4. Allow up to 24 hours for the DNS changes to take effect, then re-check.

Track a specific message. Use cPanel's Track Delivery tool (under Email) to trace exactly what happened to an outgoing message — whether it was delivered, deferred, or bounced, and why. This is the fastest way to get a specific error reason.

Problem: SSL Certificate Warning

Symptom

Your email client shows a security warning about an untrusted or mismatched certificate when connecting.

Cause and Fix

This almost always happens because the incoming or outgoing server is set to your domain name (e.g. mail.yourdomain.com) instead of the shared mail hostname. The SSL certificate is issued for mail.momo.tz, so using your own domain name triggers a mismatch warning.

1. Open your incoming (IMAP or POP3) server settings and change the hostname to mail.momo.tz.
2. Open your outgoing (SMTP) server settings and change it to mail.momo.tz as well.
3. Save the settings and reconnect. The warning should disappear.

Use Webmail to Isolate the Problem

If you are unsure whether the problem is with your email client or with your account itself, Webmail is the quickest way to find out. Webmail connects directly through your browser — no client configuration required.

1. Open a browser and go to your Webmail URL (usually https://mail.momo.tz or https://yourdomain.com/webmail).
2. Log in with your full email address and password.
3. Try sending and receiving a test message.

If Webmail works but your email client does not, the problem is with your client's configuration — review the settings table at the top of this article. If Webmail also fails, the issue is with your account itself (password, quota, or MX records), and the sections above apply.

Summary: Symptom → Cause → Fix

When to Contact Momo Cloud Support

If you have worked through the steps above and the problem persists, please reach out to the Momo Cloud support team. To help us resolve your issue as quickly as possible, include the following in your message: your full email address, the exact error message or screenshot, the name and version of your email client, whether the problem affects sending, receiving, or both, and whether Webmail works for you. With that information, our team can investigate your account directly and get your email running smoothly again.