HEC Montréal: Deployment of a Large-Scale Mail Installation
- « first
- ‹ previous
- 1
- 2
- 3
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Designing Electronics with Linux
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Reply to comment | Linux Journal
7 hours 50 min ago - Nice article, thanks for the
18 hours 31 min ago - I once had a better way I
1 day 17 min ago - Not only you I too assumed
1 day 34 min ago - another very interesting
1 day 2 hours ago - Reply to comment | Linux Journal
1 day 4 hours ago - Reply to comment | Linux Journal
1 day 11 hours ago - Reply to comment | Linux Journal
1 day 11 hours ago - Favorite (and easily brute-forced) pw's
1 day 13 hours ago - Have you tried Boxen? It's a
1 day 19 hours ago




Comments
Honestly way to complicated of a fix
I would just move Google apps and let them take care of the mail. It will be a lot cheaper and more advanced instead of running squirrel mail.
Shortcomings in the setup
Hi,
This is a really interesting infrastructure. But I see a few shortcomings in it. Feel free to comment on them.
1. Round-robin DNS is being used for load-balancing of webmail servers. If one of the servers goes down, connections to it will still be made and will result in failure for the end-user. A better way for load-balancing webmail HTTP connections is to probably use some HTTP proxy.
2. There is no load-balancing of IMAP servers. This might pose a limitation if the size of the university and the IMAP usage increases considerably.
3. Single point of failure of the storage device which is already mentioned in the article.
4. I am not sure if split brain condition (http://linux-ha.org/wiki/Split_Brain) is handled for LDAP & IMAP servers. If not, this may lead to data corruption and inconsistencies.
Regards,
Rahul.
Sun Java Enterprise Mail Serv
Sun Java Enterprise Mail Server runs pretty well on RedHat9. It would be much easier to migrite to Sun Mail Server ver 6.
Easy != better
But it would result in a very inferior email infrastructure. There is also the fact that it would be a lot more expensive, far less customizable, far less maintenable, unsafe (you don't know what is inside), and you would have to pay the Sun maintenance fees.
You better target Microsoft Exchange users on your next propaganda run for Sun. Nobody that knows what he is doing would drop a Cyrus IMAPd + OpenLDAP setup for a Sun Mail Server setup on technical merits.