[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Bug#19187: kmail comments in address (RFC822) handling
From:       Marc Mutz <mutz () kde ! org>
Date:       2002-02-27 20:35:50
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 27 February 2002 20:20, C.W.Holeman II wrote:
<snip>
> This produces an error from the SMTP server.
>
> 	To: cwhii(test)@ACM.org

Then your server is buggy. But what you mean is probably the 
corresponding SMTP command. We're the talking rfc821 and rfc2821 here, 
and I guess you're right.

> IN RFC 822 it states that the stuff in ()  is not to be handed to the
> originating system's mailer but KMail 1.3.1 passes it to the SMTP
> server. Is there a change  regarding this in RFC 2822?

See above. These rfc's are not normative on the subject of talking to 
the smtp server. rfc821 is. And it doesn't allow comments in the RCPT 
command:

Quoting rfc821:
            RCPT <SP> TO:<forward-path> <CRLF>
            <forward-path> ::= <path>
            <path> ::= "<" [ <a-d-l> ":" ] <mailbox> ">"
                 ; a-d-l is for source routing
            <mailbox> ::= <local-part> "@" <domain>
            <local-part> ::= <dot-string> | <quoted-string>

Unfortunately, there's no easy way to fix this for KDE3, since doing it 
right (ie. to catch all allowed cases) means implementing a rfc822 
tokenizer. That has already been done, but the code ("KMime") was not 
ready for KDE3 and will be hopefully merged into KMail in 3.1.

Marc

- -- 
Marc Mutz <mutz@kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8fUMm3oWD+L2/6DgRAu3uAJ41j+Y72ycB1tZ3Df3caEe2QxDWaACgi/tM
VS14e9hTt8zm4kSNMRrMAac=
=/Rx0
-----END PGP SIGNATURE-----

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]