> On Jan 20, 2017, at 3:18 PM, Wietse Venema <wie...@porcupine.org> wrote:
>
>> Obviously, given your level of godly perfection, you've never suffered
>> from "config file blindness" you know after starting a whole bunch of
>> them for a while suddenly the obvious gets hidden.
>
> I can't speak for Viktor, but I surely have gotten lost with alien
> systems. I always recommend to start simple, and add things once one
> is more familiar with the workings of the system.
In my view creating a description of a problem for someone else's eyes
is a golden opportunity to solve it for yourself. Specifically, as one
gathers up the requisite details for the problem description, one should
take the time to carefully read and think about the data one is posting.
The shift of mindset from tinkering to describing to someone else can be
illuminating, and compiling all the evidence in a single place can pull
one out of a rut.
I this, case with the problem setting clearly highlighted and commented
in the first half-dozen lines of the posted configuration, the OP had
clearly forsaken all hope and effort to make further progress. So my
critique of giving up is not solely addressed to the OP.
Learn to do a close reading of the information you post. Include as
much as possible in the message body, fold long lines from main/master.cf
or logs with leading whitespace on continuation lines, ... doing this
not only makes the problem description more readable, it slows you down
and helps you read what you're posting.
There's method to my madness. Since nobody else had answered the OP's
message which was a few hours old by the time I got to it, even though
I happened to cause offense, I did provide a solution, and the correct
response is either a (secretly grudging) thanks or just silence.
--
Viktor.
