In our first ever release, we relied on iptables for port forwarding so that a regular user process could have access to privileged ports (ie, ports < 1024 can be bound only by root). Eg, our IMAP server would bind to port 7143, and iptables would be setup to forward port 143 to 7143. (more…)
Archive | Zimbra Server
All REST and no play…
One of the things we are working on for an upcoming release is REST interfaces into all our content. If you aren’t familiar with REST I’d just suggest reading Building Web Services the REST Way. Today, within the Zimbra Collaboration Suite we have a number of different server-side URLs that our client accesses to download […]
From C/C++ to Java
In 1999 when we were architecting and implementing Onebox.com, we had to select an implementation language. Given that all the principle architects at Onebox were from JavaSoft, so one would expect Java to be the natural choice. It was not. Before going further, I should perhaps write a little about Onebox.com. Onebox.com was a unified […]
New Admin UI screen shots posted
We just pushed some new Screenshots of the Admin UI.
SOAP and the Server Architecture
Why did we not use Cyrus IMAP and what’s this business of AJAX and SOAP … Roland talks about our our server architecture here and about our SOAP here.
Is your mail server an open relay?
Some of you may already know about this but for those who don’t or forgot. After setting up your mail server you should run a mail relay test. This will run several tests against your MTA and verify it’s properly configured. By default Zimbra ships postfix such that it’s not a relay. However any custom […]