Answers.Body: <p>This is a bug, covered here on the civibugtracker: </p>
  
  <p><a href="https://issues.civicrm.org/jira/browse/CRM-17163?jql=text%20~%20%22import%20email%20soft%20credit%22" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-17163?jql=text%20~%20%22import%20email%20soft%20credit%22</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-24T09:37:32.930Z
Answers.Text: Thanks for that - I'm not sure it's exactly the same bug, but I suspect it is related (probably the next incarnation of it!), and it gives me somewhere to look
Answers.UserDisplayName: naomi
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-18T13:36:55.897Z
Answers.LastActivityDate: 2015-09-18T13:36:55.897Z
Answers.UserDisplayName: Cullen McGough
Body: <p>I'm trying to import some contributions. Each contribution has a soft credit field which is an email address. I've set the field mapping to Soft Credit / Email / Solicited. All the rows are failing with <code>Invalid email address(doesn't exist) &lt;email&gt; for Soft Credit. Row was skipped</code> but there are contacts with those email addresses.</p>
  
Tags: <import><contributions><4.6>
Title: Importing contributions with soft credits fails with spurious email error
ThreadText: # Importing contributions with soft credits fails with spurious email error
  
  (Asked by: username_0 on 2015-09-10)
  
  I'm trying to import some contributions. Each contribution has a soft credit field which is an email address. I've set the field mapping to Soft Credit / Email / Solicited. All the rows are failing with `Invalid email address(doesn't exist) <email> for Soft Credit. Row was skipped` but there are contacts with those email addresses.
  
  **Tags:** import, contributions, 4.6
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-09-18. Score: 1 | Accepted answer
  
  This is a bug, covered here on the civibugtracker:
  
  <https://issues.civicrm.org/jira/browse/CRM-17163?jql=text%20~%20%22import%20email%20soft%20credit%22>
  
  > **Comments:**
  > **username_0**: Thanks for that - I'm not sure it's exactly the same bug, but I suspect it is related (probably the next incarnation of it!), and it gives me somewhere to look  
  
  ---
  
  