Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    FMAIL_HELP    |    Fmail support    |    2,396 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 335 of 2,396    |
|    Oleg Pevzner to Wilfred van Velzen    |
|    The first results...    |
|    07 Jul 14 23:26:18    |
      Hello Wilfred!              Monday July 07 2014 12:56, you wrote to me:               OP>> 1. Why can't FMail be configured by use of environment variables?        OP>> E.g., I want to use %FTN%-variable with default value H:\FIDONET        OP>> defining paths but FSetupX accepts full paths only.        WV> Why? I don't know. Maybe because I and the previous author never        WV> thought of that, and nobody asked before? ;)               Okey, I understood. It would be a very useful feature and we'll be glad to       see it realized in the next releases.               OP>> 2. I have 30 echo-groups. In FastEcho I could have 26 groups from        OP>> A to Z and 6 groups from 1 to 6. In FMail this value is limited        OP>> by 26 only from A to Z. Is it a principle limit and is it        OP>> possible to increase this value?        WV> It's a limit in the configuration file, so it's (very) difficult to        WV> change.               Well, I accepted this restriction. But, to be honest, it's a pitty. For       example, a large node can have 30 and more echo groups easily.               OP>> 3. I haven't found any possibility in the configuration to        OP>> specify the directory for an unprotected inbound. So, the        OP>> question appears where the packages will be placed during the        OP>> unprotected tossing?        WV> It will be placed in the directory where you have your mailer        WV> configured to place it. I don't think it's upto a tosser to handle        WV> this directly. I think most sysops handle this manually...               In the previous message I described the possible situation when the session       is password-protected, the node is defined in the area manager but no password       is specified for it. As already also mentioned, it's rather exotic situation       but it can take place in real life.               OP>> 4. The uppercase and lowercase characters can't be distinguished        OP>> in the file names, paths, passwords etc. In some cases, it may be        OP>> important (e.g., when we talk about the passwords).        WV> From origin fmail is a dos program, so it only allowed uppercase        WV> filenames and paths. When I come accross this, I change it to allow        WV> both upper and lower case. But I probably missed a few. If you point        WV> them out, I will change that for the next release.        WV> Passwords are mixcase where it is allowed by the standards.               I don't want to repeat all this once more, you may read all suggestions       related to this issue in my previous message too.               Thank you once more for attention. Please note that my comments should be       considered only as friendly remarks and are directed to the improvement of a       nice and useful software. :)              WBR, Oleg Monday July 07 2014       E-Mail: omp |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca