Category: Mail-in

We can already send in content to Tiki via email:

add/edit wiki
add articles
via tiki-admin_mailin.php

and add forum posts via
tiki-admin_forums.php

I would like to be able to add tracker items or a newsletter via email.

Related: http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=999

An email message hasn't integrated into the forum. Tho forum posting is just empty. I'll attach a zip with the original message.

Setup:
1) Create a new forum
2) Enable the post-by-email function (and create the associated email address)
3) Send an email post
4) Send a second identical post
5) Attempt to visit the forum - denied

We use one of our Tiki forums to archive contents from a mailing list - we have a dedicated address which is enrolled in said (external) list. This normally works great, except we were unable to visit the specific forum recently - the error message notified us that duplicate name and content posts were prohibited. It turns out the mailing list sends out regular (monthly) notifications which happen to be identical. It seems that that the POP server is polled when the forum is accessed - the message is obtained, and the post attempt it denied, and effectively locks the user out of the forum.

Verified on the opensourcecms 1.9.11 demo site.

When using the Mail-In feature with Articles, Tiki places the entire email in the article's Header. I would like a way to specify portions of the email to placed in the article's header, the rest in the Article body. Perhaps by some sort of text marker?

When a new user register, the admin receives an email notification with two links. One for validating the registration, one for assigning the new user to groups.

The first link is fine, but the second one only works if Tiki is installed in a subdirectory 'tiki' of the apache root. But Tiki may be installed anywhere. In my case, I installed it under a subdirectory 'tw' of the apache root. And lots of folks install it at the root of the apache server itself.

Below is an example of such a mail message.

>> -----Original Message-----
>> From: alain.desilets@nrc-cnrc.gc.ca [mailto:alain.desilets@nrc-
>> cnrc.gc.ca]
>> Sent: October 16, 2009 6:27 PM
>> To: Desilets, Alain
>> Subject: User Registration Request
>>
>> Hi,
>>
>> alain_desilets <alain.desilets@nrc-cnrc.gc.ca> has requested an
>> account on rte-nte.notrewiki.net
>>
>>
>> To validate that account, please follow the link:
>> http://rte-nte.notrewiki.net/tw/tiki-
>> login_validate.php?user=alain_desilets&pass=e1c159c6d72116808b642e2c0
>> 63
>> ffa73
>>
>> Assign to a group: http://rte-nte.notrewiki.net/tiki/tiki-
>> assignuser.php?assign_user=alain_desilets
>>
>>
>> Best regards
>>
>>
>
>

The registration email seems to give boxed char when mail templates are in french.

I had to add utf8_encode()
to LINE 2727 of lib/userslib.php
$mail_data = utf8_encode($smarty->fetch("mail/$mailTemplate.tpl"));
in order to correct the text display problem.


But when I debug with
$mail_data = mb_detect_encoding($smarty->fetch("mail/$mailTemplate.tpl"));

It return the tpl as already in UTF-8, but I had to utf-8 it again to correct it, can someone look into this?

Currently, (2.2) when using the mailin feature to post to a forum, Tiki does not actually check the email until a user views the forum. Only then, is the email checked and new messages posted to the forum.

This means that the RSS feed for the forums, and modules such as last_post will not be correct until a user goes to the forum.

Instead, Tiki should check the email at regular intervals (in the same way that Tiki checks for article mail-ins.

When forwarding messages to a pop "mail-in" account, the forum title is prefixed with "FW: "

Contributors

I configured the mail-in service for the wiki,I tried with wiki-append, wiki,... configuration but the mail-in doesn't work as aspected. The page, if needed, is created but the body is not updated

I tried with outlook 2003 from the local intranet and also from the web interface of GMail.

thanks
Christian

The mail-in functionality is great, but provides no security when in "non anonymous" mode. I consider this a bug, as the docs say nothing about user permissions not being applicable with mail-in. Examples:

1. Users that are in a group that cannot post may add or append via mail-in
2. Users that cannot see pages in a particular category can do a GET

This is a serious security problem - I'm glad I tested as I had no idea?

Any way to add permission checking to the mail-in code? It seems like it would be easy for someone who knows how to do it.

I realize it can't be 100 percent secure - someone could always spoof an email sender.

We can already send in content to Tiki via email:

add/edit wiki
add articles
via tiki-admin_mailin.php

and add forum posts via
tiki-admin_forums.php


joe@joe.com sends an email. The system recognizes that joe@joe.com belongs to the user "joe" and adds the tracker/wiki edit/forum post/article as if the user joe had logged in and added it via the web form.


Make this optional for security reasons. If someone spoofs the email address, he could send in content for someone else.

Hi:

I want to allow users to send photo moblog posts to our Articles section. After setting up an "Article-Put" account, I'm finding that only the text makes it into the article post, not the attached image file. Just to test, I set up a "Wiki-Put" account, and it DOES recognize and include the attachment (not inline, though, but as an icon and a link).

Does the Article-Put feature have handling for including images inline?

Rob

In my installation, I've tested sending tes

I'd like to have a way to comment on an item from GET by replying to it.

For example, right now an email with the subject:

GET:BigIdea

will send the user the BigIdea page.

A reply with the subject:

RE:GET:BigIdea

would generates a comment on the BigIdea page.

This use is different from appending or prepending. It's meant for a note in the margin not a modification of the original text.

I am using tikiwiki for a project at work, and one of the features we needed was the "mail-in" forum posting. The way we use this is a sales rep will e-mail an issue to a PDL. One of the e-mail addresses in the PDL is the pop account for one of the forums for our site. The site moderator reads the new "post" (e-mail) and decides which forum the discussion belongs in and moves the post to the "correct" forum.

The problem is that once moved, replies via the PDL do not follow the original thread (to the moved forum). The best case is that they end up in the "mail-in" forum location.

i'm still tracking this down and i hope someone might have a ready answer since i'm new to tikiwiki.

i created a mail-in account to use Google's Gmail for POP since our IT department does not support POP from Exchange. the Gmail account uses port 995 for POP connections rather than the standard port 110. the account data was stored correctly in mySQL database but when tikiwiki attempts to read mail it fails citing a timeout on the gmail IP and port 110 as shown below:

PHP (5.2.3) ERROR (E_WARNING):
File: Socket.php
Line: 136
Type: fsockopen() [function.fsockopen]: unable to connect to 209.85.133.109:110 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. )

i have not yet found where the call to lib\pear\Net\Socket.php is made and will hopefully update this later with the information.

Using the tiki-mailin feature (for Wiki-Put or Article-Put), I consistently see right after the body tag, a PHP message showing me the array being populated. This happens whether or not there's an error in the posting itself.

Can someone explain why this is happening?

Source of example is attached. (@@@ indicates prvate information). Thanks.

Is it possible to give a checkbox or setting to turn this off?

In 1.8.5, the mailin feature doesn't work properly. It may work for some combination of mail systems, but not for others. And it does not properly handle multiple mailed-in messages when a page load is attempted.

Specifically, some combination of mail client and mail server caused the email address extraction to leave a newline on the end, which should be trimmed.

Also, in determining the type of message, a case-sensitive string comparison is done against "text/html", which won't match for upper or mixed-case.

Finally, there's a bug (probably a minor design flaw) in the way the histlib object is created in lib/tikilib.php, such that if the code is executed twice in the same session, it will fail the second time because the $histlib object isn't created.

Last but not least, after parsing the message, if there are no parts found, the loop that attempts to process them assumes that $output->parts exists, which it may not.