Subj : new mail notification
To : echto
From : Digital Man
Date : Tue Jan 19 2016 03:17 pm
Re: new mail notification
By: echto to Digital Man on Tue Jan 19 2016 10:25 am
> Re: new mail notification
> By: Digital Man to echto on Mon Jan 18 2016 16:15:52
>
> > SBBSecho only deals with FidoNet mail, or more specifically, FidoNet
> > netmail and echomail. Is the kind of "mail" you're referring to? SBBSecho
> > creates the telegrams to users, notifying them of received netmail and
> > echomail, when it tosses the mail. SBBSecho doesn't need to run during
> > logon to do this as the telegrams created when SBBSecho does run just sit
> > there until they are displayed to the user and then automatically
> > deleted.
>
> Yes, apologies, it's netmail and echomail. I can send a test netmail
> message to another sbbs bbs that is operating with a default configuration
> and during the login sequence SBBSecho displays,
>
> SBBSecho: So-and-so sent you netmail from this node
>
> When I log into my sbbs, SBBSecho never displays the message about waiting
> netmail. I suspect it is because I am calling baja module after baja
> module.
I'm not really sure what you mean by "calling baja module after baja module".
Normally, telegrams are displays during the logon process. If you're somehow
defeating the logon process, I suppose that could prevent telegrams from being
displayed to the user.
If you look in your sbbs data/msgs directory, do you see a buch ####.msg files?
If so, those are telegrams waiting to be displayed to users (normally, as they
logon).
> Is there a way to read the telegrams without SBBSecho?
SBBSecho doesn't have anything to do with reading/displaying telegrams. You can
force any waiting telegrams to be displayed to the user with the JS
bbs.get_telegram() method. There's no Baja-equivalent method, but you could
force the "message waiting" flag on with the following Baja code:
or _node_misc NODE_MSGW
(this requires the !include of sbbsdefs.inc and nodedefs.inc)
The next time the BBS checks for pending telegrams (e.g. in a call to the Baja
SYNC function), any/all waiting telegrams should be displayed.
> And what
> state does SBBS have to be in to display the telegrams; I mean, what actions
> have to place before SBBS decides it's OK to display telegrams. From my
> observations, SBBS will not display telegrams while a baja module is
> running, i.e. waiting for user input. I might be wrong about that, but that
> appears to be what I am experiencing.
SBBS will check for an display telegrams in many circumstances, but to force
that check and display, use the Baja SYNC function.
> > If you're just interested in displaying the number of personal email
> > messages waiting for a user, you can use the MAILW @-code to display this
> > value.
>
> Thanks, I'll take a look at that.
Sounds like the @-code wasn't what you were looking for however.
digital man
Synchronet "Real Fact" #14:
SBBSecho was introduced (replacing SBBSFIDO) for Synchronet v2 in 1994.
Norco, CA WX: 60.8�F, 74.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net