I think I understand now.
Restrict_post and Reply_to are absolutly correct set and are not the reason for our
problem. It's that alias address that shows up in a "Received: from" section of the mail
Here's an excerpt of a typical newsletter mail from our list-server:
Delivery-date: Thu, 15 Jan 2004 16:39:28 +0100
Received: from [220.127.116.11] (helo=gttserv.lth.rwth-aachen.de)
by mxng16.kundenserver.de with esmtp (Exim 3.35 #1)
id 1Ah9ai-0008IJ-00; Thu, 15 Jan 2004 16:39:28 +0100
Received: from gttserv.lth.rwth-aachen.de (localhost [127.0.0.1])
by gttserv.lth.rwth-aachen.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id i0FFObdr020855
for <email@example.com>; Thu, 15 Jan 2004 16:24:37 +0100
Received: (from mdom@localhost)
by gttserv.lth.rwth-aachen.de (8.12.3/8.12.3/Submit) id i0FFObKn020854
for gtt-news-list; Thu, 15 Jan 2004 16:24:37 +0100
X-Authentication-Warning: gttserv.lth.rwth-aachen.de: mdom set sender to owner-gtt-
firstname.lastname@example.org using -f
Date: Thu, 15 Jan 2004 16:24:29 +0100 (MET)
Subject: GTT-News, Issue 38
The insecure address we're talking about is email@example.com.
Normal action on a mail like the one above would never result in sending a mail back to
We're using Suse Linux 8.0 on our server, which installed Majordomo and sendmail with
I know, what you would say now: Never use standard configuration, since it is a
compromise to all possible users!
I will now try to understand the current config of our sendmail and it's mail address
aliases and figure out how to change it to meet our requirements.
Since I never worked with it before, it looks like it's getting to be a very time consuming
process ... :-(
Thanks again for your help.