Content-Transfer-Encoding: binary In-Reply-To: MIME-Version: 1.0 X-RT-Interface: Web X-Mailer: MIME-tools 5.508 (Entity 5.508) Content-Type: text/plain; charset="utf-8" Content-Disposition: inline References: Message-ID: X-RT-Original-Encoding: utf-8 RT-Send-CC: Content-Length: 520 This appears to have been introduced in commit aa49af836, which added a correctness check to also-notify clauses that hadn't been there before. What I haven't worked out yet is whether the code is correct and that also-notify statement is invalid (in which case the doc should be fixed), or whether the also-notify statement is valid and the code is being overly restrictive. The fact that it was accepted by earlier versions of named doesn't necessarily mean it was working correctly at the time. I'll keep looking.