bug-mailutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The state I'm in - rfc 822 parsing.


From: Alain Magloire
Subject: Re: The state I'm in - rfc 822 parsing.
Date: Fri, 16 Mar 2001 11:19:52 -0500 (EST)

> 
> Quoting Alain Magloire <address@hidden>, who wrote:
> > > 
> > > > > If I find the awful comment, I put it where I would have
> > > > > put a phrase.
> > > > 
> > > > Seems you actually remove comments totaly.
> > > > Some clients may want them right.  Especially in the "Received:"
> > > 
> > > Uh, GetMailBox() grabs the comment and puts in the personal,
> > > doesn't it? I don't have the source in front of me, but
> > > if what I sent you doesn't do that I sent the wrong diff.
> > 
> > # ./addr
> > alain(the squirrel fighter)@qnx.com
> > alain(the squirrel fighter)@qnx.com=> pcount 1
> > 1 email <address@hidden>
> >    local-part <alain> domain <qnx.com>
> 
> That's awful. Is that really desireable? It's explicitly non-compliant.

Are you sure, maybe I'm misreading rfc822, see page 6:

So, for example, the folded body of an address field

    ":sysmail"@  Some-Group. Some-Org,
    Muhammed.(I am  the greatest) Ali @(the)Vegas.WBA
is analyzed into the following lexical symbols and types:

            :sysmail              quoted string
            @                     special
            Some-Group            atom
            .                     special
            Some-Org              atom
            ,                     special
            Muhammed              atom
            .                     special
            (I am  the greatest)  comment
            Ali                   atom
            @                     atom
            (the)                 comment
            Vegas                 atom
            .                     special
            WBA                   atom

> The code parses rfc822 syntax, with the specific exception of also
> grabbing:
> 
> address@hidden (the soon to be victorious squirrel fighter)
> 
> *One* comment, *after* the addr-spec. If you really think
> it's useful to read
> 
> alain(the)@( squirrel)qnx.( fighter)com ==
> alain(the squirrel fighter)@qnx.com ==
> address@hidden (the squirrel fighter) ==
> the squirrel fighter <address@hidden>
> 
> then we'll talk after I've done the other clean ups
> which actually impact parsing of *RFC822* email addresses,
> as opposed to "whatever somebody thought would be cool"
> email addresses.

8-)
Ok, in any case the current parser, is much more compliant and better
then the previous.  So there is no turning back.
I'm ok with what we have now, already, we should do the move
when you feel ready to make address.c call parse822.c, just say when.

> > Actually, I'm off topic with the Received field, since I do 
> > not think anyone will use it in address_create().
> 
> I've got a date-time parser as well in Mail++, I might slap
> that and a Received header field parser in next.

Sounds cool, it will be very usefull for imap4d, when I get back to it.
IMAP4d seems to have a different view of Date then rfc822.

> I really meant an address of "<>". This is a legal rfc821
> address, it's mandated for returning undeliverable messages, among
> other things, and is used by vmail, for one, in the smtp dialog when
> you bounce a message, i.e.
> 
> mail from:<>
> rcpt to:<address@hidden>
> data
> ..

Ah, ok.

> I started the cleanup last week, I'll send you more patches after
> I've got a bunch farther, rather than little diffs. Just so
> you know I haven't abandoned this.
> 

Not a problem, this ain't work.

> 
> p.s. I thought you were hunting squirrels, not wooing them!

It's always more complex when woman are involved, I could quickly solve the
problem with a sledgehammer ....
[[laughs 8-)]] But who am I kidding 8-), I could not hurt a fly, let alone
a female squirrel with her offsprings.  At least she has good food taste
and table manners, ..., probably a french squirrel.
 

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]