Troubleshoot Vioflare IMAP/SMTP issues: cannot send or receive, password errors, SSL warnings, and Outlook or phone sync problems.
Fix Vioflare email when it stops working
Start with webmail. If webmail sends and receives normally, the mailbox itself is healthy and the fault is in a desktop or phone client's settings. If webmail also fails, the problem is the password, DNS or the mailbox — a much shorter list. Working in that order saves you from reconfiguring four devices to fix a single DNS record.
Key takeaways
- Webmail is the diagnostic that splits the problem in half: client-side versus server-side.
- Almost every mailbox fault is one of four things — wrong password, wrong host or port, wrong MX record, or a full mailbox.
- "Receives but will not send" is nearly always outgoing authentication, not an outage.
- A device still holding the old password after a reset will keep failing, and can trigger repeated authentication lockouts.
- Allow for DNS TTL after any domain or hosting change before concluding mail is broken.
1. Confirm webmail still works
Open https://webmail.yourdomain.com.au and sign in with the full email address.
| Webmail result | What it means |
|---|---|
| Login works and mail is visible | Mailbox and password are fine — fix the desktop or phone client |
| Login fails | Reset the mailbox password in the panel — see the password guide |
| The page will not load at all | DNS or SSL for the webmail hostname — open a support ticket |
2. Re-check IMAP and SMTP settings
Compare against the values in the email setup guide:
- Host
mail.yourdomain.com.au, unless your panel shows a different hostname - IMAP port
993with SSL/TLS - SMTP port
465with SSL, or587with STARTTLS - Username is the full email address
- SMTP authentication switched on
The recurring mistakes are worth naming:
- Using
smtp.yourdomain.com.au, or leaving a strayimap.gmail.combehind from a previous account - Username set to
youinstead of[email protected] - SMTP left without a password after a password change
- Port
25, which is commonly blocked on home and mobile networks
3. Cannot send, but can receive
- Confirm the SMTP host, port, encryption and password match the table above.
- On iPhone, open the account, then the outgoing server, and make sure username and password are filled in. iOS presents them as optional and leaves them blank by default.
- Try port
587with STARTTLS if465fails on that particular network. - Send a short test to an external address such as Gmail or Outlook.com. If webmail can send but Outlook cannot, the fault is definitively in the client's SMTP settings.
- Check whether a VPN or corporate firewall is filtering outbound 465 and 587.
4. Cannot receive
- Check webmail first. If new mail is sitting there, the phone or Outlook simply is not syncing — usually a wrong IMAP password or an offline mode.
- Confirm MX still points at Vioflare. A recent domain transfer, or a "point the website elsewhere" change, sometimes moves MX by accident. Email-only hosting explains how MX, SPF and DKIM should be arranged when the website and the mail live on different hosts.
- Check the junk and spam folders in webmail, not just in the mail app.
- Check the mailbox quota. A full mailbox can bounce new mail — free up space or ask support to check the quota.
5. Password or authentication failures
- Reset the mailbox password in the hosting control panel.
- Update every device. A single forgotten tablet will keep retrying the old password.
- Do not confuse the client portal password with the mailbox password — they are separate credentials and only the mailbox one is used by mail apps.
6. SSL and certificate warnings
- Use hostnames that match the certificate, normally
mail.yourdomain.com.auor whatever the panel displays. - Do not switch SSL off to make a connection succeed. That sends your password in clear text over the network.
- If the certificate name genuinely does not match, open a ticket with a screenshot rather than permanently dismissing the warning on production mail.
7. Outlook-specific fixes
- Prefer IMAP for Vioflare mailboxes rather than Exchange, unless you use Microsoft 365.
- Remove a broken profile and re-add the account rather than repairing it in place.
- Disable a VPN temporarily to rule out network filtering of ports 465, 587 and 993.
8. After DNS or hosting changes
If you have moved the website, kept mail on Vioflare, or transferred a domain, then MX, SPF and DKIM must still match the mail host. DNS changes also take time to spread — wait out the record's TTL before retesting, and see DNS after checkout for how the records fit together.
Frequently Asked Questions
Why is my Vioflare email not working on my phone but fine in webmail?
Because the mailbox is healthy and only the phone's settings are wrong. Check that the host, ports and encryption match, that the username is the full email address, and that the outgoing server has its password filled in.
Why does my mail say SMTP authentication failed?
The outgoing server is either not authenticating at all or using a stale password. Switch outgoing authentication on, set it to use the same credentials as incoming, and re-enter the mailbox password after any reset.
How long should I wait after changing DNS before mail works again?
Allow for the record's TTL, which is often up to an hour and occasionally longer. Retesting every few minutes during that window will produce inconsistent results as different resolvers update at different times.
Can a full mailbox stop incoming email?
Yes. When a mailbox reaches its quota, new messages can bounce back to the sender. Delete large attachments through webmail, or ask support to confirm the current quota.
What should I include in a support ticket?
The full email address but never the password, whether webmail works, the client name and the exact error text, and whether the failure is on sending, receiving or both. That set of facts is usually enough to resolve it in one reply.
Still stuck?
Open a portal ticket with the details above, or contact the Vioflare team.

