search

pulb / mailnag

An extensible mail notification daemon
GNU General Public License v2.0
253 stars 32 forks source link

Mailnag stops checking for new mails after some time #186

Closed SandaruLJ closed 3 years ago

SandaruLJ commented 5 years ago

Mailnag sort of goes to sleep after some time and I have to restart mailnag daemon to get new mail notifications. But again after some time, it goes inactive.

pulb commented 5 years ago

What Mailnag version do you use?

pulb commented 5 years ago

And also please run journalctl -b _COMM=mailnag in a terminal and post the output here if the problem occurs.

SandaruLJ commented 5 years ago

What Mailnag version do you use?

1.3.0

And also please run journalctl -b _COMM=mailnag in a terminal and post the output here if the problem occurs.

-- Logs begin at Sat 2019-05-18 14:20:50 +0530, end at Sun 2019-05-19 14:55:24 +0530. --
May 19 11:19:37 lj-fedora mailnag[24338]: INFO (2019-05-19 11:19:37): Successfully enabled plugin 'soundplugin'.
May 19 11:19:37 lj-fedora mailnag[24338]: INFO (2019-05-19 11:19:37): Successfully enabled plugin 'dbusplugin'.
May 19 11:19:38 lj-fedora mailnag[24338]: INFO (2019-05-19 11:19:38): Successfully enabled plugin 'libnotifyplugin'.
May 19 11:19:38 lj-fedora mailnag[24338]: INFO (2019-05-19 11:19:38): Checking 3 email account(s).
May 19 11:22:33 lj-fedora mailnag[24338]: INFO (2019-05-19 11:22:33): Checking 1 email account(s).
May 19 11:23:05 lj-fedora mailnag[24338]: INFO (2019-05-19 11:23:05): Checking 1 email account(s).
May 19 11:26:07 lj-fedora mailnag[24338]: INFO (2019-05-19 11:26:07): Checking 1 email account(s).
May 19 11:26:18 lj-fedora mailnag[24338]: INFO (2019-05-19 11:26:18): Checking 1 email account(s).
May 19 11:29:47 lj-fedora mailnag[24338]: INFO (2019-05-19 11:29:47): Checking 1 email account(s).
May 19 11:39:49 lj-fedora mailnag[24338]: INFO (2019-05-19 11:39:49): Checking 1 email account(s).
May 19 11:49:50 lj-fedora mailnag[24338]: INFO (2019-05-19 11:49:50): Checking 1 email account(s).
May 19 11:59:52 lj-fedora mailnag[24338]: INFO (2019-05-19 11:59:51): Checking 1 email account(s).
May 19 12:09:53 lj-fedora mailnag[24338]: INFO (2019-05-19 12:09:53): Checking 1 email account(s).
May 19 12:19:55 lj-fedora mailnag[24338]: INFO (2019-05-19 12:19:55): Checking 1 email account(s).
May 19 12:29:56 lj-fedora mailnag[24338]: INFO (2019-05-19 12:29:56): Checking 1 email account(s).
May 19 12:39:57 lj-fedora mailnag[24338]: INFO (2019-05-19 12:39:57): Checking 1 email account(s).
May 19 12:49:59 lj-fedora mailnag[24338]: INFO (2019-05-19 12:49:59): Checking 1 email account(s).
May 19 13:00:01 lj-fedora mailnag[24338]: INFO (2019-05-19 13:00:01): Checking 1 email account(s).
May 19 13:10:02 lj-fedora mailnag[24338]: INFO (2019-05-19 13:10:02): Checking 1 email account(s).
May 19 13:20:04 lj-fedora mailnag[24338]: INFO (2019-05-19 13:20:04): Checking 1 email account(s).

Edit: I have configured 3 email accounts. I tried sending emails to each of them and Mailnag didn't notify about any of them.

Matthew-Wai commented 5 years ago

I have the same problem with Mailnag version 1.2.1-1.1 (the latest) on PPPoE connection on Mint 19.0. The following is extracted from /var/log/syslog. It started checking for new mail at 17:34:37 and stopped doing so (i.e. fell asleep) at 18:11:46, when an error arose. The same thing happens repeatedly, and I have to restart Mailnag repeatedly. Internet connection is definitely available when it falls asleep.

