Busycal connector mangles subject line
Reported by Rolf Morgenstern | January 28th, 2025 @ 02:30 PM
When creating a calendar event using the Busycal bundle, the subject line is not parsed and transfered correctly.
Example subject: 2025: Stundenzettel / timesheets für
EU-Projekte
Resulting event title in Busycal: : Stundenzettel / timesheets
für EU-Projekte >
In the ICS file the situation looks like this:
SUMMARY:: Stundenzettel / timesheets für EU-Projekte
>
DESCRIPTION:message:<000001db6114$f40a2f70$dc1e8e50$@fh-swf.de
Please note the wrong greater than character at the end of the SUMMARY line and the missing greater than character in the DESCRIPTION line.
I've had the effect that events were not visible in Busycal, but were visible in other CalDav clients (SoGO) and the calendar entries were botched, spanning over weeks, and it was not easily possible to delete those (unable to reproduce right now).
Comments and changes to this ticket
-
benny January 28th, 2025 @ 03:30 PM
Given the example subject, it might be related to the
/used, but I don't exactly see how. The (very old) script used is here. The URL handler used is described here.You could play around with the URL handler directly in a Terminal window like this if that helps:
open "busycalevent://new/test%20string"Note that the string provided needs to be URL encoded.
MailMate does not create the ICS file and therefore I find it more likely that the problem is related to BusyCal and not MailMate (even if MailMate somehow sends something wrong to BusyCal).
You can also send me an example email (via Help > Send Feedback) and I can download BusyCal and try myself when I have time.
-
Rolf Morgenstern January 28th, 2025 @ 04:23 PM
Thanks for the quick reply! I'm looking into it.
First findings:
- forward slashes in the subject don't seem to get urlencoded. The should be encoded als %2F.
- the new(er) busycal URL handler pushes things after the forward slash into the event notes (busycalevent://new/<event description>/<notes>)
- When the Mail subject has a year at the beginning (example "2025 : The rest of the subject") then this gets interpreted as a time, creating a calendar entry today at 20:25 hours.
Could not yet reproduce the greater than effect >
Will continue checking. -
benny January 29th, 2025 @ 02:13 PM
I don't think MailMate can do anything about how BusyCal interprets the “free text” string. This is not related to the URL encoding itself (which is just about getting the string “transmitted” to BusyCal). Let me know if you figure out if MailMate should do something differently.
(Forward slashes are already encoded.)
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.
benny