Great Circle Associates List-Managers
(January 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Netcom's dynamically changing addresses
From: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Date: 16 Jan 1997 17:11:09 -0600
To: list-managers <list-managers @ GreatCircle . COM>
In-reply-to: Stan Ryckman's message of Thu, 16 Jan 1997 14:42:18 -0500
References: <2.2.32.19970116194218.0032b248@pop.ma.ultranet.com>

>>>>> "SR" == Stan Ryckman <stanr@sunspot.tiac.net> writes:

SR> Perhaps the real problem is MLM software which has been assuming that
SR> all messages from the same person will always have the same "From:"
SR> header.

Right.  It shouldn't do that, but because it is in general completely
impossible to define the set of equivalency classes for email address the
software has no other choice.

I have been working on a system (for Majordomo) which, in addition to
allowing subscribers to specify aliases for themselves for purposes of list
membership checks, transforms addresses into a canonical form for purposes
of determining equivalency.  The administrator/list owner can add to these
as new systems are discovered.  It's just a set of Perl regexp transforms
applied to the stripped address:

s/(.*)(+.*)?\@(.*)/$1\@$3/i;        # Strip address+maildrop notation
s/(.*)\@.*(ix.netcom.com)$/$1\@$2/i # Netcom doesn't masquerade    

(Yes, it looks like line noise.  Suggestions for a more useful syntax that
could be compiled into regexps are appreciated.)  This is essentially an
extension of Majordomo's mungedomain function, which while useful just
makes too many addresses equivalent when they aren't.  The real problem
with doing this kind of thing is figuring out all of the transforms.  You
only have to catch the major perpetrators and deal with additional problem
subscribers as they come up.  The local administrator could add the
necessary transforms for their site, which would probably cover most
subscribers.

 - J<


References:
Indexed By Date Previous: Re: Netcom's dynamically changing addresses
From: Stan Ryckman <stanr@sunspot.tiac.net>
Next: Re: PGP attachments (WAS: Re: funky list processors)
From: Sheryl Coppenger <sheryl@seas.gwu.edu>
Indexed By Thread Previous: Re: Netcom's dynamically changing addresses
From: Stan Ryckman <stanr@sunspot.tiac.net>
Next: Re: Netcom's dynamically changing addresses
From: Randy Cassingham <arcie@netcom.com>

Google
 
Search Internet Search www.greatcircle.com