From: Harry Putnam <reader@newsguy.com>
Subject: Suppressing message-id generation locally
Date: 26 May 2001 05:55:12 -0700 [thread overview]
Message-ID: <m13d9sb7cw.fsf@totally-fudged-out-message-id> (raw)
Following along with the sender header discussion I decided I should
disable message-id generation on my end and let the posting host for
news or smtp (outgoing) for mail set it.
Kai suggested:
(setq message-required-news-headers (delete 'Message-ID
message-required-news-headers))
Which does the job for news, but what about mail?
I thought maybe a similar thing like this:
(setq message-required-mail-headers (delete 'Message-ID
message-required-mail-headers))
Which does stop gnus from generating the id but it still gets
generated locally (and incorrectly) like below:
<200105261236.f4QCaU927207@reader.local.lan>
So how to proceed, if one wanted to disable message-id at the local
MTA level so that my local MTA (sendmail-8.11.2-14) passes the message
to outgoing mail machine at ISP (where I have no say in config) with
out a message-id, so that regardless of MUA the message id would get
generated at the outgoing smtp machine.
I'd like the mail handling software to deal with this, without my
having to force a correct message-id. But not so clear how to do
that. I'm behind my own firewall, on a locally named/addressed
machine in 192.168 range with no (internet recognized) FQDN.
My firewall, a NETGEAR FR314 DSL/router holds my static IP address but
does not process mail, beyond passing it through. I can think of
several ways to kludge this so it comes out right but wanted to follow
`Rats' advice and let the mail handling software and network settings
deal with it, and get it right.
next reply other threads:[~2001-05-26 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 12:55 Harry Putnam [this message]
2001-05-27 21:32 ` Paul Jarc
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=m13d9sb7cw.fsf@totally-fudged-out-message-id \
--to=reader@newsguy.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).