@MSGID: 1:154/10 598a4e1c5555
@CHRS: UTF-8 4
@TID: hpt/lnx 1.9.0-cur 14-08-16
@SEEN+BY: 154/10 20 30 40 700 203/0 221/1 6 230/0 249/303 266/404 280/464
@SEEN+BY: 320/219 340/800 423/81 640/384 2320/100 3634/12
@PATH: 154/10 203/0
Hello All,
Here the testing begins to make sure binkd works on that
machine, connection is made, and fmail toss is ran. If it
shows up in Golded over there, I can reply back and see if
it makes it's way back.
Only reason I'm doing the test in here is because this is
the only echo I've enabled right now (for ARM testing
purposes).
Regards, Nick
... "Не знаю. Я здесь только
работаю."
-+- GoldED+/LNX 1.1.5-b20170303
+ Origin: thePharcyde_ distribution system (Wisconsin)
(1:154/10)
Hi! Nick,
Congrats! Oops, the quoted tagline is my fault...
I'm receiving messages on that point just fine, but I can't
seem to scan out a new message just yet. "fmail scan"
deletes the echomail.jam file that Golded creates and then
the logs say: "Scanning JAM message bases for outgoing
messages... No new outgoing messages"
Still working on it. ;)
I'm receiving messages on that point just fine, but I can't
seem to scan out a new message just yet. "fmail scan"
deletes the echomail.jam file that Golded creates and then
the logs say: "Scanning JAM message bases for outgoing
messages... No new outgoing messages"
Probably some new-fangled advanced security facility... ermm,
permissions thing?
Still working on it. ;)
Excellent!
Seems like something is trying to compress the echomail when scanning
even though I specified it not to. Unless I missed something
somewhere, of course!
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,145 |
Nodes: | 15 (0 / 15) |
Uptime: | 09:47:20 |
Calls: | 230,082 |
Calls today: | 2 |
Files: | 59,459 |
D/L today: |
45 files (135M bytes) |
Messages: | 291,780 |