TIP: Click on subject to list as thread! ANSI
echo: synchronet
to: RAGNAROK
from: DIGITAL MAN
date: 2020-04-26 21:37:00
subject: Re: Filefix?

  Re: Re: Filefix?
  By: Ragnarok to Rampage on Sun Apr 26 2020 07:59 pm

 > El 26/4/20 a las 10:36, Rampage escribi¢:
 > >   Re: Filefix?
 > >   By: Dumas Walker to All on Sat Apr 25 2020 18:44:06
 >
 >
 > >  DW> Is anyone using a filefix agent with Synchronet/SBBSECHO?
 >
 > > at this point in time, there is none... i'm not aware of anything in
 > > development, either... it is something that i've been thinking about since
 > > i did my work on TickIT but i've not come up with a good/proper place to
 > > insert the "agent"... the way that sbbsecho processes netmails, it would
 > > seem that inside sbbsecho with the areafix stuff would be the best place
 > > but that means that sbbsecho would then need to understand the tickit.ini
 > > file and the sbbs file areas and that's probably not a good thing to
 > > have...
 >
 >
 > Maybe sbbsecho can implement some hooks seetings that call in-preocess
 > js scripts
 > I dont known if area too muy dificult
 >
 > on_sbbsecho_start(some process paramaeter)
 > on_nemail_incoming (the message)
 > on_process_packet (the packet filename)
 > on_sbbsecho_end (void)

I considered that, but I didn't want to link in the JS engine just for this one
function. So instead, I did the robot-trigger thing:

Add support for "robots": Right now, robots are for receiving netmail messages
only (e.g. areamgr requests or whatever). In the future, they could be extended
to echomail areas too, if that's desirable.

For now, it's really intended for ticket-FileFix.

Anyway, NetMail can be received for the robot-name@ and
the mail message will be stored in the Synchronet "mail" base. The recipient
extension will be absent since there is no valid user account associated with
the robot. Robot names supercede other user names/aliases for received netmail.
If one or more netmail messages were imported for a robot and that robot has
a semaphore path/filename specified (e.g. to trigger a timed event), then that
semaphore will be "touched" before SBBSecho exits.
One weird anomly with this is if attached files are received for robots, those
files will be stored in data/user/0000.in. The altnerative is to just ignore
file attachments sent to robots.

The echofg supprot for robots is still yet to be added. In the mean time, you
can add robots to your sbbsecho.ini like so:
[robot:]
semfile=/path/to/semfile

Incremented version to 3.11.

                                            digital man

This Is Spinal Tap quote #14:
The Boston gig has been cancelled. [Don't] worry, it's not a big college town.
Norco, CA WX: 69.6øF, 55.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

SOURCE: echomail via QWK@docsplace.org

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™.