Create an app password
Use a dedicated app password from an IMAP provider that still permits password-based IMAP access. Never enter your normal mailbox password.
IMAP inbox → text parser → review
Turn authorized signal emails into reviewable trade data.
Monitor a dedicated IMAP inbox, filter new mail by sender or subject, and parse plain-text signal fields into a pending record. Nothing from Email executes blindly—you review it first.
Pro or Lifetime · app-password IMAP only · review required · demo first
Email intake reality
Current production path
AuthenticationIMAP app password
CollectionAbout once/minute
ContentPlain-text email body
FiltersSender and/or subject
ResultPending for approval
Not Microsoft OAuth. Not attachment OCR. Not blind execution.
Setup workflow
Connect carefully, filter tightly, verify on demo
Connect the inbox
Enter the IMAP hostname, secure port, mailbox username, and app password in Email Signals.
Restrict the source
Optionally require a sender-address match, a subject-text match, or both to reduce unrelated mail.
Send a text signal
New inbox messages are checked approximately once per minute. The worker extracts the plain-text body and runs the standard parser.
Review before execution
Email signals are created as pending records. Confirm every field and approve the signal only after testing the destination on demo.
What works now
- Secure IMAP over port 993 or another configured secure port
- AES-256-GCM encryption for the stored app password
- Optional sender and subject filters
- Text parsing for direction, symbol, entry, SL, and up to 10 supported targets
- Pending signal creation for manual review and approval
- Last-polled visibility on each configured inbox
What is limited
- No Microsoft or Google OAuth flow; the mailbox must permit app-password IMAP authentication
- No attachment, PDF, or screenshot extraction in the current worker
- No HTML-layout guarantee; use a clear text body for the signal
- No blind auto-execution from inbox messages; every record starts pending
- Approximately one-minute polling, not instant push delivery
- The exact destination lifecycle still depends on the selected execution route
Use a dedicated mailbox
Create a mailbox used only for authorized signal intake, enable multi-factor authentication, generate a dedicated app password, apply strict sender and subject filters, and rotate the credential if exposure is suspected.
Email is the source—not the broker route
Email creates a parsed pending record. After review, execution support depends on the destination you configured and its current capabilities. Check the route matrix before testing any management command.
Before connecting
Email Signal Copier FAQ
Does it trade every email automatically?
No. The current Email route creates a pending signal for review. It does not blind-execute inbox messages.
How fast is Email intake?
The persistent worker checks enabled inboxes approximately once per minute. Provider latency and mailbox connection time can add delay.
Can it read attachments or screenshots?
No. The current worker parses the email's text body. Do not rely on PDF, image, or attachment-only signals.
Does it support Microsoft 365 OAuth?
Not today. The connector currently uses IMAP username and app-password authentication, not Microsoft OAuth. Verify that your provider permits this method before subscribing.
Which plan includes Email Signals?
Email intake is currently gated to Pro and Lifetime accounts.