May 26 17:34:37 pc INFO (2019-05-26 17:34:37): Successfully enabled plugin 'userscriptplugin'.
May 26 17:34:37 pc INFO (2019-05-26 17:34:37): Successfully enabled plugin 'dbusplugin'.
May 26 17:34:37 pc INFO (2019-05-26 17:34:37): Successfully enabled plugin 'libnotifyplugin'.
May 26 17:34:37 pc INFO (2019-05-26 17:34:37): Checking 1 email account(s).
[...]
May 26 18:11:42 pc INFO (2019-05-26 18:11:42): Checking 1 email account(s).
May 26 18:11:46 pc ERROR (2019-05-26 18:11:46): Caught an exception.#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mailnagdaemon.py", line 214, in sync_func#012    self._mailchecker.check([account])#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mailchecker.py", line 58, in check#012    all_mails = self._mailsyncer.sync(accounts)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mails.py", line 279, in sync#012    rcv_lst = MailCollector(self._cfg, accounts).collect_mail(sort = False)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mails.py", line 80, in collect_mail#012    conn.select(folder, readonly = True)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/common/imaplib2.py", line 976, in select#012    typ, dat = rqb.get_response('command: %s => %%s' % rqb.name)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/common/imaplib2.py", line 173, in get_response#012    raise typ(exc_fmt % str(val))#012abort: command: EXAMINE => connection terminated
pulb commented 5 years ago

@SandaruLJ, @Matthew-Wai : Can you please post the contents of ~/.config/mailnag/mailnag.cfg?

Matthew-Wai commented 5 years ago

matthew@pc:~$ cat ~/.config/mailnag/mailnag.cfg [spamfilterplugin] filter_text = newsletter, viagra

[core] imap_idle_timeout = 10 enabled_plugins = dbusplugin, libnotifyplugin, userscriptplugin poll_interval = 10 credentialstore = auto connectivity_test = auto autostart = 0

[soundplugin] soundfile = mailnag.ogg

[libnotifyplugin] notification_mode = 3 max_visible_mails = 10

[account1] enabled = 1 name = 123456@yahoo.com (Yahoo) user = 123456@yahoo.com password = 123456 server = imap.mail.yahoo.com port = 993 ssl = 1 imap = 1 idle = 1 folder =

[userscriptplugin] script_file = /home/matthew/@/Mail notification

pulb commented 5 years ago

@Matthew-Wai: Your problem seems to be different from those others reported (connection terminated). Can you try the latest 1.3 release from the Ubuntu PPA?

Matthew-Wai commented 5 years ago

@ pulb, could you post the direct download link to the latest 1.3 release?

pulb commented 5 years ago

@Matthew-Wai: The best solution would be to add the mailnag PPA to your repository list, so you get future updates automatically:

sudo add-apt-repository ppa:pulb/mailnag sudo apt-get update sudo apt-get upgrade

If you just wand to install the package by hand, you can get it here: https://launchpad.net/~pulb/+archive/ubuntu/mailnag/+files/mailnag_1.3.0-0~ubuntu18.04.1_all.deb

pulb commented 5 years ago

@SandaruLJ: I can reproduce your problem

Matthew-Wai commented 5 years ago

@ pulb, I have installed "mailnag_1.3.0-0~ubuntu18.04.1_all.deb" and got the same problem. The following is extracted from /var/log/syslog. It started checking for new mail at 12:51:00 and got an error at 13:26:41, when Internet connection was definitely available.

May 31 12:51:00 pc INFO (2019-05-31 12:51:00): Checking 1 email account(s).
[...]
May 31 13:26:36 pc INFO (2019-05-31 13:26:36): Checking 1 email account(s).
May 31 13:26:41 pc ERROR (2019-05-31 13:26:41): Caught an exception.#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mailnagdaemon.py", line 208, in sync_func#012    self._mailchecker.check([account])#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mailchecker.py", line 58, in check#012    all_mails = self._mailsyncer.sync(accounts)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mails.py", line 219, in sync#012    rcv_lst = MailCollector(self._cfg, accounts).collect_mail(sort = False)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/daemon/mails.py", line 73, in collect_mail#012    for folder, msg in acc.list_messages():#012  File "/usr/lib/python2.7/dist-packages/Mailnag/backends/imap.py", line 88, in list_messages#012    conn.select(folder, readonly = True)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/common/imaplib2.py", line 976, in select#012    typ, dat = rqb.get_response('command: %s => %%s' % rqb.name)#012  File "/usr/lib/python2.7/dist-packages/Mailnag/common/imaplib2.py", line 173, in get_response#012    raise typ(exc_fmt % str(val))#012abort: command: EXAMINE => connection terminated
SandaruLJ commented 5 years ago

