TID: Mystic BBS 1.12 A48   
   MSGID: 2:201/137 be2fa28f   
   TZUTC: 0100   
   Hello again g00r00!   
      
   When experimenting with dlreq I noticed (when running things through the W3C   
   Markup Validation Service) that the ampersand in @LINK@ links should probably   
   be HTML-entitized, i.e.:   
      
   http://scbbs.nsupdate.info:50080/dlreq?443cf3d1&gwo0.11-sample-win32.lzh   
      
   ...should probably be:   
      
   http://scbbs.nsupdate.info:50080/dlreq?443cf3d1&gwo0.11-sample-win32.lzh   
      
   ...even though many web browsers might "fix" this up on their own.   
      
   Also, does @LINK@ URL encode special characters in file names?   
   (I haven't tested that.)   
      
   Finally, I'm wondering if there shouldn't be field names and equal signs   
   before the ID and the file name? Something like:   
      
   http://scbbs.nsupdate.info:50080/dlreq?id=443cf3d1&   
   f=gwo0.11-sample-win32.lzh   
      
   Although I guess the parsing can be done by dlreq anyway as it knows the   
   format...   
      
   Best regards   
   Bj”rn   
      
   --- Mystic BBS v1.12 A48 2022/03/11 (Linux/64)   
    * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 120/340 123/120   
   SEEN-BY: 123/131 124/5016 129/305 330 331 153/757 7715 154/10 201/0   
   SEEN-BY: 201/137 203/0 124 218/700 840 220/70 221/0 1 6 242 360 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 206 307 317 400 424 426 428 452   
   SEEN-BY: 229/550 664 700 230/0 240/5832 250/5 8 266/512 267/800 280/464   
   SEEN-BY: 280/5003 282/1038 292/854 8125 298/25 301/1 305/2 3 317/3   
   SEEN-BY: 320/219 322/757 335/364 341/66 234 342/200 396/45 423/81   
   SEEN-BY: 460/58 633/280 712/848 770/1 2452/250 3634/24 4500/1   
   PATH: 201/137 0 203/0 280/464 221/1 6 218/840 770/1 317/3 229/426