Hello Deon!

Thursday September 06 2018 01:08, you wrote to All:

 > 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?


Yes that is exactly what looks to be the problem.
You have not correctly set up the correct addresses
Check what is your systems address in Mystic and if it is being passed to all
echo and file areas as a 'From'.

Next is the addresses used on both correct as above shows 314:314 but your
message to mbse sent from 3:633 (509) so just what is your address?

Needless to say 314: is not a valid Fidonet network address locator.


If you have not yet got a NODELIST entry for your system/s I suggest you do so
as mbse could get confused by an invalid address how ever all that said that 
is
not the main problem which is that Mystic is not correctly set up.

Using a dummy address for this example with 314:314/n  Mbse should be set up 
as
the primary system addresses of 3:314/n

The Mystic address as 3:314/n.1 if using it as a point with all uplink address
for echos and files as per mbse (3:314/n). Mbse must have the downlink for
Mystic system as 3:314/n.1 and also mbse must be set up with system address
3:314/n.

Mbse should be set up to autocreate new areas for echos per the docs and
likewise if files are coming in ditto but here using FILEGATE.ZXX as the file
list stored in the correct directory which get updated when ever a new one
comes in from your (mbse) uplink.

In my case and normally it is ~/var/arealists and this is created using the
file magic processing.

I.e., in 10.4
A.  Copy file FILEGATE.ZXX
    1.  Magic     Copy File
    2.  Filemask  FILEGATE.ZXX
    3.  Active    Yes
    4.  Deleted   No
    5.  Area      FG_WORF
    6.  To path   /home/mbse/var/arealists
    7.  Compile   No

Again in 10.4
B.  Execute file FILEGATE.ZXX
    1.  Magic     Execute
    2.  Filemask  FILEGATE.ZXX
    3.  Active    Yes
    4.  Deleted   No
    5.  Area      FG_WORF
    6.  Command   dos2unix /home/mbse/var/arealists/FILEGATE.ZXX
    7.  Compile   No


Note that the for above paths I use /home/mbse instead of /opt/mbse as I could
boot to other distros or versions and I like to minimise my work.

This you can do when building mbse by the usage of configure prefix=path

where mine is --prefix=/home

Hope it helps,


Vince

--- Mageia Linux v6/Mbse v1.0.7.6/GoldED+/LNX 1.1.501-b20150715
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)