Sandbox: Difference between revisions
m (→Mobility) |
|||
Line 659: | Line 659: | ||
{|border="1" cellpadding="5" cellspacing="0" | {|border="1" cellpadding="5" cellspacing="0" | ||
|-style="background:gray" | |-style="background:gray" | ||
!rowspan="2"|Manufacturer | |||
!rowspan="2"|Make | |||
!rowspan="2"|Model | !rowspan="2"|Model | ||
!rowspan="2"|OS | !rowspan="2"|OS | ||
!colspan="3"|Mobility Options | !colspan="3"|Mobility Options |
Revision as of 00:26, 3 April 2010

•
|
Open source integrations. Linux®, Apache Tomcat, Postfix, MySQL®, OpenLDAP®.
|
•
|
Uses industry standard open protocols. SMTP, LMTP, SOAP, XML, IMAP, POP.
|
•
|
Modern technology design. Java, JavaScript thin client, DHTML.
|
•
|
Horizontal scalability. Because each mailbox server includes its own data store, message store, and set mailbox accounts, you don’t change anything on existing servers in order to scale the system. To scale for additional mail accounts, add more servers.
|
•
|
High availability support. Red Hat Cluster Suite is integrated with ZCS, for cluster management.
|
•
|
Browser based client interface.
|
•
|
Administration console to manage accounts and servers.
|
The data store is a MySQL database where internal mailbox IDs are linked with user accounts. The data store maps the mailbox IDs to users’ OpenLDAP accounts. This database contains each user’s set of tag definitions, folders, calendar schedules, and contacts, as well as the status of each mail message - read, unread, tags associated to message, and folder the message resides in. The data store is a MySQL database where internal mailbox IDs are linked with user accounts. The data store maps the mailbox IDs to users’ OpenLDAP accounts. This database contains each user’s set of tag definitions, folders, calendar schedules, and contacts, as well as the status of each mail message - read, unread, tags associated to message, and folder the message resides in.
Core Functionality
•
|
Email messaging
|
•
|
Calendaring
|
•
|
Address Books
|
•
|
Web document authoring
|
•
|
Mail delivery and storage
|
•
|
Indexing of mail messages upon delivery
|
•
|
Backup services
|
•
|
Mailbox server logging
|
•
|
IMAP and POP support
|
•
|
Directory services
|
•
|
Anti-spam protection
|
•
|
Anti-virus protection
|
•
|
Delegate a Domain Administrator (Network Edition)
|
•
|
Move mailboxes from one server to another (Network Edition)
|
•
|
Import Microsoft Exchange user accounts
|
•
|
Add accounts and domains
|
•
|
Set account restrictions either for an individual account or by COS
|
•
|
Manage distribution lists
|
•
|
Set up virtual hosts on a domain
|
•
|
Manage servers
|
•
|
Define policies for moving older messages to secondary storage (Network Edition)
|
•
|
Backup and restore (Network Edition)
|
•
|
Monitor usage
|
•
|
Compose, read, reply, forward, and use other standard mail features
|
•
|
View mail by conversation threads
|
•
|
Tag mail to easily group messages for quick reference
|
•
|
Use Search Builder to perform advanced searches
|
•
|
Save searches
|
•
|
Use Calendar to schedule appointments
|
•
|
Share calendars with others
|
•
|
Create address books and share with others
|
•
|
Set mailbox usage preferences, including defining mail filtering options
|
•
|
Create, organize and share web documents with Zimbra Documents
|
Zimbra Components
•
|
Apache Tomcat, the web application server that Zimbra software runs in.
|
•
|
Postfix, an open source message transfer agent (MTA) that routes mail messages to the appropriate Zimbra server.
|
•
|
OpenLDAP software, an open source implementation of the Lightweight Directory Access Protocol (LDAP) that provides user authentication.
|
•
|
MySQL database software.
|
•
|
Lucene, an open-source full featured text index and search engine.
|
•
|
Verity®, a third-party source that converts certain attachment file types to HTML.
|
•
|
Anti-virus and anti-spam open source components including:
|
•
|
ClamAV, an anti-virus scanner that protects against malicious files.
|
•
|
SpamAssassin and DSPAM, mail filters that attempt to identify spam.
|
•
|
Amavisd-new, which interfaces between the MTA and one or more content checkers.
|
•
|
James/Sieve filtering, used to create filters for email.
|
System Architecture
Zimbra Core
Zimbra LDAP
Zimbra MTA (mail routing server)
Zimbra Store (Zimbra server)
•
|
Data store
|
•
|
Message store
|
•
|
Index store
|
•
|
HTML attachment conversion utility
|
Data store.
Message store.
Index store.
HTML conversion.
Zimbra-SNMP
Installing the Zimbra-SNMP package is optional. If you choose to install Zimbra-SNMP for monitoring, the package should be run on every server (Zimbra server, Zimbra LDAP, Zimbra MTA) that is part of the Zimbra configuration. Zimbra uses swatch to watch the syslog output to generate SNMP traps.
Zimbra Logger
Zimbra Spell
Backup Process Overview
Zimbra System Directory Tree
The Directory Tree lists the main directories created by the Zimbra installation packages.Example of a Typical Multi-Server Configuration
The exact configuration for each deployment is highly dependent on variables including the number of mailboxes, mailbox quotas, performance requirements, existing network infrastructure, IT policies, security methodologies, spam filtering requirements, and so forth.
The following figure shows a typical configuration with incoming traffic and user connection. Alternate ways of configuring at many points within the network are possible.
Explanation of this typical configuration flow follows:
1 - Inbound internet mail goes through a firewall and load balancing to the edge MTA for spam filtering.
2 - The filtered mail then goes through a second load balancer.
3 - An external user connecting to the messaging server also goes through a firewall to the second load balancer.
4 - The inbound Internet mail goes to any of the Zimbra MTA servers and goes through spam and virus filtering.
5 - The designated Zimbra MTA server looks up the addressee's directory information form the Zimbra LDAP replica server.
6 - After obtaining the user's information from the Zimbra LDAP server, the MTA server sends the mail to the appropriate Zimbra server.
7 - Internal end-user connections are made directly to any Zimbra server which then obtains the user's directory information from Zimbra LDAP and redirects the user as needed.
8 - Zimbra servers' backups can be processed to a mounted disk.
Mobility
Manufacturer | Make | Model | OS | Mobility Options | ||
---|---|---|---|---|---|---|
Zimbra Mobile for Smart Phones (ActiveSync/MAPI) | Zimbra Mobile Web Client (HTML Browser) | POP/IMAP | ||||
Sony | ||||||
Ericsson | ||||||
G700 | Symbian UIQ | |||||
G900 | Symbian UIQ | |||||
M600 | Symbian UIQ | |||||
P1i | Symbian UIQ | |||||
P900 | Symbian UIQ2 | |||||
P910 | Symbian UIQ2 | |||||
P950 | Symbian UIQ | |||||
P960 | Symbian UIQ | |||||
P990 | Symbian UIQ | |||||
Satio | SymbianS60 | |||||
Vivaz | SymbianS60 | |||||
Vivaz | SymbianS60 | |||||
XPERIA X10 | Android |