INTL 3:770/1 3:770/3   
   REPLYADDR address@is.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  60867f7f   
   REPLY: 2:25/0.0 6595ec34   
   PID: SoupGate-Win32 v1.05   
   Vincent,   
      
   > > @INTL 3:770/1 3:770/3   
   > > @REPLYADDR news@druck.org.uk   
   > > @REPLYTO 3:770/3.0 UUCP   
   > > @MSGID:  2bba35bb   
   > > @REPLY:  2694f141   
   > > @PID: SoupGate-Win32 v1.05   
      
   That looks like nothing I've ever seen.   My own (ancient!) OE6 shows the   
   raw message headers to be this :   
      
   - - - - - - -   
   ...   
   Message-ID:    
   ...   
   Content-Type: text/plain; charset=UTF-8; format=flowed   
   Content-Transfer-Encoding: base64   
   ...   
   - - - - - - -   
   (legal, as specified in the RFC for newsgroup messages)   
      
      
   > > T24gMDMvMDEvMjAyNCAwNTo1OCwgNTZ....   
      
   That block is just the base-64 encodeded (as mentioned in the headers) text.   
   It looks like your message reader cut a few corners and doesn't understand   
   (didn't implement?) this, quite legal, method of encoding a message.   
      
   IOW, it looks to be a "you", and not a "druck" problem ...   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 452 470 550 616 664 700 240/1120 266/512 267/800   
   SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757   
   SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426