<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mxroute on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/mxroute/</link><description>Recent content in Mxroute on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Fri, 02 Oct 2026 08:00:00 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/mxroute/index.xml" rel="self" type="application/rss+xml"/><item><title>Sieve :copy dies: rebuild the reply copy in the IMAP poller</title><link>https://startaitools.com/posts/moved-the-reply-loop-in-app-when-sieve-died/</link><pubDate>Fri, 02 Oct 2026 08:00:00 -0600</pubDate><guid>https://startaitools.com/posts/moved-the-reply-loop-in-app-when-sieve-died/</guid><description>&lt;p&gt;MXroute disabled the Sieve &lt;code&gt;:copy&lt;/code&gt; redirect on a shared mailbox in March 2024, without SRS, and stopped forwarding human replies to the owner. The shared mailbox kept receiving them. The runbook still said the copy rule was active. Two years later, the owner noticed.&lt;/p&gt;
&lt;p&gt;The cleanest fix was to stop trusting the runbook and rebuild the copy loop in the IMAP poller. The poller already had every inbound message indexed by Message-ID and review class. Adding a single job that re-emits the body to the owner only when a skip rule says it is safe, turned the poller into the loop&amp;rsquo;s source of truth. Five hundred ninety eight tests cover UIDVALIDITY reset, retries, and the uncertain-send reconcile.&lt;/p&gt;</description></item></channel></rss>