Hmm, actually, that's what I do all the time, I just never saw it as anything but normal.
a. Wildly counter intuitive (in effect I'm sending the same password twice to the same agent).
Logically, maybe, yes. Physically, though, the two logins are probably two different server programs (say, pppd calling login, and the pop server (Telinco)) checking the same password database. Note that TCP/IP doesn't generally require authentication, it's applications that do.
b. Terminologically dubious (is my ISP password a Pop 3 password?).
See above.
But there may be design decisions here which I'm completely unaware of.
Maybe, but I don't think that any of them are part of Celeste - just the server software. If netscape doesn't require you to enter a password to access your mail, then it's probably cheating (assuming the password is the one it sent to the dialer, and getting lucky). I for one, access my mail on pop server belonging to ISP A while connected through ISP B, so if I find Netscape let's me access my mail without entering my password, I'll get pretty mad ;-) I'd check again that you don't have a profile defined where you once did enter your password.
Daniel John Hinsley jhinsley@telinco.co.uk wrote:
Steve Elkins wrote:
John Hinsley jhinsley@telinco.co.uk wrote:
[about problems using Celeste]
Do I need to do anything to the PopSocket?
I've never had to.
When Celeste requests my password, is it looking for a higher level authentification than my (ISP style) username?
Just making sure, should the last word of your question be "password" instead of "username"? I supply the same username and password (and they are not the same strings) to Celeste that I supply to Netscape. All goes well.
But I'm only guessing at what your problem might be.
Well, I'm only guessing too!
I should point out that this in on Linux, so there might just be other issues floating about (usually are!).
AFAIK. I've never entered anything in the Netscape dialogue strings apart from the name of my pop3 server, the dotted quad of my SMTP server, my email address and my user name. So, when using fetch mail in Celeste opens up a "fill in the gaps" asking for my pop 3 password, I was entering my username.
*I've just tried it using my ISP password (the one which wvdial uses) and it works!*
This strikes me as
a. Wildly counter intuitive (in effect I'm sending the same password twice to the same agent).
b. Terminologically dubious (is my ISP password a Pop 3 password?).
But there may be design decisions here which I'm completely unaware of. (After all, Windows and maybe Mac sort of bundle the whole connection routine into one whole.)
But thanks for the guess Steve, it set me off in the "right" direction!
Cheers
John
--
Marx: "Why do Anarchists only drink herbal tea?" Proudhon: "Because all proper tea is theft."
danielv@netvision.net.il wrote:
Hmm, actually, that's what I do all the time, I just never saw it as anything but normal.
a. Wildly counter intuitive (in effect I'm sending the same password twice to the same agent).
Logically, maybe, yes. Physically, though, the two logins are probably two different server programs (say, pppd calling login, and the pop server (Telinco)) checking the same password database. Note that TCP/IP doesn't generally require authentication, it's applications that do.
b. Terminologically dubious (is my ISP password a Pop 3 password?).
See above.
But there may be design decisions here which I'm completely unaware of.
Maybe, but I don't think that any of them are part of Celeste - just the server software. If netscape doesn't require you to enter a password to access your mail, then it's probably cheating (assuming the password is the one it sent to the dialer, and getting lucky). I for one, access my mail on pop server belonging to ISP A while connected through ISP B, so if I find Netscape let's me access my mail without entering my password, I'll get pretty mad ;-) I'd check again that you don't have a profile defined where you once did enter your password.
It's really the difference (I think) between a Mac/Windows way of doing things and a *nix way. On nixes, the dialler is absolutely distinct from the Netscape or whatever application: the emailer doesn't call the dialler (nor does it assume a diallup connection), but will complain if it's not connected. (I guess you could say that this is part of the *nix paradigm: rather than having each program which requires diallup to have it's own dialler, you write one good dialler and everything else can use it.) Thinking of just how complex a peice of software a dialler is, and that getting Celeste to grab the password from wherever whatever *nix dialler is in use stores it would be a wee bit tricky, I'm not *that* surprised that they wrote it as they did. And it probably also makes it easier to use the same code for different OSs. Even though it does require you to enter the password twice (and there may be security implications in this).
But no *nix email software will ask you for your password unless, I guess -- you can't do this with the 4* series of Netscape -- you're trying to grab mail from a server not belonging to the ISP you're hooked up to.
Actually, there could be advantages to doing it the Celeste way. It makes for code re-use (Celeste can do without a seperate *nix fork) and it could make putting into place the facility to grab mail from a variety of ISPs easier.It just seems rather wierd.
Cheers
John
On Tue, 31 Jul 2001 04:31:24 +0100, John Hinsley jhinsley@telinco.co.uk wrote:
But no *nix email software will ask you for your password unless, I guess -- you can't do this with the 4* series of Netscape -- you're trying to grab mail from a server not belonging to the ISP you're hooked up to.
I never use the POP3 account my dial-up (or cable) ISP provides, and haven't for years. I haven't even configured a password for my cable modem providers POP3 account...
So for me, having an email client ask me for my POP3 password makes perfect sense. I use a laptop for everything, and I connect it to the net from a wide variety of networks and ISPs, but always to the same POP3 account.
Later, Jon
-------------------------------------------------------------- Jon Hylands Jon@huv.com http://www.huv.com/jon
Project: Micro Seeker (Micro Autonomous Underwater Vehicle) http://www.huv.com
squeak-dev@lists.squeakfoundation.org