NETSE
Zimbra 10 FOSS / OSEZimbra SMS Login
Zimbra webmail 2FA extension. After the password, users verify with an SMS code or Authenticator — no separate portal, same familiar login screen.
Step 2
Two-factor verification
Enter the SMS code or the code from your Authenticator app.
Zimbra SMS sign-in · Authenticator · webmail 2FA
Zimbra SMS sign-in and Authenticator
Password alone is not enough: enable SMS or Authenticator two-factor on Zimbra webmail. Optional or required per domain; easy access from the office, strong protection from outside.
Two verification methods
You can enable both on a domain; each user enrolls in only one.
SMS verification
A one-time code to the phone after the password. Netgsm, Ileti Merkezi, or the SMS provider you request.
Authenticator (TOTP)
Google Authenticator, Authy, or a compatible app. QR setup — ideal when teams prefer not to rely on SMS.
Yearly plan
One license package — bound to your server. Even if it expires, mail is not locked; only SMS 2FA turns off.
Yearly license
$299 / year
Zimbra SMS Login — all features included. Mention a custom SMS provider in the form if needed.
Included
- Zimbra SMS sign-in (webmail SMS 2FA)
- Authenticator — Google Authenticator / Authy (TOTP)
- Netgsm and Ileti Merkezi support
- Custom SMS / GSM provider on request
- Domain-based enable / enforce
- Office and VPN trusted-IP bypass
- App passwords (Outlook / mobile)
- Turkish admin and user UI
- Server-bound yearly license
How sign-in works
Familiar webmail screen — SMS or Authenticator after the password.
- 01
Enter password
Users sign in on the familiar Zimbra webmail login screen with email and password.
- 02
Choose method
Depending on enrollment, an SMS code or Authenticator code is requested. From a trusted office IP, this step can be skipped.
- 03
Sign in with code
Entering the correct code completes Zimbra SMS Login and opens the session.
- 04
Use mail
Webmail continues as usual. Mobile and Outlook can use app passwords.
Who is it for?
Organizations running their own Zimbra
Teams that want SMS and Authenticator 2FA on webmail, easy office access, and app passwords for phones and Outlook.
Managed mail providers
Operators who manage Zimbra SMS Login rules per customer domain from one panel, including SMS provider and license settings.
Zimbra SMS Login quote form
Request the yearly $299 license. If you need a different SMS provider, include it in your message.
Frequently asked questions
Short answers about Zimbra SMS Login, SMS sign-in, Authenticator, and webmail 2FA.
What is Zimbra SMS Login?
It is an extension that adds two-factor sign-in to Zimbra webmail. After the password, users verify with an SMS code or Authenticator (TOTP). The product is named Zimbra SMS Login; Authenticator is included in the same package.
Which Zimbra versions are supported?
Built for Zimbra 10 FOSS / OSE. If you run another version, mention it in the quote form.
Will users see a different login page?
No. The existing Zimbra webmail login screen stays; an SMS or Authenticator step is added after the password.
Which SMS providers are supported?
Netgsm and Ileti Merkezi are ready out of the box. Need another SMS or GSM provider? Tell us in the quote form — we can integrate it for you.
How does Authenticator work?
You can enable Authenticator per domain. Users enroll with Google Authenticator or Authy via QR or a manual key. Each account uses one method only: SMS or Authenticator.
Do office users get a code every time?
Not if you choose so. Trusted office or VPN addresses can bypass 2FA; external logins still require SMS or Authenticator.
How do phones and Outlook connect?
With app passwords. Webmail still uses SMS or Authenticator.
Does the Admin Console require 2FA?
No. The admin console is exempt from SMS / Authenticator so operations are not interrupted.
If the license expires, is mail locked?
No. When the license ends, 2FA turns off and users keep signing in with passwords. Mail flow is unaffected.
How is pricing structured?
One plan: $299 per year. SMS and Authenticator included. Write any SMS provider request in the form on this page.