@SandaruLJ, @Matthew-Wai : Can you please post the contents of ~/.config/mailnag/mailnag.cfg?

[spamfilterplugin] filter_text = newsletter, viagra

[core] imap_idle_timeout = 10 enabled_plugins = dbusplugin, libnotifyplugin, soundplugin poll_interval = 10 credentialstore = auto connectivity_test = auto autostart = 1

[soundplugin] soundfile = mailnag.ogg

[libnotifyplugin] notification_mode = 3 max_visible_mails = 10

[account3] enabled = 1 type = imap name = @my.sliit.lk (Gmail) user = @my.sliit.lk password = *** server = imap.gmail.com port = 993 ssl = 1 imap = 1 idle = 1 folder = []

[account2] enabled = 1 type = imap name = @yandex.com user = password = *** server = imap.yandex.com port = 993 ssl = 1 imap = 1 idle = 1 folder = []

[account1] enabled = 1 type = imap name = @gmail.com (Gmail) user = @gmail.com password = *** server = imap.gmail.com port = 993 ssl = 1 imap = 1 idle = 1 folder = []

[userscriptplugin] script_file =

Matthew-Wai commented 5 years ago

Unexpectedly, Mailnag has been working properly today. So far, no error has arisen in the past three hours. See below:

matthew@pc:~$ awk '{print}' "/var/log/syslog"| grep "ERROR"
matthew@pc:~$ awk '{print}' "/var/log/syslog"| grep "email"
Jun  6 18:13:45 pc INFO (2019-06-06 18:13:45): Checking 1 email account(s).
Jun  6 18:23:50 pc INFO (2019-06-06 18:23:50): Checking 1 email account(s).
Jun  6 18:33:55 pc INFO (2019-06-06 18:33:55): Checking 1 email account(s).
Jun  6 18:44:00 pc INFO (2019-06-06 18:44:00): Checking 1 email account(s).
Jun  6 18:54:04 pc INFO (2019-06-06 18:54:04): Checking 1 email account(s).
Jun  6 19:04:09 pc INFO (2019-06-06 19:04:09): Checking 1 email account(s).
Jun  6 19:14:15 pc INFO (2019-06-06 19:14:15): Checking 1 email account(s).
Jun  6 19:24:20 pc INFO (2019-06-06 19:24:20): Checking 1 email account(s).
Jun  6 19:34:24 pc INFO (2019-06-06 19:34:24): Checking 1 email account(s).
Jun  6 19:44:29 pc INFO (2019-06-06 19:44:29): Checking 1 email account(s).
Jun  6 19:54:33 pc INFO (2019-06-06 19:54:33): Checking 1 email account(s).
Jun  6 20:04:38 pc INFO (2019-06-06 20:04:38): Checking 1 email account(s).
Jun  6 20:14:42 pc INFO (2019-06-06 20:14:42): Checking 1 email account(s).
Jun  6 20:24:47 pc INFO (2019-06-06 20:24:47): Checking 1 email account(s).
Jun  6 20:34:53 pc INFO (2019-06-06 20:34:53): Checking 1 email account(s).
Jun  6 20:44:58 pc INFO (2019-06-06 20:44:58): Checking 1 email account(s).
Jun  6 20:55:06 pc INFO (2019-06-06 20:55:06): Checking 1 email account(s).
Jun  6 21:05:11 pc INFO (2019-06-06 21:05:11): Checking 1 email account(s).
Jun  6 21:15:17 pc INFO (2019-06-06 21:15:17): Checking 1 email account(s).
glaubersm commented 5 years ago

I use mailnag 1.3 and mailnag gnome shell extension v3.32.1 on Arch Linux running Gnome 3.32.2. After I resume my system from suspend, apparently mailnag stops checking for new mails because Gnome Shell shows no notification about new emails until I reboot my system.

glaubersm commented 5 years ago

Notifications work again after I check for emails manually through the Gnome Shell extension.

Darthpenguin commented 4 years ago

