RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP437 2   
   PID: GED+W64 1.1.5-b20240209   
   MSGID: 2:280/464.112 65f93be2   
   REPLY: 3:633/280 65f8dfe5   
   Hi Stephen,   
      
   On 19 Mar 24 11:35, Stephen Walsh wrote to Wilfred van Velzen:   
     about: "FMail 2.3.0.0 public beta release":   
      
    SW> Source was 21:1/195 to 21:1/195.1   
      
    SW> pkt.zip & fmailm68k.zip in your inbound.... If you want to do something   
    SW> with M68K support... (This is after all just something todo on my part!)   
      
   Not really. ;-) I think there are more important things on the todo list.   
      
    SW> FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor   
    SW> Copyright (C) 1991-2024 by FMail Developers - All rights reserved   
      
    SW> Scanning netmail directory...   
      
    SW> Tossing messages...   
      
    SW> Packet is addressed to another node (256/49920); packet file:   
    SW> /home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with extension:   
    SW> '.wrong_destination'   
      
   256/49920 = 1/195, if you swap bytes. So a typical endianess problem...   
      
      
   Wilfred.   
      
   --- FMail-W64 2.3.0.1-B20240318   
    * Origin:  point@work  (2:280/464.112)   
   SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 129/305   
   SEEN-BY: 135/225 153/757 7715 154/10 30 203/0 218/700 221/0 226/30   
   SEEN-BY: 227/114 229/110 112 113 206 307 317 426 428 470 550 664 700   
   SEEN-BY: 240/1120 5832 266/512 280/464 5003 5555 282/1038 291/111   
   SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 341/66 234 342/200   
   SEEN-BY: 396/45 423/120 460/58 256 1124 467/888 633/280 712/848 770/1   
   SEEN-BY: 5020/400 5054/30   
   PATH: 280/464 460/58 229/426