Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    9
  • Subscribers subscribers
    8
  • Views views
    719
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hide internal IP of the GWIA

JvdMeij

Hello,

When I send mails to an external domain the message contains this:

0: FROM <receiving mail server/gateway IP>> (xxx.xx.xx.xx) BY <<receiving mail server/gateway>>  WITH ESMTP FOR someone@mydomain.com; Tue, 7 Nov 2023 17:14:59 +0200
1: FROM <<internal DNS name of  the GWIA (internal address of the GWIA e.g. 10.0.0.13) BY <<sending mailserver/gate>> WITH ESMTP FOR someone@mydomain.com; Tue, 7 Nov 2023 17:14:59 +0200
2: from gate-MTA by <<sending domain>> with Novell_GroupWise; Tue, 07 Nov 2023 17:14:58 +0100

The internal addres of the GWIA is irrelevant for the receiver. And it causes sometimes the mails to end up in spam because of the IP reputation of an internal IP address. Is there a way to hide the internal IP of the GWIA either bij changing the GWIA settings or by changing the SMG settings?

Parents
  • 0  

    I have no experience with the SMG from OT yet, but I read in the docu that there are possibilities to rewrite the SMTP header. Postfix and many firewall vendors that include a smtp / exim proxy know about "rewrite headers in outgoing mail messages". The RFC 822 and related RFC describe the "rewrite" and the allowed parameters. The GWIA itself knows startup switches with the help of which it is possible to hide GWIA header info. As a rule, I always use a postfix before a GWIA to protect the GroupWise system from errors in "internal traffic".

    @ Pam

    There are no possibilities in the GIWA switches to hide the information from the header except that the Helo can switch off the information which version the GIWA has and that it is a GroupWise GWIA of the SMTP Orginator. Is there a possibility to do something with the help of an extension of the GWIA switches?

    Greetings George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

Reply
  • 0  

    I have no experience with the SMG from OT yet, but I read in the docu that there are possibilities to rewrite the SMTP header. Postfix and many firewall vendors that include a smtp / exim proxy know about "rewrite headers in outgoing mail messages". The RFC 822 and related RFC describe the "rewrite" and the allowed parameters. The GWIA itself knows startup switches with the help of which it is possible to hide GWIA header info. As a rule, I always use a postfix before a GWIA to protect the GroupWise system from errors in "internal traffic".

    @ Pam

    There are no possibilities in the GIWA switches to hide the information from the header except that the Helo can switch off the information which version the GIWA has and that it is a GroupWise GWIA of the SMTP Orginator. Is there a possibility to do something with the help of an extension of the GWIA switches?

    Greetings George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

Children
  • 0   in reply to   

    As far as I can see there is no possibility to rewrite contents in mails with SMG.

    You can rewrite addresses, add header lines, add tags, but you cannot rewrite contents which is dangerous anyway ...

    Use "Verified Answers" if your problem/issue has been solved!

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.