Since this deals with the 2.0 rewrite, I have followed up this message
majordomo-workers instead of majordomo-users.
In message <m0pVCm5-000MS1C@unpc.queernet.org>, email@example.com writes:
> > This is caused by Majordomo's parser. The space is a fundamental separator
> > in Majordomo. I don't know how hard it would be to fix it.
> Majordomo's parser is woefully screwed up -- sorry, Brent. It does
> not accept X.400 addresses, quoted localparts, and many other
> constructs it should.
Shoot. Looks like I'll have to implement quoted string
support. Bother. The "\ " stuff went in and worked so nicely. Let me
guess X.400 allows spaces in their addreses as well, or does it break
on the /'s in the address? Crud, can we just take people who need
quoted local parts, and are trying to embed spaces into their
addresses and shoot them. While were at it, lets shoot people who use
X.400 addresses just for good measure (0.5 8-)).
> Releasing 2.0 without fixing its parser to be strictly RFC-compliant
> would be a tragedy. (Unfortunately, I don't know squat about
> writing parsers.)
Actually, its not the "parser", its the tokenizer (lexer if you will)
that is broken. How are you at writing lexers 8-).
I'll have to think about this, but on first glance it seems that the
lexer needs to know something about the arguments it is lexing so it
can keep addresses together, I may be able to do something fancy with
regexps to turn spaces in balanced quoted strings into a protected
form (I replace spaces with \001. If I have to differentiate between
the different forms of whitespace there is always \002 etc). As I
remeber there is no mechanism to quote the quotes in a quoted string,
is this correct?
I am more inclined to add code to subscribe/unsubscribe to recreate
the addresses, and deal with the " handling at that point. It would
probably break with addresses of the form
(note the two spaces in the "'ed part) but it would handle more cases
that the current one does.
Special Projects Volunteer University of Massachusetts at Boston
firstname.lastname@example.org (preferred) Boston, MA, (617) 287-6480
My employers don't acknowledge my existence much less my opinions.