On Thu, 2004-10-28 at 14:49 -0500, Eric Lambart wrote:
> Hello,
> I've moved across the US and am trying to set up a new mail server here
> locally, before migrating me and my users' data from the old system.
> I'm running netqmail 1.05 on Debian with SMTP AUTH and TLS patches,
> among others, and have no trouble connecting to my new server using
> telnet:
OK, I've been continuing to work on this problem. I added my current IP
address as an acceptable SMTP relay source, but Evo still didn't like
it.
But I figured out the problem--my patched qmail-smtpd.c file was sending
250-STARTTLS before 250-(hostname). I don't know if that violates any
RFCs, but Evolution certainly doesn't like it. So I edited the code to
return the 250-hostname message *first*, and reinstalled qmail, and lo
and behold--Evolution is happIER now--but not happy. Even Thunderboid
will now send mail, no problem (it was also choking before).
But now I've got a race condition in Evolution... and it appears to be
in the UI. When I ask Evo to "Check for Supported [smpt-auth] Types",
it presents me with the certificate from my server, and asks for my
approval. Thrilling! But at this point Evo is hosed.
Here is a screenshot:
http://www2.nomeaning.net/temp/evo_auth_problem.png
The problem is that I cannot click either OK or Cancel for the
certificate. If I press Enter, the dotted line inside the Cancel button
flashes, but no other response is recognized--clicking, tabbing, etc.
I can't get past this point, and I don't think the problem is on my
server anymore.
I've attached the Evo backtrace.
Any ideas? Fejj, shall I file a bug?