KAlarm does not work with KMail identities

[mbeltagy]

Binary package hint: kalarm

When creating a new Email Alarm on Kalarm 2.1.6 on Kubuntu jaunty with the default mail settings (Use Kmail Identities), it fails to send the email and I get a server error. It seems to place a extra brackets and around the KMail address identities. For example if I had an identity with the name: John Doe and email <email address hidden>. It it report of the server that the from field is: <John Doe <email address hidden> >, instead of the proper: John Doe <email address hidden>.

This extra bracketing cause a parse error at the server and the mail is not sent. KAlarm, then presents an error message that just refuses to be dismissed. One has to actual kill the KAlarm process to make it go away.

When one goes to the settings to fix the problem by filling the address manually, it starts sending emails.. however it sends many copies of the same email, as all the dismiss popups that wouldn't go be "dismissed", just place multiple copies on the message in some sort of queue.

Also even if one gets it to work. It does not pop a copy on the sent-mail folder in KMail (version 1.11.2).

[Jason Straight (jason-jeetkunedomaster)]

I get part of this, I created an alarm and tested email for a friend who was having problems with his, I'm getting what he got, 94 emails sent for a single alarm.

I had no problem using my kmail identity though.

[Jason Straight (jason-jeetkunedomaster)]

I don't suppose there's any chance of getting this patched and recompiled? There's no release schedule for 4.2.5, and 4.3 is a way off.

Unfortunately I updated a friend's computer [from hardy] who was quite reliant on kalarm for e-mailing notifications to SMS to remind him of meds, as his short term memory is shot.

I tried installing build-deps for kalarm to do it myself but they weren't available. It looks like it might be more than I can chew.

[Harald Sitter (apachelogger)]

It is possible, but unless you find a developer to do it, it ain't gonna happen :|

Doing it yourself:
apt-get build-deps kdepim
apt-get source kdepim
apply the changes from http://websvn.kde.org/trunk/KDE/kdepim/kalarm/kalarmapp.cpp?r1=978880&r2=978879&pathrev=978880
dch -i (that should open an editor to edit the package's changelog)
dpkg-buildpackage -us -uc

In any case the status is fix committed ;-) For Jaunty it would need a nomination, which is only valid if there is a debdiff attached to this bug... so really before we can start the stable release update process we need to have a package diff at hand.

[Jonathan Thomas (echidnaman)]

Fixed in Karmic.