Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

🐛 [firestore-send-email] Support for multiple and dynamic SMTP connection URIs

未关闭
  • 哪里不对？
#1,990 1 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
gcp, typescript
领域
backend, cloud, databases

调研方向

该 issue 未指定文件、测试或入口点；首先定位 firestore-send-email 扩展及其当前的 SMTP 配置路径。检查扩展配置、Firestore 文档和 Google Secret Manager 当前的处理方式，然后为默认、选定、缺失和动态获取的 SMTP 连接 URI 建立验收测试。

由索引模型根据 Issue 内容生成。

描述

extension: firestore-send-email type: feature request

This feature request is for extension: firestore-send-email.

What feature would you like to see?

Enhancing flexibility and scalability for managing outbound emails by enabling dynamic SMTP server configuration based on Firestore documents or Google Secret Manager.

In more detail:
  • Introduce a new configurable parameter: useDynamicSmtpConnectionUris.
  • Enable dynamic SMTP connection URI configuration for outbound emails to support multiple SMTP outbound servers, catering to different customers' needs. This could involve storing each custom outbound SMTP connection URI in a Firestore collection or linking to a secret in Google Secret Manager 🔑 .
  • Implement synchronization of corresponding secrets in Google Secret Manager 🔑 via a Cloud Function or Firestore onWrite document trigger, empowering customers to manage their SMTP configurations autonomously.
  • For new documents in the email collection, the extension would examine the outboundSmtpServerId field (a new addition to email documents). If this field is specified and not set to "default", the extension would retrieve the connection URI from a Firestore document stored at a specified path designated by the new configurable parameter smtpConfigurationsCollection. If the document is linked to a secret, it will access the secret accordingly.
  • If outboundSmtpServerId is undefined, null, or set to "default", the base SMTP connection URI will be utilized.
How would you use it?

Incorporating these features would be particularly advantageous for scenarios involving diverse customers or varying SMTP configurations, such as allowing customers to use their own email servers for outbound email.

In addition, these enhancements open up possibilities for more tailored email communication strategies, e.g. enabling businesses to personalize their outgoing emails based on specific customer segments or preferences. This increased customization can significantly improve engagement and user experience, making the extension even more versatile for various use cases in application development.

As the implementation is highly valued, I'm available to provide additional context, clarification, or details for potential implementation. 🙏

主要语言
TypeScript
星标
978
派生
433
平均合并
21 小时 58 分钟
30 天内合并 PR
16

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

firebase/extensions 的其他 Issue

查看 firebase/extensions 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。