Author Topic: It looks like I was wrong thinking it was a bug in Aquamail  (Read 2103 times)

StR

  • Hero Member
  • *****
  • Posts: 1558
It looks like I was wrong thinking it was a bug in Aquamail
« on: April 22, 2017, 12:26:43 am »
@Kostya:

I discovered some interesting fact that might be helpful to you.
I have a Thunderbird (running on a Win10 desktop) configured with the option: "Allow immediate server notifications when new messages arrive". I assume that's their option for enabling IDLE/Push notifications.
The IMAP server is dovecot v. 2.2.27.
There is some strangeness in the way notifications come under Win10, but I can conclusively report the following:
When I have several new messages, and read one of them in a different e-mail client (in my case it is either alpine or Aquamail, both connected to the IMAP server), I am getting a notification for the rest of the new and still unread messages.

A note of caution here: What is strange is that [at least in some cases] I am not always getting (within some reasonable time) a notification in Aquamail about these messages before I opened one of the new messages in alpine or Aquamail. My suspicion is that there might be some interference with Win10 posting notifications.

This, obviously, has nothing to do with Aquamail.
The reason I wrote it here, is that a few weeks ago there was a thread, where a part of the problem reported was sound notifications on Aquamail from the server when a message is read on a desktop client and Push and sound notifications were enabled in Aquamail. I suggested it was likely a bug in Aquamail.
While the situation I described here is not exactly the same, and there are other factors (such as Win10 that can mess up many things) involved, it shows that [at least] some IMAP servers trigger a notification when IDLE is enabled and one of the recent new messages changes status to read (from a different e-mail client). This doesn't happen when IDLE is disabled in the client (Thunderbird).
So, very likely I was wrong about assuming it was a bug in Aquamail. My apology.

Kostya Vasilyev

  • Hero Member
  • *****
  • Posts: 12742
Re: It looks like I was wrong thinking it was a bug in Aquamail
« Reply #1 on: April 23, 2017, 04:27:18 pm »
IMAP IDLE is *always* supposed to notify about message status (flags) changes.

I'd say that a bug in Thunderbird seems more likely than a bug in Dovecot.
Creating debug logs for diagnostics: https://www.aqua-mail.com/troubleshooting/

The official FAQ: https://www.aqua-mail.com/faq/

Лог-файлы для диагностики: https://www.aqua-mail.com/ru/troubleshooting/

Вопросы и ответы: https://www.aqua-mail.com/ru/faq/

StR

  • Hero Member
  • *****
  • Posts: 1558
Re: It looks like I was wrong thinking it was a bug in Aquamail
« Reply #2 on: April 24, 2017, 10:46:07 pm »
Yes, you are right..
Indeed, it is client's choice (and responsibility) which of the server notifications to show to the user.
Then I was wrong about being wrong before.  :(

 :o
« Last Edit: April 24, 2017, 10:48:04 pm by StR »

Kostya Vasilyev

  • Hero Member
  • *****
  • Posts: 12742
Re: It looks like I was wrong thinking it was a bug in Aquamail
« Reply #3 on: April 25, 2017, 08:48:48 pm »
Re: Indeed, it is client's choice (and responsibility) which of the server notifications to show to the user.

IMAP can send a "notification" about a change (triggered elsewhere, on another connection) at pretty inconvenient times.

These are called "unsolicited responses" in IMAP lingo, and handling them are a pain.
Creating debug logs for diagnostics: https://www.aqua-mail.com/troubleshooting/

The official FAQ: https://www.aqua-mail.com/faq/

Лог-файлы для диагностики: https://www.aqua-mail.com/ru/troubleshooting/

Вопросы и ответы: https://www.aqua-mail.com/ru/faq/