747053 - imap.googlemail.com unrecognized by SeaMonkey Mail client

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[romko.b.m]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8
Build ID: 20120312220748

Steps to reproduce:

when I add new account [e-mail] Thunderbird immediately recognizes the server IMAP.GOOGLEMAIL.COM and the port 993. 


Actual results:

SeaMonkey 2.8 does not connect to server and offers incorrect default port 143.
If I introduce manually the correct name of the server IMAP.GOOGLEMAIL.COM and port (same as in Thunderbird) SeaMonkey still will not connect and will not synchronize mail with my google account. 


Expected results:

SeaMonkey should ask my PASSWORD for MyName.gmail.com

Comment 1

[Philip Chee]

In your account settings for gmail, what are the Security settings set to?

Comment 2

[romko.b.m]

In my gmail account at gmail.com 2-step verification is set to OFF.
In my Thunderbird account for gmail Connection security for IMAP is set to SSL/TSL, 
Authentication method is set to Normal password.
My point is that Thunderbird and Opera does the job pretty well, whereas SeaMonkey can not synchronize with the same setting as for Thunderbird or Opera even if I put Connection security as None.
But SeaMonkey can SEND messages through my gmail account, and it demands password while connecting to SMTP at google, as it should. But it cannot even reach the stage when it should ask for the password while trying to connect to IMAP at google!

Comment 3

[Philip Chee]

Do you have a firewall or antivirus that scans incoming/outgoing mail? perhaps it's blocking SeaMonkey. Try going through your firewall/AV settings.

Comment 4

[romko.b.m]

Yes, I have. I'll try tomorrow. But I believe that will not help, because Seamonkey have already been allowed all traffic. And I've been using Seamonkey for a lot of time to connect to my another account, not gmail. And if it were the firewall that blocks Seamonkey, then Seamonkey would not connect to nothing, whereas actually it connects to SMTP at Google, and can not connect to IMAP alone. I think the reason is in Google. It does not like Seamonkey, I guess.

Comment 5

[Philip Chee]

Strange. We actually share the same account settings code with Thunderbird, so if the settings are identical SeaMonkey should work with Google IMAP identically with Thunderbird. FYI I am using Google gmail IMAP with SeaMonkey and I don't have problems connecting.

Comment 6

[romko.b.m]

(In reply to Philip Chee from comment #5)
> Strange. We actually share the same account settings code with Thunderbird,
> so if the settings are identical SeaMonkey should work with Google IMAP
> identically with Thunderbird. FYI I am using Google gmail IMAP with
> SeaMonkey and I don't have problems connecting.

Thank you. I will try another occasion in a while. I will inform you about my success or not. Perhaps something occurs within the procedure involving password identification on the part of SeaMonkey. You know, SeaMonkey in its options has no a field to introduce password for IMAP in advance, while Thunderbird and Opera have. I also tried Opera, it connects to google IMAP very well too. Perhaps SeaMonkey will issue next version of the product. I will check my firewall settigs once more, but you see, even when SeaMonkey says in its status line "connected to IMAP.googlemail.com", it can't enter my account to ask for the password.
I will tell you when things change.

Comment 7

[romko.b.m]

(In reply to Philip Chee from comment #5)
> Strange. We actually share the same account settings code with Thunderbird,
> so if the settings are identical SeaMonkey should work with Google IMAP
> identically with Thunderbird. FYI I am using Google gmail IMAP with
> SeaMonkey and I don't have problems connecting.

In meantime the problem has resolved by itself. I have no idea, what was its origin. I did nothing save for, perhaps, changing the Connection security setting from None to SSL/TSL. I has been connecting through PROXY, but I haven't changed that.
Sorry for bothering you. Still, this remains a mystery to me.

Comment 8

[Philip Chee]

I'm going to close this bug, but do reopen this bug if the problem re-surfaces.