Re: Refused Connection
By: mark lewis to Tommi Koivula on Thu Oct 17 2019 10:54 am
ML> paul, has a connection with this system worked in the past or is this the
first
ML> attempt at connecting between your systems?
So it has in the past. (I'm the connection Paul is refering to).
This is Argus -> Argus - whats recently changed is the tosser - and thus the
format of the ?LO files. (The packets are still going to the same path they
were previously).
I dont recall what the format was previously (it was Ezycom), but now that SBBS
is tossing the mail, the interpretation of the ?LO files is incorrect by Argus.
(My) Argus is quite happily sending to an upstream SBBS, but fails when sending
to an upstream Argus.
SBBS is configured to toss mail in the outbound C:/mailer/outbound (I've also
tried C:\mailer\outbound - but the format of the ?LO file is
^C:/mailer/outbound...)
Argus is configured for the outbound has \mailer\outbound (and its installed on
C:)
If I drop the "C:" from the SBBS config - argus interprets the outgoing packet
as C:\mailer\outbound/mailer/outbound.015/xxxx.pkt (and thus is invalid and
doesnt send). (The format of the ?LO is ^/mailer/outbound.015/xxxx.pkt)
If I leave the "C:" in the SBBS config - argus happily attempts to transfer the
files (it knows about it, reports the size, etc) - and sends happily to another
SBBS - but to another Argus, the remote refuses. (In this case the remote is
Paul). (And in this case the format of the ?LO file is
^C:/mailer/outbound.015/xxx.pkt)
My work around is to get SBBS to toss the mail into an outbox, and have that
outbox configured in Argus.
I'm not sure who is "at fault"? I would suggest Argus - it shouldnt be sending
to the remote the name of the file as /mailer/outbound.015/xxx.pkt right? it
should just say here is packet xxx.pkt and the remote saves it with whatever
name it wants, in whatever path it is configured?
...δεσπ
... Some men are discovered; others are found out.
--- SBBSecho 3.10-Linux
* Origin: Alterant | An SBBS in Docker on Pi! (3:633/509)
|
