you can use the notification system. Go to the folder in the admin interface and press "keep me updated". Every time a user publish something in this folder you will be informed.
After this you must config the notification system /cronjobs, so the mails are generated automaticly.
look here : http://www.ez.no/developer/ez_publish_3/documentation/configuration/configuration/cron_jobs
(there are some problems with notification system in 3.3.1 at the moment)
Dominik,
I'd like to use the notification system on 3.3 soon. i just did some tests with it with 3.2-3 and they like fine.
What's wrong in 3.3... Can you give me a hint (or links to bug reports?) I know, that there was some change concerning the use of the "primary key" (user-id instead of email-adress), which i absoluty will need.
Paolo, i agree 100% with dominik: The notification system is exactly, what you need ;)
i have many problems with ez at the moment. the notification is only one of them (have make many tests this week, and most problems doesn't made by me :) )
You can look here :
http://ez.no/developer/ez_publish_3/bug_reports/notification_system http://ez.no/developer/ez_publish_3/bug_reports/fatal_error_runcronjobs
and if you have time & an answer for this ;)
http://ez.no/developer/ez_publish_3/bug_reports/placements_in_plain_package_wrong http://ez.no/developer/ez_publish_3/forum/install_configuration/problem_with_siteaccess_vhost_ie6
Dominik,
the first two (bug reports) very much seem to be some SQL error.
Kaare send an SQL fix, which was in the update scripts, but not in the 3.3-1 "full" release.
For the "placement" bug: I didn't quite understand the bug report.
For the "host map" problem: I wrote a comment, but I'd assume, that it IS a cookie problem. May be a code bug anyway. If you can reproduce it 100%, file a bug report.
