| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | The first results... |
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: ompomp.dp.ua
--- XStation
* Origin: (2:464/5555)SEEN-BY: 3/0 633/0 267 280 281 402 640/384 712/0 848 770/1 @PATH: 464/5555 46/50 5020/400 4441 1042 140/1 123/500 154/10 203/0 280/5555 @PATH: 712/848 633/280 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.