Skip to content

EP Email Inbox

EP Email Inbox polls an IMAP mailbox and handles incoming email with AI. Useful for first-line support where most questions can be answered by an AI given your site context, and the remainder are routed to a human.

Published by ElmsPark Studio.

How it runs:

  1. IMAP polling against your support mailbox (e.g. [email protected]) on a configurable interval.
  2. For each new message, the plugin reads the sender, subject, and body.
  3. The message is sent to your configured AI provider with that mailbox’s instructions (its system prompt), and the AI drafts a reply.
  4. If your mail server verified the sender, the reply goes out through the mailbox’s own mail server (SMTP).
  5. If it could not verify the sender, the draft is emailed to you through EP Email instead, for you to check and send yourself.
  6. Mailing lists, bounces and automatic replies are skipped and never answered.

Every message, auto-replied or flagged, is logged with full transcript so you can audit what the AI did.

  • “What are your opening hours?” — context says so.
  • “How do I reset my password?” — standard instruction.
  • “Is feature X included in the Pro plan?” — pricing/features are site context.
  • “My download link expired, can I have another?” — plugin can check orders and send a new link.
  • Complaints. Always route to humans.
  • Legal questions. Always route to humans.
  • Technical questions specific to the customer’s setup. AI guesses; a human can check the actual server.
  • Anything where the customer is upset. The AI handles routine enquiries; emotion needs a person.
  • PageMotor 0.8.2b or later
  • EP Email (required)
  • EP Suite base class
  • An IMAP mailbox (your support email account)
  • An LLM provider API key (Anthropic, OpenAI, or any supported)
  • PHP IMAP extension installed on your server
  1. Install EP Email first.
  2. Download ep-email-inbox.zip from the EP Suite downloads page.
  3. Upload via Plugins → Manage Plugins. Activate.
  4. Open Plugin Settings → EP Email Inbox.
  • Server. IMAP host (e.g. imap.fastmail.com).
  • Port. 993 for SSL.
  • Username / Password. Mailbox credentials.
  • Mailbox folder. Usually INBOX.
  • Poll interval. 5, 15, 30, or 60 minutes.
  • Provider. Anthropic, OpenAI, etc.
  • API key. Provider credential.
  • Model. Pick one that balances quality and cost.
  • Confidence threshold. If the AI’s self-reported confidence is below this, flag for human instead of auto-replying. Default 80%.
  • Signature. Text appended to every auto-reply.
  • Always flag these keywords. Comma-separated. Messages containing any keyword are always routed to a human regardless of AI confidence. Good for “refund”, “complaint”, “urgent”, “lawyer”.
  • Site description. A paragraph about what your site does.
  • Product/service list. What you sell, with prices if relevant.
  • FAQ context. Paste your FAQs. The AI uses this to answer routine questions.
  • Brand voice. Tone guidance, e.g. “Friendly but professional. No emojis. Sign off with ‘Best, the team.’” The plugin’s default system prompt instructs the AI to match the customer’s English variant (preserves British, American, Australian, etc. — does not force a regional spelling). Override that default in this field if you want to force one variant.

Lists every message the plugin has processed:

  • Auto-replied (AI handled it; reply shown).
  • Flagged (awaiting human; AI’s reasoning shown).
  • Failed (error during processing).

For flagged messages, you can click Draft reply to generate a suggested reply the same way EP Email AI Reply does, or write your own. Either way, sending goes through EP Email.

Every AI interaction is logged:

  • Original message.
  • AI’s proposed reply.
  • Confidence score.
  • Whether auto-reply was sent or flagged.
  • Cost of the LLM call (for API-billed providers).

Logs are retained for 90 days by default.

Check:

  • Host and port are correct.
  • Username is the full email address.
  • App-specific password if your mail provider requires one (Gmail, Fastmail).
  • PHP IMAP extension installed (phpinfo() should list IMAP).

“Plugin polls but no messages are being processed”

Section titled ““Plugin polls but no messages are being processed””

Check the poll log on the settings page. If it shows “No new messages”, the mailbox is empty (or all messages are already marked as seen). IMAP polling only picks up new unseen messages.

“Auto-replies are going to the wrong people”

Section titled ““Auto-replies are going to the wrong people””

The plugin replies to the Reply-To header if present, otherwise the From. If someone emailed you from an alias, replies might go to the alias unless their mail system rewrites. Test with a colleague first.

“AI is confidently wrong about my products”

Section titled ““AI is confidently wrong about my products””

Tighten the site description and FAQ context. The AI only knows what you tell it. More context = fewer wrong answers. Also lower the confidence threshold to flag more messages for human review.

Rewrite the brand voice setting. “Friendly but professional” is generic. Be specific: “Reply in plain English. Short paragraphs. One clear answer per paragraph. No buzzwords.”

