From owner-freebsd-hackers Thu Mar 21 09:19:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA02532 for hackers-outgoing; Thu, 21 Mar 1996 09:19:57 -0800 (PST) Received: from tombstone.sunrem.com (tombstone.sunrem.com [199.104.90.54]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA02519 for ; Thu, 21 Mar 1996 09:19:55 -0800 (PST) Received: (from brandon@localhost) by tombstone.sunrem.com (8.6.12/8.6.12) id KAA02429; Thu, 21 Mar 1996 10:19:28 -0700 Date: Thu, 21 Mar 1996 10:19:27 -0700 (MST) From: Brandon Gillespie To: Nate Williams cc: freebsd-hackers@freebsd.org Subject: Re: majordomo fixes In-Reply-To: <199603211704.KAA13547@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Mar 1996, Nate Williams wrote: > > Its rather easy to hack on majordomo so that it is a little more > > sensitive to usernames. The easiest fix is to have it require usenames > > to have an '@' character. > > Except that many of the committers are subscribed as 'local' users. > This makes it easy to have all FreeBSD email come from one account, so > if you happen to change locations you can easily point the .forward file > to somewhere else w/out having to go through the hassle of unsubscribing > and re-subscribing. Then they are already in the mail file, and majordomo doesn't care, or they can be added/removed by hand, as the need arises. I have a majordomo server which serves 3600 addresses which does this, and has local addresses.