Greetings,

I have poured over the logs for both my point setup and mystic. The only errors I find are in the mutil log at or about the time I was supposed to receive a Netmail from an outside source. Please find them below, there were more but this should give you the gist.

9db62811.pkt does not match an AKA (1:340/202.1)
Import from c:\mystic\echomail\in\unsecure\
! Apr 21 06:10:10 9db62811.pkt does not match an AKA (1:340/202.1

If you know how to fix id love to know!

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/09 (Windows/64)
* Origin: Abacus BBS (21:1/190)

Hello Nitro,

9db62811.pkt does not match an AKA (1:340/202.1)
Import from c:\mystic\echomail\in\unsecure\
! Apr 21 06:10:10 9db62811.pkt does not match an AKA (1:340/202.1

If you know how to fix id love to know!

I'm not exactly sure why mutil is saying that unless that .pkt is addressed to 340/202.1? I don't know.

I sent you a netmail yesterday. The netmail was addressed to 1:340/202.1 but the .pkt was sent to, and addressed to 1:340/202 to be sent on to your point.

Here's my binkd.log just FYI..


+ 20 Apr 10:15:54 [15136] call to 1:340/202@fidonet
20 Apr 10:15:55 [15136] trying bbs.abon.us [65.102.14.165]...
20 Apr 10:15:55 [15136] connected
+ 20 Apr 10:15:55 [15136] outgoing session with bbs.abon.us:24554 [65.102.14.165]
- 20 Apr 10:15:55 [15136] OPT CRAM-MD5-8f0b7985edb4b4a6c537f3976795e0ab
+ 20 Apr 10:15:55 [15136] Remote requests MD mode
- 20 Apr 10:15:55 [15136] SYS Abacus BBS
- 20 Apr 10:15:55 [15136] ZYZ Nitro
- 20 Apr 10:15:55 [15136] TIME Mon, 20 Apr 2020 10:15:56 -0700
- 20 Apr 10:15:55 [15136] VER Mystic/1.12A46 binkp/1.0
- 20 Apr 10:15:55 [15136] BUILD 2020/04/09 22:54:52 Windows/64
+ 20 Apr 10:15:55 [15136] addr: 21:1/190@fsxnet
+ 20 Apr 10:15:55 [15136] addr: 1:340/202@fidonet
+ 20 Apr 10:15:55 [15136] addr: 46:10/136@agoranet (n/a or busy)
+ 20 Apr 10:15:55 [15136] addr: 77:1/130@scinet (n/a or busy)
+ 20 Apr 10:15:55 [15136] addr: 44:100/28@dorenet (n/a or busy)
+ 20 Apr 10:15:55 [15136] sending /usr/local/fido/outbound/015400ca.cut as bb81a8b9.pkt (564)
- 20 Apr 10:15:55 [15136] QSIZE 0 files 0 bytes
+ 20 Apr 10:15:55 [15136] sent: /usr/local/fido/outbound/015400ca.cut (564, 564.00 CPS, 1:340/202@fidonet)
+ 20 Apr 10:15:55 [15136] done (to 1:340/202@fidonet, OK, S/R: 1/0 (564/0 bytes))
20 Apr 10:15:55 [15136] session closed, quitting...
20 Apr 10:15:55 [28906] rc(15136)=0

Does bb81a8b9.pkt exist in your inbound (most likely unsecure inbound) and can you toss it successfully?

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 21 Apr 2020, Nitro said the following...

I have poured over the logs for both my point setup and mystic. The only errors I find are in the mutil log at or about the time I was supposed to receive a Netmail from an outside source. Please find them below, there were more but this should give you the gist.

9db62811.pkt does not match an AKA (1:340/202.1)

First, open up the packet with an editor to see if it is indeed a netmail or
if it's echomail.

If Mystic is telling you this, then your problem lies with Mystic's configuration of your point system. You shouldn't have to look at your point system logs anymore, unless you're having an issue with netmail going from
your point system anywhere past your Mystic system.

If the packet you opened is NETMAIL:
What do you have for your ROUTE or ROUTE TO statement in Mystic?

If the packet you opened is ECHOMAIL:
Have you setup a link in Mystic for your point?

Providing some copy/pasta or screenshots of your link setup screens (minus
any passwords) would also be helpful.

Accession

--- Mystic BBS v1.12 A46 2020/04/20 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)