It wasn't the listing of the shared host that was the problem. It was the fact that the university's filters resolve URLs in message texts to IP addresses, and block messages based on that criterion alone, rather than merely influencing a spam score. If you get a bounced message like this, you can't even report it to an administrator on the university mail network without removing all the URLs.
Block lists are useful, but, as several people in this article's discussion pointed out, they're not accurate or granular enough to be used for deterministic blocking. And this particular usage, resolving link URLs to block messages, is illogical for many more reasons.
filter *URL's pointing to a PBL'd IP that are embedded in a message*!!!
My university does that, too. I run a student organization site that has a university subdomain, but is hosted on a shared host. The host inexplicably got listed in the CBL several times, and that screwed up email for the organization staff, and mailing lists for hundreds of students for days at a time.
I didn't realize anyone else used this brilliant filtering scheme.
The X and Y chromosomes that make up a genome.
Believe it or not, X and Y chromosomes aren't the only ingredients...
I'm not sure to what extent you're kidding, but I've seen similar occurrences going as far back as Windows XP. At fault is generally Wake-On LAN, which can be disabled through your Ethernet adapter's driver settings.
Who or what manages to broadcast wake-up packets with the right MAC address is beyond me, but disabling WOL on the card tends to stop these mysterious reanimations.
If you want to put yourself on the map, publish your own map.