10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Re: Info: 550...
FromSent OnAttachments
Jeremy SmithApr 23, 2005 8:40 am 
Michelle KonzackApr 23, 2005 12:28 pm 
Jeremy SmithApr 23, 2005 12:52 pm 
Michelle KonzackApr 23, 2005 1:28 pm 
Jeremy SmithApr 23, 2005 2:03 pm 
PollywogApr 23, 2005 2:19 pm 
Leon PoonApr 23, 2005 8:31 pm 
Michelle KonzackApr 24, 2005 1:15 am 
Bill TaroliApr 24, 2005 2:44 pm 
Jeremy SmithApr 24, 2005 7:04 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: Re: Info: 550 Don't like your HELO/EHLO. Hostname must contain a dot.Actions...
From:Leon Poon (list@revehomes.com)
Date:Apr 23, 2005 8:31:13 pm
List:net.sourceforge.lists.courier-users

Hi, I think you have misunderstood the hostname command. It appears the problem you are facing is due to your domain name not set properly.

There are 2 parts to a name: hostname, domainname.

The hostname command shows the hostname part, unless you call it with the -f switch.

This is how `hostname` was intended to work on a host that is known on the internet as "foo.bar.com":

# hostname foo # hostname -s foo # hostname -f foo.bar.com # hostname -d bar.com

(Please look at hostname --help for more details about the switches).

In your original configuration, your hostname was set to "foo" and you did not set a domain. When courier talks to other smtps, it combines "foo" with blank and ends with FQDN being "foo", thus the error 550.

After you set the hostname as "foo.bar.com", courier still combine that with blank, but ends up with "foo.bar.com", which is accepted while talking to other smtp. This solves the problem for courier. Seems like 2 wrongs make 1 right.

Maybe you want to review your /etc/hosts to implement the proper domain instead:

127.0.0.1 localhost [machine ip addr] foo.bar.com foo

NOTE: the order of the names for your ip address is important. The first name to an ip address is taken to be the FQDN for the machine.

Regards, Leon

If this is a Courier configuration issue, will you please enlighten me? Is there somewhere you are setting your server's fully qualified domain name? If so, where? Thanks.

I am using Debian GNU/Linux 3.0 and 3.1 and have installed courier-(mta,mta-ssl,imap,imap-ssl,mlm,webadmin,...)

It works by default without any intervention.

The RCF say, EHLO/HELO should be a FQDN.

RIGHT. Hence the 550 error.

So if it does not work on your System, then your Linux-Installation is probably misconfigured.

RIGHT. That's what the post was about. And setting the hostname as I described has corrected this "Linux" configuration problem (not a "courier" problem). The whole point is that this is NOT a courier problem, but if people running courier experience this, they should make sure that their hostname is set properly.