From owner-freebsd-questions Tue Apr 11 10:31:20 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24068 for questions-outgoing; Tue, 11 Apr 1995 10:31:20 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA24062 for ; Tue, 11 Apr 1995 10:31:17 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14469(5)>; Tue, 11 Apr 1995 10:30:18 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49864>; Tue, 11 Apr 1995 10:30:13 -0700 X-Mailer: exmh version 1.6gamma 3/30/95 To: "Paul F. Safonov" cc: freebsd-questions@freefall.cdrom.com Subject: Re: SENDMAIL problem In-reply-to: Your message of "Mon, 10 Apr 95 21:10:58 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Apr 1995 10:29:58 PDT From: Bill Fenner Message-Id: <95Apr11.103013pdt.49864@crevenia.parc.xerox.com> Sender: questions-owner@FreeBSD.org Precedence: bulk In message you write: >There is a problem while processing "Return-Receipt-To". >The receipt is sent from a zero user (see below). >Should it be so? Yes. MAIL FROM: <> makes it so that the receiving mailer doesn't bother trying to bounce the message. It is part of RFC821. ... Of course, server-SMTPs should not send notification messages about problems with notification messages. One way to prevent loops in error reporting is to specify a null reverse-path in the MAIL command of a notification message. When such a message is relayed it is permissible to leave the reverse-path null. A MAIL command with a null reverse-path appears as follows: MAIL FROM:<> Bill