Great Circle Associates Majordomo-Users
(April 1994)
 

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

Subject: Re: Fwd: hostile address
From: Stephen P Potter <spp @ cis . ufl . edu>
Organization: Department of Impossible Probably Facts
Date: Tue, 26 Apr 1994 12:22:33 EDT
To: Pat Crawford <0001020203 @ mcimail . com>
Cc: majordomo-users @ greatcircle . com
In-reply-to: Some random ramblings on Tue, 26 Apr 1994 10:23:00 -0500.
Reply-to: Stephen P Potter <spp @ cis . ufl . edu>

Strange sunspot activity caused Pat Crawford <0001020203@mcimail.com> to write:
| Hi.
| 
| We just installed Majordomo. Within the first week we got one of these:
| 
| ------- Forwarded Message
| 
| MAJORDOMO ABORT
| 
| HOSTILE ADDRESS
| /PN=JIM.JA.FEE/DD.ID=JA.FEE/ADMD=TELECOM.CANADA/C=CA/@resonet.com
| 
| 
| ------- End of Forwarded Message
| 
| Don't remember seeing this documented anywhere. Can anyone help?
| 
| Pat Crawford
| MCI Communications

On or about line 330 or majordomo.pl there is a check for a "valid"
address.  Anything with a '|' or '/' is considered an invalid address.

The line is question is:
if (tr/|\//|\// != 0) {
    &main'abort("HOSTILE ADDRESS $addr");

I'm not sure why these are considered invalid (except that RFC 1183? says
they aren't), but wouldn't this line be *much* easier to parse if it were:

if (/|\//) {

Steve


Follow-Ups:
Indexed By Date Previous: Re: Fwd: hostile address
From: "Michael J. Corrigan" <corrigan@ucsd.edu>
Next: Re: Fwd: hostile address
From: Brent Chapman <brent@mycroft.GreatCircle.COM>
Indexed By Thread Previous: Re: Fwd: hostile address
From: "Michael J. Corrigan" <corrigan@ucsd.edu>
Next: Re: Fwd: hostile address
From: eichin@cygnus.com (Mark Eichin)

Google
 
Search Internet Search www.greatcircle.com