Bug 1073975 - Sending messages with kmail2 impossible
Sending messages with kmail2 impossible
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Applications
Current
Other Other
: P5 - None : Critical (vote)
: ---
Assigned To: E-Mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-22 09:51 UTC by Freek de Kruijf
Modified: 2017-12-22 13:02 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Freek de Kruijf 2017-12-22 09:51:05 UTC
Using Kontact/Kmail I am unable to send messages.
Sending the messages always fails. Message in Notification widget:
E-Mail sending failed
Failed to transport message. Connection to server lost.
However clicking on the message in the outbox list of messages, shows the message with an error message:
Dictionary was not found. Please verify that you will use a correct dictionary.

This started yesterday after the upgrade to Tumbleweed 20171219, now I am on 20171220, which did not solve this issue.

HELP. I can't use this e-mail system anymore.
Comment 1 Luca Beltrame 2017-12-22 10:00:32 UTC
Are you using port 465 and SSL? (the so-called SMTPS). If so, can you switch to port 587 ("submission") and STARTTLS if your server supports it? It should workaround the issue for the time being.

We are aware of this and  we are currently investigating how to fix it.

See the upstream reports:

- http://bugs.kde.org/387926
- http://bugs.kde.org/388068
Comment 2 Swamp Workflow Management 2017-12-22 12:10:06 UTC
This is an autogenerated message for OBS integration:
This bug (1073975) was mentioned in
https://build.opensuse.org/request/show/559311 Factory / ksmtp
Comment 3 Wolfgang Bauer 2017-12-22 12:59:53 UTC
The fix is available in the Tumbleweed Update repo meanwhile:
http://download.opensuse.org/update/tumbleweed/

Other people have confirmed that it works.
Comment 4 Freek de Kruijf 2017-12-22 13:02:42 UTC
(In reply to Luca Beltrame from comment #1)
> Are you using port 465 and SSL? (the so-called SMTPS). If so, can you switch
> to port 587 ("submission") and STARTTLS if your server supports it? It
> should workaround the issue for the time being.

Yes, my server does not have port 587, but I changed to 25 with TLS and no authentication. It is in my local network.
Sending to GMail also used 465, but also 25 with TLS and authentication works.
So my immediate problem is solved.