Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

identification strings on address literals #17

Open
novedevo opened this issue Jun 19, 2021 · 2 comments
Open

identification strings on address literals #17

novedevo opened this issue Jun 19, 2021 · 2 comments

Comments

@novedevo
Copy link
Member

2821 allowed this, but it was never properly used and often caused errors. It's "probably wise" (note the lack of SHOULD) for us to be prepared for such strings, but we should disregard them if they occur.

@gennyble
Copy link
Member

gennyble commented Jul 7, 2021

The only place I can find a mention of this is in section 4.4 about trace information, maybe?

Could you elaborate some more or provide a section number?

@novedevo
Copy link
Member Author

novedevo commented Jul 7, 2021

4.1.1.1 claims:

RFC 2821, and some earlier informal practices, encouraged following
the literal by information that would help to identify the client
system.  That convention was not widely supported, and many SMTP
servers considered it an error.  In the interest of interoperability,
it is probably wise for servers to be prepared for this string to
occur, but SMTP clients SHOULD NOT send it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants