🚀 go-pugleaf

In article <149@4gl.UUCP> honzo@4gl.UUCP (Honzo Svasek) writes:
>	I am working on a gateway Usenet <-> Fidonet, and like to know
>	what type of addressing this gateway should accept according
>	to the Usenet communitie.
>
>			Honzo.Svasek@333.500.FIDO
>	

In order to conform to the standards, this should be:

	Honzo.Svasek@333.500.FIDO.NET

>	This is totally in line with current Usenet practice, but might
>	need a registration of the domains. (And I hate filling in
>	registration forms (Any Volunteers :)).

I'll fill out the forms; you pay the $150/year (1/4 a :-))

>
>	The other way (quick and dirty) would be
>
>			mcvax!4gl!FIDO!500_333!Honzo.Svasek
>
>	but this would prevent getting the mail to the nearest fido
>	gateway (there must be more people interested in providing
>	such a service).
>
>	Comments please!

The syntax you should use is:

	...!4gl!333.500.FIDO.NET!Honzo.Svasek

since this would be compatible with how mail would be addressed (in
the envelope) under the domain scheme. 4gl should recognize that it is
processing a FIDO-bound message by the FIDO.NET at the end of the
hostname. 

What you need to do:

Get the person who maintains the map entry for the UUCP machine 4gl,
and get them to add a line like this to their map entry:

4gl	.FIDO.NET($COST$)

Where you would replace "$COST$" with one of the standard UUCP map
link cost values (e.g. HOURLY, DAILY, etc.) indicating how expensive
it is to get the message from 4gl into FIDONET.

Then they should send their uucp map entry to uucpmap@cbosgd.ATT.COM.

If there are any other FIDONET gateways on uucp, they should also send
such an line to their map entries (and send in their updated entry)

Once this is done, mail would then be routed from UUCP hosts to the
nearest (to the sender) FIDOnet gateway. 

I don't know the specifics of FIDONET topology, but if the subnets are
organized according to low-cost communications (i.e. local calls), it
makes sense to also put in a line like:

4gl	.500.FIDO.NET($COST$)

(again, replace $COST$ with a valid UUCP cost).  With lines like this
for each UUCP->FIDO gateway (indicating which FIDO subnet it talks
to--if it talks to more than one, you'd have more than one such line),
the mail will be routed via UUCP to a UUCP->FIDO gateway on the same
subnet as the destination address, if one exists, otherwise to a
general UUCP->FIDO gateway (one with a .FIDO.NET($COST$) line) closest
to the sender. 

The next step is to apply to register your domain.  Having the domain
registered will extend FIDO mail accessiblilty to the Internet
(including the ARPAnet, the MILNET, CSnet, etc.).  It will also
guarantee you exclusive use of the FIDO.NET name, preventing someone
else from 1) using it and screwing you up or 2) registering it and
forcing you to give it up. 

Hope this answers your questions.

Jeff Siegal