Unsuccessful - The email could not be sent at this time.

If you are having an issue with iScore Baseball, please post it here and we will try and find solutions so everybody will be aware of them.
Post Reply
squarerhino
Posts: 3
Joined: Sun May 23, 2010 4:56 pm

Unsuccessful - The email could not be sent at this time.

Post by squarerhino » Wed Mar 02, 2011 9:35 am

We have our draft coming up soon, so I have been trying to email Team Stats to the coaches. I have a iPhone 4 with the latest version installed. Tried resetting phone. No luck. Any ideas?
danmcc
Posts: 834
Joined: Thu Oct 22, 2009 5:43 am
Location: Charlotte, NC

Re: Unsuccessful - The email could not be sent at this time.

Post by danmcc » Wed Mar 02, 2011 12:38 pm

That usually indicates no internet service. Were you sending the email to multiple addresses? If so how were they separated by spaces or semi colons? I think that the format is to use spaces, but someone here would need to confirm that.
User avatar
OhioTex
Posts: 5501
Joined: Sun May 10, 2009 6:48 am
Location: Columbus OH

Re: Unsuccessful - The email could not be sent at this time.

Post by OhioTex » Wed Mar 02, 2011 1:26 pm

spaces between email addresses is correct.
User avatar
FTMSupport
Site Admin
Posts: 13193
Joined: Sat Mar 28, 2009 7:25 pm

Re: Unsuccessful - The email could not be sent at this time.

Post by FTMSupport » Wed Mar 02, 2011 2:18 pm

We have noticed some people have tried to enter "contact names" in as the email to field instead of actual email addresses. That does not work - you must enter email addresses. v3.0 is actually approved by Apple today, and it will allow you to select from your contact list as well for the people that have been trying that.
Check out the new iScore Baseball documentation page!
Includes videos and user manual.
http://iscoresports.com/baseball/training.php#docs
squarerhino
Posts: 3
Joined: Sun May 23, 2010 4:56 pm

Re: Unsuccessful - The email could not be sent at this time.

Post by squarerhino » Wed Mar 02, 2011 7:49 pm

Not sure what the original problem was. But, update v3.0 has fixed it!
Thanks.
Post Reply