On 2026-01-16 19:42, John Fawcett via Postfix-users wrote:
> On 16/01/2026 16:34, Jan Eden via Postfix-users wrote:
> > I did, and I still cannot see the reason for the different behaviour
> > with respect to the destination:
> >
> > root@social:~# postconf myorigin
> > myorigin = /etc/mailname
> > root@social:~# cat /etc/mailname
> > social.eden.one
> > root@social:~# postconf mydestination
> > mydestination = $myhostname, localhost.localdomain, localhost
> > root@social:~# postconf myhostname
> > myhostname = social.eden.one
> >
> > root@socialnew:~# postconf myorigin
> > myorigin = /etc/mailname
> > root@socialnew:~# cat /etc/mailname
> > socialnew.eden.one
> > root@socialnew:~# postconf mydestination
> > mydestination = $myhostname, localhost.localdomain, localhost
> > root@socialnew:~# postconf myhostname
> > myhostname = socialnew.eden.one
> >
> > [email protected] should be matched by mydestination on
> > socialnew – but it is not. I tried using 'socialnew.eden.one' in the
> > mydestination list directly, without success.
>
> Ff messages apparently to [email protected] are not matching
> mydestination that contains myhostname with a value of socialnew.eden.one,
> then maybe the conclusion is that the messages are not actually to
> [email protected].
>
> That would seem to tie up with the fact that if you explicitly send to
> [email protected] you get the expected behaviour, whereas if you send
> only to root you don't.
>
> Out of curiosity when you get the message sent to root, what "To:" address
> do you see in the message?
This is the raw message (minus the DKIM headers added by the relay
host). Please note: In the meantime, I switched hostnames ('social' is the
former 'socialnew', the former 'social' was turned off):
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from localhost
by mail.eden.one with LMTP
id PP40NviKamnu8AAAMvUbEA
(envelope-from <[email protected]>)
for <[email protected]>; Fri, 16 Jan 2026 20:01:12 +0100
Return-Path: <[email protected]>
Delivered-To: [email protected]
Authentication-Results: mail.eden.one;
auth=pass [email protected]
Received:
by mail.eden.one (OpenSMTPD) with ESMTPSA id 695ec29d
(TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO)
for <[email protected]>;
Fri, 16 Jan 2026 20:01:12 +0100 (CET)
Received: by social.eden.one (Postfix, from userid 0)
id 78FF0801A2; Fri, 16 Jan 2026 20:01:16 +0100 (CET)
Subject: Test
To: root <[email protected]>
User-Agent: mail (GNU Mailutils 3.17)
Date: Fri, 16 Jan 2026 20:01:16 +0100
Message-Id: <[email protected]>
From: root <[email protected]>
X-TUID: yfVQPqNjXRB6
> Are the "mail" commands the same on both systems and configured the same?
Yes, I verified the 'mail' commands are both part of 'mailutils' (as
seen in the headers above).
> I would be interested to know where the mapping is taking place on socialnew
> from destination "root" to "[email protected]", since the address is being
> treated as non local, my understanding is it is not taking that from local
> aliases.
That is my question exactly. I really have no clue at what point the
host (social, formerly socialnew) deviates from the expected path.
- Jan
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
