Okay, so as per echicken (I believe it was, my apologies if I'm wrong here), I got the following debugging information on why my mail to the sysop (and presumably anyone else, though I haven't tried implementing that yet) isn't working. He specifically requested a dump of the message header. Here's what I'm putting into that object, and a brief explanation of how some are arrived at:

mHdr values:
from : Khelair (from user.alias)
to : Khelair (selected by code at this point from sysop.alias)
subject : 'dDOC Posting' (using a static subject for all messages at this
point in my code version)

As I mentioned before, I get success from the attempt to save the message with the body as the second argument to dMB.save_msg(), with mHdr as above as the first argument. It never shows up in a personal mailbox, though; I can only access it if I go into 'all system mail' as a sysop.
This led me to a little bit more looking into the logging on the console, since I've got things debugging output there now. When these messages are being saved, messages are turning up in the log as such:
12/19 18:39:55 term Node 1 Khelair running external program: Damo's vDOC/Citadel Shell
12/19 18:40:14 mail 0000 SEND last_msg=400, smb.status.last_msg=401, elapsed=50

aaaand I'm seeing other ones sitting in the queue there, too, presumably from other messages I've tried to save to the base using code 'mail'. I'm going to check and see if I can manually override anything that might be forcing its processing as a form of NetMail, but any tips are greatly appreciated, still, as well.
TIA

---
þ Synchronet þ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

Re: issues sending mail via sub['mail'], debugging info requested
By: Khelair to All on Fri Dec 19 2014 06:47 pm

Okay, so as per echicken (I believe it was, my apologies if I'm wrong here), I got the following debugging information on why my mail to the
sysop (and presumably anyone else, though I haven't tried implementing that yet) isn't working. He specifically requested a dump of the message
header. Here's what I'm putting into that object, and a brief explanation of how some are arrived at:

mHdr values:
from : Khelair (from user.alias)
to : Khelair (selected by code at this point from sysop.alias) subject : 'dDOC Posting' (using a static subject for all messages at this
point in my code version)

As I mentioned before, I get success from the attempt to save the message with the body as the second argument to dMB.save_msg(), with mHdr as above as the first argument. It never shows up in a personal mailbox, though; I can only access it if I go into 'all system mail' as a sysop.

Email has to have the to_ext property set to the destination user's number (e.g. '1' for the sysop, user #1).

See http://synchro.net/docs/jsobjs.html and http://synchro.net/docs/smb.html for details.

aaaand I'm seeing other ones sitting in the queue there, too, presumably from other messages I've tried to save to the base using code 'mail'. I'm going to check and see if I can manually override anything that might be forcing its processing as a form of NetMail, but any tips are greatly appreciated, still, as well.

I don't see anything suggesting that the message is being processed as NetMail.

digital man

Synchronet "Real Fact" #41:
Rob Swindell was laughed out of a FidoNet Net103 (OC, Calif.) meeting in 1992. Norco, CA WX: 55.3øF, 80.0% humidity, 4 mph WNW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: issues sending mail via sub['mail'], debugging info requested
By: Digital Man to Khelair on Sat Dec 20 2014 18:24:01

Email has to have the to_ext property set to the destination user's number (e.g. '1' for the sysop, user #1).
See http://synchro.net/docs/jsobjs.html and http://synchro.net/docs/smb.html for details.

Yep, that was the bit I was missing. Thank you sir. Would've mentioned
it sooner, but the gods of OBSD threw many lightning bolts my way.

I don't see anything suggesting that the message is being processed as NetMail.

Yeah I'm not quite remembering exactly what the message was that was making me think that... I haven't started on my new shell's testing since I've gotten things back up yet, but if this behavior repeats again I'll try to get a little better log of it. I'm pretty sure the to_ext header being defined will keep that from creeping up at all any more now, though.

---
þ Synchronet þ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net