After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 229087 - One of Reminder possibilities should be to send e-mail
One of Reminder possibilities should be to send e-mail
Status: RESOLVED DUPLICATE of bug 218432
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-08-17 11:57 UTC by gisli.ottarsson
Modified: 2002-08-19 15:27 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description gisli.ottarsson 2002-08-17 11:57:40 UTC
Package: Evolution
Priority: Wishlist
Version: GNOME2.0.1 1.0.8
Synopsis: One of Reminder possibilities should be to send e-mail
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Description:
Description of Problem:

It would be highly useful to allow the sending of e-mail as a Reminder.
I would use this to send e-mail to my GSM mobile phone in the form of
SMS (simple message system).    The Subject could be composed of
the Summary, with other pertinent info, Location, Start/End Time and
Comments composited into the message body.

It occurred to me to try to handle this through the Run Program form
of the Reminder, but could not figure out how to access the Summary,
Location, etc. to pass this to the program.  Perhaps you could consider
making this information accessible, as a separate enhancement request.
Perhaps shell variables $EVOLUTION_SUMMARY, etc. could be set in
the subshell.



Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:


Unknown reporter: gisli.ottarsson@mscsoftware.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2002-08-19 15:27:08 UTC

*** This bug has been marked as a duplicate of 218432 ***