[Evolution] Camel problem: HELO command failed
Not Zed
notzed@ximian.com
Fri, 29 Oct 2004 11:38:47 +0800
--=-JhrlKttvtPmDa2qE4N3F
Content-Type: multipart/alternative; boundary="=-cnQ++R8zjlx1cXaF2rnJ"
--=-cnQ++R8zjlx1cXaF2rnJ
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
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:
>
> $ telnet 66.93.17.126 25
> Trying 66.93.17.126...
> Connected to 66.93.17.126.
> Escape character is '^]'.
> 220 ldap.nomeaning.net ESMTP
> EHLO 192.168.0.33
>
> 250-STARTTLS
> 250-ldap.nomeaning.net
> 250-PIPELINING
> 250-8BITMIME
> 250-SIZE 0
> 250 AUTH LOGIN PLAIN CRAM-MD5
> STARTTLS
> 220 ready for tls
>
> Looks good so far. Well, Evolution won't talk to the server. The first
> thing I've tried to do is set up a new account for this server (SMTP
> only, for now), and set "Server requires authentication" ON. When I
> then click "Check for Supported Types", the UI gives me no feedback
> other than disabling the "Check..." button.
>
> So I shut down Evolution, and did this from the shell:
> $ export CAMEL_DEBUG=all
> $ evolution
>
> When I try to check for supported auth types again, I get this debug
> output:
Don't check for supported auht types or upgrade to 2.0.3.
> sending : EHLO 192.168.0.33
> received:
> CamelException.setv(0xa7c59b8, 2, 'HELO command failed: Unknown')
> sending : HELO 192.168.0.33
> received: 250-STARTTLS
> received: 250-ldap.nomeaning.net
> received: 250-PIPELINING
> received: 250-8BITMIME
> received: 250-SIZE 0
> received: 250 AUTH LOGIN PLAIN CRAM-MD5
>
> (evolution:5808): GLib-CRITICAL **: file ghash.c: line 225 (g_hash_table_lookup): assertion `hash_table != NULL' failed
> { GLib error repeated 7 times... }
> sending : QUIT
> received: 250 ldap.nomeaning.net
> CamelException.setv((nil), 2, 'QUIT command failed: Requested mail action okay,
> completed')
>
> Since *I* know what kinds of authentication are supported, I tried
> setting Evo to use Login authentication. I've tried various settings
> for "Use secure connection (SSL)" (it's not clear if this has anything
> to do with TLS or if it means SMTP over SSL on port 443 or whatever...)
"always" means SSL, "whenever possible" means TLS. We've fixed that in
head already but it missed string freeze for 2.0.
> When I try to send a message from Evo using that server, I also get the
> 'HELO command failed', but Evo *does* seem to understand that my server
> is refusing the unauthenticated sender, because I get a "DATA command
> failed: Requested action not taken: mailbox name not allowed." and a 553
> error in my Camel log. But in this case Camel is still reporting "HELO
> command failed: Unknown" in the log.
>
> Searching the archives for "HELO command failed" only brought up a
> thread from August '02 that seems unrelated.
>
> Questions:
> 1) does the fact that Evo appears to be recognizing the 553 (host not
> allowed) message indicate that the "HELO[EHLO, really] command failed"
> is not a problem? Considering that Evo is subsequently sending an HELO
> after the EHLO fails, it seems this could cause problems with ESMTP.
I don' tknow. some servers have a spastic when they don't understand a
command rather than ignoring it.
> 2) is the situation with "Check for supported types" likely to imply
> that I've still got problems with my SMTP AUTH setup? The lack of any
> helpful feedback from the UI leaves me wondering where the problem is.
2.0.2 has a nasty bug with that.
> 3) somewhat tangential topic--to use STARTTLS (and eventually, IMAP with
> SSL), what certificate do I need to import, and where? I tried
> importing the .pem file that my server is using (as an "Authority"), but
> I'm not clear if I need to create a separate one for the client as well.
Hmm, I think it should happen automatically if you have the right
authority imported wiht the right rights. However i'm not sure if
evolution's ui will let you do that and you'll just get a popup box
asking you to 'use it anyway'.
> P.S. Sometimes the 'HELO command failed:' is followed by something like
> "Operation now in progress" rather than "Unknown"
Maybe its the 'comments in /etc/hosts breaks gethostname()' bug. But i
don't really know on that one. The log looks funny, what about a log of
actually sending mail, and not checking authtypes?
--
Michael Zucchi <notzed@ximian.com>
"born to die, live to work, it's all
downhill from here"
Novell's Evolution and Free Software
Developer
--=-cnQ++R8zjlx1cXaF2rnJ
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.2.2">
</HEAD>
<BODY>
On Thu, 2004-10-28 at 14:49 -0500, Eric Lambart wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Hello,</FONT>
<FONT COLOR="#000000">I've moved across the US and am trying to set up a new mail server here</FONT>
<FONT COLOR="#000000">locally, before migrating me and my users' data from the old system.</FONT>
<FONT COLOR="#000000">I'm running netqmail 1.05 on Debian with SMTP AUTH and TLS patches,</FONT>
<FONT COLOR="#000000">among others, and have no trouble connecting to my new server using</FONT>
<FONT COLOR="#000000">telnet:</FONT>
<FONT COLOR="#000000">$ telnet 66.93.17.126 25</FONT>
<FONT COLOR="#000000">Trying 66.93.17.126...</FONT>
<FONT COLOR="#000000">Connected to 66.93.17.126.</FONT>
<FONT COLOR="#000000">Escape character is '^]'.</FONT>
<FONT COLOR="#000000">220 ldap.nomeaning.net ESMTP</FONT>
<FONT COLOR="#000000">EHLO 192.168.0.33</FONT>
<FONT COLOR="#000000"> </FONT>
<FONT COLOR="#000000">250-STARTTLS</FONT>
<FONT COLOR="#000000">250-ldap.nomeaning.net</FONT>
<FONT COLOR="#000000">250-PIPELINING</FONT>
<FONT COLOR="#000000">250-8BITMIME</FONT>
<FONT COLOR="#000000">250-SIZE 0</FONT>
<FONT COLOR="#000000">250 AUTH LOGIN PLAIN CRAM-MD5</FONT>
<FONT COLOR="#000000">STARTTLS</FONT>
<FONT COLOR="#000000">220 ready for tls</FONT>
<FONT COLOR="#000000">Looks good so far. Well, Evolution won't talk to the server. The first</FONT>
<FONT COLOR="#000000">thing I've tried to do is set up a new account for this server (SMTP</FONT>
<FONT COLOR="#000000">only, for now), and set "Server requires authentication" ON. When I</FONT>
<FONT COLOR="#000000">then click "Check for Supported Types", the UI gives me no feedback</FONT>
<FONT COLOR="#000000">other than disabling the "Check..." button.</FONT>
<FONT COLOR="#000000">So I shut down Evolution, and did this from the shell:</FONT>
<FONT COLOR="#000000">$ export CAMEL_DEBUG=all</FONT>
<FONT COLOR="#000000">$ evolution</FONT>
<FONT COLOR="#000000">When I try to check for supported auth types again, I get this debug</FONT>
<FONT COLOR="#000000">output:</FONT>
</PRE>
</BLOCKQUOTE>
Don't check for supported auht types or upgrade to 2.0.3.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">sending : EHLO 192.168.0.33</FONT>
<FONT COLOR="#000000">received:</FONT>
<FONT COLOR="#000000">CamelException.setv(0xa7c59b8, 2, 'HELO command failed: Unknown')</FONT>
<FONT COLOR="#000000">sending : HELO 192.168.0.33</FONT>
<FONT COLOR="#000000">received: 250-STARTTLS</FONT>
<FONT COLOR="#000000">received: 250-ldap.nomeaning.net</FONT>
<FONT COLOR="#000000">received: 250-PIPELINING</FONT>
<FONT COLOR="#000000">received: 250-8BITMIME</FONT>
<FONT COLOR="#000000">received: 250-SIZE 0</FONT>
<FONT COLOR="#000000">received: 250 AUTH LOGIN PLAIN CRAM-MD5</FONT>
<FONT COLOR="#000000"> </FONT>
<FONT COLOR="#000000">(evolution:5808): GLib-CRITICAL **: file ghash.c: line 225 (g_hash_table_lookup): assertion `hash_table != NULL' failed</FONT>
<FONT COLOR="#000000"> { GLib error repeated 7 times... }</FONT>
<FONT COLOR="#000000">sending : QUIT</FONT>
<FONT COLOR="#000000">received: 250 ldap.nomeaning.net</FONT>
<FONT COLOR="#000000">CamelException.setv((nil), 2, 'QUIT command failed: Requested mail action okay,</FONT>
<FONT COLOR="#000000">completed')</FONT>
<FONT COLOR="#000000">Since *I* know what kinds of authentication are supported, I tried</FONT>
<FONT COLOR="#000000">setting Evo to use Login authentication. I've tried various settings</FONT>
<FONT COLOR="#000000">for "Use secure connection (SSL)" (it's not clear if this has anything</FONT>
<FONT COLOR="#000000">to do with TLS or if it means SMTP over SSL on port 443 or whatever...)</FONT>
</PRE>
</BLOCKQUOTE>
"always" means SSL, "whenever possible" means TLS. We've fixed that in head already but it missed string freeze for 2.0.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">When I try to send a message from Evo using that server, I also get the</FONT>
<FONT COLOR="#000000">'HELO command failed', but Evo *does* seem to understand that my server</FONT>
<FONT COLOR="#000000">is refusing the unauthenticated sender, because I get a "DATA command</FONT>
<FONT COLOR="#000000">failed: Requested action not taken: mailbox name not allowed." and a 553</FONT>
<FONT COLOR="#000000">error in my Camel log. But in this case Camel is still reporting "HELO</FONT>
<FONT COLOR="#000000">command failed: Unknown" in the log.</FONT>
<FONT COLOR="#000000">Searching the archives for "HELO command failed" only brought up a</FONT>
<FONT COLOR="#000000">thread from August '02 that seems unrelated.</FONT>
<FONT COLOR="#000000">Questions:</FONT>
<FONT COLOR="#000000">1) does the fact that Evo appears to be recognizing the 553 (host not</FONT>
<FONT COLOR="#000000">allowed) message indicate that the "HELO[EHLO, really] command failed"</FONT>
<FONT COLOR="#000000">is not a problem? Considering that Evo is subsequently sending an HELO</FONT>
<FONT COLOR="#000000">after the EHLO fails, it seems this could cause problems with ESMTP.</FONT>
</PRE>
</BLOCKQUOTE>
I don' tknow. some servers have a spastic when they don't understand a command rather than ignoring it.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">2) is the situation with "Check for supported types" likely to imply</FONT>
<FONT COLOR="#000000">that I've still got problems with my SMTP AUTH setup? The lack of any</FONT>
<FONT COLOR="#000000">helpful feedback from the UI leaves me wondering where the problem is.</FONT>
</PRE>
</BLOCKQUOTE>
2.0.2 has a nasty bug with that.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">3) somewhat tangential topic--to use STARTTLS (and eventually, IMAP with</FONT>
<FONT COLOR="#000000">SSL), what certificate do I need to import, and where? I tried</FONT>
<FONT COLOR="#000000">importing the .pem file that my server is using (as an "Authority"), but</FONT>
<FONT COLOR="#000000">I'm not clear if I need to create a separate one for the client as well.</FONT>
</PRE>
</BLOCKQUOTE>
Hmm, I think it should happen automatically if you have the right authority imported wiht the right rights. However i'm not sure if evolution's ui will let you do that and you'll just get a popup box asking you to 'use it anyway'.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">P.S. Sometimes the 'HELO command failed:' is followed by something like</FONT>
<FONT COLOR="#000000">"Operation now in progress" rather than "Unknown"</FONT>
</PRE>
</BLOCKQUOTE>
Maybe its the 'comments in /etc/hosts breaks gethostname()' bug. But i don't really know on that one. The log looks funny, what about a log of actually sending mail, and not checking authtypes?<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
<TABLE CELLSPACING="6">
<TR>
<TD>
<IMG SRC="cid:1099020804.4574.36.camel@lostzed.mmc.com.au" WIDTH="48" HEIGHT="48" ALIGN="top" ALT="" BORDER="0">
</TD>
<TD>
<B>Michael Zucchi</B> <<A HREF="mailto:notzed@ximian.com">notzed@ximian.com</A>><BR>
<I>"born to die, live to work, it's all downhill from here"</I><BR>
<TT>Novell's <A HREF="http://codeblogs.ximian.com/blogs/evolution/">Evolution</A> and <A HREF="http://www.gnu.org/philosophy/free-sw.html">Free Software</A> Developer</TT>
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>
--=-cnQ++R8zjlx1cXaF2rnJ--
--=-JhrlKttvtPmDa2qE4N3F
Content-ID: <1099020804.4574.36.camel@lostzed.mmc.com.au>
Content-Disposition: attachment; filename=zed-48.small.jpg
Content-Type: application/octet-stream; name=zed-48.small.jpg
Content-Transfer-Encoding: base64
/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAA0JCgsKCA0LCgsODg0PEyAVExISEyccHhcgLikxMC4p
LSwzOko+MzZGNywtQFdBRkxOUlNSMj5aYVpQYEpRUk//2wBDAQ4ODhMREyYVFSZPNS01T09PT09P
T09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0//wAARCAAwADADASIA
AhEBAxEB/8QAGQAAAwEBAQAAAAAAAAAAAAAAAwQFAgYB/8QALhAAAgEDAgUEAQIHAAAAAAAAAQID
BBEhABIFEzFBURQigZEGYXE0UmJyobHx/8QAFwEBAQEBAAAAAAAAAAAAAAAABAMCAf/EAB0RAAID
AQEAAwAAAAAAAAAAAAABAgMREjEiMkH/2gAMAwEAAhEDEQA/AK8sEEq35nLaP3e1cW/m8kfdtAfh
824L7I1YFrnaRt8+L40U1ECxiGjLzSCocRYuQhubW7jIxrcFZRzU7q3sh3e8deWvX67/AKX0Xegi
TixevoZdxjhnkk2xBj2Z7DIA74Gs+kgpoaamPLllqE5yPuO4i1+nix7+NS3qatikPNZa+idmjLGx
YE+7r16DHgnTEtRWTVIraiknUrE42mJvYTY/IyfjT66YZjNzkzSSRTrEYTuz0tbpg6oV1V62op5G
3QhV9yn+7t8DXPDiZlaepq0AYIBGEFtuRc2/WwH7aroXho98jNG5RVa4wDYNbzqNsefqdcnmM0J0
pp1kKyRywsdpU46EX/19aT4ioWgmanATG0Mpvcd89750arjMg2L1DfQtnSixTMW5hO0ZBZsEg5t5
xodU+8fhit7jZz4ChQWS99U1lC0H8RNZx74xK2DkAG48ePOtU0UUsQLC6kki/wC+jqtMpeLapjYg
XJyNLcxyr1EUHaWaEspHXPbXVcNkUcCUOjvNv2kAdAehOkVo4LrDEFG9hcnPe+rlUsNNSenUIWkk
ZHfbflqFC475IvqdnyWaRsgl6MNwysp13y8uLG3cTk6LBwCmliFR6lw7XBKdMdj50t+X8RkWOnhV
rbnLfX/dUPx1ivAoTJnmFm+CdIVEIx6XpFQSZxVVH6KrkRRaAudn9I8HXhniSPcyC/ntqzxOjMNS
6uNyMbqT0I1Ogoad6pF5S23C4t1zqOa8Y7xbEDSxmesguHDId4DKQDjGqMqHmNLGygFnujAZF8DF
820/xYpQ8RWcRLtkBINuh6Ef5B0tNRH0L7UEjGzCVTZirDBGfJ+NasrcMf4CnLp6f//Z
--=-JhrlKttvtPmDa2qE4N3F--