Usually the hostname of the local machine tends to be not unique nor a
FQDN. This brings multiple problems with it when sending messages using
such Message-ID.
First of all this makes go-message more compliant to RFC5322 [1] because
it recommends to use a FQDN on the right handed side of the @ in the
Message-ID. Second this also improves the situation with spam filters,
because some of them (for example rspamd) give a bad score for messages
without a FQDN in the Message-ID.
Usually the hostname of the local machine tends to be not unique nor a FQDN. This brings multiple problems with it when sending messages using such Message-ID.
First of all this makes go-message more compliant to RFC5322 [1] because it recommends to use a FQDN on the right handed side of the @ in the Message-ID. Second this also improves the situation with spam filters, because some of them (for example rspamd) give a bad score for messages without a FQDN in the Message-ID.
[1] https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.4