9 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Sqwebmail bug?
FromSent OnAttachments
EndaJul 2, 2008 1:58 pm 
Sam VarshavchikJul 2, 2008 3:22 pm 
EndaJul 2, 2008 3:45 pm 
Sam VarshavchikJul 2, 2008 4:31 pm 
Roger B.A. KloreseJul 2, 2008 6:24 pm 
EndaJul 3, 2008 12:02 am 
Enda CronnollyJul 3, 2008 12:11 am 
Sam VarshavchikJul 3, 2008 4:02 am 
EndaJul 3, 2008 7:08 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] Sqwebmail bug?Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jul 2, 2008 3:22:52 pm
List:net.sourceforge.lists.courier-sqwebmail

Enda writes:

The sqwebmail login has a checkbox which is checked by default, which says "disable logins from other computers while I am connected".

There's no such message on the login screen. The only two options are "Restrict access to your IP address only (increased security)", and "Accessing from a public machine (enables short idle timeout)".

To me this means, if I am logged in, nobody else can log into my account from another IP address. Yet, I can do exactly this, but logging in from a second IP address logs out the person currently logged in on the first IP address.

That's exactly how it should work. HTTP is a stateless protocol. There is no mechanism by which a web server can possibly detect that you have closed your web browser. Therefore, if a login request is received fro a different machine, the choices are:

1) To terminate the older login, and accept the new one.

2) To refuse the new login request until a lengthy timeout period has expired, without receiving any HTTP request for the active login session. If your PC crashed, you had to reboot, and were assigned a new IP address by your Internet provider -- tough luck, wait a few hours before you can read your webmail again.

So, which one makes more sense to you?