JV> No argument from me on that, but it just doesn't make sense to use
JV> another network's addressing scheme when the right one is at hand.
But you fail to understand that what is on MSGID (and on Message-ID too btw)
is not (I repeat: is not) a network address, but an arbitrary string (well,
inside of a give nset of possible chars, and some rules of combining them;
not any arbitrary combinaison is legal); an arbitrary string that, in
combinaison with another arbitrary string (or an hexa number in FTN) makes
a unique identifier for the message, unique in the whole network.
A simple way to achieve that is to build the string from the machin name
in the network, as it is a unique string (in that networ); then the other
part of the identifier being unique on a given machine the combinaison
of the two will give a unique identifier.
But there isn't any reason that the the exact node name on the network be
used (ad often it isn't); and in cases where you are in various networks;
which one would you use ?
Note also that ifgate is a messages format converter; nothing more; so it
converts the messages from rfc to FTN format; if you want a traditional FTN
MSGID you should build the originial Message-ID so it produces what you want.
Dropping the original Message-ID may be convenient in some cases (and that is
the reason why I added the feature in the 'tx') but it should never become
the default or be widely used; as it will lead to possible dupes and endless
loops. It should be used only in exceptional cases, and be activated by hand,
by people that know what they are doing.
JV> All it's doing for me is causing problems. Would make just as much
JV> sense, maybe more, to use my zipcode in there.
-- └ bient˘t, Pablo Saratxaga PGP Key available, key ID: 0x8F0E4975