Implemented
0
IMAP Trigger stops working after switching Email provider
Source: n8n-io/n8n#42206 · opened by @phred91
<!-- Please follow the template below. Skip the questions that are not relevant to you. --> Describe the problem/error/question I had a working Workflow that picked up emails for [email protected] which was hosted by AWS Workmail. As AWS is shutting this down, I successfully migrated this email account to Migadu. I changed the IMAP Trigger credentials from Workmail to Migadu and got a green tick suggesting a successful credential check. However, when new emails arrive in the Migadu account, they weren't being picked up by the Workflow. My understanding is that there is a UID sequence check and, if the new number is lower than the last recorded by the node, it won't fetch the email. By moving the account to a different provider, I assume the new UID numbers were lower. I fixed this by deleting the old node and adding a new one. My suggestion is to add an option to resent this counter or to somehow make it visible that the node has this logic. What is the error messa…
No pledges yet. Be the first to back this.
Comments
Similar requests
Email Trigger (IMAP): finds no emails on servers with broken IMAP4rev2 — please expose imapflow's disableIMAP4rev2
0 votes · 0 comments
Agent skill spec-driven-development has no path for creating a spec
0 votes · 0 comments
MCP tool calls fail in queue mode: `Tool node "<name>" does not have supplyData method` + `Worker tool execution timeout`
0 votes · 0 comments
Feature: cross-workflow agent memory — persistent verified memory for AI Agent nodes
0 votes · 0 comments
Next scheduled workflow is executed before previous workflow has finished
0 votes · 0 comments
No comments yet.