25 Oct 15 13:25, you wrote to me:   
      
    ML>> are hotdoged's PKTs Type 2, Type 2+ or Type 2.2? is there a way to   
    ML>> choose which one to use?   
      
    ML>> nick mentioned setting his tosser to look for his hotdoged PKTs as   
    ML>> Type 2 but it probably needs to be Type 2+ or Type 2.2 since Type 2   
    ML>> doesn't have fields for point addresses...   
      
    NB> They are indeed type 2+.   
      
   be aware that if they are Type 2+, the PKT header has no field for the eight   
   character FTN domain... this field is available in the Type 2.2 PKTs... with   
   this in mind, there may be problems when pulling or sending mail from/to   
   multiple FTN domains (eg: FIDO, AGORANET, TECHNET, etc) if there is any   
   duplication of nets and nodes across the domains... here in fidonet that's   
   been eliminated but the same cannot be done across FTN domain boundaries...   
      
    NB> After switching my password to 8 or less characters I was able to   
    NB> remove that setting.   
      
   excellent! that may have also contributed to the circular path detection   
   problem... some information from the PKT header is needed when processing the   
   packed messages because the packed messages don't have anywhere to carry that   
   information... one example would be knowing that the message came from a point   
   so the boss might see its 2D address in the seenby and/or path already... one   
   might be able to glean this information from the MSGID control line but that   
   line is not intended for this purpose and can be unreliable (eg: missing or   
   wrong due to a regurge)... the PKT header contains additional data that may be   
   needed in addition to that within the message...   
      
   )\/(ark   
      
   ... Coming to you live from a finite point in the space-time continuum!   
   ---   
    * Origin:  (1:3634/12.73)