[GH-ISSUE #882] A "remark" field to remember why you added a profile #510

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

Originally created by @w-b-k on GitHub (Feb 5, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/882

Originally assigned to: @IrAlfred on GitHub.

🗣 Suggestion

I create a mail alias and a corresponding identity/profile per organization/entity/contact that I deal with, to isolate data leaks and prevent merging of profiles in different providers' back-ends.
The aliases are not very self-explanatory, so I keep notes which alias goes with which entity.

For me it would be helpful to have a "remarks" field in addition to the "signature" field when managing profiles. Is it too much a niche application of aliases/profiles to have any merit outside of my application, or would it be something useful for a wider audience?

Thank you for your consideration!

Originally created by @w-b-k on GitHub (Feb 5, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/882 Originally assigned to: @IrAlfred on GitHub. ## 🗣 Suggestion <!-- Describe your Suggestion/Idea in detail. --> I create a mail alias and a corresponding identity/profile per organization/entity/contact that I deal with, to isolate data leaks and prevent merging of profiles in different providers' back-ends. The aliases are not very self-explanatory, so I keep notes which alias goes with which entity. For me it would be helpful to have a "remarks" field in addition to the "signature" field when managing profiles. Is it too much a niche application of aliases/profiles to have any merit outside of my application, or would it be something useful for a wider audience? Thank you for your consideration! <!-- Attach Screenshots and Drawings if needed. -->
kerem closed this issue 2026-02-25 21:35:12 +03:00
Author
Owner

@marclaporte commented on GitHub (Feb 5, 2024):

@w-b-k I Iike it. Let's do it.

<!-- gh-comment-id:1928255318 --> @marclaporte commented on GitHub (Feb 5, 2024): @w-b-k I Iike it. Let's do it.
Author
Owner

@marclaporte commented on GitHub (Feb 5, 2024):

@IrAlfred Please show us your skills :-)

<!-- gh-comment-id:1928296948 --> @marclaporte commented on GitHub (Feb 5, 2024): @IrAlfred Please show us your skills :-)
Author
Owner

@marclaporte commented on GitHub (Feb 6, 2024):

@w-b-k: looking at this more:

There are two text fields:

  • Display Name
  • Signature

What would be negative about using the Display Name?

<!-- gh-comment-id:1928750156 --> @marclaporte commented on GitHub (Feb 6, 2024): @w-b-k: looking at this more: There are two text fields: * Display Name * Signature What would be negative about using the Display Name?
Author
Owner

@IrAlfred commented on GitHub (Feb 6, 2024):

@IrAlfred Please show us your skills :-)

Not sure to understand well what this is about, please I need more details

<!-- gh-comment-id:1929038313 --> @IrAlfred commented on GitHub (Feb 6, 2024): > @IrAlfred Please show us your skills :-) Not sure to understand well what this is about, please I need more details
Author
Owner

@w-b-k commented on GitHub (Feb 6, 2024):

Hi, thanks for your prompt response ! :-)

What would be negative about using the Display Name?

Is the display name not the field that is sent as "My Name" to the recipient of the email?

I would write something like "added this alias for exchange with the piano teacher; starting 20240103". If "Display name" is not sent as "My Name" with the email, is another field used to supply the recipient with my name?

<!-- gh-comment-id:1929203490 --> @w-b-k commented on GitHub (Feb 6, 2024): Hi, thanks for your prompt response ! :-) > What would be negative about using the Display Name? Is the display name not the field that is sent as "My Name" to the recipient of the email? I would write something like "added this alias for exchange with the piano teacher; starting 20240103". If "Display name" is not sent as "My Name" with the email, is another field used to supply the recipient with my name?
Author
Owner

@marclaporte commented on GitHub (Feb 6, 2024):

@w-b-k Good point. Please test, and if Display Name is used as you said, we'll add one more field.

<!-- gh-comment-id:1929457638 --> @marclaporte commented on GitHub (Feb 6, 2024): @w-b-k Good point. Please test, and if Display Name is used as you said, we'll add one more field.
Author
Owner

@marclaporte commented on GitHub (Feb 6, 2024):

@IrAlfred https://github.com/cypht-org/cypht/tree/master/modules/profiles

<!-- gh-comment-id:1929680925 --> @marclaporte commented on GitHub (Feb 6, 2024): @IrAlfred https://github.com/cypht-org/cypht/tree/master/modules/profiles
Author
Owner

@w-b-k commented on GitHub (Feb 8, 2024):

@w-b-k Good point. Please test, and if Display Name is used as you said, we'll add one more field.

Tested. The text entered in the "Display name" field is displayed in Cypht when sending a new message (below the field for typing the message, a combobox to select the from-identity).

In the receiving mail client, the text is displayed as the 'friendly name' in combination with the email address.

@IrAlfred Please show us your skills :-)

Not sure to understand well what this is about, please I need more details

I got there by cilcking Profiles under Settings:

image

When adding (or editing) a profile, the confusion was about the "Display name" field:

image

I'd like to have an option to write some remarks about why I added the particular profile:

