> On Tuesday 24 January 2017 14:02:45 Baron wrote:
> > The correct combinations should be:
> >
> > port 25 + TLS
> > port 465 + SSL
> > port 587 + TLS
> >
> > Cheers
>
> Might also need to set authentication to "Login"

	Nope; doesn't work with any combination of suggested ports, protocols or authentication methods.  I still get the

"Unrecognized transport protocol. Unable to send message."

message.  Judging by the quickness of the message's appearance, I suspect that kmail is not getting to the point of attempting to connect to the server.

	It almost seems like there is some prerequisite package or service missing, but all of kmail's required libraries and packages are installed.  I've attached the list of installed services that are NOT running in hopes that someone will spot something helpful.

Leslie

-- 
Best Regards:
            Baron

-- 
		A Caution to Everybody

	Consider the Auk;
	Becoming extinct because he forgot how to fly, and could only walk.
	Consider man, who may well become extinct
	Because he forgot how to walk and learned how to fly before he thinked.

-- Ogden Nash

NetworkManager-dispatcher
NetworkManager-wait-online
YaST2-Firstboot
YaST2-Second-Stage
accounts-daemon
apparmor
atd
atop
autofs
autovt@
autoyast-initscripts
avahi-dnsconfd
blk-availability
btrfsmaintenance-refresh
clamav-milter
clamd
console-getty
console-shell
cups-browsed
dbus-org.freedesktop.Avahi
dbus-org.freedesktop.nm-dispatcher
dbus-org.opensuse.Network.AUTO4
dbus-org.opensuse.Network.DHCP4
dbus-org.opensuse.Network.DHCP6
dbus-org.opensuse.Network.Nanny
debug-shell
dm-event
dmraid-activation
freshclam
getty@
getty@tty7
gpm
grub2-once
ipmiseld
iscsid
iscsiuio
kexec-load
klogd
lunmask
lvm2-lvmetad
lvm2-monitor
nfs
nfs-blkmap
nmb
ntp-wait
nut-monitor
nut-server
purge-kernels
rpcbind
rsyncd
rtkit-daemon
rxapid
serial-getty@
serial-getty@ttyS0
serial-getty@ttyS1
serial-getty@ttyS2
smb
svnserve
systemd-bootchart
systemd-cryptsetup@cr_ata\x2dST9500424AS_6WR1CPW7\x2dpart1
systemd-cryptsetup@cr_ata\x2dST9500424AS_6WR1CPW7\x2dpart2
systemd-cryptsetup@cr_ata\x2dTS128GMSA370_D263650578\x2dpart1
systemd-cryptsetup@cr_ata\x2dTS128GMSA370_D263650578\x2dpart3
systemd-cryptsetup@cr_ata\x2dTS128GMSA370_D263650578\x2dpart4
systemd-cryptsetup@cr_ata\x2dTS128GMSA370_D263650578\x2dpart5
systemd-fsck@dev-disk-by\x2duuid-66d03763\x2dcc62\x2d4a78\x2da27c\x2dbf7091f4e6ca
systemd-fsck@dev-disk-by\x2duuid-8cb8a7fc\x2d1359\x2d4282\x2d8c7f\x2dd6b3a3815328
systemd-fsck@dev-disk-by\x2duuid-ec465747\x2dfa60\x2d407e\x2da8ff\x2d01adf99a9600
systemd-fsck@dev-mapper-cr_ata\x2dST9500424AS_6WR1CPW7\x2dpart1
systemd-fsck@dev-mapper-cr_ata\x2dST9500424AS_6WR1CPW7\x2dpart2
systemd-fsck@dev-mapper-cr_ata\x2dTS128GMSA370_D263650578\x2dpart3
systemd-fsck@dev-mapper-cr_ata\x2dTS128GMSA370_D263650578\x2dpart4
systemd-fsck@dev-mapper-cr_ata\x2dTS128GMSA370_D263650578\x2dpart5
systemd-nspawn@
systemd-timesyncd
tuned
upower
user@0
user@1000
winbind
wpa_supplicant
xinetd
ypbind