I have this issue with mailnag 1.3.0 on Arch Linux. Is this due to some changes with something mailnag is dependent on or is it a glitch introduced in the latest version of mailing? In other words, could I downgrade the package to fix this issue?

pulb commented 4 years ago

@Matthew-Wai: mailnag has been ported to python3 recently and includes a newer implementation of imaplib2. Can you check out the latest code and see if the problem still persists?

Matthew-Wai commented 4 years ago

@pulb, I regret to inform you that I no longer use Mailnag.

SandaruLJ commented 4 years ago

@Matthew-Wai: mailnag has been ported to python3 recently and includes a newer implementation of imaplib2. Can you check out the latest code and see if the problem still persists?

It still persists.

andia89 commented 3 years ago

Have the same problem (gmail). Is it maybe a problem of polling too often? The google site says (https://support.google.com/mail/answer/7126229?visit_id=637411084938413886-741518567&rd=2#cantsignin):

Make sure your mail app isn't set to check for new email too frequently. If your mail app checks for new messages more than once every 10 minutes, the app’s access to your account could be blocked.

Since the default polling rate is 10mins I guess that can lead to issues? With a polling rate of 20min I have the problems less frequently at least

antoflav commented 3 years ago

I have the same problem and I try a lot of methods but without success. Lastly I make a workaround to solve problem (for Ubuntu Gnome Xenial 16.04). I create following script, named "restartmailnag.sh", in my home directory:

#!/bin/bash
#
# Restart mailnag daemon when goes stuck.
# Command to add in in crontab (change <user> with your real user name):
#   */15 * * * * /home/<user>/restartmailnag.sh > /home//restartmailnag.log 2>&1_

user="$(whoami)"
cfg="/home/$user/.config/mailnag/mailnag.cfg" _# Mailnag config file._

# Mail check interval.
pollint=$(sed -rn 's/.*?poll_interval\s*?=\s*?([0-9]+?)\s*?$/\1/p' "$cfg")

# Last date/time mail check.
lasttime=$(journalctl | sed -rn 's/^.*?\smailnag\[.*?\sINFO\s\((.*?)\):\sChecking\s.*?$/\1/p' | tail -1)
lastepoc=$(date -d "$lasttime" +%s) _# "epoc" seconds._

# Current date/time.
currtime=$(date '+%Y-%m-%d %H:%M:%S')
currepoc=$(date -d "$currtime" +%s) _# "epoc" seconds._

((minelaps=(currepoc-lastepoc)/60)) # Elapsed minutes from the last mail checking.

# Find DBUS_SESSION_BUS_ADDRESS.
i=0
maxi=30 # Max. loops (to avoid infinite loop).
declare -a pid
export DBUS_SESSION_BUS_ADDRESS
DBUS_SESSION_BUS_ADDRESS=""
while [[ -z "$DBUS_SESSION_BUS_ADDRESS" && $i -lt $maxi ]]; do
    pid=($(pgrep -f -u "$user" gnome\-session\-binary)) # For Ubuntu Gnome. Check on Internet for others Distros._
    env=$(find /proc/"${pid[0]}" -maxdepth 2 -name 'environ')
    DBUS_SESSION_BUS_ADDRESS=$(grep -z DBUS_SESSION_BUS_ADDRESS "$env" | cut -d= -f2-)
    sleep 1
    (( i++ ))
done

#pollint=0 # test
# You have to check value to assign to "DISPLAY=" making "echo $DISPLAY" in you terminal.
if [ $minelaps -gt $pollint ]; then # Mailnag stuck.
        while p=$(pgrep -f "/usr/bin/mailnag"); do
            kill -9 $p
        sleep 1
    done
    echo "$(basename $0): Restart mailnag..."
    DBUS_SESSION_BUS_ADDRESS="$DBUS_SESSION_BUS_ADDRESS" \
        XAUTHORITY="/home/$user/.Xauthority" \
        DISPLAY=:1 /usr/bin/python /usr/bin/mailnag --quiet&
    disown
else
    if pgrep -f "/usr/bin/mailnag" >/dev/null; then
        echo "$(basename $0): Mailnag mail check running..."
    else
        echo "$(basename $0): Start mailnag..."
        DBUS_SESSION_BUS_ADDRESS="$DBUS_SESSION_BUS_ADDRESS" \
            XAUTHORITY="/home/$user/.Xauthority" \
            DISPLAY=:1 /usr/bin/python /usr/bin/mailnag --quiet&
        disown
    fi
fi

exit

NOTE: value to assign to DISPLAY should be obtain by issuing "echo $DISPLAY" in your terminal window and taking result. Save the script with name "restartmailnag.sh", then modify script permission: chmod 775 restartmailnag.sh After that, add command in crontab by: crontab -e and I insert the command: /15 * /home/&ltuser&gt/restartmailnag.sh > /home/&ltuser&gt/restartmailnag.log 2>&1 You have to substitute "&ltuser&gt" with your real home user. The script will be activated every 15 minutes (see crontab command). When script run, it compare current time with the last mailnag email check and if difference between them is greater than pooling interval (taken from mailnag configuration file) script assume that mailnag is blocked, so kill and restart it... Enjoy.

pulb commented 3 years ago

Can everybody encountering this issue please start mailnag from a terminal and post the output here after the problem occured? Furthermore, I assume everbody uses IMAP accounts? if so, please try to increase imap_idle_timeout in ~/.config/mailnag/mailnag_config from 10 to 15 to rule out a too frequent mail check (as suggested by @andia89).

antoflav commented 3 years ago

Thank you "pulb", bu I already have modified _imap_idletimeout as you suggest, without success. Recently I make a new version of my above script to check via crontab if current time exceed last mail check time, plus _imap_idletimeout. In that case, my script kill (with -TERM) mailnag and restart it. Furthermore my script (new version, not that above in this forum) also check if already exist another mailnag process before rerun it, because I discovered sometimes mailnag self-restarting. Kind regards, and happy new year!

pulb commented 3 years ago

Ok all, here's something more to try out: please decrease the idle timeout to something like 5 seconds and see if it makes a difference.

pulb commented 3 years ago

Sorry, that should read 5 minutes.

andia89 commented 3 years ago

I feel that increasing the timout did help a bit, however after some time I get this error in the terminal:

17:54.52 imap.gmail.com handler last 20 log messages:
Exception in thread imap.gmail.com handler:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 1774, in _handler
    qel.abort(typ, val)
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 179, in abort
    self.deliver(None)
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 198, in deliver
    self.callback((response, self.callback_arg, self.aborted))
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 1437, in _command_completer
    rqb.abort(typ, val)
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 179, in abort
    self.deliver(None)
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 198, in deliver
    self.callback((response, self.callback_arg, self.aborted))
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/backends/imap.py", line 152, in _idle_callback
    self._conn.logout()
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 937, in logout
    self._close_threads()
  File "/usr/local/lib/python3.8/dist-packages/Mailnag/common/imaplib2.py", line 1709, in _close_threads
    self.inth.join()
  File "/usr/lib/python3.8/threading.py", line 1008, in join
    raise RuntimeError("cannot join current thread")
RuntimeError: cannot join current thread
pulb commented 3 years ago

Thanks Andreas, this is very valuable information! The traceback shows that the connection is aborted and all running threads are joined during cleanup - including the executing thread itself, which is an error. Can you try to wrap conn.logout() in Mailnag/backends/imap.py", line 152 into an try: .. except: pass block and see if it fixes the problem?

pulb commented 3 years ago

@andia89 the commit above should fix the problem. Can you you try the latest code from master (this zip can be run from an arbitrary folder)) and check if it makes a difference?

