ISendEmail Obsolete?

I see this from the release notes but would need confirmation if "Obsolete"

• Email

  • TE-14108 - Fixed issue with sending email to users with non-standard email addresses (ex. chris@acme.engineering)

  • TE-16842 - Updated email processing library and added new Api.Version2.ISendEmail API for sending email. Note: Email configuration is now a top-level category in administration.

I agree, i saw this too but nothing related to making it obsolete.

When a new API version is added, the older version is always considered obsolete with the intent it will be removed in the future.  You should be using the V2 API at this point

The new API function is not documented.  SendEmail In-Process API Service only shows the Send function, however when I update my code to use  Telligent.Evolution.Extensibility.Api.Version2 I get an error that ISendEmail does not contain a definition for Send.

The documentation right now is 12.0 and is missing 12.1 items that will be added as soon as we can.  The new API  still has a send but its SendAsync as its now an Async method

Knowing what needs to change and how to change it per release is very valuable. We are nearing the end of our QA cycle and discovered we need to alter a few plugin now to make this change.

Hi Patrick - Was v12.1 rolled out without updated documentation? Where would we normally have found this information? Thanks

We have not yet updated the documentation for 12.1 as of yet.  The addition of the new API was included in the release notes.  The definition outside of the documentation would be available via intellisense or it will be in teh autopmation/widget studio documentation

I should also point out obsolete does not mean non-functional.  It simply means its been replaced with a newer version, the older version remains and is functional and remains that way for at least 2 versions by our current deprecation cycle.  It means no new development should use it and older usages should be updated as soon as feasible.

I believe ISendEmail.Send is non-functional in v12.1.3. We are not receiving any emails from this API and are seeing exceptions thrown while still reciiving OOTB emails from Verint.

We are seeing the following exception when trying to send an email to a valid user in v12.1.3 with ISendEmail.Send (Note, the user in this case received Verint's OOTB new thread email seconds before this):

User is not configured to receive email or is unable to receive email. (An error occurred when attempting to send an email.)

I have verified that the Email API (legacy and new API) will fail with this error when the accessing user does not have manage membership permission (which is required to read the user's private email address when sending email to a user via their ID). When sending email from a job, this is generally not an issue as jobs run as the system account by default, however, any UI-related code would be affected by this issue. This is logged as:

This will be fixed with priority.

I have verified that the Email API (legacy and new API) will fail with this error when the accessing user does not have manage membership permission (which is required to read the user's private email address when sending email to a user via their ID). When sending email from a job, this is generally not an issue as jobs run as the system account by default, however, any UI-related code would be affected by this issue. This is logged as:

This will be fixed with priority.