This attempts to clarify the description for reject_non_fqdn_helo_hostname. There seems to be end-user confusion about whether this feature should also reject address literals, which of course it is not intended to.
*** proto/postconf.proto Wed Jul 10 19:01:20 2013 --- /tmp/tmp/postconf.proto Mon Aug 5 17:07:19 2013 *************** *** 5529,5535 **** <dt><b><a name="reject_non_fqdn_helo_hostname">reject_non_fqdn_helo_hostname</a></b> (with Postfix < 2.3: reject_non_fqdn_hostname)</dt> <dd>Reject the request when the HELO or EHLO hostname is not in ! fully-qualified domain form, as required by the RFC. Note: specify "smtpd_helo_required = yes" to fully enforce this restriction (without "smtpd_helo_required = yes", a client can simply skip reject_non_fqdn_helo_hostname by not sending HELO or EHLO). <br> --- 5529,5535 ---- <dt><b><a name="reject_non_fqdn_helo_hostname">reject_non_fqdn_helo_hostname</a></b> (with Postfix < 2.3: reject_non_fqdn_hostname)</dt> <dd>Reject the request when the HELO or EHLO hostname is not in ! fully-qualified domain or address literal form, as required by the RFC. Note: specify "smtpd_helo_required = yes" to fully enforce this restriction (without "smtpd_helo_required = yes", a client can simply skip reject_non_fqdn_helo_hostname by not sending HELO or EHLO). <br> -- Noel Jones
