Your support mailbox as a channel: built, not verified with a real mailbox yet

Short version: Allinaa can connect a support mailbox, read what arrives and reply in the same e-mail thread, and this connection is built but not yet verified with a real mailbox. Everything below describes what the code does and has been tested against a simulated mail server, not a live service you can switch on today. The website chat and Telegram are the two channels that are live-verified.

Status, stated plainly

Part	Built	Verified with a real mailbox
Reading a mailbox over IMAP	Yes, against a simulated mail server	Not yet
Replying over SMTP in the same thread	Yes, against a real local mail server in tests	Not yet
Attachments from an e-mail stored as files	Yes	Not yet
Auto-reply loop protection	Yes	Not yet

If you need a mailbox answered today, the honest answer is to use the website chat and let the inquiry notifications arrive in your existing mailbox as they already do. This page exists so you know what is coming and how it will behave.

Why e-mail is harder than a chat channel

A chat message arrives once, from a person, in a thread the product owns. E-mail does none of those things. It arrives from mailing lists, from out-of-office replies, from delivery daemons, from forwarding rules and from other robots - and if an automatic answer is sent to any of those, two machines can end up writing to each other for ever. That failure has a name in the standards and a set of rules for avoiding it, and those rules are the bulk of the work in this connection.

What stops an automatic reply loop

Before any reply is sent, the incoming message is examined and left for a person rather than answered automatically when it looks like anything other than a human writing to you: when it carries an automatic-submission marker, when it has mailing-list headers, when it is marked bulk or junk, when it has no return path, when it is from a mail daemon, a postmaster or a no-reply address, or when it is from our own address. An AI reply also goes out at most once per sender per thread in a ten-minute window. Every one of those has a test behind it.

Threading, so a reply lands in the right conversation

Replies carry the standard reference headers, so your customer's mail client shows them in the same thread as their original message rather than as a new e-mail. The latest message id of the conversation is kept, which is what makes a second reply thread correctly too. AI-written replies are marked as automatically generated, which is both the polite convention and what stops other well-behaved mail systems from answering them.

What it does to your mailbox: nothing

The mailbox is opened read-only and messages are fetched without marking them as read, so your own team sees exactly what it would have seen. Nothing is moved, flagged or deleted, and no copy is placed in the Sent folder - your mailbox is a source, not a workspace the product takes over. Mail that arrived before the connection was made is never imported, so connecting it does not produce a flood of history.

How it will work when it is available

1. You create a mailbox or an app password for an existing one - on most hosts that is a few clicks in the mail control panel.
2. You connect it in the cabinet. Credentials are encrypted and never shown again, and the host is resolved and pinned so the connection cannot be redirected.
3. The mailbox is polled every couple of minutes, with at most a small batch per poll.
4. New connections start in human mode: messages are stored and your team is notified, and the AI answers nothing until you decide it should.

Limits worth knowing before you plan around it

• Polling, not instant. A couple of minutes, not a second. For e-mail that is invisible; it is mentioned because it is true.
• Forwarded mail waits for a person. When the return path and the sender disagree - which is what forwarding and some mailing tools do - the message is stored for a person rather than answered, and nobody is alerted specially. If most of your mail is forwarded, that is worth knowing.
• No read receipts. E-mail read receipts are optional and unreliable, so none are requested or reported.
• Attachments follow the file rules: type sniffed from the content, size and quota limits, malware checks, private storage and a retention schedule. See files customers send.
• Your host's own send limits apply, and they are not something the product can see.

One inbox, when it arrives

An e-mail conversation appears in the same place as the website chat and Telegram, with the same take-over, reply, note and assign actions, so your team does not learn a second tool. See one inbox and the channel overview for what is live today.