Migrate config syntax to multiline modularity without english
Subject: 2019-09-29 Generic note on configs 7.x
For a variety of reasons it seems best to migrate 7.x to only use a strict multiline config format. This will reduce maintenance and user confusion and increase programmability.
For clarity, and for discrete line oriented parsing, debugging and error printing, and for line wrapping... deprecate the "multiple config stanzas all mashed into one single line" config syntax.
Also deprecate use of "noise", "english", and "punctuation" config "features" that are mentioned in the man page.
Single line config is also hard for external scripts and parsers to deal with . And it's more work to maintain all these config parsers within fetchmail.
 Today users have to write scripts to generate per invocation based configs because the config syntax is not modular enough to separate out the concepts of user, from server, from polling. And the command line isn't able to assemble the modules into a discrete fetch. (This problem was mentioned in old tickets and posts).