[pskmail] Re: No more client stomping!
- From: Bernard Dekok <kc9sgv@xxxxxxxxx>
- To: pskmail@xxxxxxxxxxxxx
- Date: Wed, 9 May 2012 07:46:58 -0500
It would be nice if we could talk about a stable versions of PSKMail client
and server at Dayton Hamvention 2012... 18 to 20 May 2012.
Password issues and all corrected.
At least no one will be able to "prove" that PSKmail doesn't work....
On Wed, May 9, 2012 at 6:10 AM, Steve <stevez@xxxxxxxxxx> wrote:
> Hello all,
>
> The new 1.6.5 (noted Rein has now bumped the archive version for dummies
> like me who got confused) server code seems to fix the server talking over
> the client. I just experienced a number of pleasant connects, send mail and
> disconnect sequences. It's a beautiful thing to behold when it works like
> it does now. Thanks for the new server Rein.
>
> Now, for the "sorry, wrong password" problem, and other notes.
>
> 1. I remember the server used to ask you to "pls update database" if it
> didn't know who you were. Now it just says "cannot find any mail". Now, I'm
> not sure if this is just a language thing, but this does not seem like an
> error of any kind. It's telling me (English as my first, and unfortunately
> only, language) that I have no email. My intuition is to just stop here as
> I don't have any email to read.
>
> 2. I need to hit the "update server" button twice for it to get all
> packets sent. You're probably thinking that I didn't wait long enough, but
> I swear that when I hit the button once, the client sends data 1,2,3 and
> only when I hit it a second time will it send data 4,5,6. The client/server
> do the normal two-and-fro keep-alive if I don't hit it a second time.
>
> 3. Sometimes the "update database" button won't work at all. I can press
> it to my hearts' content after a connect and it just won't send the data -
> the client won't even try. It's like the button is ignored.
>
> 4. After a database update, the client never displays a "database updated"
> in the terminal window - even though the server log shows it happened.
>
> 5. I know how to get yourself stuck in the "sorry, wrong password" tangle
> every time. First, connect and do an update database. Do not do a
> :SETPASSWORD. The entry in the rflink_users.db file will have NONE for the
> session/aprs password. Now disconnect, and reconnect. Doing a :SETPASSWORD
> will never be allowed. You MUST do your initial update database, and
> :SETPASSWORD during the first connected session or you're screwed for good
> on that server. Yep, even if you go and delete the session password in the
> client. You will never be able to use that server unless the sysop
> intervenes.
>
> 6. I'm seeing problems in 1.5.8 client not displaying mail in the headers
> list, etc. I wonder if that's just my JVM or some such (jre1.6.0_20)?
>
> I know I've made some bold claims above - I'd really like to be proven
> wrong on all of them!
>
> Steve.
>
>
Other related posts:
