repository·main·Indexed 23 days ago
https://github.com/zeropointsix/outlookemailplusA specialized email management system optimized for high-frequency registration and verification workflows. It features an intelligent email pool with project isolation, automated verification code extraction via regex, and a Chrome/Edge browser extension to streamline the claim-extract-complete lifecycle. Supports Gmail, QQ, 163, custom IMAP servers, and Cloudflare Worker temporary emails, with integration for Telegram notifications and Microsoft OAuth token configuration.
The OAuth Token Acquisition Tool is a standalone utility within Outlook Email Plus designed to help users interactively log in to Microsoft accounts to obtain a refresh_token. It operates in a separate browser window (opened via window.open()) to avoid disrupting the main application's SPA state.
Key features include:
client_secret is disabled to support a compatible account import mode.Settings table, allowing for cross-device synchronization.Outlook Mail Plus is a specialized email account manager designed for individuals and teams focused on registration and verification workflows. Unlike general-purpose email clients, it optimizes for minimizing friction during sign-up processes.
Key Features:
The OutlookMail Plus browser extension (Manifest V3) is a companion tool for Chrome and Edge. It provides a lightweight popup interface to manage the entire email lifecycle without injecting code into web pages.
Core Capabilities:
Claim Email → Use → Get Verification Code/Link → Complete/Release.Prerequisites:
external pool enabled.pool_access permissions.This project implements a plugin architecture for temporary email providers. The system allows for dynamic registration, loading, and management of email providers via a registry and decorator pattern.
_REGISTRY to map provider names to their respective classes.@register_provider decorator.Route → Controller → Service → Repository pattern. Cross-layer calls are prohibited../plugins:/app/plugins for persistence)The project has undergone significant evolution from v1.x to v2.x. Key milestones include:
wait-message probing.The Browser Extension Quick Operation Panel (target version v0.1.0) is designed to achieve the following:
.crx packaging.The testing for the Compact Mode Auto-Polling feature is organized into three hierarchical layers. To ensure full coverage, follow this execution order: first run the Python tests (Layers A and B), then run the Jest tests (Layer C).
| Layer | File | Framework | Test Objective |
|---|---|---|---|
| A. Backend API Contract | tests/test_compact_poll_settings.py | Python unittest | Validates GET/PUT, field validation, defaults, and persistence for 3 settings fields. |
| B. Frontend Contract | tests/test_compact_poll_frontend_contract.py | Python unittest | Ensures existence of HTML elements, JS variables, CSS classes, and i18n entries. |
| C. JS Unit | tests/compact-poll/compact-poll-engine.test.js | Jest + jsdom | Tests core polling engine logic (event triggering, re-entrancy prevention, timeouts, parallelism). |
The Data Overview Dashboard (replacing the old page-dashboard) uses a 5-Tab structure. It utilizes existing CSS classes (settings-tab-nav, settings-tab, settings-tab-pane) with a .ov-* prefix for specialized styling. The UI follows an 'Apple-style glass card' design with rounded panels, soft shadows, and custom hover notes instead of native browser tooltips.
Key Frontend Modules (static/js/features/overview.js):
initOverview(): Initializes tab switching and refresh button bindings.switchOverviewTab(tabId): Switches tabs and triggers lazy loading.loadOverviewTab(tabId): Orchestrates API requests and rendering for a specific tab.fetchOverviewData(tabId): Fetches data from /api/overview/* endpoints.renderDataCard(options): Renders glass-style data cards (title, badge, hover note, body).renderBarChart(container, data): Renders CSS-based bar charts (Tab 3).renderTimeline(container, events): Renders timeline items (Tab 5).Loading & Caching Strategy:
overview-data-changed event, which invalidates caches for summary, verification, and activity. If the overview page is currently visible, it triggers an immediate reload.Issue #55 refers to supporting the batch fetching of emails after selecting multiple accounts in Standard Mode.
Key Technical Context:
account-select-checkbox (rendered in static/js/features/groups.js), selectedAccountIds (maintained in static/js/main.js), and the batchActionBar (in templates/index.html).static/js/features/accounts.js uses currentAccount to drive the email pane, and static/js/features/emails.js uses loadEmails(email, forceRefresh) to fetch for a single address via the /api/emails/<email_addr> endpoint.Implementation Strategy: Instead of refactoring the entire browsing model into a mixed multi-account list, the recommended approach is to enhance the Standard Mode batch actions to:
batchActionBar.selectedAccountIds and existing batch interaction patterns.The system uses a mailbox_resolver to abstract the difference between standard accounts (Outlook/IMAP) and temporary mailboxes. Instead of relying solely on the accounts table, the reading logic uses a mailbox descriptor to determine how to fetch messages.
A mailbox descriptor follows this structure:
{
"kind": "account | temp",
"email": "demo@example.com",
"source": "outlook | imap | custom_temp",
"status": "active",
"read_capability": "graph | imap | temp_provider",
"meta": {}
}Reading Workflow:
mailbox_resolver.resolve_mailbox(email_addr).kind == account: Use existing graph or imap flows.kind == temp: Use the temp_mail_service reading flow.