CNAME and hiding mumara real domain/ip.

mube_2020

Beginner
Dec 18, 2020
13
1
3
Hi Wasif,

thanks for your feedback.

Will i have this header issue also when i use the PMTA configuration? Will the launch of v5.1.30 in days or weeks?
 

wasif

Administrator
Staff member
Apr 9, 2019
576
112
43
v5.1.30 is in the beta testing phase and should be available this weekend or next week. And yes this issue will not be reproduced once it's launched.
 

wasif

Administrator
Staff member
Apr 9, 2019
576
112
43
It's about to launch tonight!
 

hwp994108018

Beginner
Feb 26, 2024
3
0
1
Yes Mumara IP will not be pingable in the email headers.
Hello,
I send emails using postfix+mumara, postfix is hosted on server provider A and mumara is hosted on another server provider B. The question is why mumara's IP address: 165.140.***.162 appears in the email header. How to remove/hide mumara ip from email header?

I have tried to turn off "open tracking","click tracking", "unsubscribe link" and" DKIM Authentication ".

Here is the email source code:

Received: by mail-tester.com (Postfix, from userid 500)
id 46220A0ACE; Mon, 26 Feb 2024 11:23:21 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail-tester.com
X-Spam-Level: ***
X-Spam-Status: No/3.7/5.0
X-Spam-Test-Scores: DKIM_INVALID=0.1,DKIM_SIGNED=0.1,
FROM_SUSPICIOUS_NTLD=0.499,FROM_SUSPICIOUS_NTLD_FP=0.001,
HTML_MESSAGE=0.001,PDS_OTHER_BAD_TLD=1.725,RDNS_NONE=1.274,
SPF_HELO_NONE=0.001,SPF_PASS=-0.001,URIBL_BLOCKED=0.001
X-Spam-Last-External-IP: 49.83.***.236
X-Spam-Last-External-HELO: mail.example.xyz
X-Spam-Last-External-rDNS:
X-Spam-Date-of-Scan: Mon, 26 Feb 2024 11:23:21 +0100
X-Spam-Report:
* 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
* blocked. See
* http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
* for more information.
* [URIs: example.xyz]
* 1.7 PDS_OTHER_BAD_TLD Untrustworthy TLDs
* [URI: example.xyz (xyz)]
* 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
* -0.0 SPF_PASS SPF: sender matches SPF record
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
* 0.1 DKIM_INVALID DKIM or DK signature exists, but is not valid
* 0.5 FROM_SUSPICIOUS_NTLD From abused NTLD
* 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
* 0.0 FROM_SUSPICIOUS_NTLD_FP From abused NTLD
Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=49.83.***.236; helo=mail.example.xyz; envelope-from=[email protected]; receiver=[email protected]
DMARC-Filter: OpenDMARC Filter v1.3.1 mail-tester.com 4CBE6A0AD2
Authentication-Results: mail-tester.com; dmarc=pass header.from=example.xyz
Authentication-Results: mail-tester.com;
dkim=fail reason="key not found in DNS" (0-bit key; unprotected) header.d=example.xyz [email protected] header.b=IFEQ0aQ9;
dkim-atps=neutral
Received: from mail.example.xyz (unknown [49.83.***.236])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mail-tester.com (Postfix) with ESMTPS id 4CBE6A0AD2
for [email protected]; Mon, 26 Feb 2024 11:23:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example.xyz;
s=202401; t=1708942994;
bh=PcUqKJdYBz6x8aBJjlcrSxdxtAXM1dvdN4Fbb9ibJKQ=;
h=Date:Subject:From:Reply-To:To:From;
b=IFEQ0aQ9Strbj3BywSAXwTHC655JUIPWv2dTwAfjjxNgEPVGM0J0huO5uUh205FJO
CqRj/i2SYfU0vAYiEKbTHUfE1CekigJa4rcTlV4nAlUXSNeyFMMzWk0cD8DmgcwvSp
LBTLaZXcpoySndQgPeAkxrzc7zWpHzdGiBpv3i1K7LnX/uoUsKDDYucd7BcnbVV+U/
N4RGjFDWkP7CznoEzuhLE/Ymr5joOgs47gLkhgNaFwYN0AJuMkASo2yMqldFDaskp0
GKhKnaqeDJ1xK6J9Z4DfQ1PC6PzhOxTe3Z0TO1n8ssdGU0FfORCaxSJF6eawYZzq2T
2fWrXlF1VXx+Q==
Received: from [127.0.0.1] (unknown [165.140.***.162])
by mail.example.xyz (Postfix) with ESMTPA id 0DA6031C2D
for [email protected]; Mon, 26 Feb 2024 10:23:13 +0000 (UTC)
Message-ID: [email protected]
Date: Mon, 26 Feb 2024 10:23:13 +0000
Subject: Show you how to find reliable ways to grow your website
From: John Musk [email protected]
Reply-To: [email protected]
To: [email protected]
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="=swift_1708942993_3656a8822803baf79017d86346585655 = "
x-var: 30015-1-11-1-1-1-2-
x-logid: 30015

--=swift_1708942993_3656a8822803baf79017d86346585655 =
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
 

r.benmansour

Beginner
Feb 22, 2024
6
1
3
BTW, just to add another feature news to this thread. We have added another option that should be launched in the next updates, and it's called "PHP Redirect". You should be able to see it on the sending domain page, once it's launched. It will give you a PHP file that should be hosted on the tracking domain server/hosting. It will postback the tracking parameters to the Mumara server and redirect the recipient to the destination URL. It has been tested for all events i.e. opens, clicks, unsubscribes, and confirmation.
does this file for redirect still availabale, because in my last version I download it I only see cloaking, htacess and cname.
I have 2 servers one for mumara and one for sending domain with .htaccess redirection.
I changed the .htacess so that if click.domainB it will work as tracking but if you put straight the name of domain it will check it if it's not a subdomain it will send you to the domainB content,, but the code I adedd is not working can you check what is wrong ?

--------------------------------------------------------------------------------------
Options +FollowSymLinks
RewriteEngine On

# Redirect all subdomains of [domain (except [domain itself) to the third-party tracking system for processing
RewriteCond %{HTTP_HOST} ^(www\.)?(.+\.)[domain]\.{domain extantion}$ [NC]
RewriteRule ^(.+)$ http://[domain]/$1 [L]

# Serve content from [domain (excluding subdomains)
RewriteCond %{HTTP_HOST} ^[domain]\$ [NC]
RewriteRule ^ - [L]
---------------------------------------
 

wasif

Administrator
Staff member
Apr 9, 2019
576
112
43
@r.benmansour The cloaking method is the PHP method, which will keep the Mumara server's identity hidden and communicate with it via API callbacks.

Regarding your second query, it appears that the tracking subdomain and the main domain are hosted within the same directory, which is not the ideal setup. For optimal performance and organization, we recommend configuring a separate subdomain dedicated to tracking. This allows for customization of the subdomain's selector/prefix to suit your specific needs or constraints. To implement this, you should direct your tracking subdomain to a distinct folder and place the .htaccess file within that folder to ensure it functions independently, thereby establishing a more structured and effective tracking environment.