Skip to main content

Why different HELOs? - Horde vs Roundcube

Comments

13 comments

  • cPanelMichael
    Hello, This is answered on the following thread: Prevention client IP to appear in mail headers Horde webmail Thank you.
    0
  • EneTar
    Hi Michael thank you for your answer. So how to set the proper HELO in Horde or Roundcube It has to be the active domain instead of server hostname Form the thread you mentioned how is this done: It's important to keep in mind that a client must send it's own Domain in the Helo/EHLO command per RFC requirements.
    Currently all emails sent from Horde are going to spam for situations I described in the first post
    0
  • cPanelMichael
    Currently all emails sent from Horde are going to spam for situations I described in the first post

    Are you sure it's from the HELO name and not because the client's IP address is added to a spam blacklist? Thank you.
    0
  • EneTar
    Totally sure the client ip is not in a spam list because the client ip is dynamic and we have tried several IPs so far from different networks. Furthermore Gmail states this in the headers 1st case from my first post (Horde)
    Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning John@domain1.com does not designate 85.75.xxx.xxx as permitted sender) smtp.mailfrom=John@domain1.com Received-SPF: softfail (google.com: domain of transitioning John@domain1.com does not designate 85.75.xxx.xxx as permitted sender) client-ip=85.75.xxx.xxx;
    second case from my first post (Roundcube)
    Authentication-Results: mx.google.com; spf=pass (google.com: found no external ips, assuming domain of John@domain1.com as permitted sender) smtp.mailfrom=John@domain1.com Received-SPF: pass (google.com: found no external ips, assuming domain of John@domain1.com as permitted sender)
    In the second case (Roundcube) Gmail assumes the original message is sent from the same domain. Neither this should happen. Gmail should know that it is indeed from the specific domain. One more thing I noticed is that when sending from @domain1.com to @domain2.com there are no SPF and DKIM headers. However when sending from @domain1.com to @gmail.com or any other external domain then DKIM and SPF and DMARC are setup correctly. If I could solve this then I think there would be no issues.
    0
  • cPanelMichael
    One more thing I noticed is that when sending from @domain1.com to @domain2.com there are no SPF and DKIM headers. However when sending from @domain1.com to @gmail.com or any other external domain then DKIM and SPF and DMARC are setup correctly. If I could solve this then I think there would be no issues.

    Hello, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.
    0
  • EneTar
    Sorry can't see the link or any signature at all. I don't know why. Can you post the link in a reply?
    0
  • cPanelMichael
    Hi, Sure, it's: Create Support Ticket - Documentation - cPanel Documentation Thank you.
    0
  • EneTar
    Michael I'm trying to understand a few things first so before opening a ticket could you please tell me 1)By default when sending from John@domain1.com to george@domain2.com using Horde or Roundcube is DKIM and SPF included in the headers? Please note that domain1.com and domain2.com belong to accounts on the same server and ip. 2)Is there any walkthrough to set the HELO when using Horde or Roundcube?I would like it to have the active domain on HELO rather than the server hostname 3)Is this above related to the values of [LIST]
  • $smtp_banner
  • $smtp_active_hostname
  • $message_id_header_domain If it is related, how should those 3 values be? 4)on my Exim Configuration I have set "Send mail from account"s dedicated IP address" to On. In this case does the content of /etc/mailhelo and /etc/mailips affect the configuration? Thank you.
  • 0
  • EneTar
    To answer some of my questions after some research, 1)In this case LMTP is used and DKIM and SPF do not exist. That's a default behavior. I'm not sure if this can be changed somehow but I would like to know. 3)I couldn't alter the HELO with those options. This needs further research though 4) If "Send mail from account"s dedicated IP address" is set then the content of /etc/mailhelo and /etc/mailips are ignored. No need to open a ticket, as that's how things work by default. So if anyone uses POP3 through Gmail to fetch emails from a server powered by cPanel then those messages which are delivered originally with the LMTP protocol and fetched later from Gmail POP3 would probably end in the spam folder. So a custom filter in Gmail to not mark as spam all domains of the server is the way to go, at least for now... Even if they not end into the spam folder the question mark icon will be there for sure which links to Check if your Gmail message is authenticated - Android - Gmail Help I think cPanel should investigate this. More headers should be added through Exim in case of LMTP so that Gmail knows that emails are already authenticated.
    0
  • cPanelMichael
    I think cPanel should investigate this. More headers should be added through Exim in case of LMTP so that Gmail knows that emails are already authenticated.

    Would you mind opening a support ticket so we can review an affected system and rule out any bugs with the cPanel & WHM software itself? It's much easier to investigate this type of issue when reviewing the issue on a system affected by the issue. Note that you may find this post helpful for modifying the Roundcube HELO setting: HELO name problem on roundcube Thank you.
    0
  • EneTar
    @cPanelMichael there is not any affected system. What I described above is standard functionality in cPanel/WHM when using LMTP. What you need to test is 1) Two domains domain1.com and domain2.com on the same WHM/cPanel server. It can be only one domain if you wish. I just want to show that it affects all email messages transferred through LMTP meaning all email accounts of all domains in the same server. 2) Two email accounts someuser@domain1.com and anotheruser@domain2.com. It can be anotheruser@domain1.com as well. It is the same. 3) Send from the first account to the second one message. In case of Horde the external user IP is included. In case of roundcube it is hidden (<- This is what the title of the current thread describes. It is standard functionality and it is how Roundcube and Horde work. no worries so far. but the real problem lies elsewhere) 4) Add the second account (anotheruser@domain2.com) to Gmail by going to Gmail -> Settings -> Accounts and Import -> Check mail from other accounts 5)Wait for Gmail to fetch messages from anotheruser@domain2.com and notice that our message goes to spam because there is no DKIM neither SPF validation from step 3. Furthermore if in step 3 Roundcube has been used then Gmail finds no external ips and assumes the domain1.com as permitted sender and passes SPF. Please check the headers. My opinion is that Gmail shouldn't do that and should fail SPF too but that's another story. In case of Horde it finds an external IP which is not valid, it doesn't find any DKIM or SPF records and the message goes to spam. I know that Gmail is a third party software but I'm sure that other similar services will run into the same issue sooner or later. They won't find any DKIM/SPF when LMTP is used in step 3 and they will forward the message to spam. This can be avoided only if DKIM and SPF headers are added even at LMTP through Exim. So do you see it now?
    0
  • cPanelMichael
    ) Add the second account (anotheruser@domain2.com) to Gmail by going to Gmail -> Settings -> Accounts and Import -> Check mail from other accounts 5)Wait for Gmail to fetch messages from anotheruser@domain2.com[/EMAIL] and notice that our message goes to spam because there is no DKIM neither SPF validation from step 3. Furthermore if in step 3 Roundcube has been used then Gmail finds no external ips and assumes the domain1.com as permitted sender and passes SPF. Please check the headers. My opinion is that Gmail shouldn't do that and should fail SPF too but that's another story. In case of Horde it finds an external IP which is not valid, it doesn't find any DKIM or SPF records and the message goes to spam. I know that Gmail is a third party software but I'm sure that other similar services will run into the same issue sooner or later. They won't find any DKIM/SPF when LMTP is used in step 3 and they will forward the message to spam. This can be avoided only if DKIM and SPF headers are added even at LMTP through Exim. So do you see it now?

    Hello, Thank you for the additional clarification. Would you mind opening a bug report for this issue so we can investigate this further? It won't require access to your server, but will allow us to complete additional testing: Submit A Bug Report Thank you.
    0
  • EneTar
    Thank you Michael I just did Request ID is: 9073349
    0

Please sign in to leave a comment.