 |
 |
Articles / TULARC / PC info / Amiga / AmigaUUCP / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
4.2) Constructing Mail Addresses. Bang Paths |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the AmigaUUCP
FAQ, by Marc SCHAEFER,
Nearly all the systems on the internet accept what are known as bang paths. There are only a few exceptions. One of the design decisions for AmigaUUCP was to convert all addresses into bang paths before sending them out. There have been one or two sites (so far) that have been unable to run AmigaUUCP because the feed they picked was running news software so old it did not recognize bang paths. To those sites I say: find a different feed, AmigaUUCP would become extremely messy were I to implement UNIX sendmail style address parsing.
A bang path work by specifying the exact path your mail is to go along, in the following format:
first_machine!machine!machine!users_machine!user
Any machine name in the path may be a fully domained name. If you have a smart feed it will be able to optimize the path accordingly. For example, the bang path to me would normally be:
uunet.uu.net!overload!dillon
If your feed has a STUPID mailer, it may be necessary to use a bang path to get *past* your feed to a nearby site that has a SMART mailer. For example, lets say your feed is named 'fubar' and has a dumb mailer. Let us also say that the feed has a UUCP connection to 'harvard' which just happens to have a smart mailer. To get your message to me you might use:
fubar!harvard!uunet.uu.net!overload!dillon
your feed may or may not accept harvard's fully domained name, which is harvard.harvard.edu, it depends on how stupid your feed's mail system is. If it does, it makes more sense to use:
fubar!harvard.harvard.edu!uunet.uu.net!overload!dillon
Continue to:
|
|
|
|
 |
|