On Sat, Mar 06, 1999 at 05:00:17PM -0600, Jason L Tibbitts III wrote:
> >>>>> "OT" == Omar Thameen <omar@clifford.inch.com> writes:
> OT> johndoe@somewhere. com
>
> That address is perfectly 100% legal. RFC822 allows whitespace all over
> the place. Here's an example (from RFC822, Section 3.1.4, page 6):
>
> Mj::Addr handles this just fine; note that the stripped form does not
> contain the spaces:
>
> Majordomo1 probably barfs on it, but it's address parser isn't very
> good so I wouldn't be surprised.
I should have mentioned that I was attempting to use this in conjunction
with Mj1. You are correct - it does barf on it, and I couldn't
figure any way to tell Mj1 that the space was simply part of the
address. Offhand, can you think of any other major address formats
that Mj1 barfs on that it shouldn't? I'll then add additional checks
to this modified Mj::Addr to be used on the server and in a web interface.
BTW, I posted this Mj1 question a couple times on majordomo-users,
and I'm still curious, so I'll bring it up here. Occasionally someone
accidentally or mischievously subscribes the address of the list itself
to the list. Even under an "auto" subscribe policy, shouldn't this
be internally disallowed to avoid loops?
Omar
Follow-Ups:
References:
|
|
