Skip to main content

Exim using different HELOs on the same outgoing IP

Comments

10 comments

  • cPanelMichael
    Hello :) Internal case CPANEL-5340 is open to discuss potential changes to the current behavior of generating a 1:MANY HELO relationship in /etc/mailhelo when "Send mail from account"s dedicated IP address" is enabled, and multiple resellers exist on the main shared IP address, and when that IP address is not the same as the "main routed IP". It also applies to the case you mentioned where separate IP addresses are assigned to addon domain names associated with the same account. The current workaround is to disable "Send mail from account"s dedicated IP address" and manually manage the /etc/mailips and /etc/mailhelo files as per the document at: How to Configure Exim's Outgoing IP Address - cPanel Knowledge Base - cPanel Documentation There's no update to report on this case at this time, but I will update this thread with additional information as it becomes available. Thank you.
    0
  • urgido
    *: domainone.com *: domaintwo.com So, when an account sends an email from some addon domain of any of two accounts mentioned above this will delivered by the dedicated IP listed in /etc/mailhelo and /etc/mailips?
    0
  • cPanelMichael
    *: domainone.com *: domaintwo.com So, when an account sends an email from some addon domain of any of two accounts mentioned above this will delivered by the dedicated IP listed in /etc/mailhelo and /etc/mailips?

    You can define the specific IP address a domain name uses when sending email in the /etc/mailips file. You would enter the specific IP address instead of the asterisk. EX:
    example.net: 192.168.0.3 example.com: 192.168.0.3
    The /etc/mailhelo file would look like this if you wanted to configure the hostname as the HELO address for specific domain names:
    example.net: hostname.example.com example.com: hostname.example.com
    Or, you could use an entry like this to configure the same HELO name for all domain names or any domain names not already defined in the file:
    *: hostname.example.com
    Thank you.
    0
  • urgido
    Hi, thanks for the clarification. I have latest question: Do I need to set addon domains and subdomains into these files?
    0
  • cPanelMichael
    thanks for the clarification. I have latest question: Do I need to set addon domains and subdomains into these files?

    It's not required, but any domain name that's not defined in these files will revert to the default entry you have configured. For instance, using the example in my last response, any addon domain name that you don't configure would revert to what's configured next to the asterisks:
    *: hostname.example.com
    Let me know if this explanation helps. Thank you.
    0
  • urgido
    Well, this is a temporary solution. I'll waiting for resolution of this case. Thanks a lot.
    0
  • RodrigoBaldasso
    @cPanelMichael Hi, is there any update on this case?
    0
  • cPanelMichael
    @cPanelMichael Hi, is there any update on this case?

    There's no update to report at this time, but additional information from a support ticket was added to the case today. I'll update this thread as soon as any changes to this case occur. Thank you.
    0
  • RodrigoBaldasso
    There's no update to report at this time, but additional information from a support ticket was added to the case today. I'll update this thread as soon as any changes to this case occur. Thank you.

    Michael, Yeah, probably the ticket was mine :). This is my tip to anyone facing this issue (thanks to Trevor Bordner), is this script:
    0
  • cPanelMichael
    Hello, To update, cPanel version 72 will include a resolution (#CPANEL-18859) that ensure a reseller owned user sharing the reseller IP address has the correct entries in the /etc/mailhelo and /etc/mailips files. Thank you. Update: This is also fixed in cPanel & WHM Version 70: Fixed case CPANEL-17899: Ensure /etc/mailips and /etc/mailhelo are updated on account add/remove.
    0

Please sign in to leave a comment.