#133 Error after login: No such mailbox 23 days ago

Ticket created by ~foxcpp on ~migadu/alps

failed to get mailbox status: No such mailbox

This error message appears just after logging in. Relevant debug log fragment:

alps[60990]: 2020-11-02T17:36:22Z method=POST, uri=/login, status=302
alps[60990]: GBzvyA LIST "" "*"
alps[60990]: * LIST (\Archive \HasNoChildren) "." "Archive"
alps[60990]: * LIST (\Drafts \HasNoChildren) "." "Drafts"
alps[60990]: * LIST (\HasNoChildren) "." INBOX
alps[60990]: * LIST (\Junk \HasNoChildren) "." "Junk"
alps[60990]: * LIST (\Sent \HasNoChildren) "." "Sent"
alps[60990]: * LIST (\Trash \HasNoChildren) "." "Trash"
alps[60990]: GBzvyA OK LIST completed
alps[60990]: ubQ8UQ STATUS INBOX (MESSAGES UIDVALIDITY UNSEEN)
alps[60990]: * STATUS INBOX (UNSEEN 0 MESSAGES 46 UIDVALIDITY 1540840298)
alps[60990]: ubQ8UQ OK STATUS completed
alps[60990]: 0pAXQQ STATUS "Outbox" (MESSAGES UIDVALIDITY UNSEEN)
alps[60990]: 0pAXQQ NO No such mailbox
alps[60990]: 2020-11-02T17:36:22Z ERROR failed to get mailbox status: No such mailbox

Looks like alps assumes Outbox mailbox exists and tries to query its status even if it doesn't actually exist.

#64 panic on BouncerServ command with subcommands but no handler 6 months ago

Ticket created by ~foxcpp on ~emersion/soju

e.g. /msg BouncerServ network

I think the default meaningful behavior is to send the list of subcommands if any.

#47 Support SASL External method 6 months ago

Comment by ~foxcpp on ~emersion/soju

On the second thought, I think generating a certificate by soju is more clean. Ability to add an existing key is not really important - you can connect to the network directly and add the fingerprint to list using any other means.

#335 Inconsistent time display 11 months ago

Comment by ~foxcpp on ~sircmpwn/aerc2

It also might be a good idea to use the same timestamp format (as specified by timestamp-format). For example, I prefer 24-hour time.

#269 EOF Error 11 months ago

Comment by ~foxcpp on ~sircmpwn/aerc2

  1. aerc specifies the literal length smaller than the actual length of the message (?)

Pardon, I meant "larger".

#269 EOF Error 11 months ago

Comment by ~foxcpp on ~sircmpwn/aerc2

https://github.com/emersion/go-imap/issues/311#issuecomment-560037069 https://github.com/emersion/go-imap/issues/311#issuecomment-560042828

My guess of what happens here:

  1. aerc specifies the literal length smaller than the actual length of the message (?)
  2. go-imap sends the truncated literal and then fails, not sending the terminating CRLF
  3. aerc then proceeds to send another IMAP command, here is how the connection stream will look like:
{6}MMMMMMNNNNTAG commandCRLF
        ^~~~~~~~~~~~~~~~

As viewed by the server, the literal last octet is at the ^ sign, but the actual command ends at CRLF, everything in between (NNNNN and the next command) and is unexpected garbage, the server reports it:

eGiEog BAD junk after literal

I created a PR in go-imap that makes Append return a more useful error in this case and then close the connection. If somebody can reproduce this problem with it, the error will confirm my guess above (and also provide some context for further troubleshooting).

To use my PR with aerc, append the following line to the go.mod file in the repo root:

replace github.com/emersion/go-imap => github.com/foxcpp/go-imap append-eof