Re: Getting started with paclink-unix


Keith Williamson
 

Hi Basil,

I deleted the rmsgwprox* files in ~/tmp and ran wlgw-check.sh -g CN88tu. Here is the resultant output from show_log.sh:


Start: 2019 06 03 17:01:54 PDT: grid: CN88tu, debug: , GW list refresh: true, connect: true, cron: false

Chan Conn
RMS GW    Freq Dist Name Index Stat Stat Time  Conn
KF7FIT-10   223780000 0 NET-21       Unqual n/a  0   0
N7NIX-10    144910000 0 NET-16       Unqual n/a  0   0
K7KCA-10    440125000 3 NET-45          n/a  to  0   0
KE7KML-10   223780000 3 NET-21       Unqual n/a  1   0
AF4PM-10    145690000 4 NET-14          n/a  to 22   1
AF5TR-10    145690000 11 NET-14          n/a  to 21   1
AE7LW-10    145050000 16 NET113          n/a  to 22   1
AE7LW-10    440950000 16 NET-46          n/a  to  1   0
KD7X-10     145630000 16 NET-13          n/a  to 21   1
KI7ULA-10   145050000 16 NET113          n/a  to 22   1
W0QJM-10    145630000 19 NET-13          n/a  to 22   1
WA7GJZ-10   145630000 19 NET-13          n/a  to 22   2
WA7GJZ-10   145630000 19 NET-13          n/a  to 22   2
NG2G-10     144990000 26 NET-11          n/a  to 21   1
W7ECG-10    144930000 28 NET-17          n/a  OK 49   3
KC7OAS-10   144950000 33 NET-12          n/a  OK 26   3
KG7WFV-10   145630000 35 NET-13          n/a  to 21   1
W7BPD-10    145630000 35 NET-13          n/a  to 22   1
W7BPD-11    145630000 35 NET-13          n/a  OK 33   2
Finish: 2019 06 03 17:07:50 PDT: Elapsed time: 5 min, 56 secs,  Found 16 RMS Gateways, connected: 3
pi@Compass:/usr/local/src/auto-rmsgw-find $

With respect to incoming messages ending up in /usr/local/var/wl2k/output/, I don't know how to fix that. I thought that postfix was configured correctly by the scripts.

Is it possible that building the latest paclink-unix broke the postfix config?

cd /usr/local/src/paclink-unix
git pull
./build-all.sh

Thanks,

Keith


On Mon, Jun 3, 2019 at 4:48 PM Basil Gunn <basil@...> wrote:

First figure out how to ssh into your RPi from the same machine you use
for email. I really prefer a cut & paste of console output rather than a
jpg.

> I think all of the infrastructure is in place and working. I just can't get
> email working. I followed the instructions for configuring Claws. I chose
> the option to use it for my winlink email client (KF7DRV@...). When
> I get to the last screen where I save the config, Claws complains that it
> can't connect to "IMAP server: localhost: 143".

Please send the console output of:
netstat -tulpn | grep 143

You may have to reboot your machine after the paclink-unix install to
start the IMAP server.

> On a separate note, I have tested wl2kax25 to w7ecg-10, kf7vol-10, and
> kc7oad-10. They all answer up fine and terminate normally. However, when I
> run "wlgw-check.sh -g CN88tu", it doesn't appear to honor the -g argument.
> The gateway list it tests appears to be the default list. Here's the output
> from show_log.sh:

I couldn't replicate this problem.
There is a mechanism in rmslist.sh to not interrogate the Winlink server
too frequently. If you have ever run rmslist.sh without any arguments
that may be what you are seeing. Try deleting the rmslist.sh output
files & running wlgw-check.sh again

cd
cd tmp
rm rmsgwprox.*

Because you sent a jpg of the console I couldn't really tell if there was
anything else in the show_log.sh output.

/Basil



Join udrc@nw-digital-radio.groups.io to automatically receive all group messages.