Botframework-sdk: Sending email addresses to slack causes formatting issue

[mattlanham]

If you include a single email address in your message, and send that to slack, it comes out as [email protected]|[email protected]|[email protected] (3 times with pipes between). I have checked URLs and they seem to act as expected.

I believe slack expects there to be 2 pipes, but not three, so not sure why this is happening, any advice would be appreciated.

[Stevenic]

@mattlanham which version of the SDK are you using, C# or Node? And is your bot going through the Bot Connector Service?

[mattlanham]

I'm using the Node version 1.0.0 and yes it's going through the connector service. @Stevenic

[Stevenic]

We're looking into the issue. I think @tomlm has a repro

[mattlanham]

I'm getting something similar on Skype too, if I ask the user via a dialog to give me their email, it's returning it as <ahref="mailto:[email protected]">[email protected]</a> let me know if you want me to log that as a seperate issue.

[theoriginalkien]

I'm also having the same issue with C# SDK 1.1.0.0

Input in slack: [email protected]
What I received in the SDK: <http://a%40a.com|a%40a.com>

[v-thgratMSGit]

Closing this issue due to age. @mattlanham - please open a new issue if this issue is not fixed and needs further discussion. @Stevenic - reopen if necessary. Thanks!

[JamieREvans]

@Stevenic This is still an issue.

I think this should be automatically formatted / cleaned by the botbuilder, because this will affect all Slack bots.

The issue is as follows:

• Ask a user for an email or url
• User responds with an email or url
• Slack sends an automatically formatted response to the bot (e.g.: <mailto:[email protected]|[email protected]>)
• Bot fails to match regex

It just seems strange to have integration specific (Slack only) logic in the bot after coming out of the botbuilder, which is supposed to genericize the bot experience.

Slack documents this here (https://api.slack.com/docs/message-formatting#linking_to_urls)

[craigjensen]

We have a fix ready for the (3 times with pipes between) issue reported by the OP. It will deployed soon (probably sometime next week).