Describe the issue/error/question
IMAP Trigger can’t process the folder start with
&UXZO1mWHTvZZOQ-, it should be a string
其它文件夹 coded with
Python IMAP can connect to it as my wish.
I’m not sure whether this problem caused by mutil layers directories or the coding with utf7
What is the error message (if any)?
Please share the workflow
Share the output returned by the last node
ERROR: Folder not exist!
Error: Folder not exist!
at Connection._resTagged (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Connection.js:1502:11)
at Parser.<anonymous> (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Connection.js:194:10)
at Parser.emit (node:events:513:28)
at Parser.emit (node:domain:489:12)
at Parser._resTagged (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Parser.js:175:10)
at Parser._parse (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Parser.js:139:16)
at Parser._tryread (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Parser.js:82:15)
at TLSSocket.Parser._cbReadable (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Parser.js:53:12)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.emit (node:domain:489:12)
Information on your n8n setup
n8n version: 0.204.0
Database you’re using (default: SQLite): SQLite
- Running n8n with the execution process [own(default), main]:
Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
Hi @1itt1eB0y, I am sorry for the trouble. I tried reproducing this for a closer look, but my email service provider only accepts latin characters it seems
Perhaps you can use the Gmail node instead to fetch your emails?
Gmail won’t be my first choice due to GFW…
I will check if there is any way to solve this encoding problem.
I see. I’ll try to sign up for another email account in the next days and see if I can reproduce the problem using those.
In the meantime, perhaps you can consider creating an additional label using latin characters in your Gmail account which is then applied to your emails and can be used in the IMAP Email node? That way, you might be able to work around the problem as well.
I moved the target sender’s address to my
Other Directory and tagged them, to make them readable for IMAP Trigger, as an alternative solution for now.
My guess is that this is a en/decoding problem caused by the other underlying components of nodejs that n8n uses, not by the node design of n8n itself.
Anyway, thx for your reply.