Invalid address?

[Gert Koefoed Andersen]

Hello Nick!

Thu Feb 04 2010, Nick Andre wrote to All:

NA>Hi, lately, some of my downlinks connect here and my end refuses to
NA>send any mail, due to some sort of "invalid address" problem I can't
NA>figure out.

NA>I'm running BinkD verison 0.9.10.

NA>My addreses are 1:1/130, 1:12/2, 1:229/426 along with a few
NA>"othernets".

NA>+ 10:41 [50800] session with 75.100.226.232 (75.100.226.232)
NA>- 10:41 [50800] OPT LST UTF
NA>- 10:41 [50800] SYS Time Warp of the Future BBS, TCP/IP 1
NA>- 10:41 [50800] ZYZ Robert E Starr JR
NA>- 10:41 [50800] LOC Cougar, WA USA
NA>- 10:41 [50800] PHN time.synchro.net
NA>- 10:41 [50800] NDL CM,IBN,ITN,IFC,IFT,IHT,ISE,IMI,INT,TCP,TEL,VMP,BND
NA>- 10:41 [50800] TIME Thu, 04 Feb 2010 15:40:56 -0800
NA>+ 10:41 [50800] addr: 1:14/***@fidonet
NA>+ 10:41 [50800] addr: 10:10/***@league10.org (n/a or busy)
NA>+ 10:41 [50800] addr: 10:10/***@league10.org (n/a or busy)
NA>+ 10:41 [50800] addr: 45:45/***@beerme (n/a or busy)
NA>+ 10:41 [50800] addr: 56:360/***@ponynet (n/a or busy)
NA>+ 10:41 [50800] addr: 782:470/***@xpresit
NA>+ 10:41 [50800] addr: 11:11/***@dovenet (n/a or busy)
NA>+ 10:41 [50800] addr: 201:2000/***@dbnet
NA>+ 10:41 [50800] addr: 618:300/***@micronet (n/a or busy)
NA>? 10:41 [50800] rerror: Invalid addrs: 1:1/***@fidonet
NA>1:229/***@fidonet 1:12/2
NA>@fidonet 1:229/***@fidonet 77:1/***@scinet 782:782/***@xpresit
NA>782:900/***@xpresit 782
NA>:900/***@xpresit 782:900/***@xpresit
NA>+ 10:41 [50800] done (from 1:14/***@fidonet, failed, S/R: 0/0 (0/0
NA>bytes))
NA> 10:41 [50800] session closed, quitting...

NA>The above may be word-wrapped but you get the idea.

Have you checked your binkd.cfg for domain setup and the nodes setup, and then
contact the link for what he have in his mailers setup.
The errors is then normally comes by a miss typed setup where a block of lines
not match the right way, then try to have all the nodes akas there match your
own in nets be presents in binkd.cfg node setup.
Some maillers have to be rigth setup to match with binkd, then will binkd show
(n/a or busy) for the nets the other end is present up to and if just one aka
not is workig will the rest neither do it.


Take care,
Gert

- Get the best with linux -

[Nick Andre]

Post by Gert Koefoed Andersen
NA>The above may be word-wrapped but you get the idea.
Have you checked your binkd.cfg for domain setup and the nodes setup, and
then contact the link for what he have in his mailers setup.
The errors is then normally comes by a miss typed setup where a block of
lines not match the right way, then try to have all the nodes akas there
match your own in nets be presents in binkd.cfg node setup.
Some maillers have to be rigth setup to match with binkd, then will binkd
show (n/a or busy) for the nets the other end is present up to and if just
one aka not is workig will the rest neither do it.

The problem has appeared to happen on its own. No changes were done to the
Нsystem configuration here and I've chatted with the node above in question
Нwhere everything appears to be fine as well. Its really strange. The node
Нabove runs Taurus. I also have another downlink which causes the same
Нproblems here and he runs Argus.

Every other downlink that connects here is fine... several dozen of them.

Nick

[Gert Koefoed Andersen]

* Reply to message originally in area CarbonArea

Hello Nick!

Fri Feb 05 2010, Nick Andre wrote to Gert Koefoed Andersen:

NA> * Forwarded from area 'BINKD'

Post by Gert Koefoed Andersen
NA>The above may be word-wrapped but you get the idea.
Have you checked your binkd.cfg for domain setup and the nodes setup, and
then contact the link for what he have in his mailers setup.
The errors is then normally comes by a miss typed setup where a block of
lines not match the right way, then try to have all the nodes akas there
match your own in nets be presents in binkd.cfg node setup.
Some maillers have to be rigth setup to match with binkd, then will binkd
show (n/a or busy) for the nets the other end is present up to and if
just one aka not is workig will the rest neither do it.

NA>The problem has appeared to happen on its own. No changes were done to
NA>the system configuration here and I've chatted with the node above in
NA>question where everything appears to be fine as well. Its really
NA>strange. The node above runs Taurus. I also have another downlink which
NA>causes the same problems here and he runs Argus.

NA>Every other downlink that connects here is fine... several dozen of
NA>them.

When you said Taurus and Argus then is there lot there say me something, I have
several linkds there using either Argus or Taurs and they have had the same
problem with connect to my binkd, this is why binkd want all information right
and the 2 Argus and Taurus can some times give troubles with connect for more
than one nets to you if Arug and Taurus not is setup the right way and using
the right domain configuring, and then can a Windows system with Argus, Taurus
and irex and mostly Argus and taurus make troubles by currupt some files for
the mailer.
So it is not on your system the trouble is, it is on your links end the problem
is.
Maybe in the reason that you link has fidonet system and work on same computer
or harddisk.
Let your links there have the connect problem know to go their setup through.
Do a communication by email or phone or msn or icq.


Take care,
Gert

- Get the best with linux -

[Nick Andre]

Post by Gert Koefoed Andersen
When you said Taurus and Argus then is there lot there say me something, I
have several linkds there using either Argus or Taurs and they have had the
same problem with connect to my binkd, this is why binkd want all
information right and the 2 Argus and Taurus can some times give troubles

Its odd that its just the two downlinks having trouble that are running НTaurus
and Argus. And whats REALLY weird is a few times they connect, there Нis no
trouble at all.

I was thinking its a problem with CRAM-MD5 encryption and the latency over Нthe
network.

Post by Gert Koefoed Andersen
Maybe in the reason that you link has fidonet system and work on same
computer or harddisk.
Let your links there have the connect problem know to go their setup
through. Do a communication by email or phone or msn or icq.

Again its a really weird problem. I have no idea where to begin
troubleshooting it other than what I already tried.

Nick

[Gert Koefoed Andersen]

* Reply to message originally in area CarbonArea

Hello Nick!

Fri Feb 05 2010, Nick Andre wrote to Gert Koefoed Andersen:

NA> * Forwarded from area 'BINKD'

Post by Gert Koefoed Andersen
When you said Taurus and Argus then is there lot there say me something,
I have several linkds there using either Argus or Taurs and they have had
the same problem with connect to my binkd, this is why binkd want all
information right and the 2 Argus and Taurus can some times give troubles

NA>Its odd that its just the two downlinks having trouble that are running
NA>Taurus and Argus. And whats REALLY weird is a few times they connect,
NA>there is no trouble at all.

NA>I was thinking its a problem with CRAM-MD5 encryption and the latency
NA>over the network.

It can be that way that is that there do it.

Post by Gert Koefoed Andersen
Maybe in the reason that you link has fidonet system and work on same
computer or harddisk.
Let your links there have the connect problem know to go their setup
through. Do a communication by email or phone or msn or icq.

NA>Again its a really weird problem. I have no idea where to begin
NA>troubleshooting it other than what I already tried.

I have several downlinks there using Arus ad Taurus and the have done it so
that for each nets they got from me have they several taurus set up for each
nets. If taurus and argus not is setup correct will node aka and domains give
trouble.
Some of my links has first tried run argus and Taurus and then changed to use
irex instead, why irex do not matter of the domains if just the akas is
present.

Take care,
Gert

- Get the best with linux -