Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to The Linux/FreeBSD MBSE BBS Suppo...  <--  <--- Return to Home Page
   Networked Database  The Linux/FreeBSD MBSE BBS Suppo...   [398 / 554] RSS
 From   To   Subject   Date/Time 
Message   Deon George    All   Hi   September 6, 2018
 1:08 AM *  

Hi,

I'm new to MBSE - I've been playing with it for the last few days, and today I
finally set it up as my "mail hub". I was a Sysop 25+ years ago (like many I
learning), so I'm enjoying getting (back) into this community.

I started BBSing 2 weeks ago and have also a Mystic up and running.

Today, I changed my Mystic to be a point for the networks I'm connected with
(Fido, FSX ...) with MBSE being the dot zero. While I havent fully tested
everything, it appears that netmail is working fine (at least to my hub
anyway).

What I'm having trouble with is echomail. I think the problem is with Mystic,
but wanted ask here for a second opinion. Incoming netmail is being sent to my
hub, however, when the hub opens the packet the source looks like below, and
thus it is being tossed into bad mail because of the wrong source address:

+ 05-Sep-2018 16:10:48 mbfido[363] Execute: /usr/bin/unzip -o -j -L
fec50000.we3
+ 05-Sep-2018 16:10:48 mbfido[363] Packet   : 031ce02f.pkt type 2+
+ 05-Sep-2018 16:10:48 mbfido[363] From     : 314:65535/180.1 to 314:314/180
+ 05-Sep-2018 16:10:48 mbfido[363] Dated    : 05-10-2018 06:10:40
+ 05-Sep-2018 16:10:48 mbfido[363] Program  : Unknown 0xfefe 0.0
+ 05-Sep-2018 16:10:48 mbfido[363] Node 314:65535/180.1 not connected to area
PIN_ADMIN

The From address is definately set as 314:314/180.1 - however all my AKAs (in
Mystic) are shown as x:65535/x.1 (where x is fidonet and fsxnet as well).

If I read the log correctly, does this mean Mystic is writing the wrong source
address?

BTW: I'm running this all on a Pi in Docker - so I dont think that should be
part of the problem. (My containers are available if anybody is interested.) I
also built MBSE as a Debian deb (for both Pi and X86) if that helps. I 
probably
 have some suggestions to improve the build process for "packaging" if that is
of interest as well... (Although my experience of Debian is new, historically
I've always used CentOS - but debian does make a small docker image :).
 
...deon        
                                                                               
                                                                              

    Greetings, Deon George

... A dirty book is rarely dusty.

--- MBSE BBS v1.0.7.6 (GNU/Linux-ARM)
 * Origin: Chinwag | MBSE in Docker on Pi (3:633/509)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to The Linux/FreeBSD MBSE BBS Suppo...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0896 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_laov3daqmar9qusu5kj5i9de35, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_laov3daqmar9qusu5kj5i9de35, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_laov3daqmar9qusu5kj5i9de35, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0