Annotation of researchv10no/lbin/mailx/man/ckbinarsys.1m, revision 1.1.1.1

1.1       root        1: '\"macro stdmacro
                      2: .if n .pH g1.chbinarsys %W%
                      3: .nr X
                      4: .if \nX=0 .ds x} ckbinarsys 1M "Essential Utilities" "\&"
                      5: .if \nX=1 .ds x} ckbinarsys 1M "Essential Utilities"
                      6: .if \nX=2 .ds x} ckbinarsys 1M "" "\&"
                      7: .if \nX=3 .ds x} ckbinarsys "" "" "\&"
                      8: .TH \*(x}
                      9: .SH NAME
                     10: \f4ckbinarsys\f1 \- determine whether remote system can accept binary messages
                     11: .SH SYNOPSIS
                     12: \f4ckbinarsys\fP
                     13: [\f4\-S\fP]
                     14: \f4\-s\fP \f2remote_system_name\fP
                     15: \f4\-t\fP \f2content_type\fP
                     16: .SH DESCRIPTION
                     17: Because \f4rmail\f1 can transport binary data, it may be important to
                     18: determine whether a particular remote system (typically the next hop)
                     19: can handle binary data via the chosen transport layer agent (uux, SMTP, etc.)
                     20: .PP
                     21: \f4ckbinarsys\fP consults the file \f4/etc/mail/binarsys\f1 for information on
                     22: a specific remote system.
                     23: \f4ckbinarsys\f1 returns its results via an appropriate exit code.
                     24: An exit code of zero implies that it is OK to send a message with the
                     25: indicated content type to the system specified.
                     26: An exit code other than zero indicates that the
                     27: remote system cannot properly handle messages with binary content.
                     28: .PP
                     29: The absence of the \f4binarsys\f1 file will cause
                     30: \f4ckbinarsys\f1 to exit with a non-zero exit code.
                     31: .PP
                     32: Command-line arguments are:
                     33: .sp .5
                     34: .PD 0
                     35: .TP 17
                     36: \f4\-s\f2\0remote_system_name\f1
                     37: Name of remote system to look up in \f4/etc/mail/binarsys\f1
                     38: .TP
                     39: \f4\-t\f2\0content_type\f1
                     40: Content type of message to be sent.
                     41: When invoked by \f4rmail\f1,
                     42: this will be one of two strings:
                     43: \f4text\f1 or \f4binary\f1,
                     44: as determined by \f4mail\f1
                     45: independent of any \f4Content-Type:\f1 header lines that may be
                     46: present within the message header.
                     47: All other arguments are treated as equivalent to \f4binary\f1.
                     48: .TP
                     49: \f4\-S\f1
                     50: Normally, \f4ckbinarsys\fP will print a message (if the binary mail is rejected)
                     51: which would be suitable for \f4rmail\fP to return in the negative acknowledgement mail.
                     52: When \f4\-S\fP is specified, no message will be printed.
                     53: .PD
                     54: .SH FILES
                     55: .PD 0
                     56: .TP 27
                     57: \f4/etc/mail/binarsys\f1
                     58: .TP 27
                     59: \f4/usr/lib/mail/surrcmd/ckbinarsys\f1
                     60: .PD
                     61: .SH SEE ALSO
                     62: \f4mailsurr\f1(4),
                     63: \f4binarsys\f1(4)
                     64: .br
                     65: \f4mail\f1(1),
                     66: \f4uux\f1(1) in the \f2User's Reference Manual\f1.
                     67: .Ee

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.