Loading...
 

 Note

This page is to document "what Tiki should do". For feature documentation (what Tiki does), please see corresponding page on doc site
using email to add articles and edit wiki pages Type of page »  Feature page

Mail-in

Mail-in Revamp in trunk (12 SVN)

The new things include

  • Structure routing. Link mailed-in content to a structure. User filters specify routing rules.
  • Inline images (HTML email). These pages are written in HTML.
  • Permission checking. There was previously no permission checking!
  • Possible to auto-assign new pages to a category
  • Manual check trigger in the mail-in admin panel
  • Limit admins mail-in permissions
  • Possible to force HTML email stored in HTML format
  • Several fixes, including subject encoding


Mail-in requires a dedicated POP3 account.
A mail download can be scheduled (e.g. every 30 minutes) or done manually.

Users are required to have both edit and attach permissions to save a wiki page.

New permission: tiki_p_send_mailin
Can send email to a mail-in accounts, and have the email integrated. Only applies when the mail-in setting "anonymous" = n (tiki_p_send_mailin)

The new permission tiki_p_send_mailin is used to limit who can mail-in web pages (must have edit and attach permissions additionally).

The option "Keep HTML format" will for HTML email, write the wiki page in HTML format, regardless of editor availability and selection. This may make it difficult to edit such pages, if in wiki mode and no HTML editor is activated. However, the visual reproduction is much better in HTML.

The wishlist below should be rechecked.

Structure Routing

Each user can define a set of "structure routes" for mailed-in content.

In the example below, all email sent in by the user containing the word "gmail" (case insensitive comparison), will be routed to the root node of the s
astruct. (
= namespace separator)

Mail In Capture 20130625050007 821 0.png
The parent page must be located in the selected structure. If specified, the mailed-in page will be listed as the first child node.

Note that the "edit structure" permission is required, on the target structure, to add a page. Thus the user mailing in the new page, must have this permission to have the page processed. If the structure is linked to a category, the "edit structure" permission must be granted at category level.

Validated email clients

Setting up mail-in

First make sure that the interaction with the email server works.
"Allow anonymous access" will disable all permission checking. This is useful when first setting up mail-in.
You usually want to disable "Allow anonymous access" afterwards.

The adjust the mail-in security settings
You may consider disabling "Allow admin access".

Possible permission setup

  1. Create a mail-in category, and a mail-in group
  2. Mark mail-in category as auto assigned the mail-in admin panel.
  3. Allow the mail-in group the following permissions on the mail-in category: "view page", "edit page", "can view attachments" and "attach to wiki".
    1. Note: If structure routing is enabled, the mail-in group also needs the "edit structure" permission on the target structure.
  4. Assign the global "mailing send" permission to the mail-in group.


Users assigned to the mail-in group should then be able to create wiki pages from email.

Wishes

Related links

Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Accounting 7.x
Administration
Ajax 2.x
Articles & Submissions
Backlinks
Banner
Batch 6.x
BigBlueButton audio/video/chat/screensharing (5.x)
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Comment
Communication Center
Consistency
Contacts Address book
Contact us
Content template
Contribution 2.x
Cookie
Copyright
Credits 6.x
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Docs 8.x
DogFood
Draw 7.x
Dynamic Content
Preferences
Dynamic Variable
External Authentication
FAQ
Featured links
Feeds (RSS)
File Gallery
Forum
Friendship Network (Community)
Group
Help
History
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
jQuery
Kaltura video management
Karma
Live Support
Logs (system & action)
Lost edit protection
Mail-in
Map
Menu
Meta Tag
Missing features
Visual Mapping 3.x
Mobile Tiki and Voice Tiki
Mods
Modules
MultiTiki
MyTiki
Newsletter
Notepad
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Payment 5.x
Performance Speed / Load / Compression / Cache
Permission
Poll
Profiles
Quiz
Rating
Realname
Report
Revision Approval
Score
Search engine optimization (SEO)
Search
Security
Semantic links 3.x
Share
Shopping Cart 5.x
Shoutbox
Site Identity
Slideshow
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Staging and Approval
Stats
Survey
Syntax Highlighter (Codemirror)
Tablesorter
Tags 2.x
Task
Tell a Friend, alert + Social Bookmarking
Terms and Conditions
Theme
TikiTests 2.x
Timesheet
Token Access
Toolbar (Quicktags)
Tours
Trackers
TRIM
User Administration
User Files
User Menu
Watch
WebHelp
Webmail and Groupmail
WebServices 3.x
Wiki 3D
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives 4.x
WYSIWTSN 4.x
WYSIWYCA
WYSIWYG 2.x
XMLRPC




Useful Tools