Path: utzoo!attcan!uunet!husc6!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!steve
From: steve@eleazar.dartmouth.edu (Steve Campbell)
Newsgroups: comp.mail.sendmail
Subject: Re: bsd4.3 sendmail and smtp mailers
Message-ID: <9573@dartvax.Dartmouth.EDU>
Date: 28 Jul 88 02:21:07 GMT
References: <3d596f69.44e6@apollo.uucp>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: steve@eleazar.dartmouth.edu (Steve Campbell)
Organization: Dartmouth College, Hanover, NH
Lines: 29

In article <3d596f69.44e6@apollo.uucp> jlb@apollo.uucp (Joel Breazeale) writes:
>   I'd like to get a description of what the mailer uses to support SMTP.

I'm not sure I know what you mean.  Our non-[IPC] SMTP mailers are 
straightforward C implementations of the SMTP protocol described in
RFC 821.  The mailers talk the protocol on stdin/stdout.

>   Occasionally, the mailer fails due to various problems and exits with
>   a status of EX_TEMPFAIL	which is 75, which means that sendmail is
>   supposed to try again later.
>   Unfortunately, sendmail returns a copy of the message when the mailer
>   exits with a "75" even though it does requeue the message.  
>   Does anyone know how to stop the returned messages (or is this the
>   way bsd4.3 sendmail is supposed to work)?

You only use the exit codes like EX_TEMPFAIL from non-SMTP mailers.
Your SMTP mailer should always exit with zero status.  It should
indicate errors to sendmail by way of the appropriate SMTP error
response message, not by exit status.

>   What mailer flags do you use with your SMTP mailer (again, not [IPC])?

Here's an example of a mailer definition from our sendmail.cf:

Mdcts,	P=/usr/local/lib/kn_smtp,  F=mMDFn,  S=14,  R=24,
	E=\r\n, M=100000, A=kn_smtp -h $h

Hope this helps.
							Steve