packet-radio <=> internet <=> uucp mail gateway questions.

packet-radio <=> internet <=> uucp mail gateway questions.

Post by David A. Russel » Mon, 02 Dec 1996 04:00:00



OK,
  Here is what is going on here:

          ----------                 ----------
         | wormhole |----(UUCP)-----| luminet1 |
          ----------                 ----------
            /   \                        |
           /     \                       |
          /       \                      |
       (AX25)   (UUCP)                (SMTP)
         /         \                     |
        /           \                    |
  *AX25 NET*     *UUCP NET*         *INTERNET*

That should be pretty easy to understand but just in case here is a key:
 ----------
| computer |  (protocal)  *network*
 ----------

luminet1 is a Sparc20 running Solaris (not sure what version exactly).
wormhole is a 386/33 running Linux Slackware 3.1 (kernel version 2.0.0).
Both are using sendmail (versions unknown... fairly new) for mail
handling.

I plan on making all the UUCP hosts have valid DNS entries (this could
be acomplished using MX records in the DNS databases right?).  That way
the UUCP network and the Internet could appear as one.  I plan on doing
this by having as many of the UUCP sites use uucp-dom as their mailer
type and those that don't I'll have a mailer-table entry to use
uucp-old.  And the uucp-old machines can sendmail to


knows what to do with it.  In addition I could allow from the internet

don't have a valid DNS entry yet they could still receive mail.  This
means that if my machine doesn't have an entry for an address in this

let luminet1 send it off as a smtp message accross the internet
otherwise it should send it off across the uucp network.  That should be
a great way to handle that right?  Any suggestions on how to improve
that?  Lastly how would I go about allowing messages send to

to be properlly re-written and sent off?

Now the tricky part is adding the packet-radio network (which is more
important than the uucp network right now).  My understanding of
packet-radio is that it has it's own mail protocals and the format of

similair).  Now I looked at one such gateway and he had it set up to
have a callsign for any user on the internet that wanted to recieve mail
from the packet-radio network.  They had a user like

Is this because packet-radio mail will croke with callsigns that are
longer than a certain limit and don't like anything except standard
chars and nums?  Or is just because of the legal restrictions?  If it's
because of the legal restrictions could I implement something like

valid place to send without breaking laws (done either by looking up
it's location with whois or somethin or using a file containing
'trusted' machines).  From the internet side I'm sure I can do something

packet radio network from the internet.   Again is this a good method to
do this?  Any suggestions?  And again how would I rewrite the headers to

other way if it's possible.  And if I need to use the callsign mapping
to a user on an internet machine that's a standard feature of sendmail
right?  virtuser or mabe I just create a valid e-mail address and use
the procmail .forward file ability?

Lastly is there a mail handler for the packet-radio network available
for linux.  If so what is it and where can I find it?  If not what is
the name of the protocal used and where can I find some information on
it so that I can write up a mail handler myself.

Or am I just being a fool and should I just allow access into the
machine via packet-radio but have the mail really only on the internet?
So you can login to it like a packet-radio bbs but when you send mail
it's to the internet and the internet can send to you but no real mail
routing.

Sorry if any of the newsgroups I posted to are not suited for this
message and sorry for the poor layout and formating of this letter.

Also please respond via e-mail in addition to the newsgroup as I don't
have time to search through the newgroups.

Thanks,

David Russell

http://www.luminet.net/~drussell
--
"Boo!"

 
 
 

packet-radio <=> internet <=> uucp mail gateway questions.

Post by Craig Smal » Sat, 07 Dec 1996 04:00:00



:           ----------                 ----------
:          | wormhole |----(UUCP)-----| luminet1 |
:           ----------                 ----------
:             /   \                        |
:            /     \                       |
:           /       \                      |
:        (AX25)   (UUCP)                (SMTP)
:          /         \                     |
:         /           \                    |
:   *AX25 NET*     *UUCP NET*         *INTERNET*

G'day David,
  I have a very similar setup running here.  You will find that it is possible
to do what you want, but rather tricky.

The first step is to get you UUCP to luminet going first.  Once you are happy
with this, you can proceed.  The reason why people can mail to a UUCP node
from the internet is that your wormhole's address is MX'ed to luminet, this
is important to remember.

: Both are using sendmail (versions unknown... fairly new) for mail
: handling.
I use smail, which is a bit less flexible but easier to work with, within
reason.  I have tried this with sendmail.

: I plan on making all the UUCP hosts have valid DNS entries (this could
: be acomplished using MX records in the DNS databases right?).  That way
See above.  You don't get a choice, unless the UUCP stuff is sent out as

: packet-radio is that it has it's own mail protocals and the format of

: similair).  Now I looked at one such gateway and he had it set up to
You have to be careful with terminology here.  Amateur Radio does already
run TCP/IP with its own class A network and domain names.   So that means
I use the exact same sendmail program to mail to an amateur or to the
Internet.  But, unfortunately, amateur radio also uses a rather clumsy
and cludgy protcol as well.  For a name let's call it MBL/RLI.

Now you can gateway between the two, but it is using manual tables to do it.
A programs called TNOS and LBBS will do it.  I prefer LBBS as it is smaller,
it is basically another deleivery agent.  I am assuming you mean MBL/RLI
forwarding from now on.


This would be using a manually-created table. that did this mapping.

: 'trusted' machines).  From the internet side I'm sure I can do something

: packet radio network from the internet.   Again is this a good method to
Be very careful with amateur radio host names.  They have a lot of problems
and are incompatible with Internet ones.  LBBS gets around this by appending
the pseudo domain nts, which acts like the UUCP pseudo domain.

: Or am I just being a fool and should I just allow access into the
: machine via packet-radio but have the mail really only on the internet?
: So you can login to it like a packet-radio bbs but when you send mail
: it's to the internet and the internet can send to you but no real mail
: routing.
The easiest way for you is to get all your amateur radio users to use
a TCP/IP program, even windows, and then setup a pop server for them.

he next fires up his popclient.

If your users say "TCP/IP is way to scary, we want to use a dumb terminal
and a TNC, because that is the only way" (or something similiar) so that
they want to do a plain vanilla AX.25 connection, then have a look at
axshell.

Now if you want to forward to a MBL/RLI BBS, you're asking for a lot of trouble.
I know this as I have been doing a similar project to your own.  Manual table
translation is the only way.  You could do it via sendmails translation
facility, but like everything else in sendmail, it is hard to do.

Finally, if you want to play amateur radio and Linux, may I suggest you
subscribe to the linux-hams email list?  This sort of thing is what it is
for.

  - Craig vk2xlz

--




 
 
 

1. <><><> MOUNTING EXTENDED PARTITION <><><>

I have a 10 GB UDMA IDE drive formatted with Windows.  The first partition
is FAT32, and the second is NTFS.  I can successfully mount the first, but
not the second.  Any ideas?

Suse 7.2 on i86
the drive is mounted on /dev/hdc, and I CAN see hda1, but not hda2

2. LCD screen and linux

3. Wanted: <><><> Unix Specialist <><><>

4. KDE trouble

5. LILO help <><><><><><>

6. X server

7. Samba problem: WinXP <-> ADSL <-> Internet <-> Cable <-> Linux

8. CUSEEME for Linux

9. <<<Gateway Question>>>

10. <Alt>+<key> = <Esc><key> ?

11. *{<><>}*Linux*Screen*Difficulties*{<><>}*

12. << <<anyone using dyn-html?>> >>

13. (<><>)*Linux*Screen*Difficulties*(<><>)