[DOCS]: Links to SparkPost are broken

[adiati98]

Description

Links to SparkPost are broken with details as below:

315  (configuration/smime_email_signing: line   27) broken    https://www.sparkpost.com/blog/s-mime-sparkpost/ - 502 Server Error: Bad Gateway for url: https://bird.com/blog/s-mime-sparkpost?sp=true
316  (configuration/smime_email_signing: line   28) broken    https://www.sparkpost.com/blog/s-mime-part-2-signed-sealed-delivered-sparkpost/ - 404 Client Error: Not Found for url: https://bird.com/api/email?sp=true

Relevant Documentation URL

No response

Are you willing to help us fix this by making a pull request?

Yes

Suggestions (Optional)

No response

Screenshots or Screen Recordings (Optional)

No response

[adiati98]

@escopecz I can't seem to find replacements for the broken links to SparkPost S/MIME. Do you have any suggestions?

@RCheesley we don't have branch 7.1 live on our docs yet. Should we add this version at Read the Docs?

[adiati98]

@RCheesley @escopecz, the SparkPost blog is missing from both SparkPost and bird.com. I've read both broken links on web archives.

Questions:

• Can we use https://mailbox.org/en/blog/smime-secure-e-mail-encryption-and-signature/ as replacement for What is S/MIME and Why Should You Use It? --> Here's the link to the web archive for your reference.

• For the 2nd broken link, S/MIME, Part 2: Signed, Sealed, and Delivered with SparkPost (here's the link to the web archive), I can't find any other alternatives that works specifically with SparkPost. This is the only resurce that I could find, but it's part of Cloudfare Docs which is tied to using SparkPost with Cloudflare Zero Trust.

If the suggested replacement links above are unrelated with the current ones, I think we better remove the reference resources completely, especially the 2nd one, and update our own docs so folks can use SparkPost with Mautic seamlessly. I need help with this as I'm not familiar with these stuffs.

Please let me know what you think. Thanks!

[escopecz]

We are trying to get some answers directly from Sparkpost.

[adiati98]

Thanks for the info, @escopecz! Then, I'll hold this for a bit. 👍🏼

[escopecz]

We got a response that they are working on the errors but they also mentioned they want to move the information to a chat bot. So perhaps we could copy the text from the archive and publish it under Mautic docs mentioning the contribution to Sparkpost? We could also let AI to simplify it a little.

[adiati98]

We got a response that they are working on the errors but they also mentioned they want to move the information to a chat bot. So perhaps we could copy the text from the archive and publish it under Mautic docs mentioning the contribution to Sparkpost? We could also let AI to simplify it a little.

That could be a choice. We might be able to use the :orphan: directive. I only don't know yet how to link back to their web page as a canonical. Would credit them would be sufficient?

I wonder, does these links have to be related to SparkPost?

@RCheesley any thoughts for this?

[RCheesley]

Honestly I'd say that if there's a good comparable source, and the information doesn't need to be Sparkpost-specific, then that'd be much more preferable than landing someone into a chatbot. Or, as @escopecz suggests, perhaps we could use the content and re-work it into a blog post or KB article, then we own the content?

[adiati98]

@RCheesley if we want to use and re-work the content, then we have to make it Mautic-related post. I'm fine with it, but I'm not familiar with this. So, we might want to open an issue for folks to work on it.

In the meantime, is it okay to remove these links (or temporarily replace them with comparable sources as I mentioned in this comment) so we can avoid the build fails?

cc: @escopecz

[escopecz]

Let's used the alternative links for now. The simplest way forward.