Changeset 5267:1416714ec4d1 for doc/manual.xml.head
- Timestamp:
- 2007-11-04 08:01:12 (14 months ago)
- Branch:
- HEAD
- Files:
-
- 1 modified
-
doc/manual.xml.head (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
doc/manual.xml.head
r5254 r5267 4616 4616 RFC1894 defines a set of MIME content types for relaying information 4617 4617 about the status of electronic mail messages. These can be thought of as 4618 ``return receipts.'' Berkeley sendmail 8.8.x currently has some command 4619 line options in which the mail client can make requests as to what type 4620 of status messages should be returned. 4621 </para> 4622 4623 <para> 4624 To support this, there are two variables. <link linkend="dsn-notify">$dsn_notify</link> is used to request receipts for 4618 ``return receipts.'' 4619 </para> 4620 4621 <para> 4622 To support DSN, there are two variables. <link linkend="dsn-notify">$dsn_notify</link> is used to request receipts for 4625 4623 different results (such as failed message, message delivered, etc.). 4626 4624 <link linkend="dsn-return">$dsn_return</link> requests how much 4627 4625 of your message should be returned with the receipt (headers or full 4628 message). Refer to the man page on sendmail for more details on DSN. 4626 message). 4627 </para> 4628 4629 <para> 4630 When using <link linkend="sendmail">$sendmail</link> for mail 4631 delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA 4632 supporting DSN command line options compatible to Sendmail: The -N and -R 4633 options can be used by the mail client to make requests as to what type of 4634 status messages should be returned. Please consider your MTA documentation 4635 whether DSN is supported. 4636 </para> 4637 4638 <para> 4639 For SMTP delivery using <link 4640 linkend="smtp-url">$smtp_url</link>, it depends on the 4641 capabilities announced by the server whether mutt will attempt to 4642 request DSN or not. 4629 4643 </para> 4630 4644
