From 6eb3b9325aba0935d43d4cdedc78c1b5f335dbbe Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 16 Aug 2018 11:36:26 -0400 Subject: followup --- ...comment_4_2c90ee4cd4fe54299ce9742c28730b9a._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/mailname_set_by_Propellor.Property.Hostname.sane/comment_4_2c90ee4cd4fe54299ce9742c28730b9a._comment diff --git a/doc/forum/mailname_set_by_Propellor.Property.Hostname.sane/comment_4_2c90ee4cd4fe54299ce9742c28730b9a._comment b/doc/forum/mailname_set_by_Propellor.Property.Hostname.sane/comment_4_2c90ee4cd4fe54299ce9742c28730b9a._comment new file mode 100644 index 00000000..b67a80d8 --- /dev/null +++ b/doc/forum/mailname_set_by_Propellor.Property.Hostname.sane/comment_4_2c90ee4cd4fe54299ce9742c28730b9a._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2018-08-16T15:23:09Z" + content=""" +I notice that the property is certianly wrong for domains such as +"foo.org.uk". And I don't want to build in the list of exceptions needed to +properly deal with those. + +How about we add a separate mailname property and make Hostname.sane not +touch the mailname. mailname could take a Maybe and guess based on the +hostname when Nothing is specified. + +Or, the mailname property could only set Info, and Hostname.sane +use that info when set and guess when not. But, I suspect that would not +have avoided your email-losing misconfiguration from happening in the first +place. +"""]] -- cgit v1.2.3