From: Jesper Harder <harder@myrealbox.com>
Subject: Re: message-default-headers
Date: Wed, 19 Mar 2003 05:13:33 +0100 [thread overview]
Message-ID: <m3d6kohu36.fsf@defun.localdomain> (raw)
In-Reply-To: <u7kawkxzp.fsf@boost-consulting.com>
David Abrahams <dave@boost-consulting.com> writes:
> I have:
>
> (setq message-default-headers "To: dave@boost-consulting.com")
>
> which is designed to make sure I'm on the recipient list of any
> message or reply I send. This works great, except that it results in
> multiple To: headers
>
> So, the question: is this curable? I'm sure hotmail is wrong and evil
> for mistreating my emails this way, but I'd really prefer to
> accomodate it rather than be unable to communicate with 10% (I guess)
> of all email users.
Hotmail is correct -- a message must not have more than one To field.
How about adding a Cc or BCC field with your address instead?
prev parent reply other threads:[~2003-03-19 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 0:20 message-default-headers David Abrahams
2003-03-19 4:13 ` Jesper Harder [this message]
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=m3d6kohu36.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).