RCPT , PTR , SMTP and Postfix suddenly stop sending mails

Discussion in 'Server Operation' started by mahmodsob, Feb 25, 2016.

  1. mahmodsob

    mahmodsob New Member

    Help me ASAP... i'm having a server and it was working perfectly till the ISP changed our "static ip" and generated new PTR record then it stopped sending any email again to any domains not hosted on our server.

    now while sending any mail it always says "mail for gmail.com loops back to myself" OR "RCPT not accepted from server: 554 5.7.1 : Relay access denied"

    i tried to test it on mxtoolbox.com and the result was "SMTP Valid Hostname -- Reverse DNS is not a valid Hostname" AND "554 5.7.1 <[email protected]>: Relay access denied [984 ms]" but although it says "SMTP Banner Check -- OK Reverse DNS matches SMTP Banner"

    i tried to test it on https://www.wormly.com/test_smtp_server and the result was "ERROR: RCPT not accepted from server: 554 5.7.1 : Relay access denied"

    i tried to test port 25 AND 587 on the IP itself using telnet and MXtoolbox.com and it was working correctly and the result was " 220 server1.rms4design.info ESMTP Postfix (Ubuntu) [1094 ms]"

    IP: 197.162.155.1
    Main Domain: rms4design.info

    i have contacted with the ISP technical support and it says that everything is ok in both IP and PTR

    so what's wrong !! what's going on!! how to solve that ,,,

    Note : Attached some print screens
     

    Attached Files:

  2. mahmodsob

    mahmodsob New Member

    any help !!
     
  3. ztk.me

    ztk.me Active Member

    If your IP changed, check your nameservers, subnetmask and gateway if those settings are still valid and working.

    How does this work together?
    and it was working correctly and the result was " 220 server1.rms4design.info ESMTP Postfix (Ubuntu) [1094 ms]"
    IP: 197.162.155.1
    Main Domain: rms4design.info

    On one of your screens it says "rms4design.info" is not a valid hostname - well it hasn't a hostname at all, just domain - server1 would be the hostname I'd interpret the warning.

    So make sure your IP, PTR for that IP nameserver-entry and postfix-greeting are all the same ( server1....info )
     

Share This Page