Create Task
Maniphest T6664

IMAP account log in is not always equal to email address
Closed, ResolvedPublic
Actions

Description

Currently when setting up a new IMAP/SMTP account, the email address is not always equivalent to the log in credentials. For example, the address may be foo@bar.com but the log in username is just foo.

Currently the account dialog only asks for the email address and uses this for IMAP and SMTP log in. Providing the correct login (e.g. "foo") works for authentication, but then sent emails have an invalid (or non-existent) from address, instead containing only the name of the user.

There needs to be separate inputs for the email address ("identity") and the login credentials.

aseigo created this task.Jul 28 2017, 1:56 PM
cmollekopf moved this task from New to Triaged on the Kube: Bugs board.Aug 31 2017, 12:07 PM
cmollekopf triaged this task as Normal priority.
rutledge added a subscriber: rutledge.May 16 2018, 7:28 AM

In the case of Dreamhost email https://help.dreamhost.com/hc/en-us/articles/215612887#Example_setup_using_a_secure_IMAP_connection the username should be the full email address. E.g. my working mutt config has

set imap_user = "s@ecloud.org"
set folder = "imaps://sub4.mail.dreamhost.com/INBOX/"
set spoolfile = "imaps://sub4.mail.dreamhost.com/
set smtp_url = "smtp://s@ecloud.org@sub4.mail.dreamhost.com:587"

but I'm not quite sure how to translate that to a working kube config. BTW if anybody wants to test with a dreamhost account, I can make you one. I have several domains there.

It would be nice if mail.ecloud.org would work, but this page says there are problems with that: https://help.dreamhost.com/hc/en-us/articles/214918038-Email-client-configuration-overview "In the past, it was possible to use mail.example.com to connect (where example.com is your actual domain name). Due to how modern mail clients handle security, this is now NOT recommended as it may throw connection errors." So, maybe that's worth figuring out. Thunderbird managed to get this right, so that I didn't have to remember / look up the sub4.mail.dreamhost.com server that it gets redirected to.

$ ping mail.ecloud.org
PING mail.ecloud.org (69.163.253.135) 56(84) bytes of data.
64 bytes from homie-sub4.mail.dreamhost.com (69.163.253.135): icmp_seq=1 ttl=49 time=156 ms

Also, why is there no log in the logview? I want to see what it actually tried to do, not just the dumbed-down "Failed to connect to server" and "Host not found" (which is wrong anyway, it's not a DNS lookup failure).

rutledge added a comment.May 16 2018, 7:46 AM

Oh it started working after restarting kube, with these addresses:

imaps://sub4.mail.dreamhost.com:993
smtps://sub4.mail.dreamhost.com:465
cmollekopf closed this task as Resolved.Jul 26 2018, 12:40 AM
cmollekopf claimed this task.
cmollekopf added a subscriber: cmollekopf.

A separate field for a username has now been implemented (will appear in the next builds, probably tomorrow).

@rutledge:

  • Yes, we're not dealing well with changing configurations because the resources only load them when starting.
  • I don't know whether the proxy mechanism works or not, or what the exact error would be if it doesn't.
  • The logview has now been renamed to "Notifications" to clarify that expectation. It's never going show actual logs. The only mechanism for logs that we have right now is debug messages on the console, to make it more verbose use "sinksh trace on", before running kube from the console.