One wrong email address has stopped me from sending emails! HALP!

[moondancerjen]

Ok, so I sent a mailing out yesterday to about 1,000 contacts.  It got through about 39 of those contacts and then it hit an SMTP error 572 saying the email address was rejected: host name is unknown.  Now, every time I run the civimail cron job I'm getting the following error:
Sorry. A non-recoverable error has occurred.

Invalid response code received from SMTP (outbound mail) server while attempting to send email. This is often caused by a misconfiguration in the CiviCRM Outbound Email settings. Please verify the settings at Administer CiviCRM >> Global Settings >> Outbound Email (SMTP).

I've talked to my hosting company and they are running into that 572 error every time I run that cron job even though I've removed the email address from the mailing queue and the contact from the group for the mailing list, but it keeps on happening!  After troubleshooting with them for most of the day I'm confident that I have to do something on the CiviCRM end to get past this error.

I've set up different mailings and tried to run them, but it is stuck! 

Does anyone know how to stop this cycle?  I just want to be able to skip that email and go on to the rest of the ones waiting.

I'm also trying to cancel the mailing that is marked running, but isn't really running because its stuck on the 39th person and that isn't working either.  I also tried deleting the mailing, which worked, but it isn't helping my cron job problem.  How does the cron work?  How can I say stop running this mailing and move to the others?  Or keep running this mailing but skip this person?

Anything you can give me will help.  Thanks!
Jen

[Donald Lobo]

what version of civicrm? I suspect an earlier version of civicrm v2.0

two options:

1. upgrade to v2.0.5 (no db changes, just code changes)

2. read this forum post

http://forum.civicrm.org/index.php/topic,3350.0.html

and apply the following patch

http://fisheye.civicrm.org/changelog/CiviCRM/branches/v2.0?cs=14465

lobo

[moondancerjen]

We are using 2.0.2 but I'll try upgrading to 2.0.5 and see if that helps.  thanks