According to Jason L Tibbitts III:
>
> >>>>> "MH" == Mike Hadavi, DTN: 244-6605, Loc: AKO2-2/A5 24-Sep-1996 0950 -0400 <hadavi@bagels.ENET.dec.com> writes:
>
> MH> It would be nice if someone familiar with 1.94 could comment on how
> MH> 1.94 deals with "John Smith"@foo.bar.com.
>
> It will perform exactly as 1.93 did. This is non-optimal, but rewriting
> the address parser is not in the cards for a 1.9x release. (I get the
> feeling I've said this before.) My 1.95 development stuff has much better
> bad address handling; I can easily add a check to make sure there is
> something before the first @ sign in a stripped address.
>
> I am not certain that this address is even legal rfc822, but something
> tells me that it might just be OK. I don't have rfc822 in front of me at
> the moment, so I won't comment further.
I came up with a simple fix although it is late and I have not run
all the different address cases through it. Try modifying majordomo.pl so
that it must have a space following the 2nd '"' before it deletes them. It
will then work for "John Smith"@foo.bar.com. As I say, use at your own risk
as I have not tested it much!
-Earle
--
Earle Ake MSG/SID akee@wpdis03.wpafb.af.mil
Hassler Communication Systems Technology, Inc. ake@hcst.com
HCST: 2332 Grange Hall Road; Beavercreek, OH 45431-2345 Phone: 513-427-9000
Base: 4375 Chidlaw Rd. Suite 6; WPAFB, OH 45433-5006 513-257-7492 DSN:787-7492
*** majordomo.pl~ Tue Sep 17 14:14:07 1996
--- majordomo.pl Wed Sep 25 00:43:36 1996
***************
*** 94,100 ****
sub main'ParseAddrs {
local($_) = shift;
1 while s/\([^\(\)]*\)//g; # strip comments
! 1 while s/"[^"]*"//g; # strip comments"
split(/,/); # split into parts
foreach (@_) {
1 while s/.*<(.*)>.*/\1/;
--- 94,100 ----
sub main'ParseAddrs {
local($_) = shift;
1 while s/\([^\(\)]*\)//g; # strip comments
! 1 while s/"[^"]*"\s//g; # strip comments"
split(/,/); # split into parts
foreach (@_) {
1 while s/.*<(.*)>.*/\1/;
Follow-Ups:
References:
|
|
