larksuite / larksuite/cli

功能请求:希望CLI 返回共享邮箱邮件的实际发送人

Open
#1,240 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

domain/mail enhancement
Dominant language
Go
Stars
17.3k
Forks
1.4k
Avg merge
2d 4h
Merged PRs (30d)
105

Description

背景

在飞书邮箱中,如果成员通过共享邮箱发送邮件,飞书邮箱客户端里可以看到共享邮箱地址,同时也会显示实际发送人。

例如,界面上会展示类似“通过某某发送”的信息。

当前情况

目前通过邮箱 API 或 lark-cli 查询已发送邮件时,可以拿到发件邮箱、收件人、标签、会话 ID、邮件状态、SMTP Message ID 等字段。

但没有找到可以表示“实际由哪个成员发送”的字段。

需求

希望邮箱 API 和 lark-cli 在查询共享邮箱已发送邮件时,能够返回实际发送人 / 代发人的信息。

使用价值

对于使用共享邮箱的团队来说,这个字段可以帮助统计和分析邮件处理归属,例如:

  • 每个成员实际回复了多少邮件
  • 某封邮件由谁处理
  • 共享邮箱邮件的责任归属

目前如果没有这个字段,只能通过标签、会话上下文或正文内容间接推断,准确性不够稳定。

已检查的接口 / 命令
  • mail.user_mailbox.messages.get
  • mail.user_mailbox.messages.batch_get
  • lark-cli mail +messages
  • lark-cli mail +thread

目前没有看到实际发送人 / 代发人相关字段。

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the mail.user_mailbox.messages.get and batch_get API responses, then trace how lark-cli mail +messages and mail +thread expose those fields. Confirm whether the API provides actual-sender or delegate information; done means the available sender data is returned consistently by the requested API and CLI queries.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.