andia89 commented 3 years ago

Hmm. I somehow think that fixed a symptom not really the issue... With the fix applied I now get:

INFO (2021-01-05 14:09:51): Checking 1 email account(s).
  24:17.70 imap.gmail.com handler last 20 log messages:
INFO (2021-01-05 14:24:17): Idler thread for account '*** (Gmail)' has been disconnected
INFO (2021-01-05 14:24:17): Trying to reconnect Idler thread for account '*** (Gmail)'.
ERROR (2021-01-05 14:24:17): Failed to reconnect Idler thread for account '*** (Gmail)' (Account is aready open).

and that repeats forever

pulb commented 3 years ago

Thanks! No that clearly was a bug and the error in your last message is the next XD

pulb commented 3 years ago

Andreas, i can't reproduce your latest error. Did you really try the latest master checkout without any changes?

pulb commented 3 years ago

Added another commit. Can someone test whether it fixes the issue?

pulb commented 3 years ago

This should realy be fixed now. Can somebody please

andia89 commented 3 years ago

Has been running fine for two days now!

andia89 commented 3 years ago

Actually it stopped working again now... It is not throwing an error anymore, but it also doesn't seem to reconnect again

INFO (2021-01-26 16:51:27): Checking 1 email account(s).
  56:42.95 imap.gmail.com handler last 20 log messages:
