smtp_bind in 8.7

[marie.o]

Hi,

first post, please be gentle.

My MTA is sending out messages from the first IP address, instead of the 2nd IP address. How can this be fixed?

Code: Select all

Return-Path: <xxx@xxx.tld>
X-Original-To: marie.o@other.org
Delivered-To: marie.o@other.org
Received: from mail.mine.tld (2nd.ipaddress.tld [x.y.23.16])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by www.other.org (Postfix) with ESMTPS id 6029F300BE9
	for <marie.o@other.org>; Tue,  7 Feb 2023 07:41:14 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by mail.mine.tld (Postfix) with ESMTP id DEC057CC0600
	for <marie.o@other.org>; Tue,  7 Feb 2023 06:41:13 +0000 (UTC)
Received: from mail.mine.tld ([127.0.0.1])
	by localhost (mail.mine.tld [127.0.0.1]) (amavisd-new, port 10032)
	with ESMTP id f1LWieTi9qKs for <marie.o@other.org>;
	Tue,  7 Feb 2023 06:41:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by mail.mine.tld (Postfix) with ESMTP id 6FCDE7CC06E6
	for <marie.o@other.org>; Tue,  7 Feb 2023 06:41:13 +0000 (UTC)
X-Virus-Scanned: amavisd-new at mail.mine.tld
Received: from mail.mine.tld ([127.0.0.1])
	by localhost (mail.mine.tld [127.0.0.1]) (amavisd-new, port 10026)
	with ESMTP id nNX1CF7At0XP for <marie.o@other.org>;
	Tue,  7 Feb 2023 06:41:13 +0000 (UTC)
Received: from mail.mine.tld (mail.mine.tld [x.y.222.162])
	by mail.mine.tld (Postfix) with ESMTP id 4C3437CC0600
	for <marie.o@other.org>; Tue,  7 Feb 2023 06:41:13 +0000 (UTC)
Date: Tue, 7 Feb 2023 06:41:13 +0000 (UTC)
From: xxx user <xxx@xxx.tld>
To: marie.o@other.org
Message-ID: <1390575678.1032.1675752073117.JavaMail.zimbra@xxx.tld>
Subject: test
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [x.y.222.162]
X-Mailer: Zimbra 8.7.11_GA_1854 (ZimbraWebClient - GC108 (Win)/8.7.11_GA_1854)
Thread-Index: njkC0kvW5xsaakQNS/fZ8hub2j6J2w==
Thread-Topic: test

In 8.6 it worked as I wanted, sending out msgs from my 2nd IP address. Now, the initial sending comes from the 2nd IP address -> goes into amavisd -> and from the on finds it way out the first IP address.

Anyone has an idea how to rectify this in 8.7?

I am slowly upgrading the system from 14.04 8.6 to something more current, but this is currently causing some grief on my side.

Any and all help is greatly appreciated.

br
Marie.

[liverpoolfcfan]

Are you sure you are reading the logs correctly. The "Received" headers are listed most-recent-first. In your example it shows the initial submission was on the first IP and the final external delivery came from the second IP

[marie.o]

Hi,

and thanks for looking.

It is the header of a mail message being send out from the mail server.

If there is a corresponding log file that is more helpful, please let me know which one is best suited.

Thanks a bunch.

br
Marie.

[liverpoolfcfan]

Your email shows these two "Received" headers (among many others - each time the mail passes between processes/servers a new Received header is added)

Code: Select all

Received: from mail.mine.tld (2nd.ipaddress.tld [x.y.23.16])
   (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
   (No client certificate requested)
   by www.other.org (Postfix) with ESMTPS id 6029F300BE9
   for <marie.o@other.org>; Tue,  7 Feb 2023 07:41:14 +0100 (CET)

and

Code: Select all

Received: from mail.mine.tld (mail.mine.tld [x.y.222.162])
   by mail.mine.tld (Postfix) with ESMTP id 4C3437CC0600
   for <marie.o@other.org>; Tue,  7 Feb 2023 06:41:13 +0000 (UTC)

Your initial problem description stated

Now, the initial sending comes from the 2nd IP address -> goes into amavisd -> and from the on finds it way out the first IP address.

But, if you look at the timestamps, the opposite is what is happening.

The top header above is the most recent at 41 minutes and 14 seconds - it is the external delivery from mail.mime.tld (2nd IP address) to www.other.org
The bottom header is the initial submission of the message on your First IP Address, and passing it internally to Postfix at 41 minutes and 13 seconds.

The email has traversed the opposite way to your problem description. It has gone out in the same manner as you described as your intended path.

[marie.o]

Hello again,

my wording and/or change of the original text was confusing to say the least.

The 222.162 is where the mail should origin from.
The 23.16 is where the mail does come from, afaict.

Do I misread the header? The names might be wrong, but the IP addresses are correct in my paste...

Thanks again and sorry for the chaotic information presented.

br
Marie.