True, I'll give it a go. Perhaps they can help track it down. On Tue, Oct 7, 2014 at 6:38 PM, John Cook <[email protected]> wrote:
> Well check to see if there was an update around the time it started, if so > it can't hurt to start a ticket, they are a free resource that might uncover > something. > > > John W. Cook > Director of Network Operations > Partnership for Strong Families > > Steve Ens <[email protected]> wrote: > > > I turned off the filtering altogether. (Animikisee is a sister company > of ours which I also administer. > > > On Tue, Oct 7, 2014 at 6:29 PM, John Cook <[email protected]> wrote: > >> That's why I asked, Viper would occasionally block senders on our install. >> If it's a business partner you may want to have them create an explicit >> allow rule to test. >> >> >> John W. Cook >> Director of Network Operations >> Partnership for Strong Families >> >> Steve Ens <[email protected]> wrote: >> >> >> On my side I use Trend Micro. The Animikisee site uses Vipre. >> >> On Tue, Oct 7, 2014 at 6:23 PM, Steve Ens <[email protected]> wrote: >> >>> Looks to be listed on the mailpolice sites. Never heard of those >>> before. I turned off blacklisting on the animikisee.ca site >>> altogether. Still same thing. >>> >>> On Tue, Oct 7, 2014 at 5:56 PM, Micheal Espinola Jr < >>> [email protected]> wrote: >>> >>>> Do your tested results show anything different on this site? >>>> >>>> http://www.blacklistalert.org/ >>>> >>>> -- >>>> Espi >>>> >>>> >>>> On Tue, Oct 7, 2014 at 1:02 PM, Steve Ens <[email protected]> wrote: >>>> >>>>> Yes, already tried that. I can do a MX lookup, but cannot telnet to >>>>> the server. Also getting this in the logs Error Code: 10061, Error >>>>> Message: No connection could be made because the target machine actively >>>>> refused it >>>>> That seems to point to us being blacklisted, but I come up clean on >>>>> the mxtoolbox tests. >>>>> >>>>> On Tue, Oct 7, 2014 at 2:48 PM, Kennedy, Jim < >>>>> [email protected]> wrote: >>>>> >>>>>> What are the domains? Could be bad bounces from spam to >>>>>> non-existent domains Your server can not contact them, so it tried >>>>>> alternates either in dns or per the RFC’s (for example A record of >>>>>> domain.com) and that failed. So it is still trying. >>>>>> >>>>>> >>>>>> >>>>>> Do an MX lookup from your transport server to verify your DNS is >>>>>> working. Then try telnet port 25 from the transport server to that IP to >>>>>> verify connectivity. What do you get? >>>>>> >>>>>> >>>>>> >>>>>> *From:* [email protected] [mailto: >>>>>> [email protected]] *On Behalf Of *Steve Ens >>>>>> *Sent:* Tuesday, October 7, 2014 3:42 PM >>>>>> *To:* [email protected] >>>>>> *Subject:* [Exchange] 421 4.2.1 Unable to connect errors >>>>>> >>>>>> >>>>>> >>>>>> Odd errors in my mail queue. Just started appearing yesterday. Most >>>>>> mail gets sent, but from certain domains I get these errors. "Attempted >>>>>> failover to alternate host, but that did not suceed." Anyone see this >>>>>> before? Exchange 2010 on Windows 2008 R2. >>>>>> >>>>> >>>>> >>>> >>> >> >> ------------------------------ >> >> CONFIDENTIALITY STATEMENT: The information transmitted, or contained or >> attached to or with this Notice is intended only for the person or entity >> to which it is addressed and may contain Protected Health Information >> (PHI), confidential and/or privileged material. Any review, transmission, >> dissemination, or other use of, and taking any action in reliance upon this >> information by persons or entities other than the intended recipient >> without the express written consent of the sender are prohibited. This >> information may be protected by the Health Insurance Portability and >> Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. >> Improper or unauthorized use or disclosure of this information could result >> in civil and/or criminal penalties. >> Consider the environment. Please don't print this e-mail unless you >> really need to. >> > > > ------------------------------ > > CONFIDENTIALITY STATEMENT: The information transmitted, or contained or > attached to or with this Notice is intended only for the person or entity > to which it is addressed and may contain Protected Health Information > (PHI), confidential and/or privileged material. Any review, transmission, > dissemination, or other use of, and taking any action in reliance upon this > information by persons or entities other than the intended recipient > without the express written consent of the sender are prohibited. This > information may be protected by the Health Insurance Portability and > Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. > Improper or unauthorized use or disclosure of this information could result > in civil and/or criminal penalties. > Consider the environment. Please don't print this e-mail unless you really > need to. >
