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.
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.
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
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
- Create a mail-in category, and a mail-in group
- Mark mail-in category as auto assigned the mail-in admin panel.
- Allow the mail-in group the following permissions on the mail-in category: "view page", "edit page", "can view attachments" and "attach to wiki".
- Note: If structure routing is enabled, the mail-in group also needs the "edit structure" permission on the target structure.
- 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.