Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

why always_add_missing_headers is not adding To: header?

547 views
Skip to first unread message

Peter Volkov

unread,
Dec 15, 2014, 7:15:27 PM12/15/14
to
Hi!

always_add_missing_headers = yes
was added in main.cf, restarted server and postconf reports it is there.
According to documentation
http://www.postfix.org/postconf.5.html#always_add_missing_headers
I'm expecting to have To: header set in every e-mail, but still there is
none (see below). Could you help me to understand why this happens?

Delivered-To: my_correct_email
Received: by 10.217.69.3 with SMTP id y3csp909369wex;
Mon, 15 Dec 2014 15:54:11 -0800 (PST)
X-Received: by 10.180.19.193 with SMTP id
h1mr35290537wie.10.1418687651090;
Mon, 15 Dec 2014 15:54:11 -0800 (PST)
Return-Path: <red...@support.domain.com>
Received: from relay9out.redstationmail.co.uk
(relay9out.redstationmail.co.uk. [109.200.0.66])
by mx.google.com with ESMTP id
e3si55261wix.69.2014.12.15.15.54.10
for <my_correct_email>;
Mon, 15 Dec 2014 15:54:11 -0800 (PST)
Received-SPF: none (google.com: red...@support.domain.com does not
designate permitted sender hosts) client-ip=109.200.0.66;
Authentication-Results: mx.google.com;
spf=none (google.com: red...@support.domain.com does not
designate permitted sender hosts) smtp.mail=red...@support.domain.com
Received: from relay3in (relay3in.redstationmail.co.uk [109.73.64.3])
by relay9out.redstationmail.co.uk (Postfix) with ESMTP id
75F53121E5B
for <my_correct_email>; Tue, 16 Dec 2014 00:31:45 +0000 (GMT)
Received: from dev.domain.com (31.3.252.250) by relay3in (Redstation
ESMTP MAIL Service) with ESMTP id 83808157; Mon, 15 Dec 2014 11:54:04
+0000
Received: from localhost.localdomain (unknown [10.254.253.151])
by dev.domain.com (Postfix) with ESMTP id D6F9AAA335E
for <my_correct_email>; Tue, 16 Dec 2014 02:53:59 +0300 (MSK)
Date: Tue, 16 Dec 2014 03:53:59 +0400
From: red...@support.domain.com
Message-ID: <548f7497d25f5_18c...@support.mail>
Subject: Redmine test
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_548f7497d0f19_18c3ff8ec10184422655";
charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: Redmine
X-Redmine-Host: support.domain.com
X-Redmine-Site: Support
X-Auto-Response-Suppress: OOF
Auto-Submitted: auto-generated
List-Id: <redmine.support.domain.com>

Thanks in advance for any help,
--
Peter.

li...@rhsoft.net

unread,
Dec 15, 2014, 7:29:17 PM12/15/14
to

Am 16.12.2014 um 01:14 schrieb Peter Volkov:
> always_add_missing_headers = yes
> was added in main.cf, restarted server and postconf reports it is there.
> According to documentation
> http://www.postfix.org/postconf.5.html#always_add_missing_headers
> I'm expecting to have To: header set in every e-mail, but still there is
> none (see below). Could you help me to understand why this happens?

does the client match "local_header_rewrite_clients"
http://www.postfix.org/postconf.5.html#local_header_rewrite_clients

always_add_missing_headers (default: no)

Always add (Resent-) From:, To:, Date: or Message-ID: headers when not
present. Postfix 2.6 and later add these headers only when clients match
the local_header_rewrite_clients parameter setting. Earlier Postfix
versions always add these headers; this may break DKIM signatures that
cover non-existent headers.

Wietse Venema

unread,
Dec 15, 2014, 7:54:31 PM12/15/14
to
Peter Volkov:
> Hi!
>
> always_add_missing_headers = yes
> was added in main.cf, restarted server and postconf reports it is there.
> According to documentation
> http://www.postfix.org/postconf.5.html#always_add_missing_headers
> I'm expecting to have To: header set in every e-mail, but still there is

There is no RFC that requires a To: header.

Wietse

li...@rhsoft.net

unread,
Dec 15, 2014, 8:00:59 PM12/15/14
to

Am 16.12.2014 um 01:52 schrieb Wietse Venema:
> Peter Volkov:
but the postfix documentation pretends to add it :-)