ERROR (2021-01-26 16:56:42): Idle callback for account '*** (Gmail)' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - connection terminated).
ERROR (2021-01-26 16:56:42): Idle callback for account '*** (Gmail)' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - connection terminated).
INFO (2021-01-26 16:56:42): Resetting connection for account '*** (Gmail)'
INFO (2021-01-26 16:56:43): Idler thread for account '*** (Gmail)' has been disconnected
INFO (2021-01-26 16:57:55): Checking 0 email account(s).
INFO (2021-01-26 16:58:33): Checking 0 email account(s).

And afterwards it never checks the same account again

pulb commented 3 years ago

Andreas, thanks again for this very valuable input. This looks like yet another problem. I'ill investigate.

pulb commented 3 years ago

@andia89 I have an idea what's going on and it's probably easy to fix. But what confuses me are the "Checking 0 email account(s)" messages. Did you somehow trigger a manual mail check, e.g. via the gnome-shell extension?

andia89 commented 3 years ago

Yes I did trigger a check via a gnome shell extension. But i also tried without afterwards and then it never checked again

pulb commented 3 years ago

Great, then I found the (hopefully last) problem. Will push a fix ASAP.

pulb commented 3 years ago

@andia89 the above commit should fix remaining issues. Can you please re-download the zip, test and provide the logs?

andia89 commented 3 years ago

Perfect!

INFO (2021-01-28 01:22:54): Checking 1 email account(s).
  26:56.44 imap.gmail.com reader last 20 log messages:
  26:56.44 imap.gmail.com handler last 20 log messages:
ERROR (2021-01-28 01:26:56): Idle callback for account '** (Gmail)' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - socket error: <class 'OSError'> - Too many read 0).
INFO (2021-01-28 01:26:56): Resetting connection for account '** (Gmail)'
INFO (2021-01-28 01:26:56): Idler thread for account '** (Gmail)' has been disconnected
INFO (2021-01-28 01:26:56): Trying to reconnect Idler thread for account '** (Gmail)'.
INFO (2021-01-28 01:26:57): Successfully reconnected Idler thread for account '** (Gmail)'.
INFO (2021-01-28 01:26:57): Checking 1 email account(s).
pulb commented 3 years ago

Great, thanks! Please let me know if something unexpected happens. if not, i'll prepare a new release shortly.

Matthew-Wai commented 1 year ago

I have installed "uos.app.mailnag_1.2.1-1.1_all.deb" on my UnionTech OS. So far, so good. It keeps checking for new mails regularly and does not go to sleep.

mfreeman72 commented 1 month ago