Switch to a smaller model (Haiku vs Opus). Or raise the poll interval to reduce frequency. Or add more keywords to the always-flag list so only straightforward messages hit the AI.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.

A security update. Please install it.

  • Unverified privacy@ mail is not acted on. A message to a privacy or data-protection mailbox from a sender whose address cannot be verified no longer files a data request or looks up what you hold; the reply points them to your request form.
  • Sender checks are stricter. A mailbox whose server does not report its own checks never learns a mail server automatically (set it by hand), and a hand-set server is believed only on the topmost check header.

A security update. Please install it.

  • Your AI bill has a ceiling. Someone sending many emails to a monitored mailbox from an address its mail server could not check could make the plugin call your AI service for every one of them. Now an unchecked address gets at most two AI drafts a day, and each mailbox at most three times its hourly reply limit in AI calls an hour. Everything past that is kept as skipped, so you still see it.
  • Attachments are read. Images, PDFs and other files sent with an email are now noticed, at any depth in the message, and the AI is told what was attached. Links in the email are picked out too.
  • Keep attachments if you want them. A mailbox option saves its image and PDF attachments safely on your site. Off by default.
  • Sort each email. Add "classify": true to a mailbox and each email is sorted as a new advert, an approval, a change request, a question or something else, with the requested changes listed. Recent Activity shows the result. This is one extra AI call per email.
  • Client approvals are now checked more carefully.
  • Replies about a job can use its details. Your site can give a conversation trusted facts, such as the page’s version and when it goes live, so the AI can state them instead of having the reply held for you.
  • Mail can arrive at once. A mailbox can now take mail pushed to it instead of waiting for the next check, with the delivery authenticated.
  • Add and remove mailboxes without editing code. The settings screen has a form to add a mailbox and buttons to switch one off or remove it. Click Save Settings as before. Removing a mailbox now also deletes its stored password.
  • Replies now carry their own message ID, so a customer’s answer joins the right conversation more reliably.
  • An email in an older character set (such as Latin-1) is now stored correctly. Before, it could stop that mailbox at the same message on every check.
  • For developers: other plugins can now be told about accepted emails and can attach a conversation to their own job. Details are on this plugin’s documentation page.
  • Needs PageMotor 0.11.5 or later.
  • Replies come back if your site still had an old Claude model saved. Claude Sonnet 4 was switched off in June. A site with it typed into Model could not answer any email. A Claude 3 or 4 model now runs as its Claude 5.5 successor, so replies work again with nothing to change.
  • Claude Haiku 5.5 now answers quickly too, with the same light effort setting as Sonnet.
  • Needs PageMotor 0.11.5 or later.
  • A busy AI service no longer leaves an email unanswered. Until now, if Claude or OpenAI was overloaded, limiting requests or having a brief fault when a message was checked, that message was marked as failed and never got a reply. EP Email Inbox now tries again by itself, up to three tries in all, waiting as long as the service asks (up to 15 seconds).
  • An account that is out of credit, a wrong key or an email too long for the model is not retried, and still shows as failed under Recent Activity as before.
  • Nothing to do after updating.
  • Automatic mail such as newsletters, mailing lists, bounces and no-reply senders is never answered, and Recent Activity shows the reason under each skipped, held or failed message.
  • No-reply senders are recognised in more forms, such as shop.noreply@, no-reply-orders@, do_not_reply@ and bounces+tag@.
  • The AI states only what your instructions say. A reply that goes beyond them, such as quoting prices or offers you have not given, comes to you for review instead of being sent.
  • The AI never claims to be a person. A reply that does so is held for you, and replies always go out from the mailbox’s own address and name.
  • AI replies are now checked before sending, and any that cannot be sent show as failed with the reason.
  • Data from EP GDPR on a privacy@ mailbox is now treated as your information, not as part of the sender’s email.
  • Choose your mailbox’s outgoing mail server. Replies go out through the mailbox’s own SMTP server, which the plugin used to guess from the IMAP address (imap. changed to smtp., port 465). If yours is different, add "smtp_host", "smtp_port" and "smtp_encryption" to the mailbox: "ssl" for a secure connection from the start, or "tls" for STARTTLS on port 587. Mailboxes without them work exactly as before.
  • Clearer errors when sending fails. If the mail server refuses the login, or will not secure the connection, the plugin stops there and logs why. Your password is never sent over an unencrypted connection.
  • "validate_cert": false now applies to sending as well as reading mail, for a server with a self-signed certificate.
  • Microsoft 365 and Outlook.com mailboxes. Microsoft no longer accepts a password for reading mail over IMAP and requires its own sign-in method (OAuth), which EP Email Inbox does not support yet. The Mailboxes panel now says so beside any Microsoft mailbox, instead of the mailbox failing quietly.
  • Automatic replies work again when the Model setting is blank. The default model, Claude Sonnet 4 (claude-sonnet-4-20250514), has been retired by Anthropic and no longer answers, so every reply failed and the Recent Activity list showed “AI API call failed”. The default is now Claude Sonnet 5.5 (claude-sonnet-5-5).
  • If you typed a model into the Model setting yourself, it is still used. If you typed claude-sonnet-4-20250514, clear the field or change it to claude-sonnet-5-5.
  • Replies from current Claude models are read correctly. These models can return their reasoning before the reply, and the plugin could mistake that for an empty answer.
  • Replies are kept quick, and long ones are no longer cut short.
  • Drafts now reach you. When the AI holds a reply because the sender could not be verified, the draft is emailed to you through EP Email, as 1.1.10 intended. Until now these drafts, and the emails telling you a mail server had been learned or forgotten, were never sent. The Recent Activity list showed “draft not sent”.
  • Replies to your customers still go out through each mailbox’s own mail server, as they always have. They now also carry the headers that thread them under the customer’s message and mark them as automatic replies.
  • A privacy mailbox no longer stops the inbox when EP GDPR hits an error. The AI replies without the data summary, and the other mailboxes carry on.
  • Requests such as “please delete my data”, “erase”, “rectify” or “stop processing” are now recorded in EP GDPR as the right type. Before, many of them were recorded as access requests.
  • Visiting the admin login screen while signed out no longer starts a mailbox check. Checks on admin page loads now need a signed-in admin.
  • Sender Check now sets itself up and emails you when it is ready. Until then, drafts come to you as before.
  • Sender Check updates itself and emails you if your mail provider changes.
  • A mailbox’s "auth_server", if you have set one, is still used instead. A new Sender Check choice, Manual, turns learning off and uses only "auth_server".
  • Sender verification understands the form Microsoft writes. Microsoft’s mail servers write their checks without a server name. The Mailboxes panel now shows these as “untagged”, and "auth_server": "untagged" trusts them. (Microsoft 365 and Outlook.com mailboxes themselves cannot be read by this plugin: see 1.1.15.)
  • Tightens security on automatic replies. Anything not sent automatically is emailed to you as a draft.
  • Links written as bare domain names (for example “example.com/pay”) are now filtered like full links.
  • Automatic replies are now limited per sender. New setting: Max Replies per Sender per Day.
  • Automatic replies skip messages that should not be answered, and log them instead.
  • Replies are marked as automatic. Each reply now carries the standard “auto-replied” marker and threads under the customer’s message, so well-behaved mail systems at the other end do not answer it back. Replies go out through the mailbox’s own mail server, which passes the marker on.
  • A failed send is no longer recorded as replied.
  • Data protection requests now include the inbox. EP GDPR’s export now lists every message stored for a person, and erasure deletes them. Messages in the mailbox on your mail server are not touched.
  • Your API key and mailbox passwords are now stored more securely, automatically after the update. Nothing to re-enter. In the Mailboxes box a saved password is shown masked; leave it as it is to keep it, or type a new one to change it.
  • Tightens security of the connection to your mail server. If yours uses a self-signed certificate, see the documentation page for the mailbox option to allow it.
  • Switching the plugin off now stops the external cron too. Before, “off” only stopped checks on admin page loads, so a server cron kept replying.
  • Replies no longer go out under another business’s name. A mailbox with no From Name replied under a name left over from another site. It now uses EP Email’s From Name, or your site title.
  • A conversation can no longer be pulled in by someone outside it. A message that claimed to belong to another customer’s conversation (by quoting its message ID) got that conversation fed to the AI. Now a message only joins a conversation the sender is already part of.
  • Stronger protection against misuse of the AI by incoming email.
  • New optional setting, Only Reply To. List addresses or @domains, one per line, and the AI will only answer those, plus people it has answered before. Everyone else is logged for you to deal with. Leave it blank to keep answering everyone.
  • Two checks can no longer reply to the same email twice. If an admin page load and the external cron ran at the same moment, both could answer one message. Only one check now runs at a time.
  • Added a more secure option for scheduled runs from outside the site. Your existing setup keeps working.
  • Data protection requests that arrive by email at a privacy mailbox are now logged in EP GDPR as unconfirmed (EP GDPR 1.1.49).
  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • The Docs link on the Plugins screen now opens this plugin’s page on documentation.elmspark.com.
  • Removes a function call that PHP 8.5 reports as deprecated, so it no longer fills your error log.
  • Fixes “Your session has expired. Please reload to ensure your security.” on PageMotor 0.11. The message appeared on this plugin’s admin screens even though you were signed in perfectly normally, and whatever you were doing failed to save.
  • Nothing was wrong with your session. PageMotor 0.11 started handling part of the security check that this plugin was already handling itself, and the two together made every save look invalid. The plugin now checks whether PageMotor has already done it.
  • Visitors who were not signed in were never affected, on any version.
  • There is nothing to reconfigure, and nothing else changed.