Jim Perrin <jperrin at gmail.com> wrote: > Close. It has to do with RH policy. > ... > RHEL tries. the named.conf file says to not edit it, and to > use named.custom. Some people don't follow the directions. see > bugs: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145094 > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145244 Yep, a policy I was ignorant of until now. Thanx for setting my straight. > And it will continue to for as long as people do what > redhat perceives as the "wrong" thing. The "wrong" thing is something that you'll _rarely_ ever see me say. I'm more than ready to point at my own ignorance than anything, such as in this case. > Yes this post is mostly a dupe of what I just posted under > the original thread. People keep changing subjects and choking > gmail. Actually, GMail is the problem -- it should track based on Message-ID. Subject tracking has _never_ been a viable solution. 30+ years of SMTP/NNTP Message-ID header tracking, yet Google thinks it knows better. My posts thread correctly in the archives which, ironically, most people find via Google. How? Again, Message-ID. Even more ironic is that appending or changing the subject has _always_ been _encouraged_ in discussion lists -- UseNet or e-mail. Because after dozens of posts, it's a major PITA to have to read everything just to find one thing. Appending or changing the subject as appropriate has always been encouraged for such threaded lists/groups. I get thanks for doing so from people who find my posts in Google searches almost daily. Because they don't have to read through 30+ posts of the exact same subject (let alone some where the topics have changed) just to find the answer. GMail needs to get with the program. But they won't. That's why Yahoo takes the awards, because Google doesn't track Message-ID. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith at ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers)