Getting WARN messages "missing required UNSEEN OK untagged response" on every open

[pashynskykh]

=== INFO ===
Device: MacBook Air M1
OS: MacOS 15.2
Installed from: Brew
App version: v1.1.0 aarch64

=== CONFIG ===

[accounts.AccountName]
default = true
email = "[email protected]"
display-name = "John Doe"
downloads-dir = "/Users/jdoe/Downloads"
backend.type = "imap"
backend.host = "example.com"
backend.port = 993
backend.login = "jdoe"
backend.encryption.type = "tls"
backend.auth.type = "password"
backend.auth.command = "pass show example.com/jdoe/password"
message.send.backend.type = "smtp"
message.send.backend.host = "example.com"
message.send.backend.port = 465
message.send.backend.login = "jdoe"
message.send.backend.encryption.type = "tls"
message.send.backend.auth.type = "password"
message.send.backend.auth.command = "pass show example.com/jdoe/password"

=== WARNING MESSAGES ===

2025-01-28T12:33:30.039208Z WARN imap_client::tasks::resolver: received unsolicited unsolicited=Status(Untagged(StatusBody { kind: Ok, code: Some(Other(CodeOther(b"HIGHESTMODSEQ 19"))), text: Text("Highest") }))
2025-01-28T12:33:30.040916Z WARN imap_client::tasks::tasks::select: missing required UNSEEN OK untagged response

=== SCREENSHOT ===

[pashynskykh]

I just found #522.

I don't think it's okay to show anything but critical errors by default. This was my first time using the application and I thought something was not working right before checking the full log and making sure it was not a problem.

These non-critical warnings could not only mislead the average user into thinking the application is not working properly, but could also clutter the terminal with information you don't want to see and make it harder to use the output via pipes or even in scripts.

I would suggest showing only critical errors by default. If someone wants to see application logs, it would still be possible to set a log level using the variable or add the --debug option.

Please note that this is my personal opinion. I could be wrong.

[soywod]

Thank you for your point. I would argue that showing warnings is not the real issue for me. As someone pointed in the chat, warnings should be errors that can be fixed by the users (and I totally agree with that statement), instead the warning we actually get from the IMAP lib should be a simple debug log. Let's keep this issue open for the following purpose.