Clacks
LiveEmail Bridge for Legacy Accounts
"It's not about the message. It's about sending it."
— GNU Terry Pratchett
A Symfony-based application that bridges POP3 and IMAP email accounts to Gmail. Poll legacy email servers and securely forward messages straight through to your Gmail inbox—no storage, no delays, just seamless delivery with full filter and rule compatibility.
Key Features
- POP3 & IMAP Support
- Pure PHP socket-based polling with no ext-imap dependency
- Gmail API Integration
- Uses Gmail messages.import for native filter compatibility
- Secure Pass-Through
- Message content passes straight through to Gmail and is never stored
- Multi-Account Management
- Connect multiple legacy accounts to one or more Gmail destinations
- AdminLTE Dashboard
- Modern web UI for account management and monitoring
Tech Stack
Case study
- Problem
- Bring mail from older POP3 and IMAP accounts into Gmail so that Gmail’s own filters, labels and spam classification apply to it — as if it had arrived there directly.
- Our role
- We designed, built and operate it: the mail clients, the Gmail integration, the credential encryption, the scheduling and the paid plans.
- Constraints
- Every Gmail scope this needs is one Google classes as restricted, which brings a security review and a duty to justify each scope requested. And a service that touches people’s mail should keep as little of it as possible.
- Decisions
- Import rather than forward: messages go in through Gmail’s messages.import, so filters and spam classification run as normal. Request five narrow scopes, and deliberately not gmail.readonly — the application never reads an existing Gmail message. Keep no message content: mail is fetched and imported in one pass, and only metadata — sender, subject, date and the identifiers that prevent duplicate imports — is retained, then purged on a retention schedule. Write the POP3 and IMAP clients over plain sockets rather than depend on PHP’s IMAP extension. Encrypt the secrets that must be stored, such as mailbox passwords and Gmail refresh tokens, under a key-encryption key.
- Trade-off
- Importing needs restricted scopes, and restricted scopes bring Google’s review. Forwarding would have avoided both — and broken the filters and labels that were the point.
- Result
- A live service with free and paid plans, bridging POP3 and IMAP accounts into one or more Gmail inboxes.
- Evidence
- Each restricted scope is documented against the exact API calls that use it, and the codebase has been checked against Google’s CASA Tier 2 criteria ahead of formal assessment.