>>>>> "OT" == Omar Thameen <firstname.lastname@example.org> writes:
OT> I have just discovered that if I feed it an email address with a space
OT> like so:
OT> johndoe@somewhere. com
OT> it finds it to be valid.
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):
Muhammed.(I am the greatest) Ali @(the)Vegas.WBA
Mj::Addr handles this just fine; note that the stripped form does not
contain the spaces:
[tibbs@morpheus 2.0]$ mj_shell -p XX show 'Muhammed.(I am the greatest) Ali @(the)example.com'
Address: Muhammed.(I am the greatest) Ali @(the)example.com
Address is valid.
Comment: I am the greatest the
Address is not registered.
OT> Is this an oversight, or is my use of the module inappropriate?
OT> I realize that if you try to subscribe such an address to the list via
OT> the usual interface, it will indeed fail.
Hopefully not with Majordomo2. This kind of thing seems to work fine for
me. Majordomo1 probably barfs on it, but it's address parser isn't very
good so I wouldn't be surprised.
BTW, Mj::Addr has been significantly rewritten since the early days; it's
now completely object-oriented (which makes address operations much easier
within Mj2) but the parser is essentially the same. I suppose I could add
a setting to reject extraneous whitespace, but it wouldn't be terribly easy
to make use of it and whitespace isn't even of questionable legality so I
don't know what the point would be.