Skip to main content
Solved

FME 2017.0 Emailer issue: C125117 (PR76958)

  • June 2, 2017
  • 4 replies
  • 21 views

takashi
Celebrity

Hi @NatalieAtSafe,

From this Q&A;: SMTP error

The issue has been filed as C125117 (PR76958) and I was notified that it has been fixed in FME 2017.1 Beta already. I confirmed that the original issue has been resolved in FME 2017.1 Beta with Python 3.5, but the fixed Emailer newly causes this error when running with Python 2.7. I think the error apparently indicates that the implementation of the Emailer in FME 2017.1 Beta doesn't conform to Python 2.7 specifications.

Emailer: <type 'exceptions.TypeError'>: character mapping must return integer, None or unicode 

Nearly two months have passed since I reported the error above, but it has not been resolved yet in the latest Beta build 17498.
Could you please check the current status of the PR?

Best answer by stephenwu

Thanks for finding and checking in on this @takashi! A fix has been submitted and should be available in the FME 2017.1 Beta build 17503.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

fmelizard
Safer
Forum|alt.badge.img+21
  • Safer
  • June 4, 2017

I've also escalated to Swu


Forum|alt.badge.img
  • Best Answer
  • June 7, 2017

Thanks for finding and checking in on this @takashi! A fix has been submitted and should be available in the FME 2017.1 Beta build 17503.


takashi
Celebrity
  • Author
  • June 7, 2017

Thanks for finding and checking in on this @takashi! A fix has been submitted and should be available in the FME 2017.1 Beta build 17503.

Thanks for your efforts to investigate and fix the issue, @stephenwu.

 


takashi
Celebrity
  • Author
  • June 8, 2017

Thanks for finding and checking in on this @takashi! A fix has been submitted and should be available in the FME 2017.1 Beta build 17503.

I confirmed that the issue has been resolved in FME 2017.1 Beta build 17503.

 

Thanks again.