Closed
Bug 323785
Opened 20 years ago
Closed 20 years ago
Will not allow access to AIM mail
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 323283
People
(Reporter: njgorra, Assigned: mikepinkerton)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060116 Camino/1.0b2+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060116 Camino/1.0b2+
When attempting to log onto AIM mai, the following screen appears: has happened with the last few nightly builds of Camino
http://mail.aol.com/Help/detail_misc_sysrequirements.aspx
Reproducible: Always
Steps to Reproduce:
1.log onto AIM. com.
2.click on Mail button
3.Error screen appears
Expected Results:
Should load access to Aim. mail
Comment 1•20 years ago
|
||
INVALID.
This is AOL's problem, not Camino's. Please complain to AOL.
Smokey or Sam, if either of you thinks this should be moved to Tech Evangelism, please feel free.
cl
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 2•20 years ago
|
||
Chris: Did you even verify this bug before closing?
Chip: I don't see the error at all. With Camino 1.0b2 I go to aim.com, click on the Mail icon and it asks me for my screen name and password. When I give it my screen name and password, it logs me into AIM mail.
What exactly are your steps to reproduce?
Comment 3•20 years ago
|
||
And an important, if perhaps obvious question: have you made absolutely sure that you are not, in fact, blocking cookies from aol.com?
I can confirm this bug. When I go to aol.com and click on the AOL & AIM Mail link, I get the error right away. When I go to aim.com and click on the AIM Mail link, I can redirect fine to the login/password page, but when I enter my info, I get the error.
Tested on 1.0b2 and it works fine.
Comment 5•20 years ago
|
||
I can confirm this too with the latest nightly (but I'm not going to confirm the bug yet). This works fine with 1.0b2 but not with builds after it (though I haven't checked them all). I'm guessing that AOL is doing browser sniffing and picking out 1.0b2. (Which, really, is good they care about us.) This bug may become fixed when 1.0 is released.
There's a chance this is an actual regression and I'll check for that soon.
Comment 6•20 years ago
|
||
*** This bug has been marked as a duplicate of 323283 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•