Bug: WILDDUCK [Exception] APPEND not allowed now

[titanism]

It appears that WildDuck has issues due to invalid state on a valid APPEND (post AUTH):

5|imap-993  | {
5|imap-993  |   short_message: 'WILDDUCK [Exception] APPEND not allowed now',
5|imap-993  |   full_message: 'Error: APPEND not allowed now\n' +
5|imap-993  |     '    at IMAPCommand.validateCommand (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-command.js:387:23)\n' +
5|imap-993  |     '    at /var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-command.js:296:18\n' +
5|imap-993  |     '    at IMAPCommand.append (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-command.js:201:9)\n' +
5|imap-993  |     '    at IMAPCommand.end (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-command.js:213:14)\n' +
5|imap-993  |     '    at IMAPConnection._onCommand (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-connection.js:517:28)\n' +
5|imap-993  |     '    at IMAPStream._readValue (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-stream.js:149:14)\n' +
5|imap-993  |     '    at Object.readyCallback (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-stream.js:130:33)\n' +
5|imap-993  |     '    at PassThrough.<anonymous> (/var/www/production/source/node_modules/.pnpm/[email protected]/node_modules/wildduck/imap-core/lib/imap-command.js:197:25)\n' +
5|imap-993  |     '    at PassThrough.emit (node:events:517:28)\n' +
5|imap-993  |     '    at endReadableNT (node:internal/streams/readable:1400:12)\n' +
5|imap-993  |     '    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)',
5|imap-993  |   _exception: 'yes',
5|imap-993  |   _error: 'APPEND not allowed now',
5|imap-993  |   _responseCode: '500',
5|imap-993  |   _code: 'InvalidState',
5|imap-993  |   _payload: '62 append "Sent Mail" (\\Seen) UTF8 ("(* 580388B literal *)")',
5|imap-993  |   _userId: 'xxxxxxxxxxxxxx',
5|imap-993  |   _sess: 'xxxxxxxxxxxxxx',
5|imap-993  |   _remoteAddress: 'xxxxxxxxxxxxxx',
5|imap-993  |   _isUTF8Enabled: 'true',
5|imap-993  |   facility: 'wildduck',
5|imap-993  |   host: 'imap.forwardemail.net',
5|imap-993  |   timestamp: 1730193761.904,
5|imap-993  |   _component: 'wildduck'
5|imap-993  | }

Still trying to determine underlying culprit, if you have any thoughts let us know 🙏

[titanism]

Perhaps the code is running too quickly, and we need to wrap similarly with setImmediate calls as WildDuck does.

[titanism]

If you have any thoughts @andris9 let us know!

[titanism]

In one example, the handler state is Selected and the connection's state is Authenticated. The parsed command is { tag: '5', command: 'unselect' } which results in WILDDUCK [Exception] UNSELECT not allowed now.

[titanism]

Another example is from the client name com.google.android.gm (Samsung Android) whereby handler state is [ 'Authenticated', 'Selected' ] and the connection's state is Not Authenticated, which seems like a client bug (e.g. _payload value is '5 CREATE "Sent"') which results in WILDDUCK [Exception] CREATE not allowed now.

[titanism]

Another one (while using Thunderbird): CLOSE not allowed now

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 15 days.

[titanism]

@andris9 can you mark as open so it doesn't go stale?