Submitted by unsalkorkmaz on Sat, 02/07/2015 - 14:59
Hi, Here is a test mail from server:
Delivered-To: unsalkorkmaz@gmail.com
Received: by 10.52.11.71 with SMTP id o7csp2236428vdb;
Sat, 7 Feb 2015 12:53:13 -0800 (PST)
X-Received: by 10.194.81.104 with SMTP id z8mr23227362wjx.45.1423342392091;
Sat, 07 Feb 2015 12:53:12 -0800 (PST)
Return-Path: <webmin@firmasite.com>
Received: from ns1.firmasite.com ([2a01:4f8:211:2c43::2])
by mx.google.com with ESMTP id bk8si12984538wjc.11.2015.02.07.12.53.11
for <unsalkorkmaz@gmail.com>;
Sat, 07 Feb 2015 12:53:11 -0800 (PST)
Received-SPF: softfail (google.com: domain of transitioning webmin@firmasite.com does not designate 2a01:4f8:211:2c43::2 as permitted sender) client-ip=2a01:4f8:211:2c43::2;
Authentication-Results: mx.google.com;
spf=softfail (google.com: domain of transitioning webmin@firmasite.com does not designate 2a01:4f8:211:2c43::2 as permitted sender) smtp.mail=webmin@firmasite.com;
dkim=pass header.i=@firmasite.com
Received: by ns1.firmasite.com (Postfix, from userid 0)
id 86A6F6880696; Sat, 7 Feb 2015 22:53:10 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=firmasite.com;
s=ns1-firmasite; t=1423342390;
bh=eJIQyQ3blnlWmcLHCfPPh/oCByl+0DL5s801UBkM31Y=;
h=From:To:Cc:Subject:Date:Message-Id;
b=jlJPdnXPmtRn1+7VkmFmWo5WBfPwxHgVzri42A45rMMyHCrHASwhmcz83mB296jxD
yd04N8hYdwJepmqEotofuh2Jr8BOA7Ddp6bHtvEjVNobEfq9mR5XUKQXjRB/e6dkgV
B0WB9QBF+v1u7vpIDqQjKnprS2YZIJ2FQExn/t2nBRzeWGJjm2NTPMUwz0JwJDyMRG
27Wj51K3iMP/tE83ubhhQ+l3YmAvXt1ekwvRrLGp7Ho4aOrXQN9g/tidg+yrHTVBdR
5bZwrugGXp75PKeHUWVGCd8Sl9jc4aY1vEWyYwX93MBWTY0dq10jWC12rFxeIhWkeM
1PmkpBhusMjTw==
From: webmin@firmasite.com
To: unsalkorkmaz@gmail.com
Cc:
Subject: Test email from Webmin
Date: Sat, 07 Feb 2015 22:53:10 +0200 (EET)
Message-Id: <1423342390.32424.1@ns1.firmasite.com>
This is a test message from Webmin, sent with the settings :
Mail server: Mail server: Postfix
Sent via: Local mail server
SMTP login: None
SMTP authentication: Default
You can check my dns records for firmasite.com. It has spf record but its only ip4. Is that my fault or bug? Can you help please?
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Sat, 02/07/2015 - 15:32 Comment #1
Is the IPv6 address 2a01:4f8:211:2c43::2 active on your system? If so, is it private to this domain, or shared by all domains?
Submitted by unsalkorkmaz on Sat, 02/07/2015 - 15:44 Comment #2
Its server's default ip6 that came with hosting packet.
IP Address: 136.243.18.196IPv6 Address: 2a01:4f8:211:2c43::2
Its not private and supposed to use by all domains.
Submitted by JamieCameron on Sat, 02/07/2015 - 16:42 Comment #3
If you go to System Settings -> Re-Check Configuration, does it show that as the primary IP address on the system?
Submitted by unsalkorkmaz on Sat, 02/07/2015 - 16:56 Comment #4
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..
Your system has 31.13 GB of memory, which is at or above the Virtualmin recommended minimum of 256 MB.
BIND DNS server is installed, and the system is configured to use it.
Apache is installed.
The following PHP versions are available : 5.6.5 (/bin/php-cgi)
Apache is configured to host SSL websites.
MySQL is installed and running.
Logrotate is installed.
Using network interface eth0 for virtual IPs.
IPv6 addresses are available, using interface eth0.
Default IPv4 address for virtual servers is 136.243.18.196.
Default IPv6 address for virtual servers is 2a01:4f8:211:2c43::2.
Default IP address is set to 136.243.18.196, which matches the detected external address.
Both user and group quotas are enabled for home and email directories.
All commands needed to create and restore backups are installed.
The selected package management and update systems are installed OK.
.. your system is ready for use by Virtualmin.
Submitted by JamieCameron on Sun, 02/08/2015 - 00:43 Comment #5
You might try turning SPF off and on again for that domain, and then checking if the IPv6 address gets included in the SPF record correctly.
Submitted by unsalkorkmaz on Sun, 02/08/2015 - 10:02 Comment #6
Yeah, it worked. Thanks :)
Submitted by JamieCameron on Sun, 02/08/2015 - 12:12 Comment #7
Cool - my guess is that it was created before Virtualmin detected the IPv6 address on your system.
Submitted by Issues on Sun, 02/22/2015 - 12:12 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Sun, 02/22/2015 - 12:12 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.