Hi apam,
Some feature requests:
1. The ability to delete a message in case it's all screwed up.
(Only the auther should be able to delete there own messages)
2. The ability to adjust the timeout settings, before a disconnect.
3. The ability to auto-save messages, in referance to 2 above.
4. When viewing messages, have the page-down/up keys also work.
On 11-21-18 10:11, vorlon wrote to apam <=-
1. The ability to delete a message in case it's all screwed up.
(Only the auther should be able to delete there own messages)
2. The ability to adjust the timeout settings, before a disconnect.
3. The ability to auto-save messages, in referance to 2 above.
4. When viewing messages, have the page-down/up keys also work.
On 11-21-18 09:55, apam wrote to vorlon <=-
Just committed this.. there is a new option "Idle Timeout" in the
BBS.ini main section that takes an integer representing minutes.
(defaults to 10)
4. When viewing messages, have the page-down/up keys also work.
Done, should be in the commit along with idle timeout :)
On 11-21-18 09:55, apam wrote to vorlon <=-
Just committed this.. there is a new option "Idle Timeout" in the BBS.ini main section that takes an integer representing minutes. (defaults to 10)
Any chance of having an idle timeout on a per security level basis
too? That way, the sysop could idle longer than ordinary users.
Handy for sysops who pop in and out of the BBS interface.
On 11-21-18 09:55, apam wrote to vorlon <=-
Just committed this.. there is a new option "Idle Timeout" in BBS.ini main section that takes an integer representing minut (defaults to 10)
Any chance of having an idle timeout on a per security level basis
too? That way, the sysop could idle longer than ordinary users.
Handy for sysops who pop in and out of the BBS interface.
Yep that could be done. I'll have a look at doing it tomorrow.
On 11-21-18 15:06, apam wrote to Vk3jed <=-
Any chance of having an idle timeout on a per security level basis
too? That way, the sysop could idle longer than ordinary users.
Handy for sysops who pop in and out of the BBS interface.
Yep that could be done. I'll have a look at doing it tomorrow.
1. The ability to delete a message in case it's all screwed up.
(Only the auther should be able to delete there own messages)
Should this only be applicable to local message bases? Or all message bases?
2. The ability to adjust the timeout settings, before a disconnect.
Just committed this.. there is a new option "Idle Timeout" in the BBS.ini main section that takes an integer representing minutes. (defaults to 10)
3. The ability to auto-save messages, in referance to 2 above.
I could do this with magiedit, make it save a draft on exit if it's not being saved or aborted (ie exiting due to timeout) Not sure about the internal line editor as that doesn't have draft support (yet).
4. When viewing messages, have the page-down/up keys also work.
Done, should be in the commit along with idle timeout :)
1. The ability to delete a message in case it's all screwed up.
(Only the auther should be able to delete there own messages)
I'd prefer to have a message semaphore so outbound mail could be sent immediately. Obviously there's some configuration needed to allow sysops to set their preferences.
On 11-21-18 22:27, vorlon wrote to Vk3jed <=-
1. The ability to delete a message in case it's all screwed up.
(Only the auther should be able to delete there own messages)
I'd prefer to have a message semaphore so outbound mail could be sent immediately. Obviously there's some configuration needed to allow sysops to set their preferences.
There is a semaphore file created now, when new messages get written.
It's called "mail.out" and is in the Magicka home dir. #>=
On 11-21-18 22:27, vorlon wrote to Vk3jed <=-
1. The ability to delete a message in case it's all screwed u (Only the auther should be able to delete there own messages)
I'd prefer to have a message semaphore so outbound mail could be s immediately. Obviously there's some configuration needed to allow
to set their preferences.
There is a semaphore file created now, when new messages get writ
It's called "mail.out" and is in the Magicka home dir. #>=
Cool. Is there a way to directly trigger a polling event? Or does
one simply use cron or a looping script to check for the semaphore
and poll when it's present? :)
On 11-22-18 09:26, apam wrote to Vk3jed <=-
You can use inotify tools to "watch" the mail.out file and run a script when it notices a change (like modification date etc) this is what I
do.
There was an example in the old docs, I'm not sure if I've updated that part of the wiki, but you can find the old docs in the docs folder.
Yep that could be done. I'll have a look at doing it tomorrow.
That would be awesome. :)
On 11-22-18 11:03, apam wrote to Vk3jed <=-
Yep that could be done. I'll have a look at doing it tomorrow.
That would be awesome. :)
Per security level timeouts should be working now, edit the
corresponding sXX.ini and add an idle timeout = Z where Z is the
minutes.
If an sXX.ini doesn't have an idle timeout set it will default to the system idle timeout, if that is also not set, it will default to 10 minutes.
It's called "mail.out" and is in the Magicka home dir. #>=
Cool. Is there a way to directly trigger a polling event? Or does one simply use cron or a looping script to check for the semaphore and poll when it's present? :)
On 11-22-18 23:10, vorlon wrote to Vk3jed <=-
It's called "mail.out" and is in the Magicka home dir. #>=
Cool. Is there a way to directly trigger a polling event? Or does one simply use cron or a looping script to check for the semaphore and poll when it's present? :)
Cron is your friend. #=)
Cron is your friend. #=)
A very close friend, I might add. :D
On 22-Nov-2018 22:03, apam wrote to Vk3jed <=-
Yep that could be done. I'll have a look at doing it tomorrow.
That would be awesome. :)
Per security level timeouts should be working now, edit the
corresponding sXX.ini and add an idle timeout = Z where Z is the
minutes.
On 11-23-18 17:02, vorlon wrote to Vk3jed <=-
Cron is your friend. #=)
A very close friend, I might add. :D
I haven't botherd him yet, as my system is a point setup just for my testing of the software....
On 22-Nov-2018 20:26, apam wrote to Vk3jed <=-
There is a semaphore file created now, when new messages get writ
It's called "mail.out" and is in the Magicka home dir. #>=
Cool. Is there a way to directly trigger a polling event? Or does
one simply use cron or a looping script to check for the semaphore
and poll when it's present? :)
You can use inotify tools to "watch" the mail.out file and run a script when it notices a change (like modification date etc) this is what I
do.
There was an example in the old docs, I'm not sure if I've updated that part of the wiki, but you can find the old docs in the docs folder.
There was an example in the old docs, I'm not sure if I've update
part of the wiki, but you can find the old docs in the docs folde
Any chance of having a semaphore written for outgoing mail for each
network
type? Or does mail.out only get touched for maginet outbound
messages?
On 12-10-18 12:23, apam wrote to vk3jed <=-
I've just added "per-conference" echomail semaphores. If a conference semaphore is set, it will touch that, if not it will touch echomail semaphore from the bbs.ini, if that is not set, it will do nothing.
So, for your maginet conference you could now put under [main]
semaphore = /path/to/maginet.out
and it will touch that instead of the echomail one.
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 10:45:35 |
| Calls: | 516 |
| Files: | 6,999 |
| Messages: | 289,583 |