[{"data":1,"prerenderedAt":231},["ShallowReactive",2],{"blog:how-to-use-gmail-in-china":3},{"zh-CN":4,"en":123},{"blocks":5,"faq":104},[6,9,11,13,17,19,21,23,26,28,30,32,34,36,39,70,72,75,84,87,89,91,93,95,97,100,102],{"type":7,"html":8},"p","Gmail 在国内一个常见的情况是：靠谷歌加速器之类的网络工具把网页版打开了，手机或者电脑上的邮件客户端却收不到、发不出，或者反过来，网页不行客户端却正常。这不是巧合，两者走的根本不是同一条路。",{"type":7,"html":10},"判断方法是这样的：网页和客户端都打不开，是网络没到；网页正常但客户端不行，或者反过来，是两者连接方式不一样导致的，下一节专门讲这个区别；登录之后频繁被要求两步验证，是谷歌自己的账号安全判定，和网络无关。",{"type":7,"html":12},"下面先讲清楚网页版和客户端为什么会表现不一样，再给一套排查步骤。",{"type":14,"id":15,"html":16},"h2","bp-why","三种不同的「收不到、发不出」",{"type":7,"html":18},"第一种是网络本身没到。网页和客户端全都打不开，这是最基础的一层，换一条能稳定连接海外网络的线路通常就能解决。",{"type":7,"html":20},"第二种是账号需要验证。登录地点变化太快，谷歌会判定为需要额外确认身份，弹出两步验证或者安全提示，这是账号保护机制，不是网络问题，验证通过之后一切照常。",{"type":7,"html":22},"第三种是行为触发了限制。短时间内多次登录失败，或者用不受信任的方式反复尝试访问，会被判定为风险行为，进一步限制访问，直到额外验证通过为止。这和网络无关，换网络工具解决不了，需要按提示走完验证。",{"type":14,"id":24,"html":25},"bp-clients","网页版和客户端为什么表现不同",{"type":7,"html":27},"网页版 gmail.com 走的是标准的网页连接方式，和日常刷网页用的是同一条路，端口也是同一个，网络只要通，网页基本就没问题。",{"type":7,"html":29},"邮件客户端不一样。手机自带邮件、Outlook、Apple Mail 这类客户端，很多情况下用的是收发邮件专用的协议，走的端口和网页浏览完全不是同一批。这些端口平时用不到，容易被忽略。",{"type":7,"html":31},"问题就出在这里：如果当前的网络环境或者分流规则只保证了网页浏览常用的端口通畅，没有覆盖邮件客户端专用的这些端口，就会出现「网页正常，客户端却连不上」的情况——文字上完全说得通，因为两者本来就是两条独立的路，一条通不代表另一条也通。反过来，如果规则只覆盖了客户端的端口而漏了网页常用的端口，也会出现相反的情况，只是没那么常见。",{"type":7,"html":33},"全局模式会把所有流量都走同一条路，不区分端口，覆盖面最全；智能分流为了效率会自动判断哪些流量需要转发，哪些直连，邮件客户端这类不常见的端口有时候会被漏判。这也是为什么邮件客户端出问题时，切到全局模式往往比换节点更管用。",{"type":7,"html":35},"这一点和网页打不开的常见原因不太一样。网页打不开，多半是域名或者整段线路没通，换节点基本能解决；客户端连不上，很多时候节点本身是好的，只是它用的端口没有被规则覆盖到，换节点不解决这个问题，换模式才对症。分清楚这两种情况，能省掉不少来回折腾的时间。",{"type":14,"id":37,"html":38},"bp-steps","排查步骤",{"type":40,"items":41},"steps",[42,46,50,54,58,62,66],{"title":43,"body":44},"第一步：连接并优先用全局模式测试",[45],"打开\u003Ca href=\"\u002Ffeatures\u002F\">快橙\u003C\u002Fa>，连接的时候选全局模式而不是智能分流。先用这个模式排除端口覆盖不全的可能性，问题定位之后再决定要不要切回智能分流。",{"title":47,"body":48},"第二步：先测网页版，确认账号和基础网络没问题",[49],"登录 gmail.com，看看能不能正常收发。这一步顺利，说明账号和基础网络都没问题，问题范围就缩小到客户端这一边。",{"title":51,"body":52},"第三步：单独测试邮件客户端",[53],"打开手机或者电脑上的邮件客户端，看它能不能连上、收不收得到新邮件。网页正常但客户端不行，基本可以确定是客户端用的端口没通。",{"title":55,"body":56},"第四步：客户端提示密码错误时，生成一个应用专用密码",[57],"登录信息没输错却一直提示密码不对，去账号安全设置里生成一个应用专用密码，把这个填进客户端，而不是反复尝试登录密码。",{"title":59,"body":60},"第五步：客户端长时间没反应，重启而不是一直等",[61],"换了节点或者网络波动之后，客户端有时候会卡在一个不再有效的连接上，重启 App 通常比等它自己恢复更快。",{"title":63,"body":64},"第六步：测试结束后，按需换回智能分流",[65],"确认客户端能正常收发之后，如果更看重效率，可以换回智能分流模式。只是之后如果客户端又开始连不上，先怀疑是不是分流规则漏了它用的端口，换回全局模式验证一次。",{"title":67,"body":68},"第七步：新设备第一次配置邮箱时，两种模式都试一遍",[69],"新手机或者新电脑第一次添加 Gmail 账号，先用全局模式把客户端配置走完，确认能收能发之后再考虑要不要换成智能分流。第一次配置就用智能分流，遇到问题时很难判断是配置错了还是端口没覆盖。",{"type":71},"downloads",{"type":14,"id":73,"html":74},"bp-errors","常见报错和情况",{"type":76,"items":77},"list",[78,79,80,81,82,83],"\u003Cstrong>网页能打开，客户端一直转圈或反复要求登录\u003C\u002Fstrong>：多半是客户端用的端口没被覆盖，切到全局模式测试一次。","\u003Cstrong>客户端提示「用户名或密码不正确」\u003C\u002Fstrong>：多数客户端需要应用专用密码，不是账号登录密码，去安全设置里生成一个。","\u003Cstrong>收信正常，发信失败\u003C\u002Fstrong>：两者有时候走的端口不完全一样，先确认发信用的端口在当前模式下是通的。","\u003Cstrong>频繁弹出两步验证，要求重新确认\u003C\u002Fstrong>：账号安全判定，按提示验证一次即可，和网络工具无关。","\u003Cstrong>换节点后客户端长时间无响应\u003C\u002Fstrong>：客户端可能卡在旧连接上，重启一次比等待更快恢复。","\u003Cstrong>提示「此设备不受信任」\u003C\u002Fstrong>：正常确认一次即可，之后这台设备通常会被记住，不会每次都弹出来。",{"type":14,"id":85,"html":86},"bp-stable","让收发更稳的几个习惯",{"type":7,"html":88},"邮件客户端优先用全局模式。比起智能分流省下来的一点效率，少踩「端口没覆盖」这个坑更值得。",{"type":7,"html":90},"固定一个常用节点，别在短时间内频繁切换地区。账号的安全判定和登录地点的稳定性有关，切换太频繁容易触发不必要的验证，收发邮件也会跟着变得不稳定。",{"type":7,"html":92},"网页版和客户端分开测试是个好习惯，不只是排查问题的时候用得上，日常配置新设备时先这样过一遍，能提前发现端口覆盖不全的问题。",{"type":7,"html":94},"遇到「偶尔收不到邮件」这种不稳定的情况，别急着改配置。先确认是不是网络本身在那个时间点不稳定，而不是客户端设置出了问题，两者的排查方向完全不一样。",{"type":7,"html":96},"\u003Ca href=\"\u002Forder\u002F\">快橙\u003C\u002Fa>一键连接、断线自动重连，全局模式下网页和客户端都能覆盖到，日常收发邮件更省心。如果是公司或校园网络本身限制了端口，公司或校园网把 VPN 拦了怎么办里讲得更细；App 能用网页打不开、或者反过来的情况，App 能用、浏览器打不开的原因这篇也是同一类问题的另一个场景。",{"type":14,"id":98,"html":99},"bp-final","总结",{"type":7,"html":101},"Gmail 在国内收发不正常，通常是三层里的某一层：网络没到、账号要验证，或者行为触发了限制。网页版和客户端表现不一样，又是单独一层原因——两者走的端口不同，覆盖不全就会出现「一边正常一边不行」，全局模式是最直接的解法。",{"type":7,"html":103},"网络这一段可以做得很省心：连接时优先选全局模式，固定一个节点，断线自动重连，剩下的账号验证交给谷歌自己的规则去处理。\u003Ca href=\"\u002Forder\u002F\">快橙\u003C\u002Fa>每天有免费试用时长，注册后就能领取——先把网页版和客户端都测一遍，再决定要不要长期用。",[105,108,111,114,117,120],{"q":106,"a":107},"网页能打开 Gmail，手机自带邮件 App 却一直连不上，为什么？","网页版和邮件客户端用的端口和连接方式不一样，网页能通不代表客户端用的端口也通，多数时候是客户端那条路单独没打通。",{"q":109,"a":110},"客户端一直提示密码错误，但网页登录是对的，怎么办？","多数邮件客户端不能直接用登录密码，需要在账号安全设置里生成一个应用专用密码，再把这个填进客户端里。",{"q":112,"a":113},"为什么总是弹出两步验证，要求重新确认？","登录地点变化会触发谷歌自己的账号安全检查，这和网络稳不稳没关系，确认是本人操作，按提示验证一次就行。",{"q":115,"a":116},"全局模式和智能分流，哪个更适合邮件客户端？","全局模式更保险。智能分流有时候会漏掉客户端使用的端口，导致网页正常但客户端连不上。",{"q":118,"a":119},"快橙能保证 Gmail 一直收发正常吗？","网络这一段快橙负责做稳；账号验证规则和谷歌自己的安全判定，由谷歌自己决定。详见\u003Ca href=\"\u002Ffeatures\u002F\">功能介绍\u003C\u002Fa>。",{"q":121,"a":122},"换了节点之后需要重新设置客户端吗？","通常不需要重新配置账号，重新连接一次网络就行；如果客户端长时间没反应，重启一下 App 会比一直等更快恢复。",{"blocks":124,"faq":212},[125,127,129,131,133,135,137,139,141,143,145,147,149,151,153,183,184,186,194,196,198,200,202,204,206,208,210],{"type":7,"html":126},"A common Gmail situation in mainland China: a network tool gets the web version open fine, while a mail client on a phone or computer still can't send or receive — or the other way around, with the web failing while the client works. That's not a coincidence; the two simply don't take the same path at all.",{"type":7,"html":128},"Here's the test: both the web and the client failing to load is the network. The web working while the client doesn't, or the reverse, comes down to the two using different connection methods — covered in the next section. Being asked for 2-step verification repeatedly after logging in is Google's own account-security judgement, unrelated to the network.",{"type":7,"html":130},"The rest of this guide first explains why the web version and mail clients behave differently, then gives a step-by-step check.",{"type":14,"id":15,"html":132},"Three different reasons mail won't send or arrive",{"type":7,"html":134},"The first is that the network itself never arrives. Both the web and the client fail to load — the most basic layer, and a stable route to servers outside mainland China usually clears it.",{"type":7,"html":136},"The second is that the account needs verification. A login location that changes too quickly gets Google to require extra identity confirmation — 2-step verification or a security prompt. That's account protection, not a network fault, and everything goes back to normal once it clears.",{"type":7,"html":138},"The third is a behavior-triggered restriction. Several failed login attempts in a short time, or repeated access attempts through an untrusted method, get read as risky behavior and lead to further restricted access until extra verification clears. That has nothing to do with the network — no network tool fixes it, and it needs the verification flow completed as prompted.",{"type":14,"id":24,"html":140},"Why the web version and mail clients behave differently",{"type":7,"html":142},"The web version at gmail.com uses a standard web connection — the same path, and the same ports, as ordinary browsing. As long as the network is reachable, the web version is usually fine.",{"type":7,"html":144},"A mail client is different. A phone's built-in mail app, Outlook, Apple Mail and similar clients often use protocols dedicated to sending and receiving mail, running on a completely different set of ports from web browsing. Those ports rarely get used for anything else, which is exactly why they're easy to overlook.",{"type":7,"html":146},"That's exactly where the problem shows up: if the current network setup or routing rules only guarantee the ports ordinary web browsing uses, without covering the ports a mail client depends on, you get "the web works fine, the client just can't connect" — which makes complete sense once you see it, because the two are genuinely separate paths, and one working says nothing about the other. The reverse can happen too, with rules covering the client's ports but missing the web's, though that's less common.",{"type":7,"html":148},"Global mode routes all traffic over the same path regardless of port, giving the widest coverage. Smart routing, for efficiency, automatically decides which traffic to forward and which to send direct, and a mail client's less common ports sometimes get misjudged in that process. That's exactly why switching to global mode tends to fix a mail client issue more reliably than switching nodes.",{"type":7,"html":150},"This differs from the usual reason a web page won't load. A web page failing is usually the hostname or the whole route being unreachable, and switching nodes generally fixes it. A client failing to connect often means the node itself is fine — it's just that the rules didn't cover the port it uses, so switching nodes doesn't fix it, but switching modes does. Telling the two apart saves a lot of back-and-forth.",{"type":14,"id":37,"html":152},"Working through it",{"type":40,"items":154},[155,159,163,167,171,175,179],{"title":156,"body":157},"Step one: connect and test with global mode first",[158],"Open \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">FastOrange\u003C\u002Fa> and choose global mode rather than smart routing when connecting. Ruling out incomplete port coverage first, then deciding whether to switch back to smart routing once the problem is located, is the more efficient order.",{"title":160,"body":161},"Step two: test the web version first to confirm the account and base network",[162],"Log in at gmail.com and check whether it sends and receives normally. If that goes smoothly, both the account and the base network are fine, and the problem narrows down to the client side.",{"title":164,"body":165},"Step three: test the mail client on its own",[166],"Open the mail client on your phone or computer and check whether it connects and receives new mail. Web working while the client doesn't is close to confirmation that the client's ports specifically aren't getting through.",{"title":168,"body":169},"Step four: generate an app-specific password if the client says the password is wrong",[170],"If the login details are correct but the client keeps rejecting the password, generate an app-specific password in the account's security settings and use that instead of retrying the regular login password.",{"title":172,"body":173},"Step five: restart the client instead of waiting it out if it stays unresponsive",[174],"After switching nodes or a network hiccup, a client sometimes gets stuck on a connection that's no longer valid — restarting the app usually recovers faster than waiting for it to sort itself out.",{"title":176,"body":177},"Step six: switch back to smart routing afterward if you want to",[178],"Once the client is confirmed to be sending and receiving normally, switch back to smart routing if efficiency matters more day to day. If the client starts failing again later, suspect a routing rule missing its port first, and confirm by switching back to global mode.",{"title":180,"body":181},"Step seven: try both modes the first time you set up mail on a new device",[182],"The first time a new phone or computer adds a Gmail account, get the client configured under global mode first, and only consider switching to smart routing once it's confirmed to send and receive. Starting with smart routing on a first setup makes it hard to tell whether a problem is a configuration mistake or a missed port.",{"type":71},{"type":14,"id":73,"html":185},"Errors people actually run into",{"type":76,"items":187},[188,189,190,191,192,193],"\u003Cstrong>The web works, but the client spins forever or keeps asking to log in again.\u003C\u002Fstrong> Usually the client's port isn't covered — test once in global mode.","\u003Cstrong>The client says "incorrect username or password."\u003C\u002Fstrong> Most clients need an app-specific password rather than the account's login password — generate one in security settings.","\u003Cstrong>Receiving works, sending fails.\u003C\u002Fstrong> The two sometimes use slightly different ports — confirm the port sending depends on is open under the current mode.","\u003Cstrong>2-step verification keeps popping up, asking to reconfirm.\u003C\u002Fstrong> An account-security judgement — verify once as prompted; it has nothing to do with the network tool.","\u003Cstrong>The client stays unresponsive for a long time after switching nodes.\u003C\u002Fstrong> It may be stuck on an old connection — restarting it usually recovers faster than waiting.","\u003Cstrong>"This device isn't trusted."\u003C\u002Fstrong> Confirm it once as usual, and the device is normally remembered afterward instead of prompting every time.",{"type":14,"id":85,"html":195},"Habits that keep mail steady",{"type":7,"html":197},"Default to global mode for a mail client. The bit of efficiency smart routing saves is not worth repeatedly hitting the "port not covered" trap.",{"type":7,"html":199},"Stick to one usual node and avoid switching regions often in a short window. The account's security judgement is tied to how stable the login location is, and switching too often triggers unnecessary verification — and makes mail delivery less steady along with it.",{"type":7,"html":201},"Testing the web version and the client separately is a good habit beyond just troubleshooting — running through this once when setting up a new device catches incomplete port coverage early.",{"type":7,"html":203},"Don't rush to change the configuration over an occasional missed email. Confirm first whether the network itself was briefly unstable at that moment, rather than assuming the client's setup is wrong — the two point in completely different directions for troubleshooting.",{"type":7,"html":205},"\u003Ca href=\"\u002Fen\u002Forder\u002F\">FastOrange\u003C\u002Fa> connects in one tap and reconnects automatically when a link drops, and global mode covers both the web and the client, which keeps everyday mail simpler. If a company or campus network is restricting ports itself, when a company or campus network blocks your VPN goes into more detail; for the reverse case where an app works but a browser doesn't, why an app works but the browser doesn't covers the same kind of problem from another angle.",{"type":14,"id":98,"html":207},"In summary",{"type":7,"html":209},"Gmail not sending or receiving properly in mainland China usually comes down to one of three layers: the network never arrives, the account needs verification, or behavior tripped a restriction. The web version and a mail client behaving differently is a separate layer on top of that — they use different ports, and incomplete coverage produces "one side works, the other doesn't," with global mode as the most direct fix.",{"type":7,"html":211},"The network side can be made genuinely low-effort: default to global mode when connecting, stay on one node, and reconnect automatically when it drops, leaving account verification to Google's own rules. \u003Ca href=\"\u002Fen\u002Forder\u002F\">FastOrange\u003C\u002Fa> gives every registered account free trial time daily — test both the web version and the client first, then decide whether to keep it.",[213,216,219,222,225,228],{"q":214,"a":215},"Gmail opens fine on the web, but my phone's built-in mail app can't connect. Why?","The web version and a mail client use different ports and connection methods. The web being reachable doesn't mean the client's ports are too — most of the time, the client's path specifically isn't getting through.",{"q":217,"a":218},"My client keeps saying the password is wrong, but the same password logs in fine on the web. What now?","Most mail clients can't use your regular login password directly. Generate an app-specific password in the account's security settings and enter that into the client instead.",{"q":220,"a":221},"Why does 2-step verification keep popping up asking me to confirm again?","A login location that changes triggers Google's own account-security check, unrelated to how stable the network is. Confirm it was you and complete the verification once, as prompted.",{"q":223,"a":224},"Which suits a mail client better, global mode or smart routing?","Global mode is the safer bet. Smart routing sometimes misses the ports a mail client uses, which is exactly why the web works while the client can't connect.",{"q":226,"a":227},"Can FastOrange guarantee Gmail always sends and receives normally?","FastOrange is responsible for the network leg being stable. Account verification rules and Google's own security judgement are Google's call. See \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">what the app does\u003C\u002Fa>.",{"q":229,"a":230},"Do I need to reconfigure the client after switching nodes?","Usually not — reconnecting the network is enough. If the client stays unresponsive for a while, restarting the app tends to recover faster than waiting it out.",1791881578629]