jca@pnet01.cts.com (John C. Archambeau) (01/18/91)
I'm having a problem with Smail 3.1. Smail works just fine except when I
specify user@site.domain addresses.
Example:
jca@site Works ok
site!jca Works ok
jca@site.domain Bombs. Mailer-daemon comes back with
unknown host.
Given that site is in my /usr/lib/uucp/paths file.
The operating system being used is ISC 2.0.2. I have Smail 3.1 compiled with
the unix-generic drivers. I have using the same /usr/lib/uucp/paths file that
worked with Smail 2.5 under SCO Xenix 386 2.3.3. A smart-host entry is
defined in the paths file.
If my machine doesn't talk directly to the machine, it should bounce it to my
smart-host and have it handle its path.
I absolutely hate sendmail and I have heard that sendmail under ISC 2.0.2 will
bomb when smtp mail is used.
Any ideas?
Thanks,
// JCA
/*
**--------------------------------------------------------------------------*
** Flames : /dev/null | What to buy?
** ARPANET : crash!pnet01!jca@nosc.mil | EISA or MCA?
** INTERNET: jca@pnet01.cts.com | When will the bus wars end?
** UUCP : {nosc ucsd hplabs!hp-sdd}!crash!pnet01!jca
**--------------------------------------------------------------------------*
*/les@chinet.chi.il.us (Leslie Mikesell) (01/19/91)
In article <7006@crash.cts.com> jca@pnet01.cts.com (John C. Archambeau) writes: >I'm having a problem with Smail 3.1. Smail works just fine except when I >specify user@site.domain addresses. >jca@site Works ok >site!jca Works ok >jca@site.domain Bombs. Mailer-daemon comes back with > unknown host. >Given that site is in my /usr/lib/uucp/paths file. You must have either have site.domain (exact match) with appropriate routing in the paths file or .domain (partial match). An exact match will route to the site, dropping the domain, while a partial match will assume it is sending to a gateway and pass on the fully qualified name. I.e, if your paths file has "site.domain site!%s" then user@site.domain becomes site!user, but if you have ".domain gateway!%s" then it will become gateway!site.domain!user. The exception is when .domain is your own and your machine must resolve the subdomain itself, which is done (in the paths routing) by putting the domain name in a "domain = " entry in the routers entry. This causes the matching domain name(s) to be stripped off before the search. >The operating system being used is ISC 2.0.2. I have Smail 3.1 compiled with >the unix-generic drivers. I have using the same /usr/lib/uucp/paths file that >worked with Smail 2.5 under SCO Xenix 386 2.3.3. A smart-host entry is >defined in the paths file. >If my machine doesn't talk directly to the machine, it should bounce it to my >smart-host and have it handle its path. Smail3 is a very different beast than smail2.5. For smail3 you need to define "smart_path" and "smart_transport" in the config file to get smart-host routing. If you have a central machine that has master aliases or forwarding files for a group of users, you can also define smart_user to send unresolvable local mail there. Les Mikesell les@chinet.chi.il.us
jim@tiamat.fsc.com (Jim O'Connor) (01/23/91)
In article <7006@crash.cts.com>, jca@pnet01.cts.com (John C. Archambeau) writes: > > The operating system being used is ISC 2.0.2. I have Smail 3.1 compiled with > the unix-generic drivers. I have using the same /usr/lib/uucp/paths file that > worked with Smail 2.5 under SCO Xenix 386 2.3.3. A smart-host entry is > defined in the paths file. Under smail3.1, the "smart-host" is configured in the "config" file, not in the paths file. For example, ours is: # # Ahlstrom Filtration, Inc. # smail3 global configuration file # # $Header: /usr/local/sysconfig/global/smail.tiamat,v 1.2 90/06/04 14:32:52 root Exp $ # $Log: smail.tiamat,v $ # Revision 1.2 90/06/04 14:32:52 root # changed to use "uunet" as smart host # date_field = "Date: $ctime" -director_file queue_only received_field = "Received: by $primary_name ($bat Smail$version); $spool_date" spool_mode = 0400 smail = /usr/lib/sendmail smart_path = uunet smart_transport = uux smart_user = $user@tiamat.fsc.com > If my machine doesn't talk directly to the machine, it should bounce it to my > smart-host and have it handle its path. Setting smart_path and smart_transport as indicated above should do the trick. Good luck. ------------- James B. O'Connor jim@tiamat.fsc.com Ahlstrom Filtration, Inc. 615/821-4022 x. 651