New answers tagged

1

Such emails are supposed to be sent directly from the user's email client to an SMTP server you control, on port 587 (submission) with user authentication (and STARTTLS). Port 25 is inappropriate for this, for the reasons you've already run into and others.


0

This one is hard to answer as there is any number of ways the email count have been sent. The most common ways are... Unsanitized inputs through your website - This happens where you don't sanitize your user inputs and a user is able to pass PHP code directly into your application through your web forms. All user inputs should be sanitized and limited to ...


0

In many instances even though the error message returned states that Spamhaus was the reason for the block this is a template error message and it could be from any number of blacklists. If you do a blacklist search using http://mxtoolbox.com/ for both the domain and for the IP address that will search all blacklists to see if you are blacklisted anywhere. ...


0

The issue here would appear as though the IP for your shared server has been blacklisted by a range of other blacklist companies, and/or the receiving mail servers still have the Spamhaus blacklist in their cache. Many companies with email servers, in order to speed up email handling times, and decrease overhead, cache the blacklist records from Spamhaus ...


0

I realise that this is a 2015 question and that it has probably been resolved internally already but for others who encounter the same issue in the future... Cox does reply back even if the decision is to not unblock. Sometimes unblocking can take a while to decide, especially if there has been a large number of unblock requests made at the same time by ...


1

This would appear to be due to the emails being detected being sent as a relaay instead of from a correctly configured SMTP server. The best option is to configure your PHP.ini file to use SMTP and to use your gmail server for SMTP and then use the PHP mail() function to avoid this error in the future.


0

I am going to make an assumption here that the hosting panel is either cPanel or Plex. In either case the passwords are stored in the shadow file which unless your host has made an unsecured server will not be accessible directly to you. The best option in this case is to reset all passwords and notify your customers of the reset password before the change ...


0

Unfortunately you are unable to alias the MX records in that manner. While all the domains can target A records to the same server to use the exact same code for all the domains each domains MX record would have to individually be pointed to the mail server and the mail server would have to be configured to work with each domain and define the mailboxes for ...


1

Looks like someone is spoofing your ourmailer@gmail.com address. This line shows a spam relay server: Diagnostic-Code: smtp;554 resimta-ch2-11v.sys.comcast.net comcast 23.227.123.207 found on one or more DNSBLs, see http://postmaster.comcast.net/smtp-error-codes.php#BL000010 This line shows that the original e-mail lacked an rfc822 message ID: Message-...


0

Google not only depends on third party blacklists but also maintains their own internal blacklist. To remove your domain / IP from gmails blacklist you can use the form located at https://support.google.com/mail/contact/msgdelivery to report the issue and get it dealt with but Google may not automatically remove the blacklist entry depending on what Google ...


1

Based on the error message it would appear as though your sending the email through a Google email server. Google requires SSL/TLS and authentication on all SMTP connections. Your code indicates that you are authenticating but that you aren't specifying the SMTP username and password.


0

After SPRBRN confirmed my suspicion that requesting to get off of Blacklists was a losing game, I came up with a few other ideas to reduce my emails from going into spam. I first noticed that my DNS TXT record for my SPF had a bad syntax, something that Google warns can create a spam designation. So I fixed it using easySPF wizard. Rather than just ...



Top 50 recent answers are included