>>>>> "OT" == Omar Thameen <firstname.lastname@example.org> writes:
OT> Offhand, can you think of any other major address formats that Mj1
OT> barfs on that it shouldn't?
Probably anything using backslash quoting of a special (like '(' and '"')
but then it's not guaranteed that Mj::Addr will deal with those properly,
either. (Although I know it does deal with most instances; it's just
impossible to test everything.)
Most other parser failures are of the kind where it allows things through
that are really illegal, which is probably why you're using Mj::Addr.
If you're actually going to try to hack Mj::Addr to trap stuff that's
really legal, good luck. At least I commented it pretty well (otherwise I
couldn't figure it out now).
OT> Occasionally someone accidentally or mischievously subscribes the
OT> address of the list itself to the list. Even under an "auto" subscribe
OT> policy, shouldn't this be internally disallowed to avoid loops?
Mj2 definitely takes steps to prevent this. It's implemented through
access control, though, so the list owner can override it, which is
probably dumb. It is actually pretty difficult to figure out just when
someone is subscribing the list to itself, since a potentially huge number
of addresses may map to the list address.