Search results for software


A better round-robin DNS server
Software patents
Linux and multimedia
Jesus saves, but Buddha makes incremental backups
How to update your Nokia N80 to the N80 Internet Edition firmware
rm strcpy
HOWTO: Linux and iSCSI
Enjoyable development
Safe browsing
Compiling gqrx on CentOS


Of course, there'll always be some mail servers that don't follow the RFCs properly.

Checking the logs, I noticed the following:

Sep 26 03:11:47 hosting postfix/smtpd[19263]: connect from[]
Sep 26 03:11:49 hosting postfix/smtpd[19263]: NOQUEUE: reject: RCPT from[]: 450 4.7.1 <>: Helo command rejected: Host not found; from=<> to=<a.user@a.domain> proto=ESMTP helo=<>
Sep 26 03:11:49 hosting postfix/smtpd[19263]: disconnect from[]

Now, according to the SMTP RFC (

The domain name given in the EHLO command MUST BE either a primary
host name (a domain name that resolves to an A RR) or, if the host
has no name, an address literal as described in section

So why isn't there a DNS entry for

Anyway, to allow these broken setups to skip the "reject_unknown_hostname" in "smtpd_helo_restrictions", (as I don't want to disable it - it catches 95% of the spam) - you need to do the following:
* In, add parent_domain_matches_subdomains = yes
* In the smtpd_helo_restrictions section, add "check_helo_access hash:/etc/postfix/helo_access"
* In that helo_access file, list the offending "HELO/EHLOs" - in this case: OK

* Finally, run postmap /etc/postfix/helo_access to build the DB file, and restart postfix.

It does appear to be a problem more with some mail server admins than others. (