Nil
2019-03-01 22:23:50 UTC
On my Android phone I've been unable to retrieve email for the past
couple of weeks or more, using my preferred IMAP client, Blue Mail or
K9 Mail. I am able to send email. I can get to webmail on a web
browser. I can get email when connected via WiFi. The error message I
get is:
Error - Sync failed, your username or password may be incorrect (3010)
Email server returned: "NO, [ALERT], Temporarily blacklisted IP Address
- try again later."
I'm sure the UID/password is correct, since I haven't changed it
lately. I assume my IP address changes every time I make a mobile data
connection, so that error message seems unlikely or misleading. My
server settings are those recommended by Comcast (server:
imap.comcast.net, Security: SSL/TLS, Port: 993.)
A couple of days ago I thought I had discovered a workaround: changing
my User ID from my full Comcast email to just the prefix, eliminating
the "@comcast.net" bit. This actually worked for about half a day, then
I started getting the same error message.
Has anybody else seen this, can anyone explain what's going on, and/or
can anyone suggest a workaround or fix?
couple of weeks or more, using my preferred IMAP client, Blue Mail or
K9 Mail. I am able to send email. I can get to webmail on a web
browser. I can get email when connected via WiFi. The error message I
get is:
Error - Sync failed, your username or password may be incorrect (3010)
Email server returned: "NO, [ALERT], Temporarily blacklisted IP Address
- try again later."
I'm sure the UID/password is correct, since I haven't changed it
lately. I assume my IP address changes every time I make a mobile data
connection, so that error message seems unlikely or misleading. My
server settings are those recommended by Comcast (server:
imap.comcast.net, Security: SSL/TLS, Port: 993.)
A couple of days ago I thought I had discovered a workaround: changing
my User ID from my full Comcast email to just the prefix, eliminating
the "@comcast.net" bit. This actually worked for about half a day, then
I started getting the same error message.
Has anybody else seen this, can anyone explain what's going on, and/or
can anyone suggest a workaround or fix?