@Stephanie: good point, good explanation - thanks.
@neo: Look, there are two entirely different aproaches to ecards:
1) The ecard resides on the server, only a notification email is being sent
When you create an ecard, a record is being stored in a database table that contains the ecard message, the pic, the recipient and the sender data. All the recipient gets is an email telling him to visit a particular web page (by clicking on a url), where he can see his ecard online. As this particular website the recipient is sent to is being specifically created for him, there can be tracking on this page as well, and the visit of the page can be used to trigger a notification email to the original sender. Pro: tracking possible. Con: additional fiddling with database, increased use of webserver resources, invasion of user's privacy.
This type of ecards is being used by most applications that are dedicated ecard programs. This is not the way coppermine ecards work.
2) The ecard is sent along with the email, no storing of the ecard on the server
When you create an ecard, the full data the recipient is meant to see is being sent along with the ecard (full html mark up, plus pic). The server sends the ecard and then "forgets" about it.
This type of ecard is being used by coppermine (and of course some other apps as well). To handle the issue of some email clients not displaying the ecard email as expected, coppermine generates an additional link that is sent along with the ecard: it contains encrypted data that contains reference to the pic that was meant to be inside the ecard, as well as the text that goes along with it. The ecard is not stored, it is created "from scratch" when someone actually visits the link that is contained in the email.
Only later (after cpg1.2.x was released) people have requested some (limited) ecard tracking, so there's an option in cpg to store the sent ecards as well, but this is as far as we dare to go. We will not send further announcements.
Quite frankly: I don't care what features you would like to see in your customized coppermine install; as a project manager I try to see this from a global scale: do we want such a feature you're requesting to go into the future core code? The answer is "no", so I won't look into it any more. Like I said: you need it - you code it (or hire someone who will code it for you). It doesn't matter to me if you actually have the budget to do so or if you're just a student without any money. After all it's my choice what I'm ready to do and what not. It also doesn't matter to me what solution other "competing" gallery apps have come up with in this respect, as I simply don't see the point in sending even more email or even encourage users to do so by giving them tools that will.
On my email client I have set up a rule to delete all ecards sent to me, just because I'm fed up with them. Ecards used to be nice years ago (when the www was young), as well as guestbooks, web rings, link exchanges etc. Today, nobody needs those features any more - they're just deprecated.
Joachim
P.S. in cpg1.4, the ecard will be sent both as html and plain text email, so either way, the recipient will be able to see the ecard, one way or the other. The spam score should be reduced this way as well.