Bug 4551 - Claws Mail doesn't open mailto: Link correctly
Summary: Claws Mail doesn't open mailto: Link correctly
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.18.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2021-11-21 14:05 UTC by Manuel
Modified: 2021-11-21 16:37 UTC (History)
0 users

See Also:


Attachments

Description Manuel 2021-11-21 14:05:50 UTC
When opening the following link with Claws Mail, it opens a window to write a new message, but the CC and BCC recipients are missing.

<a href="mailto:Mr.%20Test%20%3CMr.Test@something.com%3E,Mrs.Test@something.com,Junior%20Test%20%3Cjunior.test@something.com%3E?cc=Mrs.Test@something.com,Junior%20Test%20%3Cjunior.test@something.com%3E&amp;bcc=Mrs.Test@something.com,Junior%20Test%20%3Cjunior.test@something.com%3E&amp;subject=This%20is%20an%20example&amp;body=Hi%2C%0A%0Athis%20is%20a%20test.">
test</a>

Maybe Claws Mail removes the Mail addresses as they are duplicates, but this is not the behavior that users would expect.
Comment 1 Paul 2021-11-21 14:10:01 UTC
Is that not what users would expect?

Under what circumstances would sending the same message several times to the same address make sense?

Claws Mail will add Cc and Bcc address from such a link if they are not already included.
Comment 2 Manuel 2021-11-21 14:13:54 UTC
I think there are edge cases in which it makes sense and the point here is, that the link explicitly requests adding the duplicates. 
(I also compared the behavior with some other mail clients, Claws Mail was the only one that filtered the addresses.)
Comment 3 Manuel 2021-11-21 14:15:15 UTC
Maybe it would be a better solution to highlight duplicates or to ask the user if he wants to remove them.
Comment 4 Paul 2021-11-21 16:37:20 UTC
More likely than not, the server will only deliver one copy to its recipient anyway, so the "edge cases" are theoretical and asking the user is a waste of everybody's time.

Note You need to log in before you can comment on or make changes to this bug.