Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 117  |
|  Sergey Poziturin to mark lewis  |
|  No Echolist with hotdogED?  |
|  23 Oct 13 10:07:18  |
 Hello, mark lewis. On 22.10.13 20:59 you wrote: US>> CDP proposal FSP-1016.003 Automatic configuration of Points in US>> Fidonet has answered this question regarding echo forwarding US>> lists .... in section US>> 3.1.2.1.2 ECHOZZZZ.ZIP US>> and US>> 3.2.2 Transmitting the application date ->> Freq ECHOLIST US>> The only thing to consider ... nodes supporting HotDogED clients US>> should add the freq magic ECHOLIST in their system and US>> ECHOZZZZ.ZIP to be sent. So on the supporting system the echo US>> uplink lists have to be compiled and named ECHOZZZZ.LST and zip'd US>> thereafter ... =;) ML> is there anything wrong with sending the existing, published and ML> distributed Echolist? is the above perhaps talking about something ML> else other than the Echolist? something, perhaps, like the list of ML> available areas (%AVAIL) from the feed's uplinks? where are other, ML> unlisted, area names to be found? how is one to know of the ML> existance of an area if it is not in the %AVAIL or %LIST areafix ML> responses? I prefer creating a communicating interface between hotdoged and the node to transfer not only echo names, but also amount of messages in the group, last message date and so on. -- Best regards! Posted using Hotdoged on Android --- Hotdoged/2.7.2/Android * Origin: Android device, Milky Way (2:5020/2141.3) |
[ << oldest | < older | list | newer > | newest >> ]