Great Circle Associates Majordomo-Workers
(November 1996)
 

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

Subject: Re: Dealing with multiple Reply-To:s and other message faults
From: Brock Rozen <brozen @ webdreams . com>
Date: Thu, 7 Nov 1996 03:31:56 -0500 (EST)
To: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Cc: majordomo-workers @ greatcircle . com
In-reply-to: <ufasp6nf82p.fsf@sina.hpc.uh.edu>

On 6 Nov 1996, Jason L Tibbitts III wrote:

> What would everyone see as the proper solution to this problem?  RFC822
> seems to say that multiple Reply-To: headers are illegal, but that the
> Reply-To: can have as many addresses as a user desires, separated by
> commas.  (Hey, From: can have the same.)  Since under the current framework
> we can't distinguish between the two, the question comes down to whether or
> not we should allow acting on multiple addresses in a From: or reply-To:
> header, and exactly what should happen in this case.

Why not just require the user to use:

subscribe list-name address@whatever.domain

It might bounce if the list isn't auto, but then the list-owner will just
approve it.

 ------------------------------------------------------------------------- 
 | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | 
 ------------------------------------------------------------------------- 



Follow-Ups:
References:
Indexed By Date Previous: Re: Majordomo mails itself
From: Brock Rozen <brozen@webdreams.com>
Next: Re: Majordomo mails itself
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Indexed By Thread Previous: Re: Dealing with multiple Reply-To:s and other message faults
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Dealing with multiple Reply-To:s and other message faults
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>

Google
 
Search Internet Search www.greatcircle.com