Files
email-heros/secure-mail-delivery.html
viscous a060173177 Update secure-mail-delivery.html
add mini FAQ and GAQ to nav
2026-01-22 21:05:27 +00:00

107 lines
3.7 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>Secure Mail Delivery</title>
<link rel="stylesheet" href="assets/styles.css" />
</head>
<body>
<div class="container">
<div class="topbar">
<div class="brand">
<div class="brand-mark" aria-hidden="true"></div>
<div class="brand-title">
<strong>Secure Mail Delivery</strong>
<span>Privacy protection while messages travel</span>
</div>
</div>
<nav class="nav" aria-label="Primary">
<a class="pill" href="index.html">Overview</a>
<a class="pill" href="routing-reliability.html">Reliability</a>
<a class="pill" href="spam-junk-reduction.html">Cleaner Inboxes</a>
<a class="pill" href="delivery-help-errors.html">Delivery Help</a>
<a class="pill" href="#faq">FAQ</a>
</nav>
</div>
<section class="hero">
<div class="hero-inner">
<div>
<div class="kicker"><span class="kdot"></span> Security improvement</div>
<h1>Your email stays private while its being delivered.</h1>
<p class="lead">
Email often contains sensitive business information—contracts, invoices, customer details, and internal conversations.
Weve upgraded delivery safeguards so messages are protected in transit and less likely to fall back to weaker security.
</p>
<div class="cta-row">
<a class="btn primary" href="#what-changed">What changed</a>
<a class="btn secondary" href="delivery-help-errors.html">Need delivery help?</a>
</div>
<div class="small-note">No new steps for users. No workflow changes.</div>
</div>
<aside class="hero-side">
<h3>What this improves</h3>
<ul>
<li>Stronger protection against insecure delivery fallback</li>
<li>Better consistency with modern mail providers</li>
<li>Reduced risk of interception during transit</li>
</ul>
</aside>
</div>
</section>
<div class="section-title" id="what-changed">What changed</div>
<section class="grid">
<article class="card">
<h2>Secure delivery is expected—not assumed</h2>
<p>
We strengthened how receiving systems communicate secure delivery expectations to senders,
improving consistency of encrypted delivery where supported.
</p>
</article>
<article class="card">
<h2>Modern safeguards in the background</h2>
<p>
Stronger defaults and upgraded behavior help reduce downgrade risk and encourage encrypted delivery paths
without impacting normal business email usage.
</p>
</article>
</section>
<div class="section-title">What employees will notice</div>
<section class="card">
<p>
Nothing changes in day-to-day work: no prompts, no new software, no new steps.
Email simply benefits from stronger safeguards behind the scenes.
</p>
</section>
<div class="section-title">FAQ</div>
<section class="grid">
<article class="card">
<h2>Do users need to change anything?</h2>
<p>No. This runs in the background and does not change daily workflow.</p>
</article>
<article class="card">
<h2>Will this disrupt delivery?</h2>
<p>No downtime was required, and the goal is improved consistency—not disruption.</p>
</article>
</section>
<footer class="footer">
<span><span class="tag"><b>Tip</b> Most users never need to think about this—security runs quietly.</span></span>
<span><a href="index.html">Back to overview</a></span>
</footer>
</div>
</body>
</html>