The reason I think it is Windstream is when I tried to email their support department to inquire about the problem I could not send an email to their support department either as my email was sent back with the same errors I get when I try and email my customer. I believe it is a problem on Windstreams servers but as usual everyone is pointing fingers to everyone else. The following address(es) time not reached for any host after a long failure period Host : 421 Service not available:Ī message that you sent could not be delivered to one or more of its recipients. The following address(es) error from remote mail server after initial connection: I get these two errors in the returned email Ī message that you sent could not be delivered to one or more of its recipients. I usually get a couple different messages none of them are saying that the email is rejected for spam or anything like that it just will not connect to their mail servers. for their email and I can send to them with no problems. It is only Windstream that is kicking my email back as I have lots of other clients using Comcast, MSN, AOL, etc. I can send him mail if I use my Comcast mail or Yahoo mail. I should probably note that the problem only occurs on my computer using Outlook and my mail accounts from lunarpages. I have been emailing him almost daily over the past 6 months and now I can no longer respond to his email nor can I send any email to anyone with a account. I also have a website hosted by lunarpages and these are the email accounts I use 99.5% of the time.Ībout two weeks ago I started having problems sending email to a very good customer. I use Comcast as my ISP but I very rarily use their email services or their webmail. All have virusware protection and only one of them uses Outlook 2003 for e-mail (Mine) the other two use webmail. I have several PC's setup on a wireless N network using a Linksys wireless N router.Īll the PC's are running Windows XP Pro service pack3. I am not a complete idiot but I am far from being an expert on email issues.
0 kommentar(er)
