unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: emacs-devel@gnu.org
Subject: Re: use of 'sendmail -t'
Date: Tue, 06 May 2003 19:30:41 +0200	[thread overview]
Message-ID: <ilu8ytk6kzi.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m19D5Gh-000B3oC@proven.weird.com> (Greg A. Woods's message of "Tue, 6 May 2003 12:26:15 -0400 (EDT)")

"Greg A. Woods" <woods@weird.com> writes:

> [ On Tuesday, May 6, 2003 at 06:13:50 (-0400), Richard Stallman wrote: ]
>> Subject: Re: use of 'sendmail -t'
>>
>> I believe fencepost is running exim.  Can you tell me how to verify
>> that it is really exim?
>  
> I wasn't able to get Exim to build with just a very quick try in
> NetBSD's pkgsrc, however I was able to find the following paragraph in
> Exim's manual (exim-4.10/doc/spec.txt):
>
>        If there are any "Resent-" headers in the message, an error is
>        generated, and Exim gives up. RFC 2822 talks about different sets of
>        "Resent-" headers (when a message is resent several times), and it is
>        not at all clear how -t should operate in this situation. Experiments
>        with Sendmail have shown that it amalgamates multiple sets of "Resent-"
>        headers when -t is used. This does not seem to be in the spirit of RFC
>        2822.
>
> This does indeed suggest that Exim is one of the few, and maybe only,
> sendmail-compatible mailer which does not support "Resent-*" destination
> headers in combination with use of 'sendmail -t'.

I believe this is a bug in Exim.  I think it is pretty clear from RFC
2822 that the first Resent-* block is the valid one, if any Resent-*
blocks exist at all.  It is unfortunate that a MUST statement wasn't
used when saying that the fields are prepended to the message.  This
was undefined in RFC 822 though.

,----
| 3.6.6. Resent fields
| 
|    Resent fields SHOULD be added to any message that is reintroduced by
|    a user into the transport system.  A separate set of resent fields
|    SHOULD be added each time this is done.  All of the resent fields
|    corresponding to a particular resending of the message SHOULD be
|    together.  Each new set of resent fields is prepended to the message;
|    that is, the most recent set of resent fields appear earlier in the
|    message.  No other fields in the message are changed when resent
|    fields are added.
`----

> In the mean time I will submit a proposal to Philip Hazel suggesting
> that he re-evaluate his position on the support of "Resent-*" headers
> when '-t' is used and hopefully Exim will soon become compatible with
> Sendmail, Smail, Postfix, and other sendmail-compatible mailers.

Ah, we agree.  Good.

Don't forget to ask for the documentation to be updated.  "-t"
currently doesn't mention Resent-* at all, in all manuals I looked in.

  reply	other threads:[~2003-05-06 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 14:32 [ttn@glug.org: [gerd.moellmann@t-online.de: Re: [Don Saklad <dsaklad@gnu.org>] How to correct or bypass an error. Control-u f rmail in emacs onfencepost]] Richard Stallman
2003-05-05 16:25 ` use of 'sendmail -t' Greg A. Woods
2003-05-06 10:13   ` Richard Stallman
2003-05-06 16:26     ` Greg A. Woods
2003-05-06 17:30       ` Simon Josefsson [this message]
2003-05-08 11:47       ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ilu8ytk6kzi.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).