The update server procedure
for test. You can invoke it by
menu->link->update server or just crtl-u:
Failed to get your email, pse upload correct email
Updated database for PA0R-4
Session password changed!
The 'setpassword' and
'update server' routines have been merged.
To change a password just
set a new one on the client and re-update the server.
The server caches the mail
record until you reset it (with ctrl-r).
**Test versions of server
(1.8.0) and client (2.0.14) implementing this
have been uploaded to the
Why all this hassle with
PSKmail has been
optimized for narrow band operation, which means it has
to be very efficient
with its protocols.
To prevent the client
from having to upload the mail data record again for
every session, the
server caches the data.
The drawback of this
scheme is that everybody connecting the server using your
callsign can get your
mail (userid and password are cached on the server).
To prevent this the
client and server exchange session cookies, which only
succeeds if you have set
the right secret password on the client.
The servers do not
exchange mail records, and there is no central database.
When you are very
paranoid, you could set a different password for each server