You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
In current -emails sent by the Nextcloud calendar application there are not a part with the "human readable" sender name, so in the common mail agents (yahoo, gmail, outlook ... etc) the message diaplays only mail address, but not a sender name (as it is usual with this type of dervices).
Other Nextcloud service which also sends e-mails (Server itself? only I guess) sends e-mails with the server name, so it is definitelly possible to do it in the Nextcloud. Server name is taken from the server configuration.
See attached piclures.
The best solution would be that the server API would provide (among others also) e-mail API which would construct sender string automatically (based on the server configuration) - then it would be consistent over the whole NC instance.
How the sender looks in the Gmail in message from calendar:
How the sender looks in the Gmail in message from other part of Nextcloud:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
In current -emails sent by the Nextcloud calendar application there are not a part with the "human readable" sender name, so in the common mail agents (yahoo, gmail, outlook ... etc) the message diaplays only mail address, but not a sender name (as it is usual with this type of dervices).
Other Nextcloud service which also sends e-mails (Server itself? only I guess) sends e-mails with the server name, so it is definitelly possible to do it in the Nextcloud. Server name is taken from the server configuration.
See attached piclures.
The best solution would be that the server API would provide (among others also) e-mail API which would construct sender string automatically (based on the server configuration) - then it would be consistent over the whole NC instance.
How the sender looks in the Gmail in message from calendar:
![Image](https://private-user-images.githubusercontent.com/52619304/405613772-1dac23af-670c-410a-b97a-03d9e0edb8b7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwMDM2MjMsIm5iZiI6MTczOTAwMzMyMywicGF0aCI6Ii81MjYxOTMwNC80MDU2MTM3NzItMWRhYzIzYWYtNjcwYy00MTBhLWI5N2EtMDNkOWUwZWRiOGI3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDA4Mjg0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQyMGRkMDE0ZmYyZmVlNDQ1ZWUzOWIxNTAwNzAyNTY3ZjhiNzc1NzVkODhhYjA4NzQ1MWY0YTA1NmI5NjNkNmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.TzKsnpBbiBpX5WFtMf9wfBRNHgUKvWvoOxkTnHn27Qs)
How the sender looks in the Gmail in message from other part of Nextcloud:
![Image](https://private-user-images.githubusercontent.com/52619304/405613896-55d37ec7-5df6-47b8-9a5d-1ae28ae2461a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwMDM2MjMsIm5iZiI6MTczOTAwMzMyMywicGF0aCI6Ii81MjYxOTMwNC80MDU2MTM4OTYtNTVkMzdlYzctNWRmNi00N2I4LTlhNWQtMWFlMjhhZTI0NjFhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDA4Mjg0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWEwZWY5MjRjNTA3NDMwZTNlZTk2ZTI0ZDc0NWYwNDE3YmE4MDMxNTM4N2NmNmMzNTMxNDJiZjBkNTI4ZDhlY2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.poKM1T3XUIHXvwcX1zcRyUr3Ftjb_3W-Au2pe58IhpI)
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: