On 05/20/16 16:47, Samuel Sieb wrote:
What difference will that make? It will still be the same software
and it seems to be more of a configuration issue.
.
I believe applications provided by dnf can have changes that may not
exist when obtained from other sources?
In order for you to find out what command is causing the trouble, you
can use stunnel (you will probably need to install it). Put the
following lines in a file called stunnel.conf:
foreground=yes
syslog=no
[pop3]
client=yes
accept=localhost:110
connect=mail.wildblue.net:995
As root, run "stunnel stunnel.conf". Now, set Balsa to use
localhost:110 as the incoming mail server. Start wireshark and listen
to the localhost interface with the filter rule "port 110". Tell
Balsa to check for emails. Hopefully you get the same error message.
Right-click one of the packets and select "follow tcp stream". You
should now see the conversation between Balsa and the server.
--
Yes I will try this. It appears that stunnel is already installed in F-23.
Thanks,
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-23/64bit LINUX XFCE POP3