Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: Fully-qualifying Email addresses in outgoing mail
Date: 10 Dec 1999 14:14:29 -0800	[thread overview]
Message-ID: <ylzoviv3y2.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Stainless Steel Rat's message of "10 Dec 1999 17:03:09 -0500"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> No, it is a mail transport agent (MTA) that speaks simple mail transfer
> protocol (SMTP).

qmail-inject is not an MTA and it does not speak SMTP.

> Rewriting headers of an RFC 822 message for canonicity is a good thing.
> But if a message is not an RFC 822 message, qmail-inject has absolutely
> no grounds for turning it into an RFC 822 message.

If you pass a message to qmail-inject, you're telling it that you want it
to turn it into an RFC 822 message and then inject it into qmail's queue.

> And even then, rewriting To and Cc is a Really Bad Idea because it can
> and eventually will cause mail not to be delivered properly (see my
> response to Kai's message for some details).

qmail-inject is a piece of an MUA, specifically the bit that takes
potentially unqualified and incomplete local mail and turns it into RFC
822 mail.  If you don't want your message to be canonicalized according to
the rules that it applies, don't pass it to qmail-inject.  qmail only does
message rewriting if you explicitly use the interface that is documented
to rewrite messages, namely qmail-inject.

-- 
Russ Allbery (rra@stanford.edu)         <URL:http://www.eyrie.org/~eagle/>


  reply	other threads:[~1999-12-10 22:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09 21:51 Patrick J. LoPresti
1999-12-10  9:32 ` Per Abrahamsen
1999-12-10 14:59   ` Patrick J. LoPresti
1999-12-10 15:41     ` Kai Großjohann
1999-12-10 15:51       ` Kai Großjohann
1999-12-10 16:02         ` Patrick J. LoPresti
1999-12-10 17:22           ` Stainless Steel Rat
1999-12-10 18:28             ` Patrick J. LoPresti
1999-12-10 18:32               ` Patrick J. LoPresti
1999-12-10 19:08               ` Stainless Steel Rat
1999-12-10 20:20                 ` Patrick J. LoPresti
1999-12-10 20:48                 ` Patrick J. LoPresti
1999-12-10 22:03                   ` Stainless Steel Rat
1999-12-10 22:14                     ` Russ Allbery [this message]
1999-12-10 22:24                       ` Stainless Steel Rat
1999-12-10 22:41                         ` Russ Allbery
1999-12-11  1:03                     ` Patrick J. LoPresti
1999-12-10 22:15                 ` Russ Allbery
1999-12-10 22:30                   ` Stainless Steel Rat
1999-12-11  1:28                     ` Patrick J. LoPresti
1999-12-11  3:09                       ` Stainless Steel Rat
1999-12-11  3:14                         ` Russ Allbery
1999-12-12 15:55                           ` Stainless Steel Rat
1999-12-10 19:44             ` Kai Großjohann
1999-12-10 20:58               ` Stainless Steel Rat
1999-12-10 21:36                 ` Patrick J. LoPresti
1999-12-10 22:17                   ` Stainless Steel Rat
1999-12-11  0:55                     ` Patrick J. LoPresti
1999-12-11 11:44                       ` Per Abrahamsen
1999-12-11 16:58                         ` Amos Gouaux
1999-12-10 20:25 ` Patrick J. LoPresti

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

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

  git send-email \
    --in-reply-to=ylzoviv3y2.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    /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.
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 NNTP newsgroup(s).