If your Zimbra admin was not smart enough to enable HTTPS logins, or an automatic redirect from HTTP to HTTPS, then you should be complaining to them, and not to the Zimbra devs.
All the tools are there to enable HTTPS logins with HTTP access to the Zimbra web client. And to even force all web traffic over an HTTPS connection (this is how our Zimbra NE server is configured).
Also, POP3 the protocol is a plain-text protocol. Period. No matter which client you use (Thunderbird, Outlook, Outlook Express, Pegasus Mail, The Bat!, etc). Which means, usernames and passwords are sent in plain-text. If you want it encrypted, you have to manually configured your e-mail client to use POP3S (aka POP3-over-SSL). And connect to a server that supports POP3S.
Same for IMAP4. The protocol itself is plain-text. Period. No matter which client you use (Thunderbird, Outlook, Outlook Express, Pegasus Mail, The Bat!, etc). Which means, usernames and passwords are send in plain-text. If you want an encrypted connection, then you need to manually configure the client to use IMAPS (aka IMAP-over-SSL). And connect to a server that supports IMAPS.
For the Zimbra Desktop, it's the same as every e-mail program out there: you have to manually configure it to use an encrypted channel. For example, the ZD supports HTTP or HTTPS connections to a Zimbra server; HTTPS connections to a GMail account; HTTPS connections to a Yahoo! account; POP3 or POP3S connections to a POP3 server; and IMAP or IMAPS connections to an IMAP server.
Don't blame the Zimbra devs if your Zimbra server (or client) is misconfigured.

The knobs are there to enable HTTPS, POP3S, and IMAPS connections.