Can not receive or email when stwiched from WIFI to 3G

[lwajohn@sina.com]

Hi,

    I've been using Aqua Mail for sometime and find it very helpful until recently I try to do it in 3G network. When I close WIFI connection and use 3G network, it can not receive nor send email any more. What's the problem?

    I also tried to switch on and off the "Use WIFI Only" option in settings, but I won't work too.

    Any help would be much appreciated.

[Kostya Vasilyev]

Are you getting "network errors", "connection errors", etc?

The app doesn't really care for the type of network you're on, but some networks could be blocking ports needed for mail to work (and allow web browsing). That's something to investigate, or ask the mobile operator's support about.

[David13105]

Hi,  i have the same problem. I tried to receive or send email on 3 differents 3g network (sfr in france,  safaricom in kenya and djibnet in djibouti) and it doesn't work.
No pb at all on wifi
Excellent app except for this 3g pb
Hope that someone will be abble to help me
My phone is on android 4.4
Thanks

[Kostya Vasilyev]

And as usual, this has nothing to do with the app.

I predict that we're going to discover that:

- The mail provider is blocking access based on geo-location

OR

- The phone's "access point" config is set to "wap", which only allows web browsing traffic (and not email or anything else)

OR

- Something else I can't quite think of.

But "app doesn't work on 3G" sounds so much more reasonable.

[David13105]

When i use gmail app,  i can download my messages with no pb on 3g.
Only when using aquamail that am stuck on 3g.
And i really don't like using the gmail app..... Really not a nice app compared to aquamail, reason why i really struggle to find a solution.
Thanks for your help

[Finferlo]

What was described happens to me too. If after a WIFI CONNECTION in step with a 3G connection, whatsapp, Twitter, etc. are working correctly, while Aquamail not. It is necessary to restart the device and everything works. This does not happen with the client stock and even with other clients that do not quote here. I have three email accounts, one exchange and the other two imap, the problem occurs for all three.

[Kostya Vasilyev]

It could be the device, the network, or some interaction between the two.

Could be affecting actual network traffic or just DNS.

AquaMail does not care about WiFi vs. mobile, about 802.11ac vs. 802.11n, about LTE-A vs. HSDPA, any of that stuff.

Networking is networking, and it all goes through Android system code, amazingly enough.

The only thing to check is AquaMail settings -> network -> make sure "DNS" is enabled (it is by default).

PS - Cloud based mail apps (TypeMail, MyMail, etc) might be affected to a lesser extent or not at all, maybe their traffic looks more like web browsing. Same goes for Twitter.

PPS -- To summarize, there is no "special code for 3G" in AquaMail, nor is it needed (and there aren't any bugs in it since it doesn't exist).

[StR]

Just in case, a couple of other ideas of what might produce a difference between WiFi and mobile netwrok.
1. (It is obvious, - but who knows...)
You may want to check that  Settings -> Mail, receiving -> [scheduled sync] Use WiFi only and -> [IMAP push] Use WiFi only" are not checked.

2. You may want to check that in Android settings you do not block background network traffic for the app while on mobile network. (In Android 4.* it is under "All Settings" -> Data usage -> Mobile tab, then click on the app in the list and make sure the box "Restrict background data" is not checked. Also, if you have some mobile traffic-controlling apps (e.g. Onavo Count), - those also might affect the traffic on per-app basis.
A simple way to check for that type of situation is to try syncing manually any of the accounts in Aquamail (while on mobile network) by pressing on the two-arrow circle next to the account in the account view.

[Kostya Vasilyev]

Oh, and needless to say -- I'll be happy to look at a debug log showing the issue.

Just afraid that I'll find a DNS error or a socket level failure, and that's going to be it.

[Kostya Vasilyev]

Issue resolved:

"Gmail or Google Apps" account type, which authenticates by using OAUTH and Google Play Services -- sometimes fails, inside these Google Play Services, on mobile networks.

I've seen a few logs confirming this. Has to be fixed by Google (haha!)

Removing the account and adding it back as "Internet Mail" account type (using password auth not OAUTH) is now working.