04 Jun 15 23:22, you wrote to me:
MK> -={ jeudi, juin 04 2015, 16:22:02 -0700 }=-
MK> Hey mark!
ml>> to handle 5D FTN addresses like 1:11/111.0@fidonet
MK> It occurs to me that it doesn't matter since the origDomain is never used
MK> as a variable.
which type2 packet format do you use? there is a position for the FTN domain in
the header of one of the three...
MK> I could probably say the same for origPoint but occasionally it does
MK> matter when either/and the destination and/or originating address is a
MK> point (netmail comes to mind).
yes... exactly... the point address is needed in the TOPT and/or FMPT control
lines and may also be used in the packet header in certain packet formats...
MK> As of this writing I have never run across a situation that required
MK> the domain part of the address and very seldom the point part in 4D
MK> addressing.
likely because you aren't involved in any other networks than fidonet ;)
MK> However in the spirit of completeness, and possibly future
MK> compatibilty which I am EXTREMELY doubtful about, 5D addressing can
MK> readily be detected if and when needed with something along this line;
MK> if [ "echo $origAddr | $(cut -f2 -d@)" ]; then
MK> do something about 5D addressing
MK> else
MK> business as usual (4D addressing as previously posted)
MK> fi
:)
MK> I honestly don't see myself doing anything with the above but one
MK> never knows for sure.
very true...
)\/(ark
... Dogs can lick their own genitalia, they must be the superior species.
---
* Origin: (1:3634/12.73)
|