On 13/03/2012 18:39, Dino Anzellotti wrote:
I agree with you, this is useful.
BTW, I am not able to evaluate the effort,
but if it were huge you should take into consideration that on Windows
environment you can easily drop emails into a folder using this free mail
server tool:
http://www.toolheap.com/test-mail-server-tool
I used it with Sun IDM several times and it works perfectly.
I haven't found something similar for unix environment yet, but it might exist
if we google a bit more.
I guess that here one can play with postfix (for example) and configure
to deliver every e-mail locally, to a single mailbox.
So, is it worth the effort?? :)
Only for redirecting e-mail notifications to a file? Probably No.
If instead we want to extend the whole approach to notification
delivery, we can think to define an interface (say "Notifier") and move
the current SMTP-based implementation from NotificationJob to a new
"SMTPNotifier" class; this would allow to define other "FileNotifier",
"JMSNotifier", "SMSNotifier" (and so on) implementations - even for a
single deployment, as already happening for many other features.
At this point we will also need to modify the current Notification and
NotificationTask objects by adding the possibility to choose which
notifier will be triggered.
This worth the effort, in my opinion.
But it's not a trivial change, so if we like this feature I'd suggest to
put somewhere in the still-to-be-defined roadmap.
Regards.
Il giorno 13/mar/2012, alle ore 17.40, Fabio Martelli ha scritto:
Il giorno 13/mar/2012, alle ore 16.24, Marco Di Sabatino Di Diodoro ha scritto:
This feature is usefull in demo and dev situations where no SMTP server is
available.
WDYT?
Hi Marco,
I agree with you. I do think that this feature is really useful.
--
Francesco Chicchiriccò
Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
