Postfix/Spamhaus PBL list

Discussion in 'Server Operation' started by Xase, Sep 20, 2018.

  1. Xase

    Xase Member

    I'm not sure how to exactly fix this as I've looked at the Spamhaus PBL fixes, and most seem to be implemented by the ISPConfig installer setup.
    I am being sent to spam while sending to Gmail addresses and straight out being blocked from outlook's system.
    I did nothing more configuration wise other than following the Debian Cluster setup and Perfect ubuntu apache server guides.

    Code:
    This is the mail system at host miyagi.gethosting.today.
    
    I'm sorry to have to inform you that your message could not
    be delivered to one or more recipients. It's attached below.
    
    For further assistance, please send mail to postmaster.
    
    If you do so, please include this problem report. You can
    delete your own text from the attached returned message.
    
                       The mail system
    
    <[email protected]>: host
        outlook-com.olc.protection.outlook.com[104.47.44.33] said: 550 5.7.1 Client
        host [174.105.101.49] blocked using Spamhaus. To request removal from this
        list see http://www.spamhaus.org/lookup.lasso (S3130).
        [SN1NAM04FT014.eop-NAM04.prod.protection.outlook.com] (in reply to MAIL
        FROM command)
    Reporting-MTA: dns; miyagi.gethosting.today
    X-Postfix-Queue-ID: 0FAC115C04C5
    X-Postfix-Sender: rfc822; [email protected]
    Arrival-Date: Thu, 20 Sep 2018 10:05:53 -0400 (EDT)
    
    Final-Recipient: rfc822; [email protected]
    Original-Recipient: rfc822;[email protected]
    Action: failed
    Status: 5.7.1
    Remote-MTA: dns; outlook-com.olc.protection.outlook.com
    Diagnostic-Code: smtp; 550 5.7.1 Client host [174.105.101.49] blocked using
        Spamhaus. To request removal from this list see
        http://www.spamhaus.org/lookup.lasso (S3130).
        [SN1NAM04FT014.eop-NAM04.prod.protection.outlook.com]
    
    I tried checking the SMTP Auth settings in postfix, but decided not to touch anything as ISPConfig seems to have done most of the dirty work. So I don't understand why this is happening. When I was running one server it worked fine. Could this be because the cluster setup I did?
     
  2. florian030

    florian030 ISPConfig Developer ISPConfig Developer

  3. Xase

    Xase Member

    I did read it. I specified in my OP that I had read the PBL list fixes... And they DID NOT resolve anything. You CANNOT be removed from the PBL for the most part. I am accessing round cube from port 80...not 587. I am not sure if that is what I'm supposed to do... But SMTP Auth is failing.
     
  4. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    174.105.101.49 is your server, right? as long as this ip is listed, you can not send mail. roundcube has nothing to with this.
     
  5. Xase

    Xase Member

    It says my mails are being sent to spam because of SMTP Auth failure, ALL or at least MOST residential IPs are on the pbl. It's been listed in the list. I've SUCCESSFULLY sent mail from it before I redid the configuration on the servers. Without being marked as spam. If you actually take a look at the PBL list fixes it CLEARLY states I should be able to still send emails if SMTP Auth is working correctly.


    I WAS sending mail SUCCESSFULLY before. Now I'm not. Spamhaus outlines how to fix it... But i have to check SMTP authentication which I'm not really sure how to do.
     
    Last edited: Sep 22, 2018
  6. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Do Google and Outlook.com know what kind of list the PBL is? And if they do, how can they know whether you SMTP authenticate or not? I find it hard to understand how this PBL list could work.
    You could circumvent this problem with IP in bad range by sending mails via a smarthost. I would guess your Internet Service provider offers a mail host the customers can send their e-mail to for delivery further.
     
  7. Xase

    Xase Member

    Well all I know is Gmail didn't mark it as spam before. So you're saying I can relay it over another mail server? I'm sorry if my caps made me seem pompous or if I came off as such. I'm not trying to accuse you of being wrong. I just don't understand why within a week span, I went from not being marked as spam to being marked as spam.
     
  8. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I tried to fine in Thunderbird where is SMTP Authentication specified. I have in sending e-mail server STARTTLS or SSL or nothing chosable, and STARTTLS is chosen. I do not know if that is SMTP Authentication.
    https://en.wikipedia.org/wiki/Smart_host
    I noticed miyagi does not have MX record, and reverse dns does not resolve to miyagi name. Looks like it does not have SPF record either. So even without that PBL list I suspect other mail servers would not accept mails.
     
  9. Xase

    Xase Member


    [​IMG]

    I haven't added anything except what DNS Wizard added, and the NS and A record for ns2.afraid.org, though that A record may be moot... Not really sure quite how it all works yet. What do you mean by ReverseDNS?

    Thanks for your help thus far. I'm starting to suspect this may have to do with the cluster setup... I keep getting messages like
    Code:
    CONFIGURATION ERROR
    
    2018-09-21 14:28 : 
    zone childrenofatom.church/IN: NS 'ns2.afraid.org.childrenofatom.church' has no address records (A or AAAA)
    zone childrenofatom.church/IN: not loaded due to errors.
    
    Which isn't the case. I had forgot the period originally, but have since set it earlier, and it doesn't seem like DNS changes are reciprocating properly. I.E. proper information is there... but it's not being reported properly.
     
  10. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I did not understand gethosting.today is your domain. I assumed it was the service provider.
    With that knowledge, gethosting.today does have MX record and SPF.
    That
    'ns2.afraid.org.childrenofatom.church'
    indeed probably was because you had left out the dot character after ns2.afraid.org in childrenofatom.chuch DNS settings. DNS info may take 48 hours to propate all over the world. It is best to check the server you set up, in this case miyagi and ns.afraid.org to see they have the correct information. Use command host and give IP number of the name server to be tested. When those servers show correct information, you have done all you can do, then it is just a matter of waiting other name servers to update.
     
  11. Taleman

    Taleman Well-Known Member HowtoForge Supporter

  12. Xase

    Xase Member

    @Taleman that first resource I don't think so. I will read these and see what I can do. I have read about ptr records before. But not well enough yet. Thanks for the resources.
     

Share This Page