Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!utkcs2!betelgeuse!moore From: moore@betelgeuse.cs.utk.edu (Keith Moore) Newsgroups: comp.mail.sendmail Subject: Re: Ultr3.1,undocum. mailer flag in sendmail.cf Message-ID: <1128@utkcs2.cs.utk.edu> Date: 28 Sep 89 17:49:53 GMT References: <1596@esat.kuleuven.ac.be> Sender: news@utkcs2.cs.utk.edu Reply-To: moore@cs.utk.edu (Keith Moore) Organization: CS Dept -- University of TN, Knoxville Lines: 27 In article <1596@esat.kuleuven.ac.be> ELSEN@esat.kuleuven.ac.be (Marc Elsen) writes: > The Ultrix 3.1 default sendmail configuration file contains the >following entry for the DECnet mailer : > >MDmail, P=/usr/bin/mail11v3, F=mnSXxH, S=17, R=18, A=mail11 $f $x $h > > Does anyone know the meaning of the H flag in F=mnSXxH ? > It doesn't seem documented on page 2-54 Appendix C , Mailer Flags > (Sendmail Installation and Operation Guide) in Ultrix-32,supplementary > documents , Volume 3 System Manager. I believe it indicates to Ultrix sendmail that it should speak a special extended SMTP to the mail11v3 program. The extended SMTP includes a mechanism to allow mail11v3 to look at the headers of the RFC822 message before verifying that any recipients are valid. This makes for a easier interface to the MAIL-11 protocol, where it's helpful to know what the message headers look like *before* you open the DECnet connection, and therefore before you ask the remote MAIL-11 object whether any recipient(s) are valid. Mail11v3 won't work unless you speak extended SMTP to it. This means you can't use mail11v3 with e.g., Berkeley sendmail. Incidentally, the extended SMTP protocol (as far as I can tell) is also undocumented. -- Keith Moore Internet: moore@cs.utk.edu University of Tenn. CS Dept. BITNET: moore@utkvx 107 Ayres Hall, UT Campus UT Decnet: utkcs::moore Knoxville Tennessee 37996-1301 Telephone: +1 615 974 0822