Jump to content

Richagobal Zimbra Archietcture and other compoments: Difference between revisions

From TetraWiki
No edit summary
No edit summary
Line 1: Line 1:
[[category:Richaglobal]]
[[category:Richaglobal]]
==Architecture==


[[Image:Richaglobal.png|600px]]
[[Image:Richaglobal.png|600px]]
== Environment Explanation ==
* Dedicated Zimbra Server in Godaddy ISP Farm which is an Virtual Server with Centos 6
* Locally , they are running Licensed Windows based Mdaemon Mail Server .
* Mdaemon Server has all the accounts and all users access it . No user access the Zimbra Server directly
* Mdaemon server polls all the user accounts in zimbra and download there mails in mdaemon server .
* Also while sending mails the mdaemon server relays mails via zimbra Server and then zimbra Server via mail.tetrain.com ( godaddy has poor smtp services , i.e why mails are finally routed via mail.tetrain.com  )
== Additional Implementations ==
* Spam tuning via http://wiki.zimbra.com/index.php?title=Improving_Anti-spam_system
* Custom Scripts to change all the users of both the domains , lying in /home/richa directory
* All mails which are marked Junk / spam by Zimbra is also going to a single mail box all_spam_tagged

Revision as of 08:02, 1 June 2013


Architecture

Environment Explanation

  • Dedicated Zimbra Server in Godaddy ISP Farm which is an Virtual Server with Centos 6
  • Locally , they are running Licensed Windows based Mdaemon Mail Server .
  • Mdaemon Server has all the accounts and all users access it . No user access the Zimbra Server directly
  • Mdaemon server polls all the user accounts in zimbra and download there mails in mdaemon server .
  • Also while sending mails the mdaemon server relays mails via zimbra Server and then zimbra Server via mail.tetrain.com ( godaddy has poor smtp services , i.e why mails are finally routed via mail.tetrain.com )

Additional Implementations