[pskmail] Re: FW: Re: Problem With Connection Reliability on New VHF Server
- From: "Dan Ozment" <dan@xxxxxxxxxx>
- To: <pskmail@xxxxxxxxxxxxx>
- Date: Mon, 27 Feb 2012 10:56:56 -0500
Thanks for the info. It is looking much better this morning. I did a more
testing Initially, I was still getting the "wrong password" message when I
tried to send or retrieve email. I wondered if I had corrupted the
configuration during all of my testing. So, I tried the following...
1) I renamed the configuration.xml file on the client
2) I copied the rflink_users.db.template file to rflink_users.db. (I believe
I had accidentally added records with null or spaces as values, and I was
trying to clear those out).
3) I restarted the server and client, and reconfigured the settings on the
client.
After that I was able to send a message, retrieve headers, and retrieve
messages (SUCCESS!).
We tried again from another client (after removing the configuration.xml file
on it as well), and had the same result initially. He tried to send another
file, and we never saw it come across to the server. After several tries he
once again got the "Sorry, wrong password" message. What could cause that?
Should we continue to try to send when it happens?
This other user has had a situation where he would try to send a message, and
we would see old messages coming across. He once sent a message with an
invalid email address (he left off the domain name). The server replied that
it wasn't a properly formatted message, and he got the response. He cleared
his outbox multiple times, but this message kept repeating. We noticed files
in the Outbox, Outpending, and Pending folders in his /user/username/pskmail
directory. We deleted those files, and that seemed to stop the send attempts
with the bad email address.
-----Original Message-----
From: pskmail-bounce@xxxxxxxxxxxxx [mailto:pskmail-bounce@xxxxxxxxxxxxx] On
Behalf Of Rein Couperus
Sent: Monday, February 27, 2012 2:18 AM
To: pskmail@xxxxxxxxxxxxx
Subject: [pskmail] Re: FW: Re: Problem With Connection Reliability on New VHF
Server
Dan,
the ARQ system also works if there is no info for transmission. This is
necessary because the system is quasi full duplex... if there is noo traffice
for a certain period the server will disconnect.
You have to do the server update only 1x per server, the info is cashed in the
data base.
The password is an extra session password, which you set in the user data in
preferences.
You have to explicitly set it after you update the mail record, as it uses your
pop password for verification (the server wants to know it is you setting the
password).
You set the password with entering :SETPASSWORD. Wait until you have the
authorization OK from the server....
You are doing well...
Rein EA/PA0R/M
>Maybe I'm over-analyzing, then. So, the back and forth chatter is ok? Not
>being familiar with the application I had suspected the chatter to only happen
>occasionally or when I am telling it to do something.
>
>I just did another test.
>
>Ping - successful
>Beacon - successful
>Connect @ PSK500 -successful
>Update Server - successful
>Get IAC Forcast -successful
>Send Email - Sorry, wrong password
>QTC - Sorry, wrong password
>Get Fleetcodes - successful
>
>
>The update server is successful probably no more than 50% of the time. I have
>deleted the user from the database on the server and did an update from the
>client. Sometimes it works. Sometimes it doesn't. I have successfully sent
>email. Sometimes it work, other times I get the "Sorry, wrong password"
>message.
>
>Can you tell me which password is not being accepted? The SMTP password on the
>server is the same as when I started (and I have sent email successfully). The
>POP password in the client is correct.
>
>I appreciate your help, and I apologize if I'm asking questions I should be
>able to answer myself. The application is very interesting, and we're excited
>about being able to offer it over VHF in our area for general use and for ARES
>use.
>
>Dan
>
>
>
>
Other related posts:
