steve@nshore.uucp (Stephen J. Walick) (01/07/91)
Environment: i386 running SCO-Xenix 2.3.3
Mailer(s): 'Elm2.3.10' and 'smail3.1.18.1 #18.32'
Problem(s): Inability to use < ~/config > and < ~/transports >
effectively.
History:
I have had < smail3.1 > executing satisfactorily for nearly a year
until, with the beginning of the new year, I found it necessary to be-
gin using the < ~/transports > file. Sent "test" mail (i.e., tried),
but various errors were generated for reasons that I could not recog-
nize. Recompiled the sources, using three different versions (genera-
tions) of C-compilers (some were buggie) and recompiled successfully;
same errors generated with the < ~/transports > file; recompiled again,
with the errors generated. Have even tried to define "attributes" in
the < ~/config > file (post compiling), with no help.
Error History: [message id's removed - fequency of errors also minimized]
--------------
01/02/91 19:39:26: /usr/lib/smail/transports: unix_from_hack: unknown attribute
01/02/91 19:47:33: /usr/lib/smail/transports: log_output: unknown attribute
01/02/91 19:54:01: /usr/lib/smail/transports: shadow: unknown attribute
01/06/91 00:04:52: /usr/lib/smail/transports: unix_from_hack: unknown attribute
01/06/91 00:08:22: /usr/lib/smail/config: unknown attribute: unix_from_hack
01/06/91 00:30:02: /usr/lib/smail/config: unknown attribute: shadow
01/06/91 00:30:44: /usr/lib/smail/transports: shadow: unknown attribute
01/06/91 00:32:03: /usr/lib/smail/transports: log_output: unknown attribute
Question(s):
1) Not believing that the < ~/config > file should be needed, why
will the "attributes": unix_from_hack, log_output, shadow ...
not be recognized in the < ~/transports > file?
2) Is the file < ~/config > required to have the "stock" attri-
butes recognized?
Sample entry from < ~/transports > file:
----------------------------------------
# @(#)/usr/lib/smail/transports 8.4 1/12/88 25:03:17
# perform local deliver by appending to user mailbox files
local:
# generic transport attributes:
driver=appendfile,
local, # local form for header and envelope
from, # supply a From_ envelope line
-log_output, # don't log the shell-command output (SEE NOTE)
return_path; # supply a Return-Path: field
# driver-specific attributes:
file=/usr/spool/mail/${lc:user}, # BSD/V7 (& SCO-Xen) mailbox directory
check_user, # user cannot contain `/' character
mode=0600, # only allow access by the recipient
shadow=return_receipt, # check for return-receipt
unix_from_hack, # put > in front of From's in text
suffix="\n" # mailboxes require one extra newline
[ NOTE: the line "-log_output" doesn't belong with local, but inserted
for sake of this discussion. ]
Though not necessary previously, use of the < ~/transports > file has
become necessary to re-declare certain < ~/transports > parameters.
Yes, all the attributes are properly declared in the source file
< ~/src/transport.c >, but seem to be ignored.
MANY THANKS to anyone who cares to either post as follow-up and/or
sends an 'Email' reply.
Regards.... Steve Walick
--
Stephen J. Walick, Asst Sysop of the < XBBS > program at NCoast.ORG
{uunet|backbone}!ncoast.org!nshore!steve nshore!steve@ncoast.orgles@chinet.chi.il.us (Leslie Mikesell) (01/14/91)
In article <1991Jan6.180609.2201@nshore.uucp> nshore!steve@ncoast.org (Stephen J. Walick) writes: >01/06/91 00:04:52: /usr/lib/smail/transports: unix_from_hack: unknown attribute >01/06/91 00:30:44: /usr/lib/smail/transports: shadow: unknown attribute >01/06/91 00:32:03: /usr/lib/smail/transports: log_output: unknown attribute >Question(s): > 1) Not believing that the < ~/config > file should be needed, why > will the "attributes": unix_from_hack, log_output, shadow ... > not be recognized in the < ~/transports > file? They have to be in the right place. > 2) Is the file < ~/config > required to have the "stock" attri- > butes recognized? No - and your log entries indicated (correctly) that those transport attributes aren't recognized there at all. >Sample entry from < ~/transports > file: >---------------------------------------- ># @(#)/usr/lib/smail/transports 8.4 1/12/88 25:03:17 > ># perform local deliver by appending to user mailbox files >local: > # generic transport attributes: > driver=appendfile, > local, # local form for header and envelope > from, # supply a From_ envelope line > -log_output, # don't log the shell-command output (SEE NOTE) > return_path; # supply a Return-Path: field > > # driver-specific attributes: > file=/usr/spool/mail/${lc:user}, # BSD/V7 (& SCO-Xen) mailbox directory > check_user, # user cannot contain `/' character > mode=0600, # only allow access by the recipient > shadow=return_receipt, # check for return-receipt > unix_from_hack, # put > in front of From's in text > suffix="\n" # mailboxes require one extra newline The ";" separates the "generic" attributes from the "driver-specific" attributes in a definition. The problem here is that the unix_from_hack and shadow attributes are generic for transports and should be given before the ";". Anything after the ";" should be an attibute specific to the appendfile driver. The manual pages specify the which attibutes are generic as well as the specific ones that apply to each driver. Les Mikesell les@chinet.chi.il.us