All email accounts have been migrated to Zimbra, click on the Icon below to access Zimbra via a Browser.
Before you start, ensure the time, timezone and date are set correctly and accurately on your device. Secure connections can fail if time/date is incorrect.
Due to the plethora of different email clients, the different terminilogy they use and the frequency with which things change, it is impractical to maintain an exhaustive list of specific instructions. The information below is generic, but you may need to seek expert help. Whilst Zelan email is currently nominally FREE, this is only for access via WebMail, any support required for configuring email clients will incur a support charge.
Zelan Email Server Hostname = mail.zwi.co.nz
Service | Description | SSL Mode | Protocol | Port |
---|---|---|---|---|
SMTP | Unsecured email submission | None or STARTTLS | TCP | 587 |
SMTPS | Secured email submission | SSL | TCP | 465 |
POP | Unsecured email retrieval | None | TCP | 110 |
POPS | Secured email retrieval | SSL | TCP | 995 |
IMAP | Unsecured email retrieval | None | TCP | 143 |
IMAPS | Secured email retrieval | SSL | TCP | 993 |
Whenever possible only use secure services with S suffix. For very old applications that do not support TLS v1.2 or higher you will need to use the unsecured services.
All services require authentication using the full email address as UserID, e.g. joebloggs@zelan.co.nz and password. New accounts will be supplied with an inital password that will need to be changed on first use.
Due to security updates, very old applications may no longer be able to access the Zelan Email Server. Regrettably due to increasing attacks on servers by malicious people, we cannot leave the server vulnerable simply to support very outdated applications. The following list is by no means exhaustive, but lists the minimum versions for some applications that are in widespread use. In general terms, if the application is less than 5 years old and/or is configured for regular security updates and the software supplier is still actively maintaining the product, it should continue to work. The technical requirement is that all applications must now support TLS v1.2 or higher.
The workaround for very old applications that do not support TLS v1.2 and need to be retained, is to configure them for unsecured access to the email server. Secure access to email servers only protects email between the user and the local server, it does not protect the email between the sender's server and the receiver's server and potentially not between the receiver's server and the receiver's email client. Additional software and processes are required for full end to end security, which older applications probably aren't capable of being integrated with.
The most likely applications to fail are old printers/fax machines/scanners that forward via email.