Great Circle Associates Majordomo-Workers
(November 1996)
 

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

Subject: Dealing with multiple Reply-To:s and other message faults
From: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Date: 06 Nov 1996 11:26:54 -0600
To: majordomo-workers @ greatcircle . com

There is someone who keeps trying to zubscribe to one of my lists.  The
problem is that his messages have two Reply-To: headers, both with the same
address.  &ParseMailHeader will take these and put them in the header array
like so:

$array{'reply-to'} = "address, address"

Now majordomo sees this and thinks "HOSTILE ADDRESS" and bounces it as
such, aborting in the process.  This results in an ugly "mailer error 2"
bounce from sendmail.

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.

A subsidiary problem is that returning error 2 and aborting is rarely a
good idea.  Some kind of information should be communicated back to the
requestor, even to say that something's screwed up somewhere.  Especially
now since we redirect standard error to a file, so the abort message won't
get back to the mailer.

 - J<


Follow-Ups:
Indexed By Date Previous: Just a nit
From: Michael Rice <michael@cfox.bchs.uh.edu>
Next: Re: Dealing with multiple Reply-To:s and other message faults
From: Evan Champion <evanc@synapse.net>
Indexed By Thread Previous: Just a nit
From: Michael Rice <michael@cfox.bchs.uh.edu>
Next: Re: Dealing with multiple Reply-To:s and other message faults
From: Evan Champion <evanc@synapse.net>

Google
 
Search Internet Search www.greatcircle.com