<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Email on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/email/</link><description>Recent content in Email on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 09 Apr 2026 22:22:51 -0500</lastBuildDate><atom:link href="https://startaitools.com/tags/email/index.xml" rel="self" type="application/rss+xml"/><item><title>Intent Mail: Full Email Platform in a Day — Gmail, Outlook, and a Rules Engine</title><link>https://startaitools.com/posts/intent-mail-full-platform-gmail-outlook-rules-engine/</link><pubDate>Tue, 23 Dec 2025 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/intent-mail-full-platform-gmail-outlook-rules-engine/</guid><description>&lt;p&gt;35 commits in one repo. By the end of December 23rd, intent-mail was a working email platform with two provider connectors, full-text search, threaded send, attachment support, and a rules engine that could automate triage without touching the inbox until you said go.&lt;/p&gt;
&lt;h2 id="the-storage-layer-sqlite--fts5"&gt;The Storage Layer: SQLite + FTS5&lt;/h2&gt;
&lt;p&gt;Email data has two access patterns: exact lookup (give me this thread) and fuzzy search (find all emails about the deployment incident). SQLite handles the first pattern natively. FTS5 — SQLite&amp;rsquo;s full-text search extension — handles the second.&lt;/p&gt;</description></item><item><title>HustleStats Production Auth Meltdown: NextAuth, PrismaAdapter, and the Cascade That Blocked Every User</title><link>https://startaitools.com/posts/hustlestats-production-auth-debugging-nextauth-prisma/</link><pubDate>Tue, 21 Oct 2025 10:00:00 -0500</pubDate><guid>https://startaitools.com/posts/hustlestats-production-auth-debugging-nextauth-prisma/</guid><description>&lt;h2 id="the-customer-was-blocked"&gt;The Customer Was Blocked&lt;/h2&gt;
&lt;p&gt;A user tried to log into hustlestats.io and got a generic &amp;ldquo;Configuration&amp;rdquo; error. No stack trace. No useful message. Just a NextAuth error page with a single word.&lt;/p&gt;
&lt;p&gt;This was a paying customer on a custom domain. The app had been working in development. It had been working on the default Vercel URL. But on the production custom domain, login was completely dead.&lt;/p&gt;
&lt;p&gt;What followed was a 14-commit debugging marathon where every fix uncovered a new failure. The kind of session where you fix the auth, then registration breaks, then emails break, then the database schema is wrong, and you realize the entire deployment pipeline had been silently broken for days.&lt;/p&gt;</description></item></channel></rss>