From owner-freebsd-hackers Fri Mar 7 19:52:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA15611 for hackers-outgoing; Fri, 7 Mar 1997 19:52:02 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15562 for ; Fri, 7 Mar 1997 19:51:54 -0800 (PST) Received: from oneida.internet.com (oneida.internet.com [198.183.190.138]) by who.cdrom.com (8.8.5/8.6.11) with SMTP id OAA01190 for ; Fri, 7 Mar 1997 14:46:15 -0800 (PST) Received: (qmail 9734 invoked by uid 1000); 7 Mar 1997 22:45:05 -0000 Message-ID: <19970307174504.08147@oneida.internet.com> Date: Fri, 7 Mar 1997 17:45:04 -0500 From: Brian & To: freebsd-hackers@freebsd.org Subject: ampersand in GECOS field Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Howdy- In dicking with various MTAs/MUAs, I've noted an inconsistant handling of an ampersand ('&') in the GECOS field in the password file. It was an assumption of mine that getpwent() would expand an ampresand to be a capitalized represention of the username. Ie.: my username (reichert), and GECOS entry ('Brian &') would yield: 'Brian Reichert'. Yet, this does not seem to be the case. Apparently, only _some_ mail-related agents manually expand the ampersand. I can't find any formal documentation about this behaviour, imagined or otherwise. Does anyone have any pointers? -- Brian Reichert The Internet Company 617-547-3600 x161 96 Sherman Street reichert@internet.com Cambridge, MA 02140