From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268390AbTGSJ4P (ORCPT ); Sat, 19 Jul 2003 05:56:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268559AbTGSJ4P (ORCPT ); Sat, 19 Jul 2003 05:56:15 -0400 Received: from zork.zork.net ([64.81.246.102]:45956 "EHLO zork.zork.net") by vger.kernel.org with ESMTP id S268566AbTGSJzl (ORCPT ); Sat, 19 Jul 2003 05:55:41 -0400 To: "Riley Williams" Cc: Subject: Re: X-Message-Flag References: From: Sean Neakums Mail-Followup-To: "Riley Williams" , Date: Sat, 19 Jul 2003 11:10:36 +0100 In-Reply-To: (Riley Williams's message of "Sat, 19 Jul 2003 09:09:12 +0100") Message-ID: <6uy8yuaktf.fsf@zork.zork.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Riley Williams" writes: > Some of you have apparently been including an X-Header-Flag: header > in your outgoing emails. A recent signature update means that any > emails containing that header now get labelled as viruses, so get > deleted unread by my anti-virus system. As a result, whilst those > might be fun for you to use, they will soon prevent your emails > from being read by many other people. This is utterly laughable. It is clearly *not* a virus, or a plausible vector for one[0], so folks who object to having such a header in their incoming mail should configure their mail systems to simply delete the header. But if you want to wall yourself off from the rest of the Internet by means of ridiculous measures such as this, be my guest. [0] Modulo buffer overflows and other such potential software defects.