Originally Posted by falko
Please change the value of myorigin in /etc/postfix/main.cf and restart Postfix.
Myorigin points to /etc/mailname and that file contains mail.newdomain.tld .
I think the squirrelmail problem is that when I try to access http://www.newdomain.tld:81/squirrelmail/
, I will be redirected to http://www.olddomain.tld:81/squirrelmail/
. Redirect to old domain also happens with roundcube webmail access.
Both emails are not classified as spam anymore. The only problem are the traces to the old domain in squirrelmail and the webmail redirects. The latter is even worse, because users do not only need to confirm one certificate error, but two - one for the newdomain and one for the old domain before redirection.
Received: (qmail invoked by alias); 17 May 2008 10:13:44 -0000
Received: from mail.newdomain.tld (EHLO mail.newdomain.tld) [xxx.xxx.xxx.xxx]
by mx0.emailprovider.tld (mx002) with SMTP; 17 May 2008 12:13:44 +0200
Received: from www.olddomain.tld (localhost [127.0.0.1])
by mail.newdomain.tld (Postfix) with ESMTP id 196621E94153
for <firstname.lastname@example.org>; Sat, 17 May 2008 12:13:44 +0200 (CEST)
Received: from yyy.yyy.yyy.yyy
(SquirrelMail authenticated user username)
by www.olddomain.tld with HTTP;
Sat, 17 May 2008 12:13:44 +0200 (CEST)
Message-ID: <email@example.com domain.tld>
I think that solving the redirect problem will also solve the squirrelmail header problem. It looks like squirrelmail puts the access domain (from which you accessed squirrelmail webmail) into the header and uses that domain for the message id, too.
All of these seem to reflect the new domain:
I don' t know if this is important. First I have not created a new site for the new domain. I followed this howto to setup new nameservers:
But today I have added the new domain (created a new reseller in admin folder, then created new client for the new reseller and afterwards added the site to the new client). Unfortunately the redirect still takes place.