73 lines
3.4 KiB
HTML
73 lines
3.4 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title># Why build your own mail server instead of outsourcing to external entities
|
|
</title>
|
|
<link rel="stylesheet" type="text/css" href="./css/markdown.css" />
|
|
</head>
|
|
<body>
|
|
|
|
<div id="navigation">
|
|
<a href="https://www.iredmail.org" target="_blank">
|
|
<img alt="iRedMail web site"
|
|
src="./images/logo-iredmail.png"
|
|
style="vertical-align: middle; height: 30px;"
|
|
/>
|
|
<span>iRedMail</span>
|
|
</a> // <a href="./index.html">Document Index</a>
|
|
</div>
|
|
|
|
<h1 id="why-build-your-own-mail-server-instead-of-outsourcing-to-external-entities">Why build your own mail server instead of outsourcing to external entities</h1>
|
|
<p>Quote from <a href="http://www.spamhaus.org/news/article/719/a-survival-guide-for-the-small-mail-server">Spamhaus news article</a>:</p>
|
|
<blockquote>
|
|
<p>outsourcing (the mail service) does not come without costs, even when the
|
|
outsourced service appears to be "free". Hidden costs include:</p>
|
|
<ul>
|
|
<li>
|
|
<p>Another organization can see the content of all messages. In some cases,
|
|
the contents of messages are stored on the outsourcing company's servers
|
|
indefinitely. External access to unencrypted emails poses privacy and
|
|
confidentiality issues. Furthermore, the outsourcing company may be located
|
|
in another country and be subjected to different regulations and obligations.</p>
|
|
</li>
|
|
<li>
|
|
<p>In some cases, the outsourcing company's terms and conditions allow it to
|
|
search the content of emails to aid in targeting advertising, which poses
|
|
even greater privacy and confidentiality problems.</p>
|
|
</li>
|
|
<li>
|
|
<p>The organization no longer has control of its own email security.
|
|
Server-based encryption and authentication is managed by the outsourcing
|
|
company, requiring end-to-end encryption for sensitive communications.</p>
|
|
</li>
|
|
<li>
|
|
<p>Large companies with many customers are often a target of cybercrime
|
|
attacks aimed at stealing customer data, and some of these attacks have
|
|
succeeded.</p>
|
|
</li>
|
|
<li>
|
|
<p>Inspection of SMTP transaction logs may be impossible for the end user.
|
|
Troubleshooting failed deliveries and other email problems requires
|
|
interacting with an external support desk. Support desks are sometimes
|
|
slow to respond. First-line support, in particular, might lack the
|
|
training and access to fix any but simple problems, requiring escalation
|
|
and further delays.</p>
|
|
</li>
|
|
<li>
|
|
<p>Sharing a mail server with other organizations can cause delivery issues
|
|
when a user at another organization sends spam through that mail server.
|
|
When the outsourcing company fails to detect and block spam, or is slow to
|
|
terminate service to spammers, the likelihood of problems increases
|
|
substantially.</p>
|
|
</li>
|
|
</ul>
|
|
</blockquote>
|
|
|
|
<div class="footer">
|
|
<p style="text-align: center; color: grey;">All documents are available in <a href="https://github.com/iredmail/docs/">GitHub repository</a>, and published under <a href="http://creativecommons.org/licenses/by-nd/3.0/us/" target="_blank">Creative Commons</a> license. You can <a href="https://github.com/iredmail/docs/archive/master.zip">download the latest version</a> for offline reading. If you found something wrong, please do <a href="https://www.iredmail.org/contact.html">contact us</a> to fix it.</p>
|
|
</div>
|
|
|
|
</body>
|
|
</html>
|