After discussing this with the Moto Email Client dev team, they've concluded that although RFC 2595 does describe in more detail the SASL AUTH PLAIN authentication mechanism, that RFC is specifc to IMAP, POP3 and ACAP. It's title is, after all "Using TLS with IMAP, POP3 and ACAP".
As far as they are concerned, RFC 2554 "SMTP Service Extension for Authentication" is the only RFC that is applicable in this situation because the problem is specific to SMTP, and does not involve IMAP, POP3 or ACAP protocols specifically. So until RFC 2595 supercedes or replaces RFC 2554 as it applies to authentication mechanisms, they are not planning to make any changes to the email client application. In other words, they are going to send 'AUTH PLAIN\n', omitting the optional '[initial response]' parameter. The client will expect a reply of '334' from the server before sending the plaintext password, as described in RFC 2554. Is there anything else I can do to convince either side of this discussion to make the changes that would allow the Motorola Email Client to interoperate with Courier mail servers that require authentication for SMTP? Thanks for listening, jason ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