image

(In a perfect world the field would be multi line, or a wider letter box :-P )

<!-- gh-comment-id:1935032348 --> @w-b-k commented on GitHub (Feb 8, 2024): > @w-b-k Good point. Please test, and if Display Name is used as you said, we'll add one more field. Tested. The text entered in the "Display name" field is displayed in Cypht when sending a new message (below the field for typing the message, a combobox to select the from-identity). In the receiving mail client, the text is displayed as the 'friendly name' in combination with the email address. > > @IrAlfred Please show us your skills :-) > > Not sure to understand well what this is about, please I need more details I got there by cilcking Profiles under Settings: ![image](https://github.com/cypht-org/cypht/assets/27885942/89916d64-50fc-4cf1-8a57-7664f4282ae1) When adding (or editing) a profile, the confusion was about the "Display name" field: ![image](https://github.com/cypht-org/cypht/assets/27885942/e8576614-64f4-4056-a705-4e0b07d32aa6) I'd like to have an option to write some remarks about why I added the particular profile: ![image](https://github.com/cypht-org/cypht/assets/27885942/236b090e-0279-4643-84c8-50d3afc29428) (In a perfect world the field would be multi line, or a wider letter box :-P )
Author
Owner

@IrAlfred commented on GitHub (Feb 12, 2024):

Okay, thanks

<!-- gh-comment-id:1939074876 --> @IrAlfred commented on GitHub (Feb 12, 2024): Okay, thanks
Author
Owner

@marclaporte commented on GitHub (Feb 17, 2024):

@w-b-k Can you please test? https://github.com/cypht-org/cypht/pull/903

<!-- gh-comment-id:1950078344 --> @marclaporte commented on GitHub (Feb 17, 2024): @w-b-k Can you please test? https://github.com/cypht-org/cypht/pull/903
Author
Owner

@w-b-k commented on GitHub (Feb 17, 2024):

Hi Alfred & Marc,

Thank you, looks (and works, on first test) great!

A small non-functional remark on the changes in modules.php : in most places the rmk is added after sig, but in a cases it is added on a different position, for example on line 129 it follows 'type', instead of 'sig' (at line 121). Is that on purpose?

Edit: on second, more general test:

  • Setting/retrieving a remark with a profile works (new with this change)
  • Setting/retrieving a signature works (is not new)
  • A signature is not added to outgoing mail (is not as expected)

I'm not a heavy user of preconfigured signatures. I am not sure whether it used to work, or that the not-working is specific to my installation: I noticed the new files being quite different from the ones I had installed (1.4.1, via Yunohost; what is the current version?)

<!-- gh-comment-id:1950445023 --> @w-b-k commented on GitHub (Feb 17, 2024): Hi Alfred & Marc, Thank you, looks (and works, on first test) great! A small non-functional remark on the changes in modules.php : in most places the rmk is added after sig, but in a cases it is added on a different position, for example on [line 129](https://github.com/cypht-org/cypht/pull/903/files#diff-2375a5d259659c96bfacd4c4e717655616a0e7afe58f398934baec685572cc1fR129) it follows 'type', instead of 'sig' (at line 121). Is that on purpose? Edit: on second, more general test: * Setting/retrieving a remark with a profile works (new with this change) * Setting/retrieving a signature works (is not new) * A signature is not added to outgoing mail (is not as expected) I'm not a heavy user of preconfigured signatures. I am not sure whether it used to work, or that the not-working is specific to my installation: I noticed the new files being quite different from the ones I had installed (1.4.1, via Yunohost; what is the current version?)
Author
Owner

@IrAlfred commented on GitHub (Feb 18, 2024):

Thank you for your feedback. Regarding the non-functional remark concerning the position of rmk in the module.php file compared to its position in other places, this was not done on purpose but just that we didn't pay too much attention to it . I fix that for good harmony.

<!-- gh-comment-id:1950944107 --> @IrAlfred commented on GitHub (Feb 18, 2024): Thank you for your feedback. Regarding the non-functional remark concerning the position of rmk in the module.php file compared to its position in other places, this was not done on purpose but just that we didn't pay too much attention to it . I fix that for good harmony.
Author
Owner

@marclaporte commented on GitHub (Feb 18, 2024):

I noticed the new files being quite different from the ones I had installed (1.4.1, via Yunohost; what is the current version?)

Cypht 1.4.1 is the current stable version. Because of major changes in master, the next release will be 2.0

<!-- gh-comment-id:1950958920 --> @marclaporte commented on GitHub (Feb 18, 2024): > I noticed the new files being quite different from the ones I had installed (1.4.1, via Yunohost; what is the current version?) Cypht 1.4.1 is the current stable version. Because of major changes in master, the next release will be 2.0
Author
Owner

@marclaporte commented on GitHub (Feb 24, 2024):

@w-b-k Is the latest code good to merge?

<!-- gh-comment-id:1962218385 --> @marclaporte commented on GitHub (Feb 24, 2024): @w-b-k Is the latest code good to merge?
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#510
No description provided.