On Sat, 14 Feb 2015, Tommi Koivula wrote to mark lewis:   
      
    ml> there was like 300+ of them that appeared over here... all from    
    ml> the same Z2 system...   
      
    TK> Was it one of my systems?   
      
   yessir it was... i saw that it was a one time occurance and figured you would   
   get enough grief from others about it ;)   
      
    TK> I rescanned this echo from 2:221/360 to 2:221/6. It may be so that    
    TK> all those messages got exported from 2:221/6 to 2:221/0 and out.    
      
   yeah, i'd have to go look but yes, i believe they were from your /6...   
      
    TK> If that is the case, I'm sorry about that.   
      
    TK> It was not computer error, I'm the guilty one.   
      
   not a problem...   
      
   one thing that does not seem right, though, is that the rescan evidently   
   redated all those messages to the current date of the rescan... that isn't   
   right, AFAIK... maybe it was done so the messages could be retained on the   
   system for X days... i can see that if the software being used only has one   
   date field to work with... i like those with three date fields... one for the   
   message's date, one for the arrival on my system and one for when the   
   receipient has read the message... in this way, purges are done on the arrival   
   date and/or the receipient read date leaving the original message date alone...   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)