5 ms·
... "In fact, an ARC chain can be counterfeited,[3] so ARC processing applies when receivers trust the good faith of ARC signers, but not so much their filterin
by kazinator 4y ago
... "In fact, an ARC chain can be counterfeited,[3] so ARC processing applies when receivers trust the good faith of ARC signers, but not so much their filtering practices."
Hmm, article references an e-mail post by good old John Levine, moderator of comp.compilers for over 30 years, who has some interesting things to say:
"[If] I were a certain kind of bad guy, I would take the two seal ARC chain
from a message from a virtuous sender, replace the message body and
>From and Subject line with my spam, add a fresh new i=3 seal and blast
it out. That ARC chain is 100% valid, even though the messsage is
spam."
- jeffbee 4y agoYou're implying that this message has been tampered with, but it has not. It is perfectly authentic. Whoever produced this message possesses the private signing key of youtube.com. This message has in no way been forged. The only mystery here is why someone is mirroring google mail back to gmail with unexpected envelope recipients. It could be a weird error, or it could be they think they can game the IP reputation system by doing it. In any case, the fine moderators ought to correct the title, because it is wrong and misleading.
- jmillikin 4y agoThe message has been forged, as can be observed from the From: header being a domain that the sending server was not authorized to send from. Whether a subset of the message -- in this case the body -- is authentic doesn't matter. If I were to MITM google.com and send back an archived snapshot from a month ago, that would be forged traffic even if it matches responses that Google had once sent.
- jeffbee 4y agoWith all due respect, you don’t know what you’re talking about. Relaying month-old traffic is completely acceptable in email.
- azca 4y agoRemembering back to the uucp days and when certain OOB nodes came back up after outages, this is precisely why email as a standard can handle delayed delivery and MX records have preferences for relays that can queue for future delivery.
- jmillikin 4y agoIt's not about the age! Look at the headers! Received: from 7n.robtoledoyour.com (7n.robtoledoyour.com. [2a01:7c8:bb01:51a::7]) From: YouTube <no-reply@youtube.com> That email was sent by <robtoledoyour.com>, claiming to be <youtube.com>. YouTube has not created DNS records allowing <robtoledoyour.com> to send or forward email on its behalf.
- jeffbee 4y agoYou are inventing imaginary requirements for email that do not exist. The "From:" header is not part of the envelope. The "From:" header is protected by the DKIM signature. This message is from youtube.com. You received it via some other relay. Nothing about that is weird. People love relaying email all over the place.
- deleted 4y ago[deleted]
- kazinator 4y agoDo you have a hypothesis about why someone would be re-sending these YouTube messages? One possibility is that the original To: recipient of this message is an bad actor's address. Maybe some small percentage of users will contact that address, and thereby get harvested.
- jeffbee 4y agoI think they're trying to goose their sender reputation, but I don't know if that is going to work.
- deleted 4y ago[deleted]