I know this thread is closed, but I've been having this problem after I wake my system from a suspend. This is with version 2.2.0-1 that's included in Ubuntu 22.04 (I'm running Linux Mint 21.3). Here's the journalctl log:

mike@ASUS-TUF-Gaming:~$ journalctl -b _COMM=mailnag Jul 24 07:20:32 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:20:32): Successfully enabled plugin 'libnotifyplugin'. Jul 24 07:20:32 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:20:32): Successfully enabled plugin 'goaplugin'. Jul 24 07:20:32 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:20:32): Checking 1 email account(s). Jul 24 07:22:31 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:22:31): Checking 1 email account(s). Jul 24 07:22:47 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:22:47): Checking 1 email account(s). Jul 24 07:22:53 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:22:53): Checking 1 email account(s). Jul 24 07:32:54 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:32:54): Checking 1 email account(s). Jul 24 07:36:31 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 07:36:31): Idle callback for account 'mikefreeman1972@gmail.com' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - socket error: <class 'OSError'> - Too many read 0). Jul 24 07:36:31 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:36:31): Resetting connection for account 'mikefreeman1972@gmail.com' Jul 24 07:36:31 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:36:31): Idler thread for account 'mikefreeman1972@gmail.com' has been disconnected Jul 24 07:36:31 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:36:31): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 07:36:37 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:36:37): Successfully reconnected Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 07:36:37 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:36:37): Checking 1 email account(s). Jul 24 07:46:37 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:46:37): Checking 1 email account(s). Jul 24 07:47:23 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 07:47:23): Idle callback for account 'mikefreeman1972@gmail.com' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - connection terminated). Jul 24 07:47:23 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 07:47:23): Idle callback for account 'mikefreeman1972@gmail.com' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - connection terminated). Jul 24 07:47:23 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:47:23): Resetting connection for account 'mikefreeman1972@gmail.com' Jul 24 07:47:23 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:47:23): Idler thread for account 'mikefreeman1972@gmail.com' has been disconnected Jul 24 07:47:23 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:47:23): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 07:47:25 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:47:25): Successfully reconnected Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 07:47:25 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:47:25): Checking 1 email account(s). Jul 24 07:57:26 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 07:57:26): Checking 1 email account(s). Jul 24 08:04:41 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:04:41): Checking 1 email account(s). Jul 24 08:14:42 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:14:42): Checking 1 email account(s). Jul 24 08:16:33 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:16:33): Checking 1 email account(s). Jul 24 08:26:34 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:26:34): Checking 1 email account(s). Jul 24 08:31:11 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:31:11): Checking 1 email account(s). Jul 24 08:41:12 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:41:12): Checking 1 email account(s). Jul 24 08:51:14 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 08:51:14): Idle callback for account 'mikefreeman1972@gmail.com' returned an error (<class 'Mailnag.common.imaplib2.IMAP4.abort'> - socket error: <class 'OSError'> - Too many read 0). Jul 24 08:51:14 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:51:14): Resetting connection for account 'mikefreeman1972@gmail.com' Jul 24 08:51:14 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:51:14): Idler thread for account 'mikefreeman1972@gmail.com' has been disconnected Jul 24 08:51:14 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:51:14): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 08:51:16 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 08:51:16): Failed to reconnect Idler thread for account 'mikefreeman1972@gmail.com' (b'[AUTHENTICATIONFAILED] Invalid credentials (Failure)'). Jul 24 08:51:16 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:51:16): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com' in 5 minutes Jul 24 08:56:16 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:56:16): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 08:56:18 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 08:56:18): Failed to reconnect Idler thread for account 'mikefreeman1972@gmail.com' (b'[AUTHENTICATIONFAILED] Invalid credentials (Failure)'). Jul 24 08:56:18 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 08:56:18): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com' in 5 minutes Jul 24 09:01:18 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 09:01:18): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com'. Jul 24 09:01:21 ASUS-TUF-Gaming mailnag[2970]: ERROR (2024-07-24 09:01:21): Failed to reconnect Idler thread for account 'mikefreeman1972@gmail.com' (b'[AUTHENTICATIONFAILED] Invalid credentials (Failure)'). Jul 24 09:01:21 ASUS-TUF-Gaming mailnag[2970]: INFO (2024-07-24 09:01:21): Trying to reconnect Idler thread for account 'mikefreeman1972@gmail.com' in 5 minutes

Matthew-Wai commented 1 month ago

I know this thread is closed, but I've been having this problem after I wake my system from a suspend.

After your system has woken, if you restart Mailnag, will the same problem arise?

mfreeman72 commented 1 month ago

I know this thread is closed, but I've been having this problem after I wake my system from a suspend.

After your system has woken, if you restart Mailnag, will the same problem arise?

Restarting mailnag does fix the issue temporarily. After suspending and waking up the computer again, mailnag stops working again.

Matthew-Wai commented 1 month ago

Restarting mailnag does fix the issue temporarily. After suspending and waking up the computer again, mailnag stops working again.

You may use a shell script to restart Mailnag automatically each time when the system has woken up. It is not difficult to do so.

mfreeman72 commented 1 month ago

Restarting mailnag does fix the issue temporarily. After suspending and waking up the computer again, mailnag stops working again.

You may use a shell script to restart Mailnag automatically each time when the system has woken up. It is not difficult to do so.

I had thought of that, but I was hoping there might be an official solution to the problem, other than forcing a restart.

Matthew-Wai commented 1 month ago

I had thought of that, but I was hoping there might be an official solution to the problem, other than forcing a restart.

Try a different version. The old version "mailnag_1.3.0-0_ubuntu18.04.1_all.deb" is still on my hard disk.