-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mailnag doesn' t work after connecting VPN sometimes or WiFi disappeared suddenly always #188
Comments
Update I used mailnag tomorrow, and suspend my laptop when I went to bed.
|
Another Update I downloaded your source coed and modified it to try to solve my issue.
|
Third Update Those exceptions happened after connecting VPN. This time, in mailnagdaemon.py line 206, I added a "while true", and other code keep them original.
And after the first exception, mailnag retried but another exception happened.
|
Can you please post the contents of ~/.config/mailnag/mailnag.cfg? |
Did some replacement of email address and user_name for privacy.
|
Confirmed. |
I am using Ubuntu 19.04, after mailnag-config
|
Ubuntu: 18.04 LTS |
@SFBB: your connection is terminated due to a socket error in the python2 implementation of imaplib. Mailnag has been ported to python3 recently - can you check out the latest code from master and see if the problem still persists? @alfabuster |
With VPN (wireguard) configured globally by provider application, launch at startup, dbus NetworManager connection state returned is 60 (ie NM_STATE_CONNECTED_SITE). ConnectivityTest.is_offline() returns False if state != 70 (ie NM_STATE_CONNECTED_GLOBAL) |
@machinbrol: Great finding, that's exactly what I was suspecting - when connected via VPN, the connection test indicates "offline" in networkmanager mode, since this mode checks for a direct internet connection. Can somebody please confirm if changing the |
This should realy be fixed now.
|
|
@alfabuster this is onaother, Gmail specific issue, please have a look at the troubleshooting section of the readme.
|
@pulb Ok. Continue... This is maybe the longest time I spent for make program work...
|
@alfabuster i googled this up. This seems to be a gmail issue related to your environment/port setup. Are you behind a firewall/connected to a VPN? |
@pulb Yes, I use nordvpn now... |
Ok so this seems to be a port configuration problem of your vpn. It's not mailnag related, every other app accessing that port will have that issue.
|
Ok. But without VPN same problem. It seems like google close connection or something like that... |
"Cannot assign requested address" means mailnag cannot bind to the specified mail server at the specified port. There must be something wrong with your network/routing setup. What mail server/port did you enter?
Am 27. Januar 2021 19:22:06 MEZ schrieb alfabuster <notifications@github.com>:
…Ok. But without VPN same problem. It seems like google close connection
or something like that...
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#188 (comment)
|
I used same settings like in this tutorial only password what google give me 16 symbols... |
Should be fixed in 2.2.0 release. |
Ubuntu 18.10
Mailnag 1.3.0
Hello,
1. VPN
I just find that if I connected to a VPN, sometimes Mailnag won't work well even I clicked the "Check for Mail" button.
I connected VPN at about 21:11:41. And I clicked the "Click for Mail" button at 21:13:29 and later to make Mailnag report some messages, otherwise, it will report nothing. Messages are like "Checking 0 email account(s)."
2. WiFi
And always after I make my WiFi disappear when my laptop still connected to it, Mailnag will have the same issue. For example, my laptop connected to my phone's mobile network, and I disabled the network on my phone when my laptop still connected to it, and after some minutes, I enabled this network, and make my computer connect to it, Mailnag will not work well.
3. More Testing
And I tested the
sudo netstat -tup -W | column -t
command to see if Mailnag is checking to my IMAP email sites, and the answer is no.4. My Opinion
Since I am not familiar with those things in python, I just can make some guesses.
I think the VPN and WiFi issues are caused by the same exception. And you don't handle this exception. Maybe something related to dbus.
The text was updated successfully, but these errors were encountered: