Forum Home


Remove Internal Xeams IP from header Abdulmutallib
    Remove Internal Xeams IP from header Synametrics Support
        Remove Internal Xeams IP from header Anonymous
            Remove Internal Xeams IP from header Synametrics Support
                Remove Internal Xeams IP from header Abdulmutallib
    Remove Internal Xeams IP from header Reddy

From: Abdulmutallib
Date: 12/11/17 2:19 AM
Topic: Remove Internal Xeams IP from header
Type: General Discussions
Post a follow up

I am using Xeams for DKIM, and set it as smarthost for exchange's send connector.

When I see the message header, I can see the internal IP of my mailbox sever as:

Received: from [(192.168.1.47)] by Xeams-VM with Xeams SMTP
192.168.1.47 is my mailbox server ip, Xeams-Vm is the host name for our Xeams server.

How can I remove or hide this?
Top
From: Synametrics Support
Date: 12/11/17 8:19 AM
Topic: Remove Internal Xeams IP from header
Type: General Discussions
Post a follow up

You cannot remove these headers. Every SMTP server, including Xeams, will insert headers that can be used to trace the message. Try looking at a message you received from Gmail or hotmail.com. They will also contain headers that are on your internal network.

May I know what the reason for removing them? This is not a security risk if that is what concerns you.
Top
From: Anonymous
Date: 12/12/17 3:54 AM
Topic: Remove Internal Xeams IP from header
Type: General Discussions
Post a follow up

I had send email from my corp-email to my yahoo mailbox, Please check the header below:

 

X-Apparently-To: mutallibk2@yahoo.com; Sun, 10 Dec 2017 05:58:38 +0000
Return-Path: <my-Corp-Email@mydomain.com>
X-YahooFilteredBulk: 83.96.74.25
Received-SPF: pass (domain of mydomain.com designates 83.96.74.25 as permitted sender)
X-YMailISG: p4P.9MEWLDs2u.aHeUHtdaSjjP1fDkkpQVwYazMNI3UvOILi
 gtqCiMAOgEGWvJGwUb1cK7yxmrRmQ1omPT8LQKv3acbpK92eW3kGKMQC8Ol4
 XludqriEsC0q8DC0toZ3csxBBemHPZblSieNawxlIK5a6YEsueiAvMAoW_jm
 oSjTVM8zELOCDU9zypnKQ3Sc_XjmX6c43dVtuf29Ypo6dFY8VbTyhvtxB2rL
 MIFLMRh_KJszqzdwjDr0ZlNQS89EuRFDTw.n3NDQQBX6KrY8Msk8rsKUKOmQ
 0AsvkQTUm.YX6bLRR9jaGDY09W6YQDwS3HNxJZ_BaaFNTkNDhWCXlCUTSVvy
 x6oCkpzc_oE3G4KE.ubqgNj8j7hbyqAkEt_cprNfccd2vrWPsfGxWBtit1.N
 BLamb0_mBZMEMDpkXkX8s9TKedr8mQp8.e1S7AeljNWnKthzcQ5bO.W92Q8H
 V2yMwvEoAKAMq_HkRpSh.y.z27u0OPrJq6OnVFYWadM0CD4io4hLvvjSgI9S
 YCdkw6h1VWiGtGXIRYhRxFPNDeyW4qYKHvW3_ZH0CKqL3dwkodtHsZVrGSCQ
 05h_GVGviR4y0Yhp6PwWKvlDwWI3gZavcLdia4cP1QX5Z5ZlydpMZuXWeSSe
 AWcsFnyoli7tPvqMb85gl2JflZT2_ujFbQm3ZAKHzYviU.fcn.rDMo6wtYF.
 AXvpYXEJrz_RYCWhbyC9aRqiONxirvlcd0aOQ0G0j_.gqywFy0RPTdXgvhuv
 qqqPbStljvXCx0E.tj98N5iPGf4O9QqOgxdgjX1BtLxUiDBFz1Sc8dh0tAv7
 zqOk7zOTCMV19Pn4UW020h3RYQrD53EtDUsHZMbaFS7s9QuKSAQvJQT.UHYx
 nG8W5DJJSunHjGqEgJqOwLvR4A89UqGSaxSVShEX83SQ6iJiJMKZIfis1qNc
 prjruliRLaa5Hm16ydcaOPsitAbKUpTNUD324uNk.m7Pc5u9jk4bLc14_EsH
 fsqf0jlWJaUFcUf.4A55o6LOMV0X18xqy4G_CgpqKoQkH9ADJoOFhvlLP9jh
 NV_tET1h67RTibigaCW60F1mVppE0PavEmQjfslC9wzf4HV89ej0o9jKrXtS
 PrNwLdLepfR9Q4PZSmbw
