bill@twwells.uucp (T. William Wells) (04/21/89)
I've now got a domain name from uunet so it is time to update my map entry
and my signature. I'd like some advice on doing this.
Firstly, besides being twwells, a uucp site, I'm now twwells.com with an MX
off uunet. What is the correct way to put this into my map entry?
Secondly, is it sufficient to just tell Internet sites to mail to twwells.com,
or is it necessary for them to do some fudging to make sure that the mail goes
to uunet first?
Thirdly, are there any unexpected things that I might have to cope with
because of this additional name for my system? Any additional things I might
take advantage of to make mail routing easier?
---
Bill { uunet | novavax } !twwells!bill
(BTW, I'm may be looking for a new job sometime in the next few
months. If you know of a good one where I can be based in South
Florida do send me e-mail.)avolio@decuac.dec.com (Frederick M. Avolio) (04/22/89)
I'd like to tell you what you can do with... no, no! Just kidding. In article <841@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes: >... >Firstly, besides being twwells, a uucp site, I'm now twwells.com with an MX >off uunet. What is the correct way to put this into my map entry? > #N twwells.com, twwells then later... twwells twwells.com twwells = twwells.com >Secondly, is it sufficient to just tell Internet sites to mail to twwells.com, >or is it necessary for them to do some fudging to make sure that the mail goes >to uunet first? The former is sufficient. UUNET is saying that they will be your mail exchanger site. Internet hosts will be able to send to user@twwells.com and the mail will get there going through UUNET.UU.NET without any other work or magic. >Thirdly, are there any unexpected things that I might have to cope with >because of this additional name for my system? Any additional things I might >take advantage of to make mail routing easier? Make sure *your* mailer knows that you are twwells.com! May have to twiddle the sendmail.cf. Fred
fair@ucbarpa.Berkeley.EDU (Erik E. Fair) (04/22/89)
Fred, You goofed! The correct format for the map files now that the original UUCP Zone is dead, and UUNET is handling things is: #N uucpname #F forwarder1.frobozz.org [, forwarder2.cheapo.net ] And in the pathalias data: uucpname .do.main uucpname = fully.qualified.domain.name Note the leading dot on the first domain declaration! That's a domain gateway declaration to pathalias. The second declaration is a name equivalence (what are all the names your host has? Make sure, as Fred said, that you can recognize your own name). Erik E. Fair ucbvax!fair fair@ucbarpa.berkeley.edu
jimmy@pic.ucla.edu (Jim Gottlieb) (04/23/89)
In article <2666@decuac.DEC.COM> avolio@decuac.dec.com (Frederick M. Avolio) writes: >twwells = twwells.com > >>Secondly, is it sufficient to just tell Internet sites to mail to twwells.com, >>or is it necessary for them to do some fudging to make sure that the mail goes >>to uunet first? > >The former is sufficient. UUNET is saying that they will be your mail >exchanger site. Internet hosts will be able to send to >user@twwells.com and the mail will get there going through >UUNET.UU.NET without any other work or magic. In a perfect world, yes, but please keep in mind that many internet sites still do not use the name domain server, and even some of those that do (like ours) do not have sendmail versions that understand MX records. So, unfortunately, you may still want to give an alternate address of username%twwells.com@uunet.uu.net . Someday this won't be necessary. Glenn Sueyoshi gtsueyoshi@ucsd.edu ucbvax!ucsd!keynes!glenn gtsueyoshi@ucsd
chip@vector.Dallas.TX.US (Chip Rosenthal) (04/28/89)
In article <28868@ucbvax.BERKELEY.EDU> fair@ucbarpa.Berkeley.EDU (Erik E. Fair) writes: > You goofed! The correct format for the map files [...] is: >#N uucpname >#F forwarder1.frobozz.org [, forwarder2.cheapo.net ] Then shouldn't the map README file be updated? It doesn't say anything about a "#F" field. -- Chip Rosenthal / chip@vector.Dallas.TX.US / Dallas Semiconductor / 214-450-5337
bill@twwells.uucp (T. William Wells) (04/30/89)
Here's a summary of the answers I got:
I'm supposed to add right after my #N line a #F line:
#F uunet.uu.net
This is my Internet forwarder, the site that has my MX record. If I
have more than one, I put them comma-separated on one #F line.
I also add the lines:
twwells .twwells.com(LOCAL)
twwells = twwells.com
to my map entry with the other pathalias input. I don't need the
first line if I don't have any other machines in my domain. Or if my
main machine will handle mail addressing so that all my users appear
as if they were on the main machine.
And besides being twwells!bill and bill@twwells.com, I might also
want Internet sites to try bill%twwells.com@uunet.uu.net.
The following people contributed info used in this article:
avolio@decuac.dec.com Frederick M. Avolio
chip@vector.Dallas.TX.US Chip Rosenthal
fair@ucbarpa.Berkeley.EDU Erik E. Fair
jimmy@pic.ucla.edu Jim Gottlieb
ulmo@ssyx.UCSC.EDU brad allen
Thanks.
---
Now, I have two further questions before I go do this:
Here are my assumptions on what will happen:
Twwells will work as always, from uucp sites.
Uucp people with a smart router can mail to twwells.com and
the router will turn that into a path to twwells.
Uucp people can mail using a path like
....!smart-mailer!twwells.com!bill and the same thing will
happen.
Internet people can mail to twwells.com and, if the mail stays
in the Internet, will end up at uunet which will then route it
to me at twwells. (Assuming that the Internet site is
up-to-date. If not, it's not my problem, man!)
People on other networks will either end up gatewaying to uucp
or to the Internet and so will end up doing one of the above.
Once the .com name appears in the maps, I can both update the
software and tell people that mail to twwells.com will work.
Until then, mail to twwells.com will be erratic except for
mail originating from Internet sites.
Is there anything in the above that isn't true?
And my final question:
I'm thinking that I'll need to make these changes to my software:
For smail, all I need to do is to set MYDOM to .com.
For inews, I only need to change MYDOMAIN to .com.
For rn, I need to add a modified NEWSHEADER and CANCELHEADER
to config.h, and fix the Reply-To: line in Pnews.
I'm running smail 2.5 patch level 3, B news 2.11 patch level 14, and
rn 4.3.1.4 patch level 40, on a Microport SysV/386 3.0e. Does there
appear to be anything I've overlooked?
---
Bill { uunet | novavax } !twwells!billdg@lakart.UUCP (David Goodenough) (05/01/89)
From article <102@vector.Dallas.TX.US>, by chip@vector.Dallas.TX.US (Chip Rosenthal): > In article <28868@ucbvax.BERKELEY.EDU> fair@ucbarpa.Berkeley.EDU (Erik E. Fair) writes: >> You goofed! The correct format for the map files [...] is: >>#N uucpname >>#F forwarder1.frobozz.org [, forwarder2.cheapo.net ] > > Then shouldn't the map README file be updated? It doesn't say anything about > a "#F" field. Sounds like a very good idea to me. Let's see, looking in the u.usa.ma.? map files we find: ------------------ #N .adelie.com, adelie #F harvard.edu ..... ------------------ #N .alliant.com, alliant #F eddie.mit.edu ..... ------------------ #N aoa #S VAX 8650; Ultrix 2.0 #F bbn.bbn.com ..... ------------------ #N .applicon.com, applicon #F eddie.mit.edu ..... ------------------ #N atexnet #F kodak.com ..... ------------------ And this is just the 'a's. For something that doesn't exist there sure as hell are a lot of them out there :-) -- dg@lakart.UUCP - David Goodenough +---+ IHS | +-+-+ ....... !harvard!xait!lakart!dg +-+-+ | AKA: dg%lakart.uucp@xait.xerox.com +---+