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.

     The client mail server is totally wedged and I can not figure out why so I am restoring it from backups.  I have saved the spool prior so no mail will be lost.

     Last night I became aware that our outbound mail server mail.eskimo.com had been added to the SORBS real time black hole list.

     I received no warnings or notifications or spam complaints prior so I had no reason to believe we had an active spammer.

     Afterwards, I was able to locate enough information in their database to identify the sender and to determine his machine was infected rather than a case of compromised password.  I have disabled the account pending some confirmation that the customers machine has been cleaned.

     Two carriers I am aware of rely solely on SORBS for spam filtering (an extremely bad practice), those are Yahoo.com and Cox.com.  As a consequence of being on SORBS, more than 7000 messages backed in queue to these two domains.

     In an effort to try to force some of the backlog out I reduced the timeouts so that cox and yahoo were more appropriately hammered, but was unaware there were limits to the allowed parameters (they were NOT documented in the Postfix documentation AND postfix check which is supposed to check for a valid configuration did not complain) but it ended up breaking the outgoing server after I went to bed which by this time was about 6AM.

     I finally figured out there was a problem around 11AM and fixed it.

     I applied to be delisted at SORBS but being a volunteer run organization it does not happen fast and so we are still listed today and Yahoo and Cox are still refusing our e-mail.

     Please understand I have no control over the poor policies at Cox or Yahoo, please contact their support staff regarding your mail not going through to these sites.

     I rarely write or post about things which are not highly relevant to our service here, but I came across this and what he is saying here is so relevant to life in general, I thought it worth sharing: