OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Adding Message-ID is wrong

From: Jay Maynard (jmaynardconmicro.cx)
Date: Tue Jun 01 2004 - 19:19:11 CDT


On Wed, Jun 02, 2004 at 01:56:54AM +0200, Alex van den Bogaerdt wrote:
> On Tue, Jun 01, 2004 at 11:25:28AM -0500, Jay Maynard wrote:
> > On Tue, Jun 01, 2004 at 06:05:37PM +0200, Alex van den Bogaerdt wrote:
> > > Note that "the following changes" are allowed at the origin, not on an
> > > intermediate relay!
> > How about the destination? You keep talking about destination SMTP servers
> > as though they are intermediate relays. Is this, in fact, what the RFC
> > intends?
> Where am I talking about "destination SMTP servers" ?

When Postfix is the SMTP server that, in turn, delivers to the client's
mailbox (either via its own local delivery mechanism, or by LMTP), it's the
destination server. It's not an intermediate relay in that case. That is the
case where I see Postfix adding Message-ID: headers.

> It specifically forbids altering/adding Message-ID, "From:" and "To:"
> when the MTA is an intermediate relay. This is a "MUST NOT" which is
> as strong as it gets.

It says nothing about when it's the destination server, then?

> I know next to nothing (nor does postfix) about the client connecting
> over the internet. Why would I want to add -my- domain to the headers?
> Why confuse my users?

Because having a Message-ID: is better than not having one?

Face it: you can't reject based on not having a Message-ID: header. You'll
lose far too much mail. BTDT. Given that, why do you care if there's one or
not, or what the contents are?