Hi, I just wanted to register to this forum. As a final step I got a activation email sent, which had been rejected, because there is no reverse lookup for your mail server?
I got this error message in my logs with the default ispcp installation:
NOQUEUE: reject: RCPT from http://www.isp-control.net[78.47.219.222]: 504 5.5.2 <ispCP>: Helo command rejected: need fully-qualified hostname; from=<www-data@isp-control.net> to=<myemail@mydomain> proto=ESMTP helo=<ispCP>

I comment reject_non_fqdn_helo_hostname from smtpd_helo_restrictions and then it did work. Isn't that a bit weird?

Is this configuration a recommended one or should it better be disabled?

Cheers Jonas

Rather ironic ^^

Anyway, I think those helo restrictions shouldn't be in the default config... There are a lot of mailservers that don't send valid helos.

yes i know its just i moved the server and some parts are missing ...
such as this . thanks for the hint. I'll correct that.

zpin Wrote:Anyway, I think those helo restrictions shouldn't be in the default config... There are a lot of mailservers that don't send valid helos.

The check is OK. The servers are requiered (by RFC) that the helo must be an resolvable fqdn...

that's nice and all, but if half of my friends/relatives can't send me mail anymore rfc can require all it wants, I will deactivate it.

[ot]
@zpin:
Do you also allow "no helo" so it's a little bit easier (faster) for me to send you an email (with telnet for example)?

You always can set the level of standards you support on your server - it's just a question if many smaller server admins have to set the level down just because some big players (or maybe also small players :-) are to lazy or unwilling to configue their mail server to speak the right protocol language.
[/ot]

Just my opinion...

/J

No I don't... All I'm saying is that - while it might not be rfc compilant - a majority of the mailservers don't set their helo correctly. And I've had quite some trouble with emails not reaching me because of that (from various sources). If you think it's reasonable to set the requirements like that by default, I'm ok with it, I can always change it. The question is just if it's the right setting for the standard small scale admin (the big one will hopefully double check every line of his config files).

Well - I also have mails that are rejected because of a non fqdn helo, but a short view about them tells me that it's only spam (> 200 and about 140 of regular mails that passed policyd - server is not very "loaded"). So, for me this is a first Spam filter.

I think most of the important/regular mail servers *do* send a fqdn helo.

even t-online (biggest german provider) won't.

I guess several other big providers don't either...

I've searched through the rfc a bit, I think it's not very specific about the helo having to be a fqdn. Might be interpreted differently...
http://www.ietf.org/rfc/rfc0821.txt