Wietse Venema

unread,
Dec 15, 2014, 8:09:11 PM12/15/14
to
li...@rhsoft.net:
> Am 16.12.2014 um 01:52 schrieb Wietse Venema:
> > Peter Volkov:
> >> always_add_missing_headers = yes
> >> was added in main.cf, restarted server and postconf reports it is there.
> >> According to documentation
> >> http://www.postfix.org/postconf.5.html#always_add_missing_headers
> >> I'm expecting to have To: header set in every e-mail, but still there is
> >
> > There is no RFC that requires a To: header
>
> but the postfix documentation pretends to add it :-)

That text was written before RFC 2822. I can't help it that
the RFC authors are constantly improving the protocols.

Wietse

Wietse Venema

unread,
Dec 15, 2014, 8:25:36 PM12/15/14
to
Wietse Venema:
> li...@rhsoft.net:
> > Am 16.12.2014 um 01:52 schrieb Wietse Venema:
> > > Peter Volkov:
> > >> always_add_missing_headers = yes
> > >> was added in main.cf, restarted server and postconf reports it is there.
> > >> According to documentation
> > >> http://www.postfix.org/postconf.5.html#always_add_missing_headers
> > >> I'm expecting to have To: header set in every e-mail, but still there is
> > >
> > > There is no RFC that requires a To: header
> >
> > but the postfix documentation pretends to add it :-)
>
> That text was written before RFC 2822. I can't help it that
> the RFC authors are constantly improving the protocols.

The undisclosed_recipients_header parameter setting
controls whether a To: header will be added.

Wietse

Peter Volkov

unread,
Dec 16, 2014, 1:43:46 AM12/16/14
to
Hi!

В Вт, 16/12/2014 в 01:28 +0100, li...@rhsoft.net пишет:
> Am 16.12.2014 um 01:14 schrieb Peter Volkov:
> > always_add_missing_headers = yes
> > was added in main.cf, restarted server and postconf reports it is there.
> > According to documentation
> > http://www.postfix.org/postconf.5.html#always_add_missing_headers
> > I'm expecting to have To: header set in every e-mail, but still there is
> > none (see below). Could you help me to understand why this happens?
>
> does the client match "local_header_rewrite_clients"
> http://www.postfix.org/postconf.5.html#local_header_rewrite_clients
>
> always_add_missing_headers (default: no)
>
> Always add (Resent-) From:, To:, Date: or Message-ID: headers when not
> present. Postfix 2.6 and later add these headers only when clients match
> the local_header_rewrite_clients parameter setting. Earlier Postfix
> versions always add these headers; this may break DKIM signatures that
> cover non-existent headers.

I read this text as:
1. with this option always adds headers
2. postfix >2.6 add this headers even without always_add_missing_headers
option if clients match local_header_rewrite_clients parameter setting

Is my reading wrong? Should I really check local_header_rewrite_clients?

--
Peter.

Peter Volkov

unread,
Dec 16, 2014, 1:49:40 AM12/16/14
to
Hi, Wietse!

В Пн, 15/12/2014 в 20:24 -0500, Wietse Venema пишет:
> Wietse Venema:
> > li...@rhsoft.net:
> > > Am 16.12.2014 um 01:52 schrieb Wietse Venema:
> > > > Peter Volkov:
> > > >> always_add_missing_headers = yes
> > > >> was added in main.cf, restarted server and postconf reports it is there.
> > > >> According to documentation
> > > >> http://www.postfix.org/postconf.5.html#always_add_missing_headers
> > > >> I'm expecting to have To: header set in every e-mail, but still there is
> > > >
> > > > There is no RFC that requires a To: header
> > >
> > > but the postfix documentation pretends to add it :-)
> >
> > That text was written before RFC 2822. I can't help it that
> > the RFC authors are constantly improving the protocols.

Does this mean that documentation is lagging and postfix is not supposed
to add To: header?

> The undisclosed_recipients_header parameter setting
> controls whether a To: header will be added.

As I read documentation this sets some predefined header, while I'd like
postfix to add To: header from envelope. Is this possible at all?


(slightly off-topic: how can I see headers of mail for messages sent by
system? postfix sends so fast that I'm unable to read it in queue).

Thanks for you help so far,
--
Peter.

0 new messages