I've just picked up a duplicate of this. Both this and the other bug involve hostnames involving comcast.net. I suspect that Comcast's DHCP service is resulting in these hostnames.
If this is true, then either:
1) A dot terminating a hostname should be disallowed, and the DHCP client should remove a terminating dot from a DHCP response before applying it to the hostname, or
2) The postfix package should remove any terminating dot before supplying a hostname automatically.
Note that the other duplicate (bug 629685) is slightly different - it is invalid for a different reason.
Workaround: configure the Postfix hostname using /etc/mailname as Clint describes in comment #2.
I've just picked up a duplicate of this. Both this and the other bug involve hostnames involving comcast.net. I suspect that Comcast's DHCP service is resulting in these hostnames.
If this is true, then either:
1) A dot terminating a hostname should be disallowed, and the DHCP client should remove a terminating dot from a DHCP response before applying it to the hostname, or
2) The postfix package should remove any terminating dot before supplying a hostname automatically.
Note that the other duplicate (bug 629685) is slightly different - it is invalid for a different reason.
Workaround: configure the Postfix hostname using /etc/mailname as Clint describes in comment #2.