On Sep 22, 2014, at 11.41, Wietse Venema <wie...@porcupine.org> wrote:
> This time PLEASE refrain from sidetracking the discussion. I want > to know what will break when the default changes, if that is not > too much to ask for. > > Summary: > > Until now, Postfix has a default setting "append_dot_mydomain = yes". > This performs autocompletion from user@host to user@host.$mydomain. > But this default setting is becoming problematic. > > I need to find out what will break when the default is changed to "no". > > How many people expect that this change would be a problem? It *may* > affect mail that is submitted with the sendmail command line, or > aliases that expand to user@host instead of user@host.domain. Email > addresses in SMTP *should* already be fully qualified. But I also > know that the real world often does not behave as it *should*. > Hence this query to the postfix-users list. given a poll, my vote would be to change the default to “no”. this would not be a problem for me, because i set this to “no" anyway, as a general rule, on all my systems. sendmail submission and alias expansion will not break for me, as addresses used/referenced in these contexts are fully qualified. mail submitted via smtp will not break for me because reject_non_fqdn_sender/reject_non_fqdn_recipient are always included in smtpd_*_restrictions, also as a general rule. i do this because i prefer that the onus for constructing properly formed messages be placed on the client rather than on postfix, and to some degree, out of principle, driven by aspirations for “purity”, so to speak. while i have had to make concessions on occasion for uncooperative software, changing append_dot_mydomain back to “yes” has never been among them. the practical value of this for me is that it aids in identifying/correcting clients/software which aren’t behaving as desired. that being said, it’s not something i’m particularly adamant about. the value for me is that it’s something i can set. -ben
