05 Jun 15 02:30, you wrote to me:   
      
    MK> -={ jeudi, juin 04 2015, 19:30:26 -0700 }=-   
      
    MK> Hey mark!   
      
    ml>> ahhh... yeah, that was written without any testing or   
    ml>> consideration to the '.'...   
      
    MK> Understood.  However it did raise the issue that if 5D addressing isn't   
    MK> taken care of then the original posting will produce an origPoint as well   
    MK> as a destPoint with the '@domainname' taked on at the end such as;   
      
   yup! that was the first thing i saw when i looked over it with the 5D address   
   format...   
      
   [...]   
      
    MK> which produces the desired splits while retaining the 5D-ness of both   
    MK> the complete origAddr and destAddr (ie 1:11/111.0@fidonet in your   
    MK> original posting).   
      
   it was based on your example just in the full 5D format...   
      
    MK> I currently cannot think of a need for either origDomain or destDomain   
    MK> but have already come up with a way to extract it if and when it is   
    MK> needed.  I have serious doubts that it is needed.   
      
   as previously noted, if you don't participate in any additional FTNs, you may   
   not ever see a need for it... if you share your code and others use it, they   
   may need this capability if they are in multiple FTN networks...   
      
   )\/(ark   
      
   ... Don't worry. I'm fluent in weird.   
   ---   
    * Origin:  (1:3634/12.73)