[Evolution] Camel problem: HELO command failed

[Eric Lambart]

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