[Bug 625023] Re: invalid myhostname parameter allowed during configuration

Robie Basak 625023 at bugs.launchpad.net
Tue Feb 28 12:59:35 UTC 2012


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.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/625023

Title:
  invalid myhostname parameter allowed during configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/625023/+subscriptions



More information about the Ubuntu-server-bugs mailing list