X-Originating-IP: [83.96.74.25]
Authentication-Results: mta1025.mail.gq1.yahoo.com  from=; domainkeys=neutral (no sig);  from=mydomain.com; dkim=pass (ok)
Received: from 127.0.0.1  (EHLO mail.mydomain.com) (83.96.74.25)
  by mta1025.mail.gq1.yahoo.com with SMTPS; Sun, 10 Dec 2017 05:58:37 +0000
X-BYPSHEADER: 21476610
DKIM-Signature:  a=rsa-sha256;
 b=MeWQgtr601Vwn7pl0/JmYfQl0dO3QWbIXMw9NpbSCXzqLx3/5d3ptkiDSEZqZNqh5PSt8zIshvq8LwH0WYsnfZJfMsfHfuDlZ9MTWnOHIbZ8G1TZ1Z+lkaN8cipnurjNQuI1MW1FYhIeEDvRgN8RS0rrQiAVxAfIS5NfzXi4JOXd8cHFJngcvZbr5+bcEeb+zd4vlSy3UpiR9LJxwgDqakvTYphoCAD4kLmJAYkzSo7QrKqMWM9qNNJWjCLxTbpljL7DzsoZ6Hf5DB8vR4JblDc2y2qbvVtpSl9+FXLrxnBhSjZ3ode3vNvbhQQzifzbayyzU/xoJt/vYPqMvG4Hqg==;
 s=xm29112017; c=relaxed/relaxed; d=mydomain.com; v=1;
 bh=XPUSwClTet9IjdMvO6skAIou3VUcc7qc+4xMQxLT1q8=;
 h=from:to:subject:date:message-id;
X-SMScore: 0
X-LCID: 34
Received: from [(192.168.1.47)] by Xeams-VM with Xeams SMTP; Sun, 10 Dec 2017 08:58:32 +0300 (AST)
X-SM_EnvelopeFrom: my-Corp-Email@mydomain.com
X-SM_RECEIVED_ON: Sun, 10 Dec 2017 08:58:32 +0300 (AST)
From: Abdulmutallib Khokar <my-Corp-Email@mydomain.com>
To: "mutallibk2@yahoo.com" <mutallibk2@yahoo.com>
Subject: test 858a
Thread-Topic: test 858a
Thread-Index: AdNxe+esURU9ySiAQXOX8/VCdaI3vg==
Date: Sun, 10 Dec 2017 05:58:31 +0000
Message-ID: <ae8f71f176944231b6f3439ed4ec9d0e@BIMBX2.myDomain.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.6]
Content-Type: multipart/alternative;
 boundary="_000_ae8f71f176944231b6f3439ed4ec9d0eBIMBX2myDomainlocal_"
MIME-Version: 1.0
Content-Length: 2763

--_000_ae8f71f176944231b6f3439ed4ec9d0eBIMBX2myDomainlocal_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I need to hide the Local (LAN) IP address of my mailbox server which is 192.168.1.47.

I had applied the PS command on my exchange to hide the other exchange related LAN information from the header.

PS command example:

 [PS] C:\>Get-SendConnector "EdgeSync - Datacenter1 to Internet" | Remove-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights ms-Exch-Send-Headers-Routing

So I need to hide the line where is says:

 Received: from [(192.168.1.47)] by Xeams-VM with Xeams SMTP; Sun, 10 Dec 2017 08:58:32 +0300 (AST)

If this is possible please let me know.

 

Thanks
Top
From: Synametrics Support
Date: 12/12/17 8:05 AM
Topic: Remove Internal Xeams IP from header
Type: General Discussions
Post a follow up

This cannot be done in Xeams as the feature does not exist. The PowerShell command you posted above will only change how Exchange behaves - it will not have any effect on Xeams. We can certainly add a feature request for a future release. I am going to forward this message to our dev. team.

Just for curiosity, what is the purpose of hiding this?

 
Top
From: Abdulmutallib
Date: 12/13/17 3:10 AM
Topic: Remove Internal Xeams IP from header
Type: General Discussions
Post a follow up

Recently having issues with Yahoo, as wouldnt send emails to yahoo mailboxes. So there were some complaince requirement from yahoo, like SPF,DMARC,DKIM,RDNS fix etc.

So configured Xeams for DKIM. Just to be on safe side as the header dont provide some extra internal LAN info.

 

Thanks for having this as a feature request, will be glad to get it.
Top
From: Reddy
Date: 7/26/19 5:58 AM
Topic: Remove Internal Xeams IP from header
Type: General Discussions
Post a follow up

I have the same issue. it does not look professional to show your LAN Ip and internal server names. It should only show Public IP for PTR and reverse lookup. I think it would be good add-on  and very much in need.
Top