[GH-ISSUE #1793] 🚀 [Feature] Prevent duplicate email entries in To/CC/BCC fields #710

Closed
opened 2026-02-25 21:35:43 +03:00 by kerem · 3 comments
Owner

Originally created by @davmaene on GitHub (Nov 12, 2025).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1793

🚀 Feature

Prevent duplicate email entries in "To" and "Cc" or "Bcc" fields

Currently, it seems possible to add the same email multiple times in the "To" or "CC" fields.
I suggest that once an email is already present in either field, it should no longer be suggested or allowed for addition.
This would help prevent duplicates and improve usability.

Originally created by @davmaene on GitHub (Nov 12, 2025). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1793 ## 🚀 Feature Prevent duplicate email entries in "To" and "Cc" or "Bcc" fields Currently, it seems possible to add the same email multiple times in the "To" or "CC" fields. I suggest that once an email is already present in either field, it should no longer be suggested or allowed for addition. This would help prevent duplicates and improve usability.
kerem 2026-02-25 21:35:43 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner
<!-- gh-comment-id:3524392985 --> @marclaporte commented on GitHub (Nov 12, 2025): Related: https://github.com/cypht-org/cypht/wiki/Comprehensive-review-of-to-cc-bcc-when-reply-reply%E2%80%90to%E2%80%90all-forward-in-all-possible-contexts
Author
Owner

@davmaene commented on GitHub (Nov 13, 2025):

Related: https://github.com/cypht-org/cypht/wiki/Comprehensive-review-of-to-cc-bcc-when-reply-reply%E2%80%90to%E2%80%90all-forward-in-all-possible-contexts

Thanks for sharing.
The related task is: https://avan.tech/item97716

The context is: I should not add the same email twice, so once an email is in either To or Cc, it should no longer be offered.

Should I consider this link you just shared as a new approach?

<!-- gh-comment-id:3525887482 --> @davmaene commented on GitHub (Nov 13, 2025): > Related: https://github.com/cypht-org/cypht/wiki/Comprehensive-review-of-to-cc-bcc-when-reply-reply%E2%80%90to%E2%80%90all-forward-in-all-possible-contexts Thanks for sharing. **The related task is**: https://avan.tech/item97716 **The context is**: I should not add the same email twice, so once an email is in either To or Cc, it should no longer be offered. **Should I consider this link you just shared as a new approach?**
Author
Owner

@marclaporte commented on GitHub (Nov 13, 2025):

@davmaene What you did is great. Nothing more to do.

The URL I shared was just for folks interested in to/cc/bcc scenarios.

<!-- gh-comment-id:3528033960 --> @marclaporte commented on GitHub (Nov 13, 2025): @davmaene What you did is great. Nothing more to do. The URL I shared was just for folks interested in to/cc/bcc scenarios.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#710
No description provided.