Can I submit content to my wiki by email?
5 people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi! This is something we're considering adding in. I'd be interested to hear how you'd like to see this done - the more people we have interested in this feature, the more likely it is we'll bang it out. :)
The company says
this answers the question
-
Yes I'd be interested in being able to update pages in our wiki by e-mail -
Inappropriate?WEBHOOKS FTW - http://webhooks.pbwiki.com/
-
Inappropriate?Hi David,
Email in facility would get my vote. I think you have probably heard me banging on about a better way to upload the contents of word documents into pages. What ever happened to the drop box (http://blog.pbwiki.com/2007/06/18/sha...) I ask? Anything that would make the process uploading information from local machines into pbwiki is my opinion very important and that is why I would support an email in facility. I'd like to have the ability to attach a document to an email, send it off to my wiki and hey presto I have a page with the information. I think most people receive important updates by email and the ability to forward this to a specific 'updates' page to maintain an archive of this info would be welcome. I really am sceptical whether you are serious about better local integration. Given that the drop box never got out of beta kind of suggest to me pbwiki is not that interested. But as you say, people need to shout out if they want this. Here is another vote anyway.
Seanmac
1 person says
this answers the question
-
Inappropriate?The DropBox (coded by yours truly) was meant as a way to prototype desktop integration. While you're right that this incarnation didn't make it out of beta, that shouldn't be taken as a sign that PBwiki's uninterested. Quite to the contrary, we have a very aggressive plan this year for doing desktop integration, including the drop box.
In the interim, however, hearing about the right way to do email inbound would be helpful. For instance, what should the title of the page be for an attachment? The subject of the email? What if the page already exists? What if there are multiple attachments? Knowing how you would expect the tool to work will help us build it correctly. -
Inappropriate?I'm guessing that's the way a "2.0" wiki looks? Please tell me that there's a way to hide the IP addresses of contributors...
-
Inappropriate?For my $0.02 on the email-to-wiki facility, I'd see the subject line be the default wiki page title, with a simple renaming algorithm, perhaps the as used in various OS filesystems. The body of the message would be the wiki post -- perhaps it could handle HTML -- and any attachments to the email would get saved to "Files" and attached to the wiki page. Of course all normal input filters would apply, just like sending the content via web browser. In case of an error, a reply email might fire back with instructions on how to rectify the error (this could be the recourse in case of page name collisions too).
This could be made already, too, if someone sets up an extract-email script that then sends the content to the pbwiki API...
1 person says
this answers the question
-
Inappropriate?Hi,
My thoughts on it are slightly different. I use email in facilities for google docs and zoho writer and I would like a similar level of functionality. Here, the attached word document would be converted into a new page, the title of which would be extracted from the title of the document by default. If the page did already exist an email would be shot back to you say that there was a problem. If you wanted to append information to a page, you would specify the page name in the subject line and the contents of the email would be appended to the of the page. The details of person doing the appending would be presented adjacent ot it (say like a comment). I suppose I am envisaging a blog type format for appending. I don't agree that word files should saved to 'files' if they were attached. I'm not a big fan of having editable documents upload on to pbwiki. Nothing is stopping users form downloading the document, changing it and then uploading it. You have no way to track the changes and maintain versions as you would if you had to edit a pbwiki page. I have no problem with non editable attachments (eg pdfs) being uploaded to the files page.
Seanmac
I’m happy its Friday!
-
Inappropriate?Hey Seanmac,
Good points. I admit I'm a pbwiki newbie, but the behavior you describe seems to me counterintuitive. Whether or not editable docs can be uploaded into the files area depends on your usage -- in our private wiki most of our uploaded files are Word docs. Ideally, pbwiki would version the uploaded files too, like Basecamp does (iirc).
What would happen to embedded images or other embedded objects if the Word doc was to be converted to a wiki page? What about other non-MS formats such as those used for OpenOffice?
On the other hand, when people send something as an attachment, often the message body is mainly a comment about the attachment, so maybe what you're describing would be a viable route.
On the other other hand if you're opening up an email client to send a post, and you didn't want the attachment saved as an uploaded file, why couldn't you just copy-paste into the email?
Part of my input is an attempt to address David's rightful questions about dealing with page name collisions. Some of these things could be dealt with via configuration options (Attachment handling options, page name collisions) and/or variant addresses: post@mywiki.pbwiki.com, comment@mywiki.pbwiki.com, upload@mywiki.pbwiki.com.
1 person says
this answers the question
-
Inappropriate?I would love to see this functionality. I post to my blog this way from my blackberry. I take a picture, write my text as the subject line and it appears as a posting. This is one of the main reasons I have favored blog use over pbwiki up to now. I would come running back to pbwiki if I could do this because the rest of your features are so rich.
-
Inappropriate?Maybe I'm not understanding this functionality because it doesn't sound very collaborative. If you want a blog, use a blog. Is anyone using PBWiki as a blog? Why?
-
Inappropriate?JotSpot used to have a working implementation of this feature. Their solution was to assign each page a unique email address (e.g. wikipage+authentication_code@your.domain) and treat the whole thing as similar to a wiki comment. So the email message (an any attachments) would be appended to the page rather than replacing existing content.
Sounds like a reasonable model to me. No risk of data loss, and dead simple to contribute content. It'd be very useful for intranet-ish activities (e.g. keeping track of decisions, historical reference, file archiving, etc.) as long as users only need to be contributing to a handful of pages each. There's a practical limit to how many pages' email addresses they can reasonably juggle. 3? 5? I'd guess somewhere in that range.
1 person says
this answers the question
-
Sorry, should have included a reference URL so you can visualize it better. http://209.85.173.104/search?q=cache:mOVOmn3EW_kJ:feedback.jot.com/WikiHome/JotDoc/EmailToWikiEditPageDoc+jotspot+email+to+wiki&hl=en&ct=clnk&cd=4&gl=us -
Inappropriate?Here are two more implementations that could be models.
Not built-in, but there's a MediaWiki plugin http://www.mediawiki.org/wiki/Extensi... that accepts page appends via email e.g. pagename@your.domain
SocialText just says their wiki pages also accept content by mail. <http://www.socialtext.com/products/fe...>. Not clear what scheme to determine where a message goes, and whether they treat that as an append or a replace. Anyone else know how they've chosen to handle it?
Add my vote for an email to wiki feature. Very useful to have something like this!
I’m curious why more wikis don't have it
1 person says
this answers the question
-
Inappropriate?I second the motion that updating via email would be grand.
The way I would want to use it is send an email to <wikiname><current name="true">@pbwiki.com with subject name <new name="true">.
After uploading, a link would appear on <current> (a page that has already been created in PbWiki) that would like to a newly created page named <new name="true"> (the subject from the email). This page would contain the body of the email as well as any attachments.
Would be killer for me.</new></current></new></current></wikiname>
I’m happy to be back and commenting here.
-
Inappropriate?I wrote a little program that will automatically create or update pbwiki pages via e-mail or local files. I wrote this because it was tedious to make changes to MS Word and Excel files and then have to upload the revised file to my wiki every time I made a small change. I also wanted to add e-mail integration to make it easier for people to add content.
You need to have a v1.0 pbwiki site and an API key from PBWiki to use this program. It seems to work okay with my private v1.0 wiki, but won't work with a 2.0 wiki. You can download a Windows program or a perl script if you want it to work with other operating systems.
See http://fredwiki2.pbwiki.com/pbwiki-Au... to get more information.
This is really just a first attempt. It works for me, but there may be bugs so please be cautious. If you find a problem, you can let me know and I will attempt to fix it.
- Andrew -
Thanks. I have a 2.0 so I'm out of luck. Nice work though! -
I was under the impression that the v2.0 API was read-only, but that is not the case. I will work on updating the script to be able to work with v2.0 wikis. There are still important parts of the 2.0 API that are not yet implemented such as PutFile and DeleteFile, but the e-mail integration parts should be possible to write. -
Inappropriate?Andrew,
I'm liking this, I'm liking this a lot. But .....I can't get it to work. Here is the content of my config file (with some of the content occluded)
PBWiki Auto Update Configuration File
************************************************************************
Wiki Name: "oncallwikitest"
API key: "d2e4ee6eb8286de4a6494032115axxxxxxxxxxxx"
Wiki Content File Name = "wikiContent.txt"
Verbose Mode: "1"
Debug Mode: "0"
************************************************************************
C:\Documents and Settings\Admin\Desktop\Pbwiki\Autoupdate datedesc
XXXXXXXXXX@yahoo.co.uk XXXXXX pop.mail.yahoo.co.uk 1
I'n running XP here. By the way is this secure? I just thought I could be sending someone the password to my email address!! Are you planning to tweak it for 2.0?
Cheers,
Seanmac
I’m happy and sad!
-
Try replacing the 1 with a 0 at the end of the email configuration line. It appears as though your e-mail provider doesn't use SSL: http://help.yahoo.com/l/uk/yahoo/mail/yahoomail/pop/pop-06.html Please let me know how you make out. I am not an expert on security, but with the exception of having a file on your computer containing your e-mail password, I don't think you are exposing yourself to any more risk than using MS Outlook. Someone more knowledgeable may need to comment. -
Andrew, I changed the SSL config. No difference. I also tried my gmail account and I get the same message 'Can't open directory xxxxxxxxxx@googlemail.com xxxxxx pop.googlemail.com 1' -
The error message means it doesn't realize you have provided an e-mail address. My only thought would be to make sure you have downloaded the v0.2 program and make sure you have tabs in between each piece of data. -
The tabs were misalligned so sorted that out....but I'm getting a new message now! 'PBwikiAutoUpdate+v0.2.exe - Unable to locate component .....The application has failed to start because LIBEAY32.dll was not found. Reinstalling the application may help fix the problem.' Reinstalled version 0.2 but to no avail! -
Okay, that was already installed on my PC. I will do some more development and come out with v0.21 that includes that dll in the program file. Sorry for the inconvenience and thank you for trying it out. I'll post back when I fix that problem.
Loading Profile...





EMPLOYEE
EMPLOYEE






