1import{_ as a,c as r,a7 as l,o}from"./chunks/framework.Q1KJJagW.js";const d=JSON.parse('{"title":"How to create your own mailbox/es?","description":"","frontmatter":{},"headers":[],"relativePath":"bootcamp/tips/mailbox.md","filePath":"bootcamp/tips/mailbox.md","lastUpdated":1698361641000}'),t={name:"bootcamp/tips/mailbox.md"};function i(n,e,m,s,c,p){return o(),r("div",null,e[0]||(e[0]=[l('<h1 id="how-to-create-your-own-mailbox-es" tabindex="-1">How to create your own mailbox/es? <a class="header-anchor" href="#how-to-create-your-own-mailbox-es" aria-label="Permalink to "How to create your own mailbox/es?"">â</a></h1><p>Creating a full-fledged email server complicated. A significant overhead due to the need for server installation and configuration. Stacks deploys a streamlined solution leveraging AWS SES for email handling and S3 for data storage. AWS Lambda ties these components together, providing a simple, serverless email server solution.</p><ul><li>Unmanaged email server</li><li>Unlimited email addresses/mailboxes</li><li>Easily organize messages</li><li>No server installation or configuration</li><li>No server maintenance</li></ul><h2 id="endless-email-addresses" tabindex="-1">Endless email addresses <a class="header-anchor" href="#endless-email-addresses" aria-label="Permalink to "Endless email addresses"">â</a></h2><p>Once you add and confirm your domain with SES, you can put any string you want in front of the <code>@</code>, as long as it conforms to the email address standard. This means that you'll have endless email addresses at your disposal, and you'll be able to organize your life in a way never possible before. For example, you can give each service you sign up for its own special email:</p><ul><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li>etc.</li></ul><h3 id="organizing-with-a" tabindex="-1">Organizing with a + <a class="header-anchor" href="#organizing-with-a" aria-label="Permalink to "Organizing with a +"">â</a></h3><p>With that said, you can organize your emails with the <code>+</code> character in this way:</p><ul><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li>etc.</li></ul><p>When dealing with clients we came up with this folder structure:</p><ul><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li>etc.</li></ul><p>For all sorts of alerts we like to group them like this</p><ul><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li><a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a></li><li>etc.</li></ul><p>This groups all emails in the corresponding folder by replacing the <code>+</code> with a <code>/</code> character which creates a folder structure in S3. The possibilities are endless.</p><h3 id="thank-you" tabindex="-1">Thank You <a class="header-anchor" href="#thank-you" aria-label="Permalink to "Thank You"">â</a></h3><p>Thank you <a href="https://github.com/0x4447/0x4447_product_s3_email" target="_blank" rel="noreferrer">https://github.com/0x4447/0x4447_product_s3_email</a> for much of the inspiration!</p>',16)]))}const u=a(t,[["render",i]]);export{d as __pageData,u as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.