starred/cypht

Fork 0

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

forward in all possible contexts #651

New issue

Open

opened 2026-02-25 21:35:35 +03:00 by kerem · 9 comments

kerem commented

2026-02-25 21:35:35 +03:00

Owner

Originally created by @marclaporte on GitHub (Jan 10, 2025).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1422

Originally assigned to: @IrAlfred on GitHub.

Sometimes, I click forward or reply to all and the list of emails in to or cc is not what I expected.

https://github.com/cypht-org/cypht/issues/384#issuecomment-1182483833
https://github.com/cypht-org/cypht/pull/608
https://github.com/cypht-org/cypht/issues/706
Does anyone know of a comprehensive list of how it should be done? Maybe @nekohayo or @dumblob ?

We could then write tests and code it.

Thanks!

Originally created by @marclaporte on GitHub (Jan 10, 2025). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1422 Originally assigned to: @IrAlfred on GitHub. Sometimes, I click forward or reply to all and the list of emails in to or cc is not what I expected. Related: - https://github.com/cypht-org/cypht/issues/384#issuecomment-1182483833 - https://github.com/cypht-org/cypht/pull/608 - https://github.com/cypht-org/cypht/issues/706 Does anyone know of a comprehensive list of how it should be done? Maybe @nekohayo or @dumblob ? We could then write tests and code it. Thanks!

kerem added the

epic

label

2026-02-25 21:35:35 +03:00

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Jan 24, 2025):

An example of an issue:

I have an email b@example.org which is delivered/forwarded to account d@example.org (b@example.org is not a real mail account and thus, can't send emails)

Say I receive a message:

From: a@example.com
To: b@example.org
reply-to: c@example.com

A cypht reply replies to c@example.com (This is OK)

A cypht "reply to all" generates:
to: a@example.com, c@example.com
cc: b@example.org
from: d@example.org

Problems:
1- I am replying to a@example.com and c@example.com but the email sender specifically asked to use the "reply to" (c@example.com)
2- I am CCing b@example.org which is myself, so will be redirected to d@example.org

@marclaporte commented on GitHub (Jan 24, 2025): An example of an issue: I have an email b@example.org which is delivered/forwarded to account d@example.org (b@example.org is not a real mail account and thus, can't send emails) Say I receive a message: From: a@example.com To: b@example.org reply-to: c@example.com A cypht reply replies to c@example.com (This is OK) A cypht "reply to all" generates: to: a@example.com, c@example.com cc: b@example.org from: d@example.org Problems: 1- I am replying to a@example.com and c@example.com but the email sender specifically asked to use the "reply to" (c@example.com) 2- I am CCing b@example.org which is myself, so will be redirected to d@example.org

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Apr 18, 2025):

@nekohayo @dumblob

@IrAlfred identified over 20 permutations:
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

@marclaporte commented on GitHub (Apr 18, 2025): @nekohayo @dumblob @IrAlfred identified over 20 permutations: 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

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Jun 3, 2025):

@IrAlfred

I love what you did at 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

Can you imagine a way to add tests so we can be sure bugs don't come back after we fix them all?

@marclaporte commented on GitHub (Jun 3, 2025): @IrAlfred I love what you did at 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 Can you imagine a way to add tests so we can be sure bugs don't come back after we fix them all?

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Jul 1, 2025):

@IrAlfred I received an email today and there was no "to". So I was in BCC along with many others.

@marclaporte commented on GitHub (Jul 1, 2025): @IrAlfred I received an email today and there was no "to". So I was in BCC along with many others.

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@IrAlfred commented on GitHub (Jul 2, 2025):

@IrAlfred I received an email today and there was no "to". So I was in BCC along with many others.

Yes, that seems to be the current setup.

@IrAlfred commented on GitHub (Jul 2, 2025): > [@IrAlfred](https://github.com/IrAlfred) I received an email today and there was no "to". So I was in BCC along with many others. Yes, that seems to be the current setup.

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@IrAlfred commented on GitHub (Jul 2, 2025):

On Cypht standalone master branch I'm seeing this in the email headers

To	undisclosed-recipients:;

when all the recipients are in BCC

@IrAlfred commented on GitHub (Jul 2, 2025): On Cypht standalone master branch I'm seeing this in the email headers ``` To undisclosed-recipients:; ``` when all the recipients are in BCC

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Jul 2, 2025):

Great. So please add that in the scenario list so we can cover in testing,

@marclaporte commented on GitHub (Jul 2, 2025): Great. So please add that in the scenario list so we can cover in testing,

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Aug 27, 2025):

71 permutations so far. wow!
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

@marclaporte commented on GitHub (Aug 27, 2025): 71 permutations so far. wow! 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

kerem commented

2026-02-25 21:35:36 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 3, 2025):

@marclaporte commented on GitHub (Oct 3, 2025): Related: https://github.com/nextcloud/mail/issues/11772

kerem referenced this issue

2026-02-25 21:36:47 +03:00

[PR #651] [MERGED] Dirty fix for 500 on outgoing mail #958