Search results

Agree... running it on two laptops now - will probably replace OneCare on other systems as time goes by (and MS isn't selling OneCare anymore)

Happy Birthday Stephen

Sorry... just being a smart-a$$ Actually, it often seems people assume this forum is how to contact technical support. From a technical persepective, removing the potentially malicous file from a shared enviroment would (should) be the number one proirity - if others have been experiencing...

Uhmmm... submit a ticket????

other than the old-school method of an invisible frame, that's about all I can think of

You got that right brother!

Hotmail is a pain-in-the-a$$ .... I forward a copy of all my JH mail to a LiveMail hosted email system and for some reason again last week the email server at JH was marked as a spammer and all email was rejected, a few hours later, through no effort of mine - everything was working fine again...

Forum spam yet again

Well I'll be damned... confirmed, removal usedefaultusercredentials did the trick. Merci!

Yes, directly from development server through VS2008 gives the exact same error. Correct. Nope, other tested mail server needs authentication too and was not connect to it anywhere at the time. Mail3 I believe. Thanks for helping me think through this, I'm not a .Net-spert and...

As an FYI, sending using localhost works fine on the server in code-behind - just trying to avoid being market as spam with no rDNS.

True or False in the code-behind or the web.config makes no difference. Same error: Mailbox name not allowed. The server response was: sorry, that domain isn't allowed to be relayed thru this MTA (#5.7.1)

Works fine manually adding the credentials in the codebehind. It does seem a bit suspicious if it works on another server. Yup, strange situation. Oh, trust me, multiple hours trying to find a solution. Web.Config coding seems fine compared to anything I can find. Yup, had taken...

Oh, and adding Smtp.Credentials and Smtp.Host directly to the code behind seems to work fine. :boom: :hurt:

I was going back and forth on that one too but it doesn't make a difference... same error. Haven't tried that yet but will give it a shot. Here's the kicker I found this morning though, using the same script with a different host that I use too works fine (of course changing the...

This is bugging the hell out of me. I am trying to send an email using System.Net.Mail It sends fine to email accounts hosted @ jodohost but errors when sending to anything outside the jodo network. The error I get is: Mailbox name not allowed. The server response was: sorry, that domain isn't...

Hit and miss it looks like - one site that I turned it on a few days back works fine, one site that has been on for a long time missed a bunch of stats and is now throwing errors, another that I added yesterday has yet to proces any stats. Non-mission critical for me so I'm just waiting it out.

LOL - misery loves company! ;-) Cheers Joe Geo

Support did get if working so that is fine - however, force SSL isn't enabling through control panel (which it really hasn't functioned properly for the last couple of SSL installs I've done both pre/post upgrade) Thanks G

FYI - I'm having the same issue with a new Rapid-SSL certificate. Once installed, it is still trying to use the 'temp cert' generated in the process. I have a ticket in on this already this AM.