-----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.
>
> =09To: cwhii(test)@ACM.org

Then your server is buggy. But what you mean is probably the=20
corresponding SMTP command. We're the talking rfc821 and rfc2821 here,=20
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=20
the smtp server. rfc821 is. And it doesn't allow comments in the RCPT=20
command:

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

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

Marc

- --=20
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=3D
=3D/Rx0
-----END PGP SIGNATURE-----

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail