mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #1793] 🚀 [Feature] Prevent duplicate email entries in To/CC/BCC fields #710
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#710
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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
@davmaene commented on GitHub (Nov 13, 2025):
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?
@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.