Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 512  |
|  Dran Draggore to mark lewis  |
|  RAMSG purging on 2.02  |
|  12 Apr 16 06:33:42  |
 Re: RAMSG purging on 2.02 By: mark lewis to Dran Draggore on Mon Apr 11 2016 10:07 am DD>> I'm currently using RemoteAccess 2.02. ML> why? It was the first version I ever used. DD>> RAMSG 2.50.b4 DD>> ============= DD>> * When purging messages in the Hudson message base by date, RAMSG ML> will DD>> now treat dates where the year is smaller than 80 to be in the DD>> 21st DD>> century (20xx). DD>> Does this mean that older versions of RAMSG will delete messages DD>> created ML> in DD>> 2016 ? ML> are you using the HMB? I plan on using HMB for local message areas. And JAM for echoes. I think this adds authenticity to the deployment. I've already created 200 unfilled areas since the documentation says Hudson can only use 200. Heh. I could just experiment but since I'm still reading the documentation, I thought I'd get an answer in advance; and check out the RA_SUPPORT echo, which is apparently bustling with activity. --- SBBSecho 2.33-Linux * Origin: (1:218/215) |
[ << oldest | < older | list | newer > | newest >> ]