4 ms·
I once accidently did this on a university computer system. Something was misconfigured with sendmail routing; when I telneted to an unexpected computer in the
by dzdt 10y ago
I once accidently did this on a university computer system. Something was misconfigured with sendmail routing; when I telneted to an unexpected computer in the lab and sent an email from there it started bouncing in an infinite loop between that and another department server. About two days later the system operator noticed when log files filled the drive. My email had been making trips up and down the building a few hundred times a second. I guess I missed the N tag though!
- ohthehugemanate 10y agoI wonder if it's possible to craft a mail to be infinite-bounced like this. There have to be servers that are appropriately (mis-)configured of course. But that would let you have a lot more than just one name, and a lot more information about each person. An epitaph of sorts.
- qwertyuiop924 10y agoThe trick is to make it so the mail isn't replicated as it's infinite bounced, so we don't get infinite copies (don't clog the tubes!). It's something I've been struggling with in a piece of software I've been writing, actually. My solution is to simply not allow for loops: There is only one canonical path between any two server (netsplits, yay!)