On Tue, Mar 22, 2016 at 2:38 PM, Wietse Venema <wie...@porcupine.org> wrote: > Tom Browder: >> On Tue, Mar 22, 2016 at 11:56 AM, Wietse Venema <wie...@porcupine.org> wrote: ... >> But, couldn't there be a user option to build Postfix to allow such >> (or maybe define some special comment character or characters such as >> the common '//' or '--')? It shouldn't change the default behavior >> and wouldn't disturb other installations. > > In practice, the only comment character that makes sense in as > Postfix file is the "#"; anything else will just confuse the hell > out of people. So there would need to be a way to turn on/off > trailing comments for an individual file. That would require some > kind of modeline support (a line with special sequences that change > how the file will be processed). > > /etc/postfix/main.cf: > # This modeline is needed otherwise trailing comments won't work > # in main.cf (chicken and egg problem). > # postfix: trailing_comments=yes > > trailing_comments = yes # Global default ... > Is this really easier to use? That is not obvious to me.
I agree, but I was think of a non-default build config define for CCARGS, say, '-DALLOW_TRAILING_COMMENTS', so that all files read by postfix would always have trailing comments stripped before the rest of the line is processed. No one outside the using would be bothered by mode lines or anything else, it would just work. If the ALLOW_TRAILING_COMMENTS were used perhaps a warning could be issued upon postfix start. Thanks. -Tom P.S. BTW, is the postcard address in AAAREADME still correct with your new job?
