Subj : Re: Sent to Staging
To   : Nick Andre
From : C.G. Learn
Date : Thu Mar 09 2017 08:39 am

 Re: Re: Sent to Staging
 By: Nick Andre to C.G. Learn on Thu Mar 09 2017 02:22 am

NA> First of all, lets verify that the BinkD mailbox directory exists for the
NA> destination. If the mailbox/staging directory does not exist, no mail can
NA> be correctly exchanged. Lets shut down both D'Bridge and BinkD.

NA> ie. if the destination is 1:229/426 and your QUEUE directory is \DB\QUEUE,
NA> then in DOS, CD \ your way to your D'Bridge directory and type:

NA> DBUTIL QNAME 1:229/426

NA> MD \DB\QUEUE\D-00106D.0BU

NA> Note the output of DBUTIL QNAME. That makes up the mailbox name, just add
NA> the "D-" infront of it. In this case, 1:229/426 equals D-00106D.0BU.

In the Queue Directory, there is another directory named D-00107N.02l, which
has 3 packets in it, named 01601341.pkt, 31127501.pkt, 31146561.pkt.

NA> While we're at it, lets also make sure nothing is being put on "Hold"
NA> status by BinkD. CD \DB\DATA and type:

NA> DEL /S *.HLD
NA> DEL /S *.TRY

NA> This will delete the control files that tell BinkD to put stuff on hold,
NA> and also resets the number of "tries" (attempts) to contact destination
NA> systems.

There were *.TRY files in the \DBRIDGE\DATA\FIDONET, and \DBRIDGE\DATA\WHISPNET
directories, which have just been deleted. There is also a 0113005D.FLO file in
the \DBRIDGE\DATA\VALHALLA directory which I have not touched.

NA> Restart both D'Bridge and BinkD. Watch very carefully on the next
NA> connection attempt, or force one out by doing a POLL to the remote system.

NA> If mail is still not being exchanged, then verify in the logs that when
NA> the system in question connects with yours, that the "domains" are
NA> matching. BinkD uses whats known as "5 dimentional" addressing where the
NA> domain portion MUST match with the remote system otherwise no mail will be
NA> exchanged. The confusing part is that in 5D addressing, it is not
NA> necessarily an actual Internet domain name, but rather moreso a
NA> mutually-agreed-upon domain.

NA> In the BinkD log, if the destination is 1:229/426 and you see something
NA> like "1:229/[email protected] busy or N/A" when a connection is established,
NA> then uh-oh, the domain is not being correctly matched and no mail will be
NA> exchanged in the session.

Connected fine, session ok *.try file has returned to the DATA\FIDONET folder,
and no mail went out.

+ 08:17 [3676] addr: 1:275/100@fidonet
+ 08:17 [3676] addr: 169:1/107@battlnet (n/a or busy)
+ 08:17 [3676] addr: 169:1/1@battlnet (n/a or busy)
+ 08:17 [3676] addr: 77:1/156@scinet (n/a or busy)
+ 08:17 [3676] addr: 1:275/0@fidonet
+ 08:17 [3676] addr: 777:777/11@xnet (n/a or busy)
+ 08:17 [3676] pwd protected session (MD5)
+ 08:17 [3676] done (to 1:275/100@fidonet, OK, S/R: 0/0 (0/0 bytes))
 08:17 [3676] session closed, quitting...

NA> In D'Bridge CONFIG-INTERNET, you see that each line in the BINKD SESSIONS
NA> screen begins with the Fido address, a space, and the domain name. In the
NA> case of Fidonet, this should be set to "fidonet". However, a lot of
NA> systems in Fidonet may not necessarily specify "fidonet" as the presented
NA> domain in a BinkD session. Very carefully watch your log and if the remote
NA> system presents something else, lets say, fidonet.org, then in
NA> Config-Internet, you will ARROW DOWN to ADDITIONAL OPTIONS and specify:

NA> domain fidonet.org alias-for fidonet

NA> Exit Config-Internet, and restart both D'Bridge and BinkD once again.
NA> Force another connection to the remote system, paying attention to the
NA> connection log. Note that I strongly recommend NOT specifying "dot"
NA> notation in 5D domains in CONFIG-INTERNET. Keep Fidonet as "fidonet". When
NA> you start getting into mixing and matching the variations of "fidonet", it
NA> becomes a bit difficult to troubleshoot domain-related problems going
NA> forward.

My Hub as it appears in Dbridge:
BINKD session information:

1:275/100 fidonet shenks.synchro.net

My BINKD Alias, Additional BINKD options:

domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
domain fido alias-for fidonet
domain fido.net alias-for fidonet

NA> If these two suggestions - The mailbox directory and the BinkD domains -
NA> if these two do NOT solve the problem, then let me know.

Still no movement.

I'm by no means gifted when it comes to mailers, and I wish I understood them
more. At the moment, I'm using Dbridge as a standalone mailer, and only using
the internal editor to produce the netmails or polls from the drop down menu.
My bbs does not have netmail capibilities at this time, and that is why I
wanted dbridge, as it has a built in editor for netmail. My mail tosser does
not even enter into the question, as I'm only doing netmail at the moment using
the built in editor, so I'm assuming dbridge is handeling everything. I do have
dbridge set up not to process any incoming packets, so my tosser can put them
into the bbs. At the moment, I'm just trying to get the netmail and poling
issue fixed before I go live with the rest, as the incoming mail is working
fine, and being processed by the tosser. I really wish There was someone in my
area that really understood dbridge, so I could get on the phone with them and
go step by step through the setup, as I'm sure it's something very simple, but
I'm not seeing it..... Thanks again for all of your help.

SysOp: C.G. Learn, AKA: DesotoFireflite
Valhalla Home Services! - (Synchronet) - bbs.valhallabbs.com
Valhalla II! - (GAP) - bbs.valhallabbs.com:24
A Gamers Paradise - Over 150 Registered Online Game Doors!

--- SENILE.COM found...Out of Memory...
* Origin: Telnet://valhalla.synchro.net - Richmond, Virginia (1:275/93)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.