Can't send messages with Fastmail
Closed, ResolvedPublic

Description

Messages get stuck in Outbox. Works fine with Kolab Now, but not FM.

jopetersen edited projects, added Kube; removed Kube: Bugs.Mar 27 2018, 11:24 PM
jopetersen edited projects, added Kube: Bugs; removed Kube.Mar 29 2018, 12:56 PM
cmollekopf moved this task from New to Confirmed on the Kube: Bugs board.Apr 3 2018, 9:06 AM
cmollekopf triaged this task as Low priority.
cmollekopf added a subscriber: cmollekopf.

fastmail and curl don't mix right now. I don't know right now why fastmail claims that the credentials are incorrect.

cmollekopf closed this task as Resolved.Apr 3 2018, 9:14 AM
cmollekopf claimed this task.

Nevermind, after generating a new app password (mail, calendar, contacts) it works. Seems to have been a problem on the fastmail side.

Please try generating a new app password in the fastmail webinterface and use that from kube.

Let me know if the problem persists.

In my case everything but Kolab Now works. Gmail won't work, nor Fastmail.

cmollekopf reopened this task as Open.Apr 9 2018, 10:24 AM

At the very least we are not doing very well with reporting what the actual problem is.

Apologies for lack of clarity.

In my instance of Kube there are three accounts, all of which sync mail perfectly fine, however the only account so far which can send email is Kolab Now.

SMTP is configured for Fastmail as per example on setup page, Gmail configured using automated settings.

Messages for Gmail simply get stuck in Outbox with a number 1 by it, and upon clicking 'send now' nothing happens.

Restart Kube, and said emails still remain in outbox

cmollekopf added a subscriber: phedlund.

@phedlund: Is your mail sending problem also on fastmail?

No, I am using mailbox.org. They recommend this setting for smtp: smtps://smtp.mailbox.org:465.

The problem was that we were attempting to use starttls over port 465. I've pushed a fix but a rebuild will have to wait until kde's git mirrors are working again.

cmollekopf closed this task as Resolved.Aug 16 2018, 2:17 PM

The flatpaks and osx images have been updated. This should be fixed now.

Confirmed working. Thanks.