ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Exchange 2019 Remove server name and internal IP from email headers

    IT Discussion
    2
    5
    331
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403
      last edited by

      So this is something I've been asked to look at, this appears possible but the information I've found on this doesn't appear to work or I'm missing something.

      Google search link

      Anyone else had to do this?

      DashrenderD 1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender @DustinB3403
        last edited by

        The instructions seem pretty straight forward. Did you give the send connector enough time to sync, or force it manually?

        DustinB3403D 1 Reply Last reply Reply Quote 0
        • DustinB3403D
          DustinB3403 @Dashrender
          last edited by DustinB3403

          @dashrender said in Exchange 2019 Remove server name and internal IP from email headers:

          The instructions seem pretty straight forward. Did you give the send connector enough time to sync, or force it manually?

          Yeah so, sorry for not following up. The instructions do work, but spam filters (sophos at least) puts this information back...... some great security there.

          Anyways... yeah...

          I was able to reduce the hop count printer in message analyzer from 5 to 3, which would remove the information. But the damn spam filter....

          So it may be a wash to even consider this.

          DashrenderD 1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender @DustinB3403
            last edited by

            @dustinb3403 said in Exchange 2019 Remove server name and internal IP from email headers:

            @dashrender said in Exchange 2019 Remove server name and internal IP from email headers:

            The instructions seem pretty straight forward. Did you give the send connector enough time to sync, or force it manually?

            Yeah so, sorry for not following up. The instructions do work, but spam filters (sophos at least) puts this information back...... some great security there.

            Anyways... yeah...

            I was able to reduce the hop count printer in message analyzer from 5 to 3, which would remove the information. But the damn spam filter....

            So it may be a wash to even consider this.

            Spam filter can't be made to drop everything before it? We assume the spam filter is at the edge of your network, so the outside world shouldn't NEED to know about anything behind it.

            DustinB3403D 1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403 @Dashrender
              last edited by

              @dashrender said in Exchange 2019 Remove server name and internal IP from email headers:

              @dustinb3403 said in Exchange 2019 Remove server name and internal IP from email headers:

              @dashrender said in Exchange 2019 Remove server name and internal IP from email headers:

              The instructions seem pretty straight forward. Did you give the send connector enough time to sync, or force it manually?

              Yeah so, sorry for not following up. The instructions do work, but spam filters (sophos at least) puts this information back...... some great security there.

              Anyways... yeah...

              I was able to reduce the hop count printer in message analyzer from 5 to 3, which would remove the information. But the damn spam filter....

              So it may be a wash to even consider this.

              Spam filter can't be made to drop everything before it? We assume the spam filter is at the edge of your network, so the outside world shouldn't NEED to know about anything behind it.

              Can it be, maybe does this use case say to do anything with it, no. Security Scan is what called this out. So remediating the item mentioned is the goal, not "fixing" the issue.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post