GNOME Bugzilla – Bug 536897
nautilus-sendto not quoting email addresses
Last modified: 2008-06-08 21:48:05 UTC
Version info... nautilus-sendto-0.14.0-1.fc9.i386 This applies to email addresses that are in a format like this... Last, First <user@example.com> I right-click a file, select "send to", and pick "Evolution"... then choose an address that auto populates as I type from my address book... The result is that Evolution sees the comma character and separates it out into two email addresses, one of which results in a bounce message because it is incomplete/invalid... 1) Last 2) First <user@example.com> Here's the line from an strace showing the call to evolution... execve("/usr/bin/evolution", ["/usr/bin/evolution", "mailto:Last, First <first.last@example.com>?attach=file:///home/flast/Desktop/untitled_1.odt"], [/* 45 vars */]) = 0 I would assume one solution would be for nautilus-sendto to quote any text in an email address that appears outside of a < > pair, ...but only if a < > pair is present. If I manually call evolution, I can recreate this from a shell prompt... ## FAILS (equivalent to how nautilus-sendto runs it)... /usr/bin/evolution "mailto:Last, First <first.last@example.com>?attach=file:///home/flast/Desktop/untitled_1.odt" ## WORKS (possible solution scenario)... /usr/bin/evolution "mailto:\"Last, First\" <first.last@example.com>?attach=file:///home/flast/Desktop/untitled_1.odt"
Note, the same type of issue exists when trying to send a file that has spaces in the filename. The filename would probably need to be quoted to protect its integrity. Not sure if that should be considered a separate bug or not, so for now I'll just mention it here. Thanks.
I'm pretty sure the issue doesn't exist with files with spaces in their names given that we pass URIs, not filenames to evolution. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 536342 ***
Regarding the "filename with spaces" issue: Actually, I'm pretty sure URIs cannot have spaces in them unless they are properly encoded. That is the problem, I believe. I was able to see the issue with a filename that contained a space. If you feel this is not the case, can you confirm that you cannot reproduce the issue ? If need be, I can do some strace commands and compare the URIs that are being passed to evolution on Monday. Let me know whatever else might be useful in identifying the cause of the issue. (The end result is that evolution opens a new message, but there is no attachment listed). And, sorry about the dupe bug regarding the address format. I searched for existing bugs, but must have forgotten to search the closed/resolved ones. I'll be more thorough next time. Should I open the filename issue as a separate bug ?
(In reply to comment #3) > Regarding the "filename with spaces" issue: Actually, I'm pretty sure URIs > cannot have spaces in them unless they are properly encoded. That is the > problem, I believe. I was able to see the issue with a filename that contained > a space. If you feel this is not the case, can you confirm that you cannot > reproduce the issue ? If need be, I can do some strace commands and compare > the URIs that are being passed to evolution on Monday. Let me know whatever > else might be useful in identifying the cause of the issue. (The end result is > that evolution opens a new message, but there is no attachment listed). > > And, sorry about the dupe bug regarding the address format. I searched for > existing bugs, but must have forgotten to search the closed/resolved ones. > I'll be more thorough next time. > > Should I open the filename issue as a separate bug ? Open a new bug with exact reproducer steps.