[Pine-info] new member but not a new user has some questions

[loninappleton]

The other thing I can' seem to do is just answer to the group so S.A. 
Birl is on the list here.


The problem with PC Pine-- actually several problems which are driving 
me straight up the wall -- started with a change from Win98se to Windows
2000 Pro.

I have since changed disks back to Win98 so I at least have access to 
mail.


Graham from Alpine gave the following change to inbox path (where all
these problems seem to come up)

{pop.servername.net/ssl/novalidate-cert/user=myname}inbox

In Pine 4.64 on _Windows pro 2000_ many boxes pop up for
data entry.  One of those is for Insecure User.


But the larger problem is editing Pine 4.64 on Windows 2000 Pro at all.
Duplicate strings stay in the path _after_ editng them out and so there's
all sorts of connecting errors much less the Insecure User error message.


I'm real irritated.

In editing the inbox path, I tried to turn off the boxes and just use
the commands on lower screen.  I used 'delete' and then 'add' to get the
inbox path straightened out but none of these worked-- the previous
string stayed in there.  This appears to be a problem with the
program running with what it figures is an insecure user.

So I can't get there from here.

Please don't give any code.  I don't know how to put it in any way.


The inbox path under Windows 98se which always works with no Insecure
User or other errors is:

{pop.servername.net/NOTLS/user=lon}inbox


This has worked for me for years.

How is Windows 2000 Pro different?  How do I fix it?


By the way, the ISP has moved and will be no help.  The point is
everything works under Win98, the same program fails under Win2k.






On Mon, 22 Jan 2007, S.A. Birl wrote:


> On Jan 21, 2007, loninappleton (nospam-lon at athenet.net.ns) typed:

>

> lon:  Hello,

> lon:

>

> [snip]

>

> lon:    I'm trying to get rid of screen prompts which say

> lon:

> lon:       HOST pop.myisp.net [INSECURE] user:myusername Enter Password

> lon:

>

>

>

> Ive read your post 3 times, and cant say I have any insight on what

> could be causing your problem.

>

> I think, for starters, you should create a shortcut to your Pine.exe

> and append to said shortcut:

>

> 	-d flush,timestamp,imap=4,tcp,verbose=6

>

> Execute the shortcut and do your thing.  The file pinedebg.txt should

> give more information as to what's going on.

>

>

> Thanks

> Birl

>

> ---

> Please do not CC me responses to my own posts.

> I'll read the responses on the list.

>

> _______________________________________________

> Pine-info mailing list

> Pine-info at u.washington.edu

> http://mailman1.u.washington.edu/mailman/listinfo/pine-info

>