TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 5fc80f93   
   REPLY: 1:153/757.26 1bdd69e1   
   Hi Charles,   
      
   On 2020-12-02 18:57:07, you wrote to me:   
      
    Wv>> As a point you can't route mail. So you have to make sure that   
    Wv>> incoming messages on 1 link aren't send out on the other. And if you   
    Wv>> write a message yourself you have to make sure it only goes out on 1   
    Wv>> connection, otherwise you would send out dupes which have different   
    Wv>> origin pointnumbers, which probably makes them difficult as dupes,   
    Wv>> which would be annoying. So probably not easy to configure in most   
    Wv>> tossers (if at all possible).   
      
    CP> Possibly. I'm learning as I go. Currently, I have one othernet and one   
    CP> point connected to this program. I'm not sure, but it could be possible   
    CP> that I could connect another point, and any identical echoes would receive   
    CP> messages from both points, but the outbound I believe is already   
   configured   
    CP> to this point address. I'm not sure. I could also wind up with duplicate   
    CP> echos.   
      
   I think it would be smart, not to try this! ;)   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 103/705 105/81 124/5016 129/305 153/757 203/0 221/0 1 6 360   
   SEEN-BY: 229/426 664 700 240/5832 280/464 282/1038 292/8125 301/1   
   SEEN-BY: 310/31 322/757 335/364 396/45 423/81 120 460/58 4500/1   
   PATH: 280/464 221/1 6 153/757 229/664 426