starred/cypht

Fork 0

mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 13:05:53 +03:00

[GH-ISSUE #531] Soft and/or hard limit to number of recipients #392

New issue

Closed

opened 2026-02-25 21:34:55 +03:00 by kerem · 7 comments

kerem commented

2026-02-25 21:34:55 +03:00

Owner

Originally created by @marclaporte on GitHub (Nov 8, 2021).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/531

Every once in a while, I'll receive an email with 50+ recipients. And with more recipients, there is a good chance someone will reply to all.

It is usually an error.

Many clients and email services have limits. Ex.:

We should have warnings to help users.

Originally created by @marclaporte on GitHub (Nov 8, 2021). Original GitHub issue: https://github.com/cypht-org/cypht/issues/531 Every once in a while, I'll receive an email with 50+ recipients. And with more recipients, there is a good chance someone will reply to all. It is usually an error. Many clients and email services have limits. Ex.: - https://github.com/roundcube/roundcubemail/issues/5132 - https://docs.gandi.net/en/gandimail/limitations.html We should have warnings to help users.

kerem closed this issue

2026-02-25 21:34:55 +03:00

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@dumblob commented on GitHub (Nov 8, 2021):

We should have warnings to help users.

Yep, persistent (i.e. visible during the whole compose session - even if opened from a draft folder) warning. But please no hard limit.

@dumblob commented on GitHub (Nov 8, 2021): > We should have warnings to help users. Yep, persistent (i.e. visible during the whole compose session - even if opened from a draft folder) **warning**. But please no hard **limit**.

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@jasonmunro commented on GitHub (Jul 15, 2022):

@marclaporte to clarify, you want to have a warning if you reply-all to a message with > X recipients. That is not what the PR does so I just want to clarify before I comment on it. The PR uses JavaScript to trigger the warning on a keyup event, so it would only trigger if you are actually typing in the recipients. Also the way it is coded the message cannot be translated and it's possible it will miscount as recipient lines are notoriously hard to parse properly.

@jasonmunro commented on GitHub (Jul 15, 2022): @marclaporte to clarify, you want to have a warning if you reply-all to a message with > X recipients. That is not what the PR does so I just want to clarify before I comment on it. The PR uses JavaScript to trigger the warning on a keyup event, so it would only trigger if you are actually typing in the recipients. Also the way it is coded the message cannot be translated and it's possible it will miscount as recipient lines are notoriously hard to parse properly.

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@marclaporte commented on GitHub (Jul 16, 2022):

You understood correctly. But basically it doesn't matter if it's typed in or reply to all, there should be a soft warning at one point.

@marclaporte commented on GitHub (Jul 16, 2022): You understood correctly. But basically it doesn't matter if it's typed in or reply to all, there should be a soft warning at one point.

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@jasonmunro commented on GitHub (Jul 16, 2022):

I don't think a warning about typing in 20 recipients makes a lot of sense, but we can add that as well if you think it does. I posted some code to the PR that will warn if you load a draft or reply to a message that has > 20 recipients from the to + cc line. Often larger recipient lists are in the bcc field so I chose not to include that toward the warning

@jasonmunro commented on GitHub (Jul 16, 2022): I don't think a warning about typing in 20 recipients makes a lot of sense, but we can add that as well if you think it does. I posted some code to the PR that will warn if you load a draft or reply to a message that has > 20 recipients from the to + cc line. Often larger recipient lists are in the bcc field so I chose not to include that toward the warning

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@marclaporte commented on GitHub (Jul 16, 2022):

Your proposal works for me :-)

@marclaporte commented on GitHub (Jul 16, 2022): Your proposal works for me :-)

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@jasonmunro commented on GitHub (Jul 19, 2022):

committed so closing this.

@jasonmunro commented on GitHub (Jul 19, 2022): committed so closing this.

kerem commented

2026-02-25 21:34:55 +03:00

Author

Owner

@marclaporte commented on GitHub (Dec 15, 2023):

For the record: github.com/cypht-org/cypht@293d1af576

@marclaporte commented on GitHub (Dec 15, 2023): For the record: https://github.com/cypht-org/cypht/commit/293d1af576d7483145c87d75be65fbefbbc9450e