769
you are viewing a single comment's thread
view the rest of the comments
[-] NaibofTabr@infosec.pub 31 points 22 hours ago

Yeah I feel like the correct answer for anything obsoleted by a more recent RFC should be "Invalid".

[-] errer@lemmy.world 38 points 19 hours ago

Complaints about the quiz? Send them to 💩@💩

[-] JohnEdwa@sopuli.xyz 21 points 20 hours ago* (last edited 20 hours ago)

But they will work, and according to the spec, you have to build your system so that it can handle those cases. Obsolete doesn't mean incorrect or invalid, just a "you shouldn't do this any more".

Obsolete Syntax
Earlier versions of this standard allowed for different (usually more liberal) syntax than is allowed in this version. Also, there have been syntactic elements used in messages on the Internet whose interpretation have never been documented. Though some of these syntactic forms MUST NOT be generated according to the grammar in section 3, they MUST be accepted and parsed by a conformant receiver.

https://datatracker.ietf.org/doc/html/rfc2822#section-4 page 29

[-] NaibofTabr@infosec.pub 4 points 8 hours ago

Well shit, yeah, that "MUST be accepted and parsed" is pretty explicit. That sucks. What is even the point of revising standards? How the fuck do we ever get rid of some of these bad ideas?

[-] frezik@lemmy.blahaj.zone 9 points 19 hours ago

Some of those "obsolete" things are outright blocked for specific reasons. For example, routing addresses through multiple servers. It was abused by spammers, so it's almost always denied these days.

Looks like this:

<@foo.example.com@bar.example.com:123@example.com>
this post was submitted on 18 Aug 2025
769 points (99.1% liked)

Programmer Humor

25802 readers
2273 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS