The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Email Sending Problem

Discussion in 'E-mail Discussions' started by Tiago Figueiredo, Aug 30, 2016.

  1. Tiago Figueiredo

    Tiago Figueiredo Registered

    Joined:
    Aug 30, 2016
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brazil
    cPanel Access Level:
    Website Owner
    Hi Peter,

    You said that "email doesn't just disappear into limbo"

    Well, mine certainly seem to do...

    I came to this forum after doing a search on Google and experiencing a problem to which I have been given no solution to so far by my hosting company, other than purchasing an additional product.

    Currently, the vast majority of my domain e-mails sent through my hosting company's mailserver - with accounts set using cPanel - are arriving at the destination's mailserver identified with my ISP's home IP as a Source IP. To me, it looks as if their server's behaviour is like a plain mail forwarding, instead of remailing/resending, although it actually adds additional "Received:" headers. Please bear with me, I'm not so tech-savvy so I may be using some terminology incorrectly.

    This happens regardless of whether I send my domain's e-mails using the Outlook client or the hosting company's webmail, unlike if I send an e-mail using my Outlook.com account and regardless of whether I use the Outlook client or webmail. When I send an Outlook.com or even a Gmail.com e-mail, the Source IP is always the mailserver's. So, it can't be an e-mail client configuration issue.

    This behaviour is sometimes causing my domain's e-mails being flagged by Gmail mailservers as "not being able to confirm that it was sent from the domain instead of a spam creator", although they still arrive at the destination's inbox, also sometimes ending in SPAM boxes hosted with other hosting companies and - worse - vanishing completely without either arriving at any of the recipient's boxes (SPAM included) based on a Microsoft server or me getting any failed delivery error messages returned. Since all ISP's domestic IPs are listed on the Spamhaus Project's PBL list and since Microsoft uses this list to filter SPAM, they just disappear.

    What I find strange is that I would expect any major hosting company's mailserver to behave like Outlook's and Gmail's but - in my case - it is not. I would really like to understand what is going on and why my hosting company's mailserver is behaving like this, since support staff is not being very forthcoming with any solution at all, other than trying to sell me an additional service while giving me a standard reply that "our server is being blocked by Microsoft".

    Funny enough, their support e-mails always arrive at my Outlook inbox.

    If you or anyone at cPanel's team could shed some light into this issue, I would really appreciate it.

    Thanks in advance.
    Tiago Figueiredo

    ------------

    The following are some header examples, where I've just replaced e-mail addresses for privacy:

    Sending a domain hosted e-mail using the Outlook client:

    Code:
    Delivered-To: [EMAIL]myname@gmail.com[/EMAIL]
    Received: by 10.28.1.68 with SMTP id 65csp77651wmb;
            Tue, 30 Aug 2016 16:45:39 -0700 (PDT)
    X-Received: by 10.237.49.5 with SMTP id 5mr7551246qtg.136.1472600739826;
            Tue, 30 Aug 2016 16:45:39 -0700 (PDT)
    Return-Path: <myname@mydomain.com.br>
    Received: from a2nlsmtp01-01.prod.iad2.secureserver.net (a2nlsmtp01-01.prod.iad2.secureserver.net. &#91;198.71.224.24&#93;)
            by mx.google.com with ESMTPS id v68si29494071qkd.230.2016.08.30.16.45.39
            for <myname@gmail.com>
            (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
            Tue, 30 Aug 2016 16:45:39 -0700 (PDT)
    Received-SPF: pass (google.com: domain of [EMAIL]myname@mydomain.com.br[/EMAIL] designates 198.71.224.24 as permitted sender) client-ip=198.71.224.24;
    Authentication-Results: mx.google.com;
           dkim=temperror (no key for signature) header.i=@mydomain.com.br;
           spf=pass (google.com: domain of [EMAIL]myname@mydomain.com.br[/EMAIL] designates 198.71.224.24 as permitted sender) smtp.mailfrom=myname@mydomain.com.br
    Received: from a2plcpnl0318.prod.iad2.secureserver.net (&#91;198.71.230.75&#93;)
        by : HOSTING RELAY : with SMTP
        id eshqbDcoZJZqHeshqbcsf3; Tue, 30 Aug 2016 16:44:38 -0700
    DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
        d=mydomain.com.br; s=default; h=Content-Type:MIME-Version:Message-ID:Date:
        Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
        Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
        :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:
        List-Subscribe:List-Post:List-Owner:List-Archive;
        bh=nBZTk+lhWpdoyEl6pLCDMnDujWHMKUz8gin/XZbHEJE=; b=AQ9YzfiQ/dgLR+Bi1VuHhbZVER
        Lcz3BcwvNRRvAf9F9ufOYU1XZb1SIjpIP9b5Zb48nI5nAYgaON4eN5Q00bZ4y71NzyvsdgFragSWJ
        OAba985mGzn3qJaupyXqBfSscAGRg6YLA98DbahpQmA3ukPUOdLEeJSO+rCLK+eu5PrUzud0BFW5S
        tGi3muz4AFatNC5BY50r6fve8Hvyy3eqY0t8OKPaAM/tCPlSiNhjvBn1IWpZd7Q2CTv0zKIIIOWvJ
        CmQJTtl7ff7fOve/DR384lV/BEeHha1Lx5m38avz33WpghScoTfbsZuJuuCJmh4ZjW8BHW2tIMY7L
        8YHC8l+g==;
    Received: from &#91;201.6.229.48&#93; (port=29434 helo=mydomain)
        by a2plcpnl0318.prod.iad2.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
        (Exim 4.87)
        (envelope-from <myname@mydomain.com.br>)
        id 1beshq-002YeO-GQ
        for [EMAIL]myname@gmail.com[/EMAIL]; Tue, 30 Aug 2016 16:44:38 -0700
    From: "My Name" <myname@mydomain.com.br>
    To: <myname@gmail.com>
    Subject: teste
    Date: Tue, 30 Aug 2016 20:44:33 -0300
    Message-ID: <000a01d20318$7ae08a80$70a19f80$@mydomain.com.br>
    MIME-Version: 1.0
    Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000B_01D202FF.55957560"
    X-Mailer: Microsoft Outlook 16.0
    Thread-Index: AdIDGGS/LAGTo/N2TLG6tOnhZ9HIuw==
    Content-Language: pt-br
    X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
    X-AntiAbuse: Primary Hostname - a2plcpnl0318.prod.iad2.secureserver.net
    X-AntiAbuse: Original Domain - gmail.com
    X-AntiAbuse: Originator/Caller UID/GID - &#91;47 12&#93; / &#91;47 12&#93;
    X-AntiAbuse: Sender Address Domain - mydomain.com.br
    X-Get-Message-Sender-Via: a2plcpnl0318.prod.iad2.secureserver.net: authenticated_id: [EMAIL]myname@mydomain.com.br[/EMAIL]
    X-Authenticated-Sender: a2plcpnl0318.prod.iad2.secureserver.net: [EMAIL]myname@mydomain.com.br[/EMAIL]
    X-Source:
    X-Source-Args:
    X-Source-Dir:
    X-CMAE-Envelope: MS4wfG6Z1lGtilMZzhhAtJL80hKn0/FC2y3ut3JvICA4B4f1UaTJSkCcgtRy/Rp8cU0Q2hvl+LMYwxOxdA2EtU1VLFZaZs2frlWnMIAd4uzFU3dqURR58z+P
    2ZuPHJcJ0qrxM1aT/sd9DiefafuqQTKhGmrYi++nQX6z4JZaU2sz0IUnB9hTS75FArtKl/GHlTQUh3r7Iu4wjfs/P87sR5VUTOZXp9SlPwxydqFRuK6SQz3R
    
    Sending a domain hosted e-mail using webmail:

    Code:
    Delivered-To: [EMAIL]myname@gmail.com[/EMAIL]
    Received: by 10.28.1.68 with SMTP id 65csp105619wmb;
            Tue, 30 Aug 2016 18:31:38 -0700 (PDT)
    X-Received: by 10.200.47.253 with SMTP id m58mr8167216qta.60.1472607098753;
            Tue, 30 Aug 2016 18:31:38 -0700 (PDT)
    Return-Path: <myname@mydomain.com.br>
    Received: from a2nlsmtp01-01.prod.iad2.secureserver.net (a2nlsmtp01-01.prod.iad2.secureserver.net. &#91;198.71.224.24&#93;)
            by mx.google.com with ESMTPS id o129si29955275qka.188.2016.08.30.18.31.38
            for <myname@gmail.com>
            (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
            Tue, 30 Aug 2016 18:31:38 -0700 (PDT)
    Received-SPF: pass (google.com: domain of [EMAIL]myname@mydomain.com.br[/EMAIL] designates 198.71.224.24 as permitted sender) client-ip=198.71.224.24;
    Authentication-Results: mx.google.com;
           dkim=temperror (no key for signature) header.i=@mydomain.com.br;
           spf=pass (google.com: domain of [EMAIL]myname@mydomain.com.br[/EMAIL] designates 198.71.224.24 as permitted sender) smtp.mailfrom=myname@mydomain.com.br
    Received: from a2plcpnl0318.prod.iad2.secureserver.net (&#91;198.71.230.75&#93;)
        by : HOSTING RELAY : with SMTP
        id euMPbEYQvJZqHeuMPbdYoK; Tue, 30 Aug 2016 18:30:37 -0700
    DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
        d=mydomain.com.br; s=default; h=Message-ID:Subject:To:From:Date:
        Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To:Cc:
        Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
        Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
        List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
        bh=IZzGk5hdbwv1XsfTE2Dngp1hMDfBwbnO3RaSFfeDt+k=; b=mnx4BW8mgchGZTMcPVQBuxHD8
        6MnPkuDilganZKzPs+DqU3tXBZR0veYlS2GTUDXEb2zVqrd9JbAR3nAK3pn3L8exFZHCOrOlB5OnL
        YeJ8WZrcss+RcJRNNxaTlyXpMOtYI2/E+bH9Ch7xqZ1oGODQwaaxC/p1mYRsMh/uh8c+3C3Uol9rn
        TtwJ2zCgTayNquFI8h4Q3TWm1NtofoK8KeTuXS7Mb80/SOqJZL1NK23y0Cyi4rWudCq4e5mEjT4df
        +84xnpVzOS+8lx4nP+Vm94YJ2iTIaWVsmIdGcaiFRy43esZWy+0l0r2tbWXdy77TajwB5V6Eylwbf
        f4w8eD5zA==;
    Received: from &#91;127.0.0.1&#93; (port=55665 helo=a2plcpnl0318.prod.iad2.secureserver.net)
        by a2plcpnl0318.prod.iad2.secureserver.net with esmtpa (Exim 4.87)
        (envelope-from <myname@mydomain.com.br>)
        id 1beuMO-003Es2-Uv
        for [EMAIL]myname@gmail.com[/EMAIL]; Tue, 30 Aug 2016 18:30:36 -0700
    MIME-Version: 1.0
    Content-Type: text/plain; charset=US-ASCII;
    format=flowed
    Content-Transfer-Encoding: 7bit
    Date: Tue, 30 Aug 2016 19:30:31 -0600
    From: [EMAIL]myname@mydomain.com.br[/EMAIL]
    To: [EMAIL]myname@gmail.com[/EMAIL]
    Subject: teste
    Message-ID: <9716802bf2952b2b63de5025b7c7dc4b@mydomain.com.br>
    X-Sender: [EMAIL]myname@mydomain.com.br[/EMAIL]
    User-Agent: Roundcube Webmail/1.1.4
    X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
    X-AntiAbuse: Primary Hostname - a2plcpnl0318.prod.iad2.secureserver.net
    X-AntiAbuse: Original Domain - gmail.com
    X-AntiAbuse: Originator/Caller UID/GID - &#91;47 12&#93; / &#91;47 12&#93;
    X-AntiAbuse: Sender Address Domain - mydomain.com.br
    X-Get-Message-Sender-Via: a2plcpnl0318.prod.iad2.secureserver.net: authenticated_id: [EMAIL]myname@mydomain.com.br[/EMAIL]
    X-Authenticated-Sender: a2plcpnl0318.prod.iad2.secureserver.net: [EMAIL]myname@mydomain.com.br[/EMAIL]
    X-Source:
    X-Source-Args:
    X-Source-Dir:
    X-CMAE-Envelope: MS4wfDqBEi1RQ/epl5GfKfjsrrjOqBYOqv+acAM6PhcX5o0lUueftTdID3Ie+sPE4phK/IHwiT1JmWBEhncnsGbLyKpJe3QC9R+2mNvO3fx5pe8QYIAnKtM2
    3wmLIBISoqpU9NsFNWeLQzjIYM5B2uvu0HsAU9ypTvB8srWoiKhdH2HNMHFhadNrrndleHSotGcSBOQxfbKoFupWeOQA9spv2/rIiIdPLUBB/MOkt2GTAyod
    
    Sending an Outlook.com e-mail using Outlook client:

    Code:
    Received: (qmail 16096 invoked by uid 30297); 31 Aug 2016 00:07:40 -0000
    Received: from unknown (HELO sg2plibsmtp01-1.prod.sin2.secureserver.net) (&#91;182.50.144.33&#93;) (envelope-sender <myname@outlook.com>) by sg2plsmtp19-01.prod.sin2.secureserver.net (qmail-1.03) with SMTP for <myname@mydomain.com.br>; 31 Aug 2016 00:07:40 -0000
    Received: from BAY004-OMC3S23.hotmail.com (&#91;65.54.190.161&#93;) by sg2plibsmtp01-1.prod.sin2.secureserver.net with bizsmtp id dc7e1t00N3VNx5501c7fLf; Tue, 30 Aug 2016 17:07:40 -0700
    Received: from BAY407-EAS31 (&#91;65.54.190.188&#93;) by BAY004-OMC3S23.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 30 Aug 2016 17:07:38 -0700
    X-TMN: &#91;cOoPN7IynkZ9ZdEQViDflzCLNqpsRcjT&#93;
    X-Originating-Email: &#91;myname@outlook.com&#93;
    Message-ID: <BAY407-EAS31F6B95784696885F0B13088E30@phx.gbl>
    Return-Path: [EMAIL]myname@outlook.com[/EMAIL]
    From: My Name <myname@outlook.com>
    To: <myname@mydomain.com.br>
    Subject: teste
    Date: Tue, 30 Aug 2016 21:07:39 -0300
    MIME-Version: 1.0
    Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01D20302.8ABD10B0"
    X-Mailer: Microsoft Outlook 16.0
    Thread-Index: AdIDG673bgm42/dWTY2aI+e3WxTTJQ==
    Content-Language: pt-br
    X-OriginalArrivalTime: 31 Aug 2016 00:07:38.0184 (UTC) FILETIME=&#91;AEFAD480:01D2031B&#93;
    X-Nonspam: None
    
    
     
    #1 Tiago Figueiredo, Aug 30, 2016
    Last edited by a moderator: Aug 31, 2016
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello,

    The information is included by the email client (including webmail applications) you are using to send the email. A client must send it's own domain in the Helo/EHLO command per RFC requirements. You may need to consider using a VPN for email purposes to avoid revealing the source IP of the emails, or look for an alternative email client that doesn't add your IP address to the header.

    Thank you.
     
  3. Tiago Figueiredo

    Tiago Figueiredo Registered

    Joined:
    Aug 30, 2016
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brazil
    cPanel Access Level:
    Website Owner
    Hi Michael,

    Thanks for your reply.

    It makes perfect sense that the client must send it's own IP to the mail server, but - still - what doesn't make much sense to me is why the mailserver is forwarding it onwards instead of resending the e-mail with the hosting mailserver's source IP, just as it happens when using a free account such as Outlook.com and Gmail.com with an e-mail client like Outlook.

    Are you saying that the former behaviour is cPanel's standard behaviour for hosted e-mail services?
     
  4. Tiago Figueiredo

    Tiago Figueiredo Registered

    Joined:
    Aug 30, 2016
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brazil
    cPanel Access Level:
    Website Owner
    Well,

    After trying a new hosting service, I can see now that it does indeed seem to be standard practice to reveal ISPs IPs.

    The new provider's e-mails also reveal my home IP, but at least e-mails arrive, so whatever the cause of the failure with the previous host was, it was obviously nothing to do with an IP block, as both Microsoft and their partner hosting company told me. Perhaps some mailserver problem with SMTP authentication as Spamhaus hinted at, though server-side since my settings were correct and even webmail didn't work, who knows. On the new provider's e-mails I did notice an "(Authenticated sender: myemail@mydomain.net)" line that didn't appear in my previous emails.

    Whether that was the problem or not, it's no longer my problem.

    Thanks anyway.
     
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Yes, it's likely unrelated to the inclusion of your own IP address, as it's uncommon to see that as the culprit for SPAM filtering. I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.

    Thank you.
     
  6. Tiago Figueiredo

    Tiago Figueiredo Registered

    Joined:
    Aug 30, 2016
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Brazil
    cPanel Access Level:
    Website Owner
    Well, that was the response I initially got from the Outlook Delivery Support team, that the block was due to my Source IP address being listed on the PBL and, since I'm not really tech-savvy, I chose to give them credit. Each to its own... My business is visual, not IT.

    A Spamhaus technician did say that should only be a problem if there was a SMTP Authentication problem, but he argued it was certainly with my client so I discarded it, since webmail was also not getting through and my host provider's support staff also aknowledged that 90% of all e-mails sent from cPanel e-mail accounts are being blocked by Microsoft servers (initially they said it was due to other users practicing spam, which would only make sense if their server was listed). One member of staff even said that the whole support team are hating cPanel because of all the complaints they are getting... Easier to blame to the tool, other users or Microsoft, than looking in the mirror I guess. Especially if your're selling additional products as a solution.

    Oh well... Time to move on... Once again...

    Thanks anyway and sorry for wasting your time.
     
    #7 Tiago Figueiredo, Sep 1, 2016
    Last edited: Sep 1, 2016
Loading...

Share This Page