Attention Sean,   
      
    SD> I'd ask that you report that broken link to someone who can   
    SD> either contact the sysop or reroute around that system.   
      
   It is being routed around else this particular reply to your reply wouldn't be   
   happening.  As for contacting the sysop that isn't an issue as last time this   
   happened there was no problem with this node - 1:153/7001 - contacting it to   
   point out there was obvious breakage.  However that fixes nothing and the   
   fts-0001.016 MSGs - up to and including this one - don't get beyond that   
   particular node as well as yours and every other message whether or not they   
   are indeed fts-0001.016 compliant, which they usually aren't.  Complaining   
   about it achieves nothing as past experience has proved many, many, many times.   
      
   This node - 1:153/7001 - is one of the few, perhaps the only Fidonet node,   
   that knows how to hack a working pktheader when a link demonstrates that it   
   cannot handle fts-0001.016 compliant pktheader(s).  I am aware of many Fidonet   
   nodes, most in very sensitive positions, that are noncompliant and have been   
   noncompliant for decades now.   
      
   End transmission.   
      
   ... Anthony's Law of Force: Don't force it, get a larger hammer.   
   --- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)   
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)