MTA’s poor reputation

emailemail-serversmtp

Rather randomly only just started happening but when sending emails to certain people my emails are getting bounced back. I've set up domain keys and SPF records. I am with Just Host using an email program from their main control pannel. Thought purchasing a dedicated IP would solve it… i bought one and it hasnt, still comes up!! Have a feeling the email receipents are still reconising somthing to do with being on just host? The main server interface IP 173.236.44.98 can't be removed from the SPF… Only got a new IP yesterday so do i need to give it more time?

Full error message:

SMTP error from remote mail server after initial connection:

host in.mx.ifl.net [217.181.2.37]: 554-in5.mx.ifl.net
554 Your access to this mail system has been rejected due to the sending MTA's poor reputation.
If you believe that this failure is in error, please contact the intended recipient via alternate means.

Best Answer

Getting a new IP address is what spammers do. Cleaning up their act is what responsible sysadmins do.

Plugging your IP address into a Google search turns up links from several places indicating that it has hosted various types of malware in the past:

http://malc0de.com/database/index.php?search=173.236.44.98&IP=on
http://spam.bubble.ro/4225-assistance-needed/ (Click on show all headers)
http://lists.clean-mx.com/pipermail/viruswatch/20111116/028730.html ( lulibdem.com again)
http://support.clean-mx.de/clean-mx/viruses.php?ip=173.236.44.98&sort=ip%20desc

You are listed at Spamcop, LashBack and BackScatterer.
SenderBase and SenderScore both think your reputation is poor.

Related Solutions

Linux – How to correct Postfix’ ‘Relay Access Denied’

TLS just enables encryption on the smtp session and doesn't directly affect whether or not Postfix will be allowed to relay a message.

The relaying denied message occurs because the smtpd_recipient_restrictions rules was not matched. One of those conditions must be fulfilled to allow the message to go through:

smtpd_recipient_restrictions =
    permit_sasl_authenticated
    check_recipient_access hash:/etc/postfix/filtered_domains
    permit_mynetworks
    reject_unauth_destination

To explain those rules:

permit_sasl_authenticated

permits authenticated senders through SASL. This will be necessary to authenticate users outside of your network which are normally blocked.

check_recipient_access

This will cause postfix to look in /etc/postfix/filtered_domains for rules based on the recipient address. (Judging by the file name on the file name, it is probably just blocking specific domains... Check to see if gmail.com is listed in there?)

permit_mynetworks

This will permit hosts by IP address that match IP ranges specified in $mynetworks. In the main.cf you posted, $mynetworks was set to 127.0.0.1, so it will only relay emails generated by the server itself.

Based on that configuration, your mail client will need to use SMTP Authentication before being allowed to relay messages. I'm not sure what database SASL is using. That is specified in /usr/lib/sasl2/smtpd.conf Presumably it also uses the same database as your virtual mailboxes, so you should be able enable SMTP authentication in your mail client and be all set.

554 – Sending MTA’s poor reputation

Your IP is blacklisted. Check here and here for more information.

Best Answer

Related Solutions

Linux – How to correct Postfix’ ‘Relay Access Denied’

554 – Sending MTA’s poor reputation

Related Topic