{"id":52069,"date":"2019-03-21T13:00:13","date_gmt":"2019-03-21T18:00:13","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=52069"},"modified":"2019-03-21T13:00:13","modified_gmt":"2019-03-21T18:00:13","slug":"the-cpanel-mail-server-cpanel-eats-its-own-dog-food","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/the-cpanel-mail-server-cpanel-eats-its-own-dog-food\/","title":{"rendered":"The cPanel Mail Server – cPanel Eats Its Own Dog Food"},"content":{"rendered":"\n
“Eating your own dog food” is a popular practice amongst companies where the employees are encouraged, and often do, use their own product in real life scenarios. The phrase “eating your own dog food” was purported to have been coined in the 1970s when television advertisements for Alpo Dog Food. Spokesman Lorne Greene pointed out that he had fed Alpo to his own dogs. Another possibility, even stranger, was a story of the president of Kal Kan Pet Food eating a can of his dog food at shareholders’ meetings. In 1988, test managers for Microsoft VLAN Manager sent out an email titled “Eating our own Dog Food” as a challenge to increase internal Microsoft usage of the product. While cPanel does not encourage or participate in the eating of dog food (except our furry office friends), we do encourage and advocate for the internal testing and usage of our product.<\/p>\n\n\n\n
Whether it is the email that employees send and receive, or the tickets that customers send, or the notifications we get from our build and testing suite, email is critical to our business. If you have sent or received an email that involved a cPanel employee or mailing list, then that mail has touched our mail server. What does our server run on you ask? It’s a cPanel Mail Server, running the newest version of cPanel & WHM there is! So let’s take a behind the scenes look at its capabilities.<\/p>\n\n\n\n
We have over 400 accounts sending and receiving email on our email server. These 400+ accounts are subscribed to (or manage) over 200 mailing lists, combining for a staggering 2T (two terabytes) worth of email storage. On average, there are tens of thousands of messages that are processed per hour on this system. Of the tens of thousands of messages sent, approximately 97.5% of these messages are delivered within 60 seconds of being sent. Pretty interesting, eh? Well sure, 97.5% sounds like a good number, but what does that mean? Let’s break that down:<\/p>\n\n\n\n
For an in-depth breakdown and some hard numbers, we’re going to take a look at a window of ~64 hours on our mailserver:<\/p>\n\n\n\n
Received Messages: 99,749 messages (2494MB) to 513 unique addresses, 1589 delayed emails with a failure rate of 1.6%<\/code><\/li>Sent Messages: 414,691 messages (12GB) to 425,429 unique addresses<\/code><\/li>Rejected Messages: 7144<\/code><\/li>Temp Rejects: 1332<\/code><\/li><\/ul>\n\n\n\nFor the same range of messages, how about the amount of mail delivered per hour? In the chart below, the number of messages delivered per hour is displayed as a series of dots. In this case, each dot represents specifically 607 messages delivered.<\/p>\n\n\n\n