Implemented
0
Email Trigger (IMAP): finds no emails on servers with broken IMAP4rev2 — please expose imapflow's disableIMAP4rev2
Source: n8n-io/n8n#41344 · opened by @jensschoene
Bug Description Since n8n 2.x the Email Trigger (IMAP) uses imapflow (1.7.1 via @n8n/imap). imapflow sends ENABLE IMAP4rev2 whenever the server offers it. Strato's IMAP server (imap.strato.de, RZimapd) accepts this but then answers every SEARCH with an empty ESEARCH response, so the trigger never finds an email. The trigger is notified of new mail via IDLE, so the problem is easy to miss: no execution, no error, workflow shows as active. The debug log shows: Protocol trace with imapflow 1.7.1 (mailbox with 21 messages, 15 unseen): With disableIMAP4rev2: true the same server returns correct results (* SEARCH 169764 169792 …, 15 and 21 hits). The bug is on the server side (reported to Strato). But imapflow already ships the opt-out for this case: disableIMAP4rev2 is documented as a "targeted opt-out for servers with broken IMAP4rev2 implementations". n8n just doesn't expose it. To Reproduce 1. Create an IMAP credential for a Strato mailbox (imap.strato.de:…
No pledges yet. Be the first to back this.
Comments
Similar requests
IMAP Trigger stops working after switching Email provider
0 votes · 0 comments
Anthropic Chat Model: expose "strict": true for client tool definitions
0 votes · 0 comments
Feature request: Expose stop execution in Instance-level MCP
0 votes · 0 comments
Dynamic Multi-Action AI Tool Nodes (Unified Tool Definition for AI Agents)
0 votes · 0 comments
Feature Suggestion: Optional token metering & paid API key support via `neuforge-pay`
0 votes · 0 comments
No comments yet.