Re: [Evolution] Camel problem: HELO command failed



On Thu, 2004-10-28 at 14:09, Eric Lambart wrote:
On Thu, 2004-10-28 at 13:44 -0700, Thomas Spuhler wrote:

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.
I had a similar problem, but my worked great fom within the FW but it
took for ever to get a reply from outside. I then opened some ports and
it now works:
nmap of your address show:
(snip)
nmap of my server gives:
(snip)
I noticed that your ldapssl is closed. I think I was helped by adding
port 465 even if it shows as closed?

Hmmmm... I spent last week struggling to get LDAP to work with Evo
before giving up (for the time being).  I hadn't even tried to get
ldap/ssl working yet.  I don't see why this would matter for Evolution's
SMTP communications, though.

I'm not at home at the moment, so all the work I'm doing is from outside
my firewall--and I have no trouble connecting to port 25.

Thanks for the ideas, Thomas.  Still wrestling with it here...

Eric


_______________________________________________
evolution maillist  -  evolution lists ximian com
http://lists.ximian.com/mailman/listinfo/evolution

Well, it seems its working with my server at home using evo 1.4 from work.

I just sent a message trough that server. I cannot post from that address to this list (not subscribed)

Telnetting gives this result:
$ telnet aargau.btspuhler.com 25
Trying 168.103.242.218...
Connected to aargau.btspuhler.com (168.103.242.218).
Escape character is '^]'.
220 aargau.btspuhler.com ESMTP Postfix (2.1.4) (Mandrake Linux)
ehlo tusonix.com
250-aargau.btspuhler.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
250 8BITMIME

I cannot get cram-md5, digest-md5 to work, just plain.
But that is not related to Evo.

Tom

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]