Changes

From SME Server
Jump to navigationJump to search
51 bytes added ,  15:16, 20 December 2008
zarafa ports
Line 23: Line 23:  
  http://bugs.contribs.org/show_bug.cgi?id=4705
 
  http://bugs.contribs.org/show_bug.cgi?id=4705
   −
Some other notes:
+
===ports===
I totally disabled horde (no big loss there) and pop and imap and my implementation either uses horde OR zarafa but not both.  I run zarafa on the standard ports and transitioned 15 users last night.  Some using Outlook (pop) and they didn't notice anything.  A few use webmail and I left the alias alone and those users all logged in this morning to a big surprise and they were all extremely happy.
     −
For this to work, you need to configure zarafa to use the certs already generated in SMEHope this helps.
+
fyi, zarafa db defaults in *-0.9.0-16
 
+
lowercase are not set, the fragment has the default
Paul
+
(SSL) are opened if service is enabled
 
+
 
  Hi Paul, please submit separate bug reports detailing all your customization notes. Darrell
+
zarafa-server tcpport 286
 +
zarafa-server TCPPort 287 (SSL)
 +
 +
  zarafa-gateway pop3port  110
 +
zarafa-gateway pop3sport  995
 +
zarafa-gateway imapport  143
 +
zarafa-gateway imapsport  993
 +
zarafa-gateway TCPPort 995,993 (SSL)
 +
 +
zarafa-ical icalport 8088
 +
zarafa-ical TCPPort 8089 (SSL)
 +
   
 +
#sme ports were changed to, and disabled
 +
 +
/sbin/e-smith/config setprop pop3 TCPPort 8110
 +
/sbin/e-smith/config setprop pop3s TCPPort 8995
 +
/sbin/e-smith/config setprop imap TCPPort 8143
 +
/sbin/e-smith/config setprop imaps TCPPort 8993

Navigation menu