aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/comment_by_mail.mdwn
diff options
context:
space:
mode:
authorbremner <bremner@web>2008-07-19 19:53:46 -0400
committerJoey Hess <joey@kitenet.net>2008-07-19 19:53:46 -0400
commitff0fc4689a594af1c2aaa980802eab3c8bd90d00 (patch)
treef6e5df0b2dbcbb1178ef229949e65900a3358ce6 /doc/todo/comment_by_mail.mdwn
parentd52e0f08b9c737d7ebecd95491e4278299716659 (diff)
downloadikiwiki-ff0fc4689a594af1c2aaa980802eab3c8bd90d00.tar
ikiwiki-ff0fc4689a594af1c2aaa980802eab3c8bd90d00.tar.gz
describe postal-filer filter
Diffstat (limited to 'doc/todo/comment_by_mail.mdwn')
-rw-r--r--doc/todo/comment_by_mail.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/todo/comment_by_mail.mdwn b/doc/todo/comment_by_mail.mdwn
index d0a9b8283..085c4896f 100644
--- a/doc/todo/comment_by_mail.mdwn
+++ b/doc/todo/comment_by_mail.mdwn
@@ -10,10 +10,10 @@ I have in mind something like
[more details](http://www.cs.unb.ca/~bremner/blog/posts/encoding)
* on the mail receiving end, these messages are either deleted, or ran through
- a filter to be turned into blog posts.
-
- - I'm thinking about how the filter should work. Within a
- mail client, or as a batch tool to scan a mailbox? How to interact with version control, if at all?
+ a filter to be turned into blog posts. As a first step, I have
+[written](http://pivot.cs.unb.ca/git/?p=ikipostal.git;a=blob_plain;f=filters/postal-filer.pl;hb=010357a08e9)
+a filter that decodes the address and writes the message into an appropriate
+mailbox. I would be interested in any ideas people have about security.
* the same plugin can check for comments on a particular page next time the wiki
is generated, and add a link. (more or less done)