<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="sans-serif">Hi Hans,<br>
<br>
I'm really looking forward to the "html" mail features. Thank you for
taking the time to develop this.<br>
I also like the way you are trying to simplify the process. Feedback
from my users to date was that<br>
it was quite difficult learning the concepts for foxnotify - but once
understood it's o.k.<br>
<br>
>From my perspective I would like users to have a simple way for them to
set up e-mail forms using fox,<br>
but to have some kind of security/approval before these forms can be
made active. <br>
<br>
I don't know how feasible/sensible this is, but something like the url
link approval, where when a new url is<br>
put into the wiki it can not be made visible with the read permission
until the url is approved by the wiki admin. <br>
Could this be made for the e-mail address too? So that the "to:" domain
for the e-mail address needs to be approved by the administrator before
the form/page can be made active. In this way the e-mail address used
for outbound mails can be "managed". For instance if I wanted to stop
all outgoing mails I could just delete the entries on the approval
page,and restore then from page history if/when needed. I'm not sure
whether this makes good sense - but something along the lines of admin
control would help.<br>
<br>
Your idea of a FoxNotifylists group also works too, I guess the user
has to "ask" for such an entry to be put on the list.?<br>
<br>
One further point, I noticed a "side affect" of writing to a page when
sending the e-mail is that this is a very good audit/reporting trail. I
can see how many and when e-mails were made - I quite like this feature!<br>
<br>
Thanks again for your work on Fox - it's very useful indeed.<br>
<br>
Rgds<br>
<br>
Graham<br>
<br>
</font><br>
Hans wrote:
<blockquote cite="mid:1565022791.20080518170218@softflow.co.uk"
type="cite">
<pre wrap="">I would love to get some feedback on new developments for Fox
and FoxNotify regards ability to send out emails to lists of
recipients.
Up till now after installing FoxNotify one could add to a Fox form
a foxfilter 'FoxNotify', which made the form, after successful
posting, send out an email to one or several lists of recipients on
notify list pages in a special 'FoxNotifyLists' group (the group could be
customised). A input control named 'foxnotify' could specify which list page
to use, but it had to be in the FoxNotifyLists group.
Now I added a foxaction 'mail' and markup (:foxmail ..:) which
similar to fox markup (:foxreplace ...:) (:foxadd ...:) (:foxptv ...:)
can take a template and target parameter. The template in this case
is used to format the email, and the target is used to specify a
notify list page.
This new markup makes it possible to use Fox for mailing an email to
a specified group of recipients, and it is not necessary that Fox has
to do a successful posting for this email to be sent. Thereby one can
built Mail Forms (Contact Forms) or use it to issue newsletters to
a group of subscribers (as long as there are not too many, since the
mailing is done by the php mail function).
Today I widened the possibilities by making it possible to issue HTML
formatted emails. The email template accepts wiki markup, the
body of the email will be marked up to HTML, and the email header
will get appropriate code to mark the email message as HTML formatted.
A variable has to be set in config.php to enable this behaviour.
I also integrated FoxNotify and Fox code further, so that it is no
longer necessary to set a foxfilter FoxNotify. It is sufficient to
set a notify list page with a foxnotify input control.
These changes of today have not yet been released.
I am wondering if it is a good idea to keep a FoxNotifyLists group,
and if the (:foxmail ..:) markup should be restricted to use only
email target lists from that group, or if target lists could be
anywhere (like other target pages). 'mail' has to be enabled as
foxaction for such pages (like 'add' or 'replace' for other target
pages, as specified with $FoxPagePermissions.
My original idea about the FoxNotifyLists group was that it is easier
to protect pages with email addresses if they are in one specific
group. Also FoxNotify worked without any extra FoxPagePermission setting.
Have you got any comments on such security questions?
And are there specific security concerns to be addressed by allowing
HTML formatted email messages? Note the formatting is done via wiki
markup in the template page, not by inserting HTML tags into the
template. At the same time it will be possible to use wiki markup for
instance in a text box of a Mail Form, if HTML emails are enabled.
Quite good looking formatted newsletters, including images and links
etc., can be mailed this way as well.
Please give me you ideas on these issues, so I can finalise the next
release of fox and FoxNotify.
Thank you!
~Hans
_______________________________________________
pmwiki-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a>
<a class="moz-txt-link-freetext" href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users">http://www.pmichaud.com/mailman/listinfo/pmwiki-users</a>
</pre>
</blockquote>
</body>
</html>