Gnus development mailing list
 help / color / mirror / Atom feed
From: patl@cag.lcs.mit.edu (Patrick J. LoPresti)
Subject: Re: Fully-qualifying Email addresses in outgoing mail
Date: 10 Dec 1999 09:59:39 -0500	[thread overview]
Message-ID: <s5g3dtan8o4.fsf@egghead.curl.com> (raw)
In-Reply-To: Per Abrahamsen's message of "10 Dec 1999 04:32:41 -0500"

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> (setq mail-host-address "cag.lcs.mit.edu")
> 
> Or did I misunderstood the problem?

This takes care of the problem for "From" line generation, but it does
not affect what appears in the "To" and "CC" headers.

When a user provides "To: patl" in the header, message-mode does no
manipulation of that at all (as far as I can tell).  It simply passes
it off as-is to the message-send-mail-function.

When that function is 'message-send-mail-with-qmail, all is well
because qmail-inject performs all sorts of canonicalization on the
message: It inserts Date and Message-ID headers (if needed); it fully
qualifies all Email addresses; and so on.

But when you use 'smtpmail-send-it, the message goes straight to the
smtp daemon which performs no canonicalizations of any kind.  For
headers like Date and Message-ID, this is OK, because message-mode has
already fixed those up as required.  But for "To" and "CC", this is
problematic for two reasons: 1) The unqualified addresses are
processed by the smtp *host*, which is not the right thing at all; and
2) the unqualified addresses appear in the recipient's copy of the
message, which is also broken.

I am pretty sure what I need is for message-mode to be able to
canonicalize the To and CC fields, in the same way it performs other
checks on the message.

 - Pat


  reply	other threads:[~1999-12-10 14:59 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 [this message]
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
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=s5g3dtan8o4.fsf@egghead.curl.com \
    --to=patl@cag.lcs.mit.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).