When a client received an email, gets these headers Code: Received: from server.domain.com ([127.0.0.1]) by localhost (server.domain.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBIqjlBhghpF for <[email protected]>; Tue, 6 Sep 2011 16:13:09 +0200 (CEST) Received: from serv22.sqp.fr (unknown [213.30.188.22]) by server.domain.com (Postfix) with ESMTP id 5408A94009F for <[email protected]>; Tue, 6 Sep 2011 16:13:09 +0200 (CEST) And when client sends an email, the destination gets these headers Code: Received: from server.domain.com ([127.0.0.1]) by localhost (server.domain.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eF6U-RNt8eNa for <[email protected]>; Tue, 6 Sep 2011 17:44:10 +0200 (CEST) Received: from [192.168.200.99] (13.Red-83-179-128.staticIP.rima-tde.net [83.179.128.13]) (Authenticated sender: [email protected]) by server.domain.com (Postfix) with ESMTPSA id 96B3994009B for <[email protected]>; Tue, 6 Sep 2011 17:44:10 +0200 (CEST) How I can change "server.domain.com" per "mail.clientdomain.com" ? And 127.0.0.1 per client's asigned ip ?
Change bthe hostname of the server in /etc/hostname, /etc/postfix/main.cf, /etc/mailname and /etc/hosts This cant be changed.
If I do that, all clients will show they send through server.domain.com and what I would like is each client shows his domain. mail.clientdomain.com where "clientedomain" change for each client If I change these values in /etc/postfix/main.cf can I break something? mynetworks = 127.0.0.0/8 mynetworks = 11.22.33.44/32 content_filter = amavis:[127.0.0.1]:10024 content_filter = amavis:[11.22.33.44]:10024 where 11.22.33.44 is server's public main ip
Thats not supported by postfix as far as I know. A mailserver uses its own server name in email, thats the case for all mail systems. It does not use the virtual domain names of clients. I wont do that if I were you. This would open up the amavis spam filter so that it could be used to inject mails into your server from external sources. spam filter proxies always run on port 127.0.0.1 to prevent that, thats not specific to ispconfig.
