sbbs@bbs:/bbs/mail/in/1-214-23$ ls
925a7a00.mo0
I have a secondary Fidonet node set up for portable use and just to have a bit of fun with the
settings. I am using OUTBOUND fileboxes for most all my links. Binkd sends these mail bundles out
without issue. I also have my aforementioned node (along with several points for othernets) to use an
inbound filebox. This, however, is not working:
SBBSecho v3.01-Linux (rev 3.36) - Synchronet FidoNet EchoMail Tosser
Loading configuration files from /bbs/sbbs/ctrl/
SBBSecho 3.01-Linux r3.36 Jul 9 2017 GCC 4.9.2 invoked with options: -cemtq 7 packers, 44 linked-nodes, 12 echolists configured
Reading ../data/areas.bbs
Read 620 areas from ../data/areas.bbs
Reading bad area file: ../data/badareas.lst
Read 0 areas from ../data/badareas.lst
Scanning /wd/bbs/sbbs/temp/sbbsecho/ for Stray Outbound Packets...
Scanning for Inbound Packets...
Scanning 314:314/0 inbox: /bbs/mail/in/314-314-0
Scanning 1:214/24 inbox: /bbs/mail/in/1-214-24
Scanning 1:218/700 inbox: /bbs/mail/in/1-218-700
Scanning 1:214/23 inbox: /bbs/mail/in/1-214-23
Scanning 24:160/23 inbox: /bbs/mail/in/24-160-23
Scanning 618:300/18.23 inbox: /bbs/mail/in/618-300-18.23
Scanning 314:314/45.1 inbox: /bbs/mail/in/314-314-45.1
Scanning secure inbound: /bbs/mail/in/
Scanning non-secure inbound: /bbs/mail/in/unknown/
Scanning for Inbound NetMail Messages...
Writing 0 areas to ../data/badareas.lst
Deleting /bbs/sbbs/ctrl/sbbsecho.bsy (from line 2354)
done
There is currently one mail packet in /bbs/mail/in/1-214-23.
sbbs@bbs:/bbs/mail/in/1-214-23$ ls
925a7a00.mo0
If I move the packet(s) to /bbs/mail/in, they are processed just fine.
On 2017 Aug 14 20:17:40, you wrote to All:
sbbs@bbs:/bbs/mail/in/1-214-23$ ls
925a7a00.mo0
what does ls -la show? i'm thinking of the owner:group but it is a long shot since the same mailer writes the same files for other traffic and they're working...
There is currently one mail packet in /bbs/mail/in/1-214-23.
sbbs@bbs:/bbs/mail/in/1-214-23$ ls
925a7a00.mo0
That's actually a bundle (archive) not a packet.
But SBBSecho should
discover and unpack that bundle just fine, even if it's in an inbox. Can you search your sbbsecho.log file for any errors (perhaps unpacking errors) with regards to that bundle filename?
If I move the packet(s) to /bbs/mail/in, they are processed just fine.
That is odd. Looking at the code, I see nothing obvious. Do other inboxes work correctly? Can you search your sbbsecho.log file for the string 'Unpacking bundle' and see if you find success or failures unpacking bundles in inboxes?
That is odd. Looking at the code, I see nothing obvious. Do other inboxes work correctly? Can you search your sbbsecho.log file for the string 'Unpacking bundle' and see if you find success or failures unpacking bundles in inboxes?
what does ls -la show? i'm thinking of the owner:group but it is a long
shot since the same mailer writes the same files for other traffic and
they're working...
sbbs@bbs:/bbs/mail/in/1-214-23$ ls -la
total 40
drwxrwxr-x 2 sbbs sbbs 4096 Aug 14 19:19 .
drwxr-xr-x 17 sbbs sbbs 28672 Aug 15 16:24 ..
-rw-rw-r-- 1 sbbs sbbs 1276 Aug 14 19:19 925a7a00.mo0
There is currently one mail packet in /bbs/mail/in/1-214-23.
sbbs@bbs:/bbs/mail/in/1-214-23$ ls
925a7a00.mo0
That's actually a bundle (archive) not a packet.
I knew that, but just typed the wrong word. It was getting late for me and past my bedtime...
But SBBSecho should
discover and unpack that bundle just fine, even if it's in an inbox. Can you search your sbbsecho.log file for any errors (perhaps unpacking errors) with regards to that bundle filename?
sbbs@bbs:/bbs/sbbs/data$ grep 925a7a00.mo0 sbbsecho.log sbbs@bbs:/bbs/sbbs/data$
Nothing found.
On 2017 Aug 15 16:30:28, you wrote to me:
what does ls -la show? i'm thinking of the owner:group but it is a long
shot since the same mailer writes the same files for other traffic and
they're working...
sbbs@bbs:/bbs/mail/in/1-214-23$ ls -la
total 40
drwxrwxr-x 2 sbbs sbbs 4096 Aug 14 19:19 .
drwxr-xr-x 17 sbbs sbbs 28672 Aug 15 16:24 ..
-rw-rw-r-- 1 sbbs sbbs 1276 Aug 14 19:19 925a7a00.mo0
so it has the proper owner:group... i was thinking that maybe that one bundle had come in while you were working on getting things set up... when we started,
we used prebuilt packages for the mailer... it was installed with a different owner:group and we had to figure all that out first before being able to get things moving between the mailer and the tosser...
Re: Re: SBBSECHO Inbound Fileboxes
By: Ray Quinn to Digital Man on Tue Aug 15 2017 05:14 pm
There is currently one mail packet in /bbs/mail/in/1-214-23.
sbbs@bbs:/bbs/mail/in/1-214-23$ ls
925a7a00.mo0
That's actually a bundle (archive) not a packet.
I knew that, but just typed the wrong word. It was getting late for me and past my bedtime...
But SBBSecho should
discover and unpack that bundle just fine, even if it's in an inbox. Can you search your sbbsecho.log file for any errors (perhaps unpacking errors) with regards to that bundle filename?
sbbs@bbs:/bbs/sbbs/data$ grep 925a7a00.mo0 sbbsecho.log sbbs@bbs:/bbs/sbbs/data$
Nothing found.
Interesting. Since you said moving the file to the inbound caused it to be unpacked, I would expect to see log entries for those files you moved and were then successfully unpacked.
Anyway, I think I see the problem: If you add a trailing slash to those inbox paths in your sbbsecho.ini, does that fix the problem?
Anyway, I think I see the problem: If you add a trailing slash to those inbox paths in your sbbsecho.ini, does that fix the problem?
That seems to be it. Here is the related log entry:
Thank you for the bug report!
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 03:35:18 |
Calls: | 510 |
Messages: | 220570 |