HEX
Server: Apache/2.4.18 (Ubuntu)
System: Linux phubuntu06.apexhosting.com 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64
User: master06 (1000)
PHP: 7.0.33-0ubuntu0.16.04.16
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,
Upload Files
File: //usr/share/webmin/postfix/help/opt_non_fqdn_reject_code.html
<header>SMTP server response on fqdn violation</header>

<center><tt>non_fqdn_reject_code</tt></center>
<hr>

This parameter specifies the SMTP server response code when a mail violates the
<tt>reject_non_fqdn_hostname</tt> or <tt>reject_non_fqdn_sender</tt>
or <tt>reject_non_fqdn_recipient</tt> rule that are:<br>
<i>Access denied: Invalid domain for client HELO hostname, sender or recipient email address (not FQDN)</i><br>
<br>
Note that the postfix default value used for <tt>non_fqdn_reject_code</tt> is
code 504, and this code in 'standard RFC 822' should means
'Command parameter not implemented'.
So with Postfix, a <tt>non_fqdn_reject_code</tt> rule violation does not reflect exactly
the RFC822 explanation of reported code.<br>
<p>
To avoid confusion, you can change this to 578 for example, otherwise, do not change
this unless you have a complete understanding of RFC 822.
</p>


<hr>