Mailspring: Couldn't resolve host name

Created on 11 Mar 2019  路  8Comments  路  Source: Foundry376/Mailspring

Are there any related issues?

No directly related with VPN


...

What operating system are you using?

... PopOS 18.10

What version of Mailspring are you using?

1.5.7-2057ca30
...

Bug?

After establishing a VPN through the Express VPN service; Mailspring is unable to resolve the DNS name. Then is offline during the VPN session. The thing is it is the only application on my system who has this issue.

../../../../mailsync-XXXX.log

5264 [2019-03-11 11:05:35.893] [metadata] [info] Metadata delta stream starting...
5264 [2019-03-11 11:05:35.893] [metadata] [info] Metadata delta stream closed.
5264 [2019-03-11 11:05:35.902] [metadata] [info] Encountered error: {"debuginfo":"","key":"Couldn't resolve host name","retryable":true,"what":"std::exception"}. Will retry in 3 sec.
5264 [2019-03-11 11:05:38.903] [metadata] [info] Metadata delta stream starting...
5264 [2019-03-11 11:05:38.904] [metadata] [info] Metadata delta stream closed.
...

Is the issue related to a specific email provider (Gmail, Exchange, etc.)?

...
Gmail accounts.

Is the issue reproducible with a particular attachment, message, signature, etc?

...

--

Feature Request?

Does this feature exist in another mail client or tool you use?

...

needs-reproduction

Most helpful comment

I am experiencing the same issue as well. Is there a way to start mailspring and require it to use a specific interface? I am also using ExpressVPN while experiencing these issues.

I am not pretty sure but, Did you use snap installation for Mailpring? I changed my OS from Ubuntu 18.10 to Debian 9 but I had the same issue, so I removed the snap version and then install the .deb version. For my, at least now it's working, maybe you should try this way.

All 8 comments

Hey! Thanks for reporting this - this is pretty interesting. That particular error is coming from the "metadata sync" part of the app that keeps your snooze dates, read receipts, etc. synced with our servers, so it's trying to reach https://id.getmailspring.com/. Could you double check and make sure that address is accessible from within your VPN? (It should be...)

Have you set up your VPN on a separate network interface by any chance? Internally, the sync engine uses libCURL to make HTTP requests (they have a C++ library as well as the well known command line tool), and it looks like curl doesn't autodetect that it should use the separate network interface if you've set up your VPN that way, but otherwise it should work.

I am experiencing the same issue as well. Is there a way to start mailspring and require it to use a specific interface? I am also using ExpressVPN while experiencing these issues.

I am experiencing the same issue as well. Is there a way to start mailspring and require it to use a specific interface? I am also using ExpressVPN while experiencing these issues.

I am not pretty sure but, Did you use snap installation for Mailpring? I changed my OS from Ubuntu 18.10 to Debian 9 but I had the same issue, so I removed the snap version and then install the .deb version. For my, at least now it's working, maybe you should try this way.

Diego, that fixed it for me. Thank you for the help. I guess that should help confirm that it is only the snap that has issues with using the VPN.

Diego, that fixed it for me too. Thanks for the help!

Wow! Thanks, it worked for me too

I am experiencing the same issue and I just close the VPN then retry, for me, it's just worked! May be you can try this way

I have the same issue because I have a very strick firewall and network blocking.

Does it mean that this app is not usable without some ID from getmailspring servers?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

imbrn picture imbrn  路  3Comments

k4rli picture k4rli  路  3Comments

spartero picture spartero  路  3Comments

justindoran picture justindoran  路  3Comments

LeandroStanger picture LeandroStanger  路  3Comments