<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Lanasia Chavez</title>
    <description>The latest articles on DEV Community by Lanasia Chavez (@lanasiachavez7).</description>
    <link>https://dev.to/lanasiachavez7</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4201505%2Fcb960473-49bd-4d38-9ba8-9726bd9f72ec.png</url>
      <title>DEV Community: Lanasia Chavez</title>
      <link>https://dev.to/lanasiachavez7</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lanasiachavez7"/>
    <language>en</language>
    <item>
      <title>How I Keep Website Test Emails Separate From My Main Inbox</title>
      <dc:creator>Lanasia Chavez</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:35:22 +0000</pubDate>
      <link>https://dev.to/lanasiachavez7/how-i-keep-website-test-emails-separate-from-my-main-inbox-4lk1</link>
      <guid>https://dev.to/lanasiachavez7/how-i-keep-website-test-emails-separate-from-my-main-inbox-4lk1</guid>
      <description>&lt;p&gt;When testing a new website, I often need to check sign-up confirmations, welcome emails, password resets, and contact-form notifications.&lt;/p&gt;

&lt;p&gt;At first, I tried several approaches: creating separate Gmail accounts, using aliases, and setting up mailboxes on my own domains. They all worked, but the setup quickly became more complicated than the actual testing.&lt;/p&gt;

&lt;p&gt;After experimenting with a few services, I realized there was no need to reinvent the wheel.&lt;/p&gt;

&lt;p&gt;For small projects, I now use SmailPro. Its free option provides up to five inboxes that I can rotate between, with common email types such as Gmail, Outlook, .edu, and custom-domain addresses.&lt;/p&gt;

&lt;p&gt;That has been enough for checking basic email flows without filling my personal inbox with test messages. It is especially useful when I want to see how emails are delivered to different types of addresses.&lt;/p&gt;

&lt;p&gt;One important limitation is that these are temporary, receive-only inboxes. I would not use them for important accounts, production data, or anything that may require account recovery later.&lt;/p&gt;

&lt;p&gt;I am still refining my testing workflow, but for a new website or a small side project, keeping it simple has worked best for me.&lt;/p&gt;

&lt;p&gt;How do you manage test emails in your projects? Do you prefer temporary inboxes, local email tools, or dedicated test accounts?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>testing</category>
      <category>anonymous</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
