If you go to Yahoo! Mail, after signing in, you can't check your mail. As with early builds of Communicator 4.51, you get Yahoo!'s "Re-login" error message telling you that your login has expired.

Using a WinNT 3/15 build I was able to get a yahoo account and when I logged in, the single signon code asked me if it wanted to remember my id and password. I told it "yes" and the next time I logged in, I didn't have to enter it. So, I don't know what the problem is unless it is optimized vs. debug build. Steve knows the most about this.

I'm confused. If I'm interpreting cpratt's description correctly, he's getting a relogin message from 4.51. I registered using a 4.5x browser but then when I tried to login (still with 4.5x) I kept getting a relogin error message. It said that either it's been eight hours after I logged in (it certainly wasn't) or I wasn't accepting cookies (I certainly was). So there's either a yahoo problem or a 4.5x problem here. Nothing yet to do with seamonkey and certainly nothing to do with single signon. If I'm interpreting karnaze's comment correctly, he tried it under seamonkey and single signon did just what it was supposed to do -- it remembered his username/password for him so he didn't have to enter it for the next session. So it appears as though he is saying there is no problem and just wanted me to look at it to confirm. So if I'm interpreting both cpratt and karnaze correctly, there really is no problem and I'm closing this as INVALID. If I'm wrong and you can give me more specific details demonstrating a problem, then please re-open this report.

Let me try to simplify my description. 1. Go to http://mail.yahoo.com. 2. Sign in. 3. Click on Check Mail. 4. Results: * Seamonkey: "Your login has expired. Re-login." * 4.51 (late builds, but not the final one): Same message. * 4.51 (final build): Works as expected. * 4.5: Works as expected. * IE 4.01: Works as expected. We've seen this problem before - it was one of the bugs that kept 4.51 from shipping towards the end of that project. I'm guessing the engineer who fixed it might have some insight into what's going wrong in seamonkey.

The results I reported before (relogin error message) was indeed with an early version of 4.51 so this is consistent with what cpratt has just reported about that browser. So I just tried it using the latest seamonkey (M3) build. I submitted my log-in form. I got the single-signon message and I replied that I wanted my user-name and password saved. Then I got right into the yahoo e-mail program. So I am seeing exactly what karnaze reported. So far everything works and we are even past the bug that I noted for the 4.51 browser. Now, following cpratt's instructions, I clicked on check-mail. And, indeed, I got the error message that he noted. But at this point we are not submitting a username/password (so it has nothing to do with me) and, in fact, we are not even submitting a form (so it has nothing to do with karnaze). I have no idea what it has to do with so I'm assigning it back to cpratt to determine that. Sorry to have to do this, but I have no idea who the engineer was that made the fix in 4.51.

Currently, bugsplat is down and I can't find the original bug in bugzilla. Until I can, this is stuck in the water...

marek - can you remember how this was fixed in 4.51? thanks, cpratt.

This was fixed for final 4.51. Looks similar to: http://bugzilla.mozilla.org/show_bug.cgi?id=7456 pollman...same issue?

QA Contact update.

I am able to reproduce this bug still. To see the error page I did: 1) Go to http://mail.yahoo.com 2) Enter login id and password, click submit The page I got said: "Your login session has expired. Re-Login..." Henceforth, if I go to http://mail.yahoo.com I receive this page instead of the page that allows me to enter login and password. It would be really nice to look at how this was fixed in 4.51 - don't think it's directly related to bug 7456 though. Does anyone know the original bugsplat bug # for the bug in 4.51?

In the 19991216xx M12 and later M12 builds (eg 1999121710 on Linux) I haven't been able to reproduce this. There seems to have been an intermittent cookie problem that prevented this from working...

Try deleting your cookies.txt file and restarting the browser. I had to do that because when I migrated my profile over from Nav, it got a good cookie. I think we might be getting or sending the cookie wrong?

Okay... I just deleted my cookies.txt file and tried again and couldn't reproduce this bug with today's build.... Hmm...

I just completely clobbered ~/.mozilla, restarted, recreated a profile and tried again and was *not* able to reproduce this. It's more than possible that I had some outdated files (cookies, registry, prefs) that were causing this. I'm agreeing with cpratt here and marking this worksforme. Thanks!

Updating QA contact.

Verifying works for me.