>Hello, here is the smtpd process strace when I try to send a mail, >I don't know if this will help but here it is : It sure looks to me like it is syslogging the connection information somewhere so that might be more useful to look at, but it like what happens is: >read(10, "STARTTLS\r\n", 4096) = 10 >getpid() = 45600 >sendto(8, "<22>Sep 20 15:41:08 postfix/submission/smtpd[45600]: < unknown[192.168.128.253]: STARTTLS", 89, MSG_NOSIGNAL, NULL, 0) = 89 The client starts TLS (good). >sendto(8, "<22>Sep 20 15:41:08 postfix/submission/smtpd[45600]: < unknown[192.168.128.253]: EHLO [172.20.4.195]", 100, MSG_NOSIGNAL, NULL, 0) = 100 The client restarts the SMTP protocol after TLS negotiation (good). >sendto(8, "<22>Sep 20 15:41:08 postfix/submission/smtpd[45600]: > unknown[192.168.128.253]: 250-AUTH GSSAPI", 96, MSG_NOSIGNAL, NULL, 0) = 96 The server says it offers GSSAPI for authentication (good). >sendto(8, "<22>Sep 20 15:41:08 postfix/submission/smtpd[45600]: < unknown[192.168.128.253]: QUIT", 85, MSG_NOSIGNAL, NULL, 0) = 85 The next thing the client sends is QUIT (bad). That suggests to me that it's a CLIENT problem. Like there aren't Kerberos tickets on the client, or the client is getting an error when it tries to get a Kerberos ticket. We use Thunderbird on Unix based systems and it works fine. I do recall that there is some complexity with getting the correct GSSAPI library to work on Thunderbird, but I do not remember the details there because it has been years. I'd start your investigation there. --Ken ------------------------------------------ Cyrus: SASL Permalink: https://cyrus.topicbox.com/groups/sasl/T1e24816c0d686c81-M8cee1eb000ce4e1b3335bef9 Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription
