On Friday, 26 April 2013 15:13:19 CEST, Mike Cardwell wrote:
It looks to me like the problem is the SMTP server is advertising two available authentication modes, and Trojita is trying to use one that isn't advertised.
Correct, that's a bug. Filed as [1].
If enabling STARTTLS fixes this, it will only be because of a side affect that the LOGIN authentication method is advertised, only when the channel is encrypted.
In IMAP, this is a very common configuration and it's made much more obvious through the LOGINDISABLED capability. When Trojita sees that, it will automatically activate STARTTLS even though the user has not explicitly asked for encryption. I speculated that the SMTP protocol might work in a similar manner -- the examples in RFC 4954 [2] show this behavior with the AUTH PLAIN not being advertized until after STARTTLS.
If there are no supported authentication methods available, then Trojita should warn about this and then close the connection. It shouldn't attempt to use one that hasn't been advertised. I'm not aware of any SMTP servers that support an authentication method that they do not advertise in their EHLO response, and I suspect it would be a protocol error if they did.
Agreed on all points. The SMTP library we use in Trojita is extremely limited, rather buggy, and should be replaced. This takes time, though. In the meanwhile, enabling STARTTLS could be a good workaround. With kind regards, Jan [1] https://projects.flaska.net/issues/622 [2] http://tools.ietf.org/html/rfc4954 -- Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
