Date: Wed, 12 Apr 1995 13:44:22 +0800 From: "Paul F. Safonov" <spf@news.sable.krasnoyarsk.su> To: Bill Fenner <fenner@parc.xerox.com> Cc: freebsd-questions@freefall.cdrom.com Subject: Re: SENDMAIL problem Message-ID: <EAsYsYlykw@news.sable.krasnoyarsk.su> In-Reply-To: <95Apr11.103013pdt.49864@crevenia.parc.xerox.com>; from Bill Fenner at Tue, 11 Apr 1995 10:29:58 PDT References: <95Apr11.103013pdt.49864@crevenia.parc.xerox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <95Apr11.103013pdt.49864@crevenia.parc.xerox.com> Bill
Fenner writes:
>In message <zGI5WYlixd@news.sable.krasnoyarsk.su> 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:<>
Well.
Null reverse-path is set in my computer, when messages (including
Return-Receipt-To) are sent from MAILER-DAEMON.
Why is then null reverse-path set and what is the way to prevent this?
> Bill
--
Safonov Paul E-mail: spf@sable.krasnoyarsk.su Phone: +7 (3912) 276-793
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EAsYsYlykw>