Virtualmin Mailman sender is localhost.localdomain?

Virtualmin
1

I’ve got several mailing lists set up on different domains in Virtualmin. Unfortunately, the Sender: header of the administrative emails is always mailman-bounces@localhost.localdomain, whereas the From: header is correct: listname-owner@correctdomain.com.

This is causing messages to be rejected by moderators’ email systems.

How can I get the senders to align?

Here’s a snippet of the received email (on an email server that accepted it):

From: thelist-owner@domain.org
To: thelist-owner@domain.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0542925138=="
Message-ID: mailman.140.1398146004.1486.thelist@domain.org
Date: Mon, 21 Apr 2014 22:53:24 -0700
Precedence: bulk
X-BeenThere: thelist@domain.org
X-Mailman-Version: 2.1.14
List-Id: Directors and committee chairs of DOMAIN <thelist.domain.org>
X-List-Administrivia: yes
Errors-To: mailman-bounces@localhost.localdomain
Sender: mailman-bounces@localhost.localdomain

It’s the last two headers that are killing all the moderator notifies.

2

Howdy,

What output do you receive if you log into your server, and run this command:

hostname

3

hostname shows va.tdc.to

Those lines didn’t publish well. The other headers have correct addresses (the domain is from the list name sender).

4

Hmm, I just checked the email that went to another moderator, and it seems to have the right domain in the Errors-to: and Sender: headers. I wonder if I change the order of the moderators in the list if I see whether it only happens to the first one?

5

Let’s see if I can get the tags right here:

From: thelist-owner@domain.org
To: thelist-owner@domain.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0237713326=="
Message-ID: mailman.143.1398181304.1486.thelist@domain.org
Date: Tue, 22 Apr 2014 08:41:44 -0700
Precedence: bulk
X-BeenThere: thelist@domain.org
X-Mailman-Version: 2.1.14
List-Id: Directors and committee chairs of DOMAIN<thelist.domain.org>
X-List-Administrivia: yes
Errors-To: mailman-bounces@localhost.localdomain
Sender: mailman-bounces@localhost.localdomain

Apparently the Sender: address is used in the SMTP handshake:

Apr 22 08:41:47 va postfix/smtp[17643]: E23771700B27: to=amoderator@adomain.com, relay=toolworks.com[192.249.122.237]:25, delay=0.44, delays=0.04/0.01/0.32/0.07, dsn=5.0.0, status=bounced (host adomain.com[192.249.122.237] said: 550-Verification failed for mailman-bounces@localhost.localdomain 550-Unrouteable address 550 Sender verify failed (in reply to RCPT TO command))

6

No, it’s still a problem. The other moderator’s email address was more tolerant of a bogus sender.

Note that this only happens with the moderator notifies; the email that gets sent back to the original sender has the correct domain for the Sender: header.

7

Okay, well, I changed the DEFAULT_EMAIL_HOST in /etc/mailman/mm_cfg.py to the canonical hostname, and now it sends that as the host in the Sender: header for notices to moderators.

So that fixes it, though I’m surprised this isn’t already overridden somewhere else.