Security Update cPremote ( Important )


There was a security bug in the old version of cpremote upto version 6.7  . You can  update the cpremote installation to latest version 6.9 . This contains the fix.

Further detail about this bug will be published  soon after  updating the installations.If you  have any questions , please feel free to contact our support desk.

For updating cPremote simply run the following command from the server shell,

# sh /etc/cron.weekly/

How to configure Zimbra + CSF – The Best Zimbra Firewall Configuration

CSF is one of the best opensource firewalls that using in most of the hosting servers like cPanel and Directadmin . Also it is one of the best firewall for installing Zimbra Mail server . This documentation will help you to configure the CSF firewall in a Zimbra Standalone installation server.

Before starting the installation , you may need to read the documentation available on , this will help you to get a quick understanding of ports that required to open in a Zimbra server.

Install CSF :

You can download CSF from and install it . After that open the CSF configuration and enable the following ports,

TCP_IN = "22,25,53,80,110,143,443,465,587,993,995,7071"
TCP_OUT = "22,25,53,80,110,113,443,465,587,993,995,7071"

Now you need to open the file /etc/csf/csf.pignore and add the following zimbra packages paths.


This will help to white list these binaries in CSF

Now you can start the CSF as follows and test it.

# /etc/init.d/csf start

You may need to test the mail server and its functionalities . After that you can disable the testing mode in csf.conf and reload CSF. You can also perform other generic CSF tweaks after that.

Syslint Technologies provide all sort of Zimbra Technical Support and management services.

Nginx Security Update For All Nginx installations upto version 1.4.0

Greg MacManus, of iSIGHT Partners Labs, found a security problem
in several recent versions of nginx. A stack-based buffer
overflow might occur in a worker process while handling a
specially crafted request, potentially resulting in arbitrary code
execution (CVE-2013-2028).

The problem affects nginx 1.3.9 – 1.4.0.

The problem is fixed in nginx 1.5.0, 1.4.1.

Patch for the problem can be found here:

As a temporary workaround the following configuration

can be used in each server{} block

    if ($http_transfer_encoding ~* chunked) {
        return 444;

Update Your cPnginx :

For updating the cPnginx run the following commands,

# /scripts/installnginx --version=1.4.1

Update Your Danginx :

For updating the Danginx please run the following command,

# /usr/local/directadmin/scripts/installnginx --version=1.4.1

How to Configure Zimbra With External Email Address

You can add your external email accounts to your zimbra email  server from your end user  interface . But sometimes the testing from Zimbr -> Preferences -> Accounts  will fail with an   error like as follows,

2013-05-05 12:29:59,533 WARN  [qtp1347725365-191:https://x.x.x.xservice/soap/TestDataSourceRequest] [;mid=3;ip=;ua=ZimbraWebClient - FF17 (Linux)/8.0.3_GA_5664;] datasource - Test failed: DataSource{id=TestId, type=pop3, enabled=false, name=Test,, port=110, connectionType=cleartext,, folderId=-1}
com.zimbra.common.service.ServiceException: system failure: Unable to connect to POP3 server: DataSource{id=TestId, type=pop3, enabled=false, name=Test,, port=110, connectionType=cleartext,, folderId=-1}
at com.zimbra.common.service.ServiceException.FAILURE(
at com.zimbra.cs.datasource.Pop3Sync.connect(
at com.zimbra.cs.datasource.Pop3Sync.test(
at com.zimbra.cs.datasource.DataSourceManager.test(
at com.zimbra.cs.service.mail.TestDataSource.handle(
at com.zimbra.soap.SoapEngine.dispatchRequest(
at com.zimbra.soap.SoapEngine.dispatch(
at com.zimbra.soap.SoapEngine.dispatch(
at com.zimbra.soap.SoapServlet.doWork(
at com.zimbra.soap.SoapServlet.doPost(
at javax.servlet.http.HttpServlet.service(
at com.zimbra.cs.servlet.ZimbraServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.eclipse.jetty.servlet.ServletHolder.handle(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(
at org.eclipse.jetty.servlets.GzipFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.zimbra.cs.servlet.ZimbraQoSFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(
at org.eclipse.jetty.servlets.DoSFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.session.SessionHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
at org.eclipse.jetty.servlet.ServletHandler.doScope(
at org.eclipse.jetty.server.session.SessionHandler.doScope(
at org.eclipse.jetty.server.handler.ContextHandler.doScope(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
at org.eclipse.jetty.server.handler.HandlerCollection.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(
at org.eclipse.jetty.server.handler.DebugHandler.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.Server.handle(
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(
at org.eclipse.jetty.server.AbstractHttpConnection.content(
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(
at org.eclipse.jetty.http.HttpParser.parseNext(
at org.eclipse.jetty.http.HttpParser.parseAvailable(
at org.eclipse.jetty.server.AsyncHttpConnection.handle(
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
at org.eclipse.jetty.util.thread.QueuedThreadPool$

It solutions is as follows

1) Login to your zimbra sever over ssh and  do the following ,

# su - zimbra
# zmlocalconfig | grep javamail_pop3_enable_starttls

If you see the result of the above command as  ”  javamail_pop3_enable_starttls = true ” , you need to change it to false


# zmlocalconfig -e javamail_pop3_enable_starttls=false
# zmmailboxdctl restart

Now try to login to your zimbra and add the  email account  and test it. If  you still see an issue with ssl , please do the following too,

# zmlocalconfig | grep certs
  data_source_trust_self_signed_certs = false
  mailboxd_truststore = /opt/zimbra/java/jre/lib/security/cacerts
  ssl_allow_accept_untrusted_certs = true
  ssl_allow_mismatched_certs = true
  ssl_allow_untrusted_certs = false
# zmlocalconfig -e ssl_allow_untrusted_certs=true
# zmlocalconfig -e data_source_trust_self_signed_certs=true
# zmmailboxdctl restart

This will fix your issue with external email accounts in Zimbra.