Outlook (Microshaft) declined to de-list even though the problem was “fixed” the day it occurred.  I guess this is their new way of attacking Linux.

     I already joined JMRP, I tried to join SNDS but they do not send the e-mail they say they will so I can’t complete the sign up process.

Dear Robert Dinse

 

We have completed reviewing the IP(s) you submitted. The following table contains the results of our investigation.

 

Not qualified for mitigation
204.122.16.4; 204.122.16.222
Our investigation has determined that the above IP(s) do not qualify for mitigation.

Please ensure your emails comply with the Outlook.com policies, practices and guidelines found here: http://mail.live.com/mail/policies.aspx.

To have Deliverability Support investigate further, please reply to this email with a detailed description of the problem you are having, including specific error messages, and an agent will contact you.

 

Regardless of the deliverability status, Outlook.com recommends that all senders join two free programs that provide visibility into the Outlook.com traffic on your sending IP(s), the sending IP reputation with Outlook.com and the Outlook.com user complaint rates.

 

Junk Email Reporting program (JMRP) When an Outlook.com user marks an email as “junk”, senders enrolled in this program get a copy of the mail forwarded to the email address of their choice. It allows senders to see which mails are being marked as junk and to identify mail traffic you did not intend to send. To join, please visit http://support.msn.com/eform.aspx?productKey=edfsjmrpp&page=support_home_options_form_byemail&ct=eformts.

 

Smart Network Data Services program (SNDS). This program allows you to monitor the ‘health’ and reputation of your registered IPs by providing data about traffic such as mail volume and complaint rates seen originating from your IPs. To register, please visit http://postmaster.live.com/snds/.

 

There is no silver bullet to maintaining or improving good IP reputation, but these programs help you proactively manage your email eco-system to help better ensure deliverability to Outlook.com users.

 

Thank you,

 

Outlook.com Deliverability Support

     Just an update, I have applied for de-listing of our servers IP address with all of these providers.  I have not heard back from any of them yet.

     We had an issue with a customer whose computer was infected with a virus on February 12th.  That was resolved the same day however in that time the virus tried to send itself to honeypot addresses on the SORBS real-time black hole list and so got us on that list.

     I went through the de-listing process four times and was told by their support people, four times, that we had been de-listed but each time I check they still show us via their web lookup however mxtoolbox showed it clean so just to be safe I decided to move the mail server to a new IP address.

     I also found out barracudanetworks firewall was blocking us based upon that SORBS list entry and they did not find it active so agreed to remove the blacklist.

     Still Yahoo.com, Cox.net, MSN.com, and Hotmail.com still are rejecting our mail with a 450 temporary refused error code and a message that says due to spam complaints our mail is being “temporarily deferred”.

     I have installed SPF, DKIM, and DMARC on our mail server as well as the clamav anti-virus milter to prevent viruses from propagating themselves. I have tested these using public testing facilities.

     Other than wait for whatever database these companies are using to timeout I don’t know what to do since their support people are basically worthless saying that what their spam filtering is based upon is proprietary.  Yea it obviously works really well.  So that’s what’s going on with those domains.

     If you are a customer of one of these companies, Yahoo, Cox, MSN, or Hotmail, please complain directly to their support group.

     The maintenance work on mail.eskimo.com has been completed.

     I have changed the IP address of mail.eskimo.com to 204.122.16.222.  If you have the IP address set numerically in your client please change it to this address.  It is presently also still listening to 204.122.16.4 but this will be discontinued in the future.

     I will be taking mail down for imaging around 4AM 2/26/2020 for approximately one-half hour.

     Finished about an hour ago but forgot to post.

     The mail client server is back online.

     Sorry for the outage this afternoon.  A PHP upgrade broke one of the plugins I used on our WordPress based website.

     If you are using:

WP-Optimize - Clean, Compress, Cache (version 3.0.16)

    On your website, you should remove it as it will break under our current environment.  Also, testing with and without it, it no longer confers ANY improvement in load time, in fact our website loaded slightly faster without it.

     There was another milter I forgot about, the clamav milter for virus scanning and it was that which was broken.  That is now fixed and mail is functioning again.

     We are still on SORBS so mail to Yahoo.com and Cox Cable is still a problem but that is a problem with SORBS ticket system and policy on those to sites relying exclusively on SORBS, neither of which I have any control over.

     Our client mail server is again rejecting mail with a strange try again later message from a milter.  The only milter is dkim so I do not know why it is doing this.  I am in the process of troubleshooting.  I’ve already restored the server from backups and it did operate for several hours before getting wedged again.

     Mail server is restored from backups.

     We are still on the SORBS list, their system lost the ticket I created earlier today and trying to create a new one generated an error, so can’t say how long it will take to get de-listed but this mainly affects Yahoo and Cox addresses.