NOTIFY SELF
NOTIFY ERRORS
NOTIFY RECEIPT
What am I missing here?
NOTIFY SELF
NOTIFY ERRORS
NOTIFY RECEIPT
What am I missing here?
is that the only thing you have set for them? i'm using the
following here in my region control file...
netaddress 1:18/0
submit 1:229/426 INTL NOKILLSENT
notify errors INTL CRASH NOKILLSENT
notify receipt INTL NOKILLSENT
notify self INTL NOKILLSENT
messages /sbbs/ftn/netmail
the NOKILLSENT attribute is due to a local patch so that my mailer
doesn't delete the segment file which is sent directly from my
makenl master directory... i forget if i offered the patch but i
think it did... i'm not sure if it has been applied to the main
source or not, though... i think it has since i don't find my patch
file and my script is not attempting to apply it after updating the code...
i always use INTL to make sure that the proper 3D/4D address
information and control lines are used... i forget if makenl can do
5D
(zone:net/node[.point]@domain) yet...
i also place the destination host's address on the net lines...
eg:
Net 116 wwwwwwww.txt 1:116/0
Net 123 xxxxxxxx.txt 1:123/0
Net 135 yyyyyyyy.txt 1:135/0
Net 3634 zzzzzzzz.txt 1:3634/0
granted, makenl defaults to sending the notice to the /0 but i do
it this way anyway...
not sure if this will help you or not, though... i'm using
self-built linux version and haven't updated in a year or three...
By: Marc Lewis to mark lewis on Mon Feb 24 2020 13:28:29
one can only hope ;)
yeah, if there is no flavor specified, makenl generates the MSG
with no special attributes so it would go normal to the destination link... normal would be related to your routing which may be crash, direct, or immediate possibly...
yeah, if there is no flavor specified, makenl generates the
MSG with no special attributes so it would go normal to the
destination link... normal would be related to your routing
which may be crash, direct, or immediate possibly...
i don't know... what version of makenl are you running? i've
self-built 3.5.1 (Linux) here that i built on 2019 Jul 29...
also, what does your log file say? does it indicate that it is
generating the notifications? i forget if there's a log level
setting that will show that, though...
+ 05-Mar-2020 07:54:47 makenl[2585] MakeNL started- 05-Mar-2020 07:54:47 makenl[2585] MakeNL 3.5.0 (OS/2 32-bit)
compiled with Watcom C on May 4 2019 22:04:35
i don't see anything wrong there... what do your Net lines look
like in your Data section? mask your file names, please...
eg:
Data
Region,18,SE_US_&_Caribbean_(2020/054),AL_FL_GA_MS_NC_SC_TN_PR_DO,m ark_lewis,-Unpublished-,300,XA,CM,INA:sestar.synchro.net,IBN,PING
Files
Node 0 vvvvvvvv.txt ; node files must precede any
network files Net 116 wwwwwwww.txt 1:116/0 ; net 116 segment definition Net 123 xxxxxxxx.txt 1:123/0 ; net 123 segment
definition Net 135 yyyyyyyy.txt 1:135/0 ; net 135 segment
definition Net 3634 zzzzzzzz.txt 1:3634/0 ; net 3634 segment
definition
FILES
Net 106 xxxxxx 106/0 ; Houston TX
Net 124 xxxxxxxx 124/0 ; Dallas TX
Net 130 xxxxxxxx 130/0 ; Fort Worth TX
Net 387 xxxxxx 387/0 ; San Antonio TX
Net 396 xxxxxx 396/0 ; New Orleans LA
FILES
Net 106 xxxxxx 106/0 ; Houston TX
Net 124 xxxxxxxx 124/0 ; Dallas TX
Net 130 xxxxxxxx 130/0 ; Fort Worth TX
Net 387 xxxxxx 387/0 ; San Antonio TX
Net 396 xxxxxx 396/0 ; New Orleans LA
why don't the above have the zone specified for the response
address? ;)
FILES
Net 106 xxxxxx 1:106/0 ; Houston TX
Net 124 xxxxxxxx 1:124/0 ; Dallas TX
Net 130 xxxxxxxx 1:130/0 ; Fort Worth TX
Net 387 xxxxxx 1:387/0 ; San Antonio TX
Net 396 xxxxxx 1:396/0 ; New Orleans LA
i don't know but that could be the fix for this problem... maybe...
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 18:22:03 |
Calls: | 633 |
Calls today: | 7 |
Files: | 7,638 |
Messages: | 291,889 |