Spam folder from gmail not listed #99
Labels
No Label
IMAP
JMAP
Maildir
Retired
User Experience
User Interface
bsd
bug
contacts
currently worked on
documentation
duplicate
easy
enhancement
help wanted
invalid
linux-gnu
macos
mbox
notmuch
question
security
wishlist
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: meli/meli#99
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
This spam folder is listed in log, but it's not displayed in UI.
I have other gmail-based accounts (from G Suite, with custom domain) and they have the spam folder listed, and in status tab it's set as special Junk folder. The same isn't happening for this other pure gmail account.
#imap
I'm gonna need some help with this, what is the
LIST
response?Can you provide a complete session log just for this account (start meli till imap connects, then exit)? You can email it to me since it's sensitive data.
Ok, so the spam folder is missing from the LSUB reply. That's probably it then. Was the LSUB reply in the original post from another server?
Not sure about the question. All I can say is that the entire log was generated with just one single account set up, the problematic one, and I sent the log to you through that account too.
FWIW, one strange thing happened. The mail has the trace.log of ~5MB. After sending, I tried to open the email in meli, then when I tried to take a look at the 5MB text attachment by typing
<number>a
, meli hanged and the memory usage went up to 9GB until I force killed it.In the log the Spam folder is not subscribed (hence why it doesn't show up). This problem turns up a lot, I'll try to do something about this!
Got that error as well, and found out the cause 👍 there was gratuitous allocation dependent on the text width. The log file had some long lines.
Closing in favour of https://git.meli.delivery/meli/meli/issues/73