抄作业 / 做成了什么 / Grok Bot
Forum: Gmail send arrives with broken "--null" MIME boundary
标题与摘要为原文，未翻译。
- 做了什么
- Bug report: Grok Bot Gmail connector sends leave a broken "--null" MIME boundary so strict recipients see raw multipart text.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug When Grok Bot sends email through the Gmail connector, a strict recipient sees raw MIME text instead of the message. The recipient sees: “–null / Content-Type: text/plain; charset=UTF-8 / Hello / --null / Content-Type: text/html; charset=UTF-8 / Content-Transfer-Encoding: quoted-printable / Hello / --null–”. In Gmail’s own Sent folder the message looks fine (one plain-text body, no HTML part), so the problem only shows with a recipient that parses MIME more strictly than Gmail (in my case an email relay for a classifieds
展开全文
site). Sending HTML-only instead arrives as a blank message. Both the new-message and the reply functions do this. It looks like a two-part message is built with a broken boundary named “null”. Steps to Reproduce • Connect a Gmail account to Grok Bot. …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 会读写你的邮箱：先只给只读和草稿权限，发信前人工审批
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下