Site Root

Wiki: Telligent Evolution Platform and Applications Documentation

Anonymous — Thu, 18 Mar 2010 02:47:00 GMT

Wiki: Developer Documentation

Anonymous — Wed, 17 Mar 2010 23:24:00 GMT

Wiki: Community Server 2008 Documentation

Anonymous — Wed, 17 Mar 2010 22:08:00 GMT

Community Server 2008 Product Documentation.

Forum Post: CS 2007.1 to CS2008.5 Upgrade Issue

jstengel — Wed, 17 Mar 2010 21:51:00 GMT

"The ConnectionString property has not been initialized."

This is the message I get from the upgrade tool when I select the CS folder to be upgraded. I get that this is the part where it tries to hook into the database, but I've verified the connectionstring and can't seem to figure out what's going on. Am I missing an incremental upgrade or something?

Wiki Page: Customization Guide

Jenny Jarrard — Wed, 17 Mar 2010 21:47:00 GMT

In this Customization Guide, we cover everything that you need to know to customize your community built on the Telligent Evolution platform. This guide contains the following sections:

NEW in Telligent Evolution release 5.5: The following types of enhancements are included:

Greatly increased Quick Post functionality
Ability to pull feed from multiple sources for "mashups"
Searching and accessing content is now possible from other groups or their applications
Enhanced capability for administrators (such as saving a tab for themselves, even if the content on it is locked)

This section contains the following subsections:

Customize with themes - Use our out-of-the-box themes to guide your style decisions, or customize both the content and appearance using tab additions, layout, and CSS theme customization. Import and export themes to other sites in your community.
Customize with widgets - Create smart user Dashboard/Home Pages by adding widgets that furnish specific useful information, or allow users to select their own options from widgets that feed posts (blog, wiki, forum, media, unfiltered HTML); supply or respond to messages, and empower collaborative relationships.
Customize your pages - Enable or disable a customization mode for users to create personal page layouts, or promote your community's brand with uniform widgets, layout, advertisements, and tabs.
[[Email-templates-tokens|Email templates' tokens]] - Customize the look of emails sent to users, as well as the information they contain.
Markup information - Utilize our specifications for provided themes; our style markup guide, and CSS targeting information to style a widget, page region, all area within a page, or combine the style selectors in expressions.

Forum Post: Re: download Enterprise Search

M.kavyani — Wed, 17 Mar 2010 21:27:00 GMT

Me tooo :-((((

Wiki Page: Install a new community

Jenny Jarrard — Wed, 17 Mar 2010 21:13:00 GMT

Unzip and copy the installation package
Set up the Web server
Set up the database
Connect the Web site and database
Set up search
Connect the Web site to search
Enable attachment indexing
Install additional IFilters to index additional attachment types
Optional components

Note: Part of this procedure, setting up search, is required for Telligent Evolution version 5.5 in order to utilize its full capabilities. Search is an optional installation for Telligent Evolution version 5.1.

Unzip and copy the installation package

Download the latest version of Telligent Community or Telligent Enterprise from http://telligent.com/resources/m/product_downloads/.
Note: If you downloaded the file using Internet Explorer, you may need to first right-click the.zip file and select Properties. Click Unblock if the option is available and click OK to close the Properties window.
Extract the contents of the download to a temporary location on your hard drive (e.g.,D:\inetpub\TempFolderUnzipBuild\ ). Note: In our examples, we show the c:\ drive because it's a sample installation. However in a real production environment, Telligent strongly recommends that you do not place the software on a system drive unless you must due to security and performance reasons; a system drive should not be subjected to application stress.

Set up the Web server

Create a Web directory folder and copy the files there.
1. Create a path to hold the Telligent Evolution Web site (e.g.,D:\inetpub\TelligentEvolution55\).
2. In the extracted .zip file folder, copy all of the zip file's web folder contents and paste them into the server's directory folder, leaving the directory structure intact.
Note: Carefully check that the folders in both locations contain the same files. A quick way to check is by comparing the temporary unzip folder's web folder files and folder data with theD:\inetpub\TelligentEvolution55\ properties.
Create a new application pool. (If using Windows XP for development purposes, skip this step.)
Note: These instructions assume you're running IIS7. If you’re using IIS6, see the Microsoft documentation.
1. Open Internet Information Services (IIS) Manager.
2. If required, connect to your Web server.
3. In the Connections pane on the right, expand your Web server.
4. Right-click Application Pools and select Add Application Pool.
5. Specify a name for your application pool.
6. Ensure that the .Net framework version selected is v.2.0.x. Note: To ensure that your IIS instance is configured to run ASP.NET applications in Windows Server 2008, find this information under application development in Role Services.
7. Click OK.
Create the IIS application.
1. In IIS's left pane, navigate to Internet Information Services > [computer name] > Web Sites > Default Web Site.
  1. Right-click Default Web Site, select New from the menu, then select Add Application.
  2. The Add Application window appears.
  3. Do the following:
    - Enter a name in the alias field (example: TelligentEvolution55).
    - Enter the path you created in Step 1 in the Physical path field (example:(D:\inetpub\TelligentEvolution55, or whatever path you created in Step 1).
    - Ensure that the selected application pool is the same one you created in Step 2.
  4. Click OK in Add Application window.
Determine your Web site service account. This account will be needed for granting permissions in the next step and in the Database section. (Note: Bear in mind that the service account differs for Windows XP, Windows Server, Windows Vista, and Windows 7.)
- If using Windows XP for development purposes, your service account is ASPNET.
- If using Windows Server 2003 or Window Server 2003 R2, your service account is NETWORK SERVICE.
- If using Windows Server 2008, Vista or higher, follow these steps to find the service account that your Web service is running under:
  1. Open IIS Manager and navigate to Application Pools.
  2. Use the value of the identity column to determine your Web site service account.
    - LocalService - NT AUTHORITY\LOCAL SERVICE
    - LocalSystem - NT AUTHORITY\SYSTEM
    - NetworkService - NT AUTHORITY\NETWORK SERVICE
    - ApplicationPoolIdentity - IIS APPPOOL\<app pool name>
    - OTHER - runs as the specified user
Add the network service user to the permission structure. Then grant the Web site service account required file and folder permissions: read permissions to the web directory (which is the main directory for IIS) and modify permissions for /filestorage/ and its subfolders.
Note: Although be default the filestorage folder is placed in the Telligent Evolution package's web folder, Telligent recommends that you do not place it in this direct access location to your site's root folder. Instead, make a separate filestorage folder that is outside the path: For example, haved:\Sites\YourCommunitySite\Web (where IIS points) andD:\Sites\YourCommunitySite\filestorage. Additionally, IIS should not be allowed to execute files under the filestorage folder. Microsoft has a document about disabling scripts for folders.
1. Right-click the Telligent Evolution platform Web site folder and select Properties.
2. Click the Security tab. (And if you are using Windows Server 2008 and above or Windows Vista and above, then click Edit.)
3. Click Add.
4. In the Enter the object names text box, type the name of the service account determined above and click Check Names. After the name resolves, click OK.
5. Ensure that the service account is selected in the top pane, and view the bottom Permissions pane to ensure that only the Read permission is granted.
6. Click OK. (If you are using Windows Server 2008 and higher or Vista and higher OS, click OK a second time.)
7. Repeat the above instructions, but this time assign rights for the filestorage folder instead of the Telligent Evolution platform Web site folder. In addition to Read, grant the service accountModify, Read & execute, List folder contents, and Write permissions.

Note: For further details on optimizing the performance of your Web server, see [[Web server and IIS configuration]].

Set up the database

Create a new database in SQL Server.
1. Open SQL Server Management Studio and connect to your database server with an account that has sysadmin or dbcreator fixed server privileges.
2. Right-click Databases and select New Database. The New Database window appears.
3. In the Database name field, enter a name for the database. (Example: _TelligentCommunity.) Try to make this name slightly different from the Web site's name. If needed, see Microsoft's instructional documentation for help.
4. Click OK.
Populate the database by executing the cs_CreateFullDatabase.sql script from the\SqlScripts\ folder of the install package.
1. In SQL Server Management Studio, navigate to File > Open > File. The Open File dialog window appears.
2. Navigate to the temporary location where you unzipped the installation package and within that folder, to SqlScripts.
3. Double-click cs_CreateFullDatabase.sql.
4. Select the database you created in step 1.
5. Execute the query against the database.
Create the community by executing the cs_System_CreateCommunity stored procedure.
1. In the SQL Server Management Studio toolbar, click New Query.
  
  This will open a blank tab in the right pane.
2. Copy and paste the following script verbatim in the new query tab.
```
EXECUTE[dbo].[cs_system_CreateCommunity]
    @SiteUrl = N'localhost/telligent_evolution' 
  , @ApplicationName = N'telligent_evolution' 
  , @AdminEmail = N'notset@localhost.com' 
  , @AdminUserName = N'admin' 
  , @AdminPassword = N'pa$$word' 
  , @PasswordFormat = 0 
  , @CreateSamples = 0
```
  where you specify the appropriate values for each parameter:
  - Site URL: The path to your site. This should be the same path you expect to access your community with (e.g., localhost/telligent_evolution as in the script above, or TelligentEvolution55 in the examples we've been using above).
  - Application name: Name of the application you created in IIS (e.g.,telligent_evolution or in the case of the examples we've been using above,TelligentEvolution55).
  - Administrator's email address: The email address of the administrator of the site. (optional)
  - Administrator's username: Login username for the administrator. You can leave this blank if you are running the application on your local PC on a limited basis. (optional)
  - Administrator's password: Default password for the administrator. You can set this to whatever you would like to use as the password for the administrative user (you can leave this blank if you are running the application on your local PC on a limited basis). We strongly recommend you do NOT use the default password in your live site. (optional)
  - Password format: 0 to store the password in the database in clear text. This can be changed to encrypt the password after it is created. (optional)
  - Create samples: 0 if you do NOT want sample content, 1 if you want sample content created in your community. (optional)
3. Select your database name from the database drop-down list on the toolbar.
4. Click Execute.
Note: Once you have created your community, we recommend you create a new administrator account and delete the one you created when setting up your community. This is to ensure that your administrator account's password is encrypted in the database. (While it is possible to encrypt the administrator account's password when you create the community, you need to provide the hashed password for the @AdminPassword parameter, which starts getting more complicated than it's worth given the easy workaround.)
Create a login for Telligent Evolution to use for accessing the database.
1. In SQL Server's Object Explorer pane on the left-hand side, expand the Security folder, then right-click Logins and select Add new login.
2. If you want Telligent Evolution to connect to the database via Windows authentication, selectGeneral and then specify the login name as the username of the service account user determined above. If you want Telligent Evolution to connect to the database using SQL authentication, then specify any username in the Login name text box. Now click OK.
  Note: We reccomend using Windows authentication.
  Note: If you want to use untrusted users, make sure your SQL server supports mixed-mode authentication.
3. Click OK.
Grant the login access to the Telligent Evolution database.
1. In the Object Explorer, expand your database, expand Security, right-click Users, and selectNew User.
2. In the User name and Login name fields, enter the name of the login you created in step 4.
3. In the bottom (Database role membership) pane, ensure only the following roles are checked:
  - aspnet_Memberhsip_FullAccess
  - aspnet_Profile_FullAccess
  - db_datareader
  - db_datawriter
  - db_ddladmin
  - db_securityadmin
4. Then click OK.

Note: For further details on optimizing the performance of your database server, see [[Database Configuration]] and [[Database Maintenance]].

Connect the Web site and database

Update connectionstrings.config in the Web site to point to your new database.
Note: For assistance with connection strings, you can refer to http://connectionstrings.com. (Telligent has no affiliation with the site.)
1. Open the connectionstrings.config file in your Web site, and update the SiteSqlServerentry to point to the database you created above.
- If using Windows authentication to connect to the database, the connection string should look something like:
```
<add name="SiteSqlServer"
     connectionString="server=SERVERNAME;database=DATABASENAME;Trusted_Connection=yes;"
     />
```
- If using SQL authentication, the connection string should look something like:
```
<add name="SiteSqlServer"
     connectionString="server=SERVERNAME;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=yes;"
     />
```
- If you're using SQL Express for development purposes, the SERVERNAME in the connection string may be (local)\SQLExpress as opposed to just (local).
```
<add name="SiteSqlServer"
     connectionString="server=(local)\SQLExpress;database=DATABASENAME;Trusted_Connection=yes;"
     />
<add name="SiteSqlServer"
     connectionString="server=(local)\SQLExpress;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=yes;"
     />
```
Check that you can access your Telligent home page.
1. Open your Telligent URL.
2. Check that the home page successfully loads without error.
3. If an error occurs, check that you've followed the above steps correctly.
Note: This should only be a quick test - any functionality that requires search will not work yet.

Set up search

In Telligent Evolution release 5.1 (5.0 SP1), installing search is optional if you have implemented your own search provider. However, most installations do not have an instated provider, so search will need to be installed. With Telligent Evolution release 5.5, many capabilities are leveraged on this application, so it does need to be installed.

Install Java on the search server.
1. Test whether Java is already installed by viewinghttp://java.com/en/download/help/testvm.xml on the search server. In Telligent Evolution, search requires at least version 6 update 13. If your installation meets this requirement, skip to the Install Tomcat step below.
  - If you're using a 64-bit operating system, you must view this test page in a 64-bit browser (such as Internet Explorer 64-bit edition which comes pre-installed on all 64-bit versions of Windows).
2. Download the latest version of java from http://java.com/en/download/index.jsp.
Install Tomcat.
1. Download version 6 of the Tomcat Windows Service Installer from Apache.
2. Open the installer and follow it through, taking note of the following:
  1. In the Choose Components window, ensure you have selected the the Tomcat > Service and Tomcat > Native options.
  2. In the Choose Install Location window, make a note of the installation directory - this will be needed in the next step.
3. Update Tomcat to support UTF8 characters:
  1. Open the /conf/server.xml file in the installation directory you selected in step b.B.
  2. Find the appropriate <Connector /> element in the server.xml file, and add the attribute URIEncoding="UTF-8"
    <Server ...>
    <Service ...>
    <Connector ... URIEncoding="UTF-8"/>
    ...
    </Connector>
    </Service>
    </Server>
4. Test that Tomcat is installed correctly by navigating to http://localhost:8080/.
Install Solr.
Note: If you want to run multiple Telligent communities from the same search server, follow the instructions at Host multiple Telligent Evolution communities on multiple Solr instances instead.
1. Copy the Solr folder in the /Search/ directory of the Telligent Evolution install files to the root directory of Apache Tomcat.
2. Copy the solr.war file in this folder to the /webapps directory of Apache Tomcat.
3. Navigate to the Solr administration page (http://localhost:8080/solr/admin) to verify that the installation was successful.

Note: Solr runs very well as it's configured out of the box. But if you have a medium- to large-sized community, you should increase the memory allocated to the Java virtual machine (JVM). The default allocated memory is 64MB. You should consider giving it 512MB or more.
To increase the memory for the JVM:

Right-click the Tomcat Manager in the system tray and select Configure.
Select the Java tab.
Set the Maximum memory pool size (in MB) that you want to allocate to the JVM.

Connect Web site to search

Important: Solr should never be accessible to the public. Ensure that neither the Tomcat home page nor the Solr home page is publicly accessible . If this endpoint is accessible, work with your IT department or read [[Securing Solr on Tomcat]] for more details on blocking this endpoint from the public.
Ensure that all Web servers can access the Solr home page by opening to the Solr home page on each server ( e.g., http://servername:8080/solr/ ).
Configure Telligent Evolution to use your Solr URL:
1. Download the following communityserver_override.config file.
2. Place this file in the root of your Web site directory.
3. Find the following section in the communityserver_override.config file and replace the highlighted URL with the URL to your Solr instance.
```
<Override xpath="/CommunityServer/Search/Solr"  
          mode="change"
          name="host"
          value="http://yourserver:XXXX/PathToSolr/"
          />
```
Note: This URL is case-sensitive.

Note: If you have any issues with search, see [[troubleshoot-search-errors|troubleshoot search errors]].

Enable attachment indexing

On the server that is running the Telligent Tasks, install either the Windows search service or indexing service depending on your operating system.

Window Server 2008 / Windows Server 2008 R2 - Install the Windows search service
1. Open the Server Manager: Navigate to Start > Run > ServerManager.msc.
2. In the Services tab, click Roles in the left pane and select Add Roles from the Roles Summary window. Alternatively, you can click the Action menu option and select Add Roles.
3. Continue with wizard and select the File Services check box. Click Next.
4. If not already checked, select the Windows Search Service check box and click Next. Note: If either Windows Search Service or Indexing Service (under the Windows Server 2003 File Services) was already checked, you can cancel the installation; one of the necessary services is already installed.
  
  In the next option window, Select Volumes to Index for Windows Search Service. You do not need to select a volume. Click Next.
5. Click Install.
Windows Server 2003 / Windows Server 2003 R2 - Install the Indexing Service
1. Navigate to the Windows Control Panel and select Add/Remove Programs.
2. Select Add/Remove Windows Components from the left pane of the Add/Remove window.
3. If not already checked, select the Indexing Service check box and click Next to install. Note: If the check box was already checked, this indicates the service is already installed - so you can cancel the installation.
Windows Vista / Windows 7 - Ensure the Windows search service is installed
1. Navigate to the Control Panel, click Programs, and then click Turn Windows features on or off.
2. If not already checked, select the Windows Search check box and click OK. Note: If the check box was already checked, you can cancel the installation; the service is already installed.

Install additional IFilters to index additional attachment types

By default, Windows includes IFilters to extract textual content from uploaded files (such as media gallery files, blog post attachments and forum post attachments). However additional IFilters may be installed to index content from additional file types. Telligent recommends that you install the following additional IFilters:

Office 2007 Filter Pack - http://www.microsoft.com/downloads/details.aspx?familyid=60c92a37-719c-4077-b5c6-cac34f4227cc&displaylang=en
PDF documents
- 32-bit server - Adobe Reader
- 64-bit server - Adobe's PDF iFilter 9

Optional components

Now that you've installed the Telligent Evolution platform, you may install additional optional components:

Mail Gateway
LDAP Integration (Telligent Enterprise only)
Sharepoint Integration (Telligent Enterprise only)

Wiki Page: Mail Gateway Account Types

Josh Ledgard — Wed, 17 Mar 2010 19:50:00 GMT

A mail gateway allows you to route all mail through your own network. Below is a description of the Evolution mail gateway.

Mailbox

A mailbox in Mail Gateway is where messages bound for the Evolution site are downloaded. Emails are delivered to the mailbox by the mail server and Mail Gateway downloads the messages to the mailbox, and then processes them for the Evolution site.

You can define multiple mailboxes. You will want to add a mailbox where messages for Mail Gateway are delivered. Mail Gateway assumes it owns the mailbox, which means it will download all messages in the mailbox and delete them when it is finished processing them. You cannot share a mailbox with another application or with a normal user.

Alias

An alias is a way of specifying another recipient for a mailbox. For instance, you could create a mailbox called cs@domain.com and an alias on the mailbox for forum1@domain.com. When the mail server receives an email for forum1@domain.com, it knows to put it in the mailbox for cs@domain.com.

Catch-all

A catch-all is another type of alias. It is a way of specifying that any email which is not directed to an already existing mailbox or alias should go to a predetermined mailbox. Using the alias example, you could create a mailbox called cs@domain.com and then specify that it is a catch-all. When an email is sent to forum1@domain.com, the mail server checks for a match with an existing mailbox. If it does not, then the mail server puts it into the cs@domain.com mailbox.

Aliases and catch-alls are preferred ways of setting up the email addresses for Mail Gateway because they can greatly cut down on the amount of administration that goes into creating a new forum. Catch-alls are preferable because when you create a new forum or set up another blog for blogging by email, you do not need to make any changes within the mail server, such as creating another mailbox or assigning a new alias.

When a catch-all or an alias is not used, you must create a mailbox for any new address, and you must add that mailbox and its credentials to the Email Settings page within the Control Panel.

If you want to use blogging-by-email, Telligent recommends using a catch-all. Blog-by-email addresses are randomly generated per-user and per-blog for security purposes. Because of this, using individual mailboxes or aliases can be difficult.

Aliases and Catch-alls with Exchange Server

When you use Exchange as your mail server, Telligent recommends that you not use aliases or catch-alls. Because of the way Exchange Server handles aliases, they are not compatible with Evolution.

For example, you could have a mailbox of cs@domain.com and alias of forum1@domain.com. When using a client like Outlook with Exchange, you can create a message and specify that it is to forum1@domain.com, but Outlook will check the recipient and notice it is an alias to cs@domain.com. As a result, it will change the recipient to cs@domain.com. The message will not end up with the intended address in the address line and it will be misaddressed when Community Server receives it.

When using Exchange, Telligent recommends creating separate mailboxes for each forum; or setting up an internal SMTP server using the IIS Virtual SMTP Server and having Exchange forward emails to recipients at that server.

Wiki Page: Configure the Mail Gateway Service

Josh Ledgard — Wed, 17 Mar 2010 19:49:00 GMT

You must configure the mail gateway before you can install the mail gateway service.

To install the Mail Gateway service:

Install the MSI and follow the instructions on the screen.
In the Mail Gateway installation directory, open the mailgateway.config file for editing to add the site settings so Mail Gateway can connect correctly.
In the <Sites> section, add your own entry similar to: <Site name="Short name" serviceURL="http://yoursite.com/utility/maildrop.asmx" passPhrase="remoteAccessCode" /> where:
1. Name: Unique short name for your site (e.g., "My CS Site")
2. serviceURL: Web service within Telligent Community
3. passPhrase: Remote access code specified in the Mail Gateway configuration within your Telligent Community site.
[optional parameters]
- username: a username to use if the site requires basic authentication
- password: the password for the basic authentication user
- useDefaultCredentials: an option to use the service identity for windows authentication sites.
- readFromDirectory: the path to a local SMTP mail-drop
Optionally, adjust the settings for how often Mail Gateway updates the site configuration and checks for messages:
1. updateConfigurationInterval: How often (time in minutes) the service checks the site's configuration for updates to list of mailboxes from which to download messages
2. pollMessagesInterval: How often (in minutes) Mail Gateway connects to the mailbox(es) to download messages to process
3. garbageInterval: We recommend that you do NOT change this setting. How often (in minutes) Mail Gateway performs clean-up operations to free memory.
4. statusInterval: How often (in minutes) Mail Gateway writes status messages to the log files, including basic information like memory usage.
Open the Services control panel and start the Telligent Mail Gateway service (which is configured to run automatically on server load). If you do not want this to run automatically, we recommend that you set the start-up type to Manual or Disabled.
Ensure that any email addresses you want to go to Telligent Community are configured to go to the proper mailbox on your server if using POP3 or IMAP. If you are using queue directory, ensure the emails are placed there. We recommend that you use a catch-all account (single mailbox that all messages which aren't tagged for a specific mailbox) so that when mailing lists are created or changed, you don't need to manually update the mail server as well and delivery failures are not sent back to the sender.
The service installs by default to "Log On As" the Network Service account; you will need to ensure this user has write permissions to the installation folder (e.g. c:\program files\telligent\mail gateway) so it can read the configuration files and write to its log. Also if using a local filesystem mail-drop, the Network Service user will need Modify permissions to that folder as well (e.g. c:\inetpub\mailroot\drop).
Ensure your email server is configured to handle the email.
Ensure that any email addresses you want to go to Community Server are configured to go to the proper email box on your server, if you are using Pop3 or Imap.
If you are using a queue directory, ensure the emails are placed there.
Telligent recommends that you use a catch all account so that when mailing lists are created or changed, you do not have to manually update the mail server as well. A catch all account is a generic mailbox to which all messages not addressed to a specific mailbox. We recommend you read this article about [[Mail Gateway Account Types]].

If you are using Microsoft Exchange we have an article on Configuring Microsoft Exchange for use with Mail Gateway.

Wiki Page: Install the Mail Gateway

Josh Ledgard — Wed, 17 Mar 2010 19:46:00 GMT

Before you install the Mail Gateway, you should have configured search.

We recommend that you configure Mail Gateway within your Telligent Evolution site before installing the Mail Gateway services.

To configure Mail Gateway in Telligent Evolution:

Enable email and Mail Gateway:
1. Navigate to Control Panel Dashboard > Site Administration > Setup > Email Settings.
2. Set Enable Email to Yes.
3. Specify your SMTP Server.
4. Set any SMTP login information in the SMTP Login Info section.
5. Set Enable Mail Gateway to Yes.
6. Specify the password that will be used to connect to the Mail Gateway service in Remote Access Code.
7. Specify the domain name that emails will be sent to and from (e.g., mysite.com or community.mysite.com) in Email Domain.
8. Add the POP3/IMAP information for the mailbox where Mail Gateway service is to download messages.
[[Configure the Mail Gateway Service]]
Create mailing lists for forums:
1. Navigate to Control Panel Dashboard > Forum Administration and choose the forum for which you want to create a mailing list.
2. Click Edit next to the forum.
3. Click the Mailing List tab.
4. Enable a mailing list for the forum by setting Enable as a mailing list to Yes.
5. Specify the email address the mailing list will use in List Email Address. The domain name you specified when enabling Mail Gateway is used here.
6. We recommend that you specify the Mailing list name that is shown in the subject line of every email sent to and from this forum, but it is not required.
7. We recommend that you specify text that is appended to the end of email messages sent from this forum in Email Footer, but it is not required.
8. Click Save. It may take up to 15 minutes for the settings to take effect due to caching.

Related information

Email integration

List of replacement tokens

Configure a Mail Gateway mailbox

Emailing new user registration acceptance links

Wiki Page: Mail Gateway

Josh Ledgard — Wed, 17 Mar 2010 19:40:00 GMT

Telligent Evolution provides a rich Web experience that allows you to use interact online with forums, blogs, files, and wikis using a rich text editor. To increase participation in your community and to increase your community's productivity, you can enable notifications and forum posts to be delivered to community members via email by installing Telligent Evolution Mail Gateway. The Mail Gateway manages queuing and sending all emails from and to the Telligent Evolution application.

With Mail Gateway installed, community members can reply to forum posts directly in their email program (all email interactions with forums are captured onsite as well).

You can set Telligent Evolution to use Mail Gateway through the Telligent Evolution Control Panel. Then all you have to do is install Mail Gateway Services.

If you need to install support for Mail Gateway in Microsoft Exchange please click here.

Wiki Page: The user invitation token

Jenny Jarrard — Wed, 17 Mar 2010 19:36:00 GMT

$invitation.Email - string - Email of the person being invited.
$invitation.DateInvited - DateTime - Date the invitation was made.
$invitation.Message - string - Message sent to the invitee
$invitation.InvitationKey - Guid - Unique key representing this invitation.
$invitation.Group - [[The-group-token|Group]] - Group the invitation is to (if applicable).
$invitation.Section - [[The-section-token|Section]] - Section the invitation is to (if applicable).

Wiki Page: The reply message token

Jenny Jarrard — Wed, 17 Mar 2010 19:35:00 GMT

$reply.Parent - [[The-message-token|Message]] - The original message in the message thread.
$reply.Author - User - Author of the message.
$reply.Subject - string - Subject of the message.
$reply.Body - string - Body of the message.
$reply.DateCreated - DateTime - Date the message was created.

Wiki Page: The post token

Jenny Jarrard — Wed, 17 Mar 2010 19:35:00 GMT

$post.ApplicationType - string - "Weblog", "Forum", "Gallery", or "Wiki".
$post.Body - string - The main body of the message.
$post.PostDate - DateTime - The time when the post was created.
$post.PostType - string - "Text", "HTML", "XML", or "All".
$post.Section - [[The-section-token|Section]] - The blog, forum, media gallery, or wiki the post is in.
$post.Subject - string - The subject of the message.
$post.Uri - string - The Web address of the post.
$post.User - [[The-user-token|User]] - The user sending the message.

Wiki Page: The group token

Jenny Jarrard — Wed, 17 Mar 2010 19:34:00 GMT

$group.AvatarUrl - string - URL to the group's avatar.
$group.DateCreated - DateTime - Date the group was created.
$group.GroupPath - string - Path to group from site root.
$group.Name - string - Name of the group.
$group.ParentGroup - [[The -group-token|Group]] - Parent group.
$group.SubGroups - [[The-group-token|Group Collection]] - List of subgroups.
$group.Tags - string Array - Tags for the group.
$group.TotalMembers - int - Number of members in the group.

Wiki Page: The profile message token

Jenny Jarrard — Wed, 17 Mar 2010 19:34:00 GMT

$comment.Recipient - [[The-user-token |User ]]- User the message is for.
$comment.Author - [[The-user-token|User ]] - Author of the message.
$comment.Subject - string - Subject of the message.
$comment.Body - string - Body of the message.
$comment.DateCreated - DateTime - Date the message was created.

Wiki Page: The global term tokens

Jenny Jarrard — Wed, 17 Mar 2010 19:33:00 GMT

$capture

$capture.Url([[The-post-token|Post]]) - string - Returns the URL to capture a forum thread to a wiki.

$globals

$globals.FullPath(string relativeUrl) - string - Returns the full path version of the relative URL.
$globals.FormatDateTime(DateTime time) - string - Returns a string formatted to the Utility_CurrentTime_dateFormat (in Resources.xml)

$helpers

$helpers.FormatFrom (string name, string address) - string - Returns a string in the form of '"name" <address>'.
$helpers.FormatFromAutomated() - string - Returns a string in form of '"$settings.SiteName - Automated Email" <$settings.NotificationFromEmailAddress>'.
$helpers.HtmlEncode(string text) - string - Returns the html encoded text.
$helpers.HtmlDecode(string text) - string - Returns the html decoded text.

$mg

$mg.FormatSubject([[The-post-token|Post]]) - string - Removes "re: " from the post subject and adds prefixes the list name to the post subject.
$mg.GetUserAddress([[The-user-token|User]]) - string - Gets the email address for the user.
$mg.RenderHtml([[The-post-token|Post]]) - string - Returns the post with HTML formatting.
$mg.RenderText([[The-post-token|Post]]) - string - Returns the post without html formatting.
$mg.IncludePreviousPosts([[The-post-token|Post]]) - bool - Returns true if the post was received via email.
$mg.MessageID([[The-post-token|Post]]) - string - Returns "<PostID-UserID@HostUri>"
$mg.ParentID([[The-post-token|Post]]) - string - Returns "<ParentID-UserID@HostUri>"

$resources

$resources.GetString(string resourceName) - string - The matching string from the resource file.

$settings

$settings.SiteName - string - The name of the site.
$settings.SiteUrl - string - The URL of the home page of the site.

$spam

$spam.GetSubject([[The-post-token|Post]]) - string - The likelihood of the blog post as spam.

$term

$term.Get(string term) - string - The value of the site term passed in.

$urls

$urls.AcceptFriendship(string requesteeUserName, string requestorUserName) - string - The URL to accept the friendship request.
$urls.AcceptUserInvitation([[The-user-invitation-token|User Invitation]]) - string - The URL to accept the invitation to join the community.
$urls.LoginClean - string - The URL of the login page for the site (Clean because it has no return URL).
$urls.Home - string - The URL of the home page of the site.
$urls.Moderate - string - The URL of the forum moderation Control Panel page.
$urls.RejectFriendship(string requesteeUserName, string requestorUserName) - string - The URL to reject the friendship request.
$urls.UserChangePassword - string - The URL of the change password page.
$urls.UserFriends(string userName) - string - The URL of the user's friend list.
$urls.UserEditProfile - string - The URL of the edit profile page.
$urls.UserProfile([[The-user-token|User]]) - string - The URL of the user's profile page.

$viewable

$viewable.Uri(IViewableContent content) - Uri - The Uri to the content.
$viewable.Uri([[The-conversation-token|Conversation]]) - Uri - The Uri to the conversation thread page.
$viewable.Uri([[The-message-token|Message]]) - Uri - The Uri to a page displaying this message thread.

Wiki Page: The follower token

Jenny Jarrard — Wed, 17 Mar 2010 19:30:00 GMT

$follower.CreatedDate - DateTime - When the follower started following.
$follower.FollowerUser - [[The-user-token|User]] - The user following someone.
$follower.User - [[The-user-token|User]] - The user being followed.

Wiki Page: The friendship token

Jenny Jarrard — Wed, 17 Mar 2010 19:30:00 GMT

$friendship.FriendshipState - string - "Pending" or "Approved."
$friendship.RequestMessage - string - The message sent with the request.
$friendship.CreatedDate - DateTime - The time when the friendship was requested.
$friendship.Requestor - [[The-user-token|User]] - The user requesting the friendship.
$friendship.Requestee - [[The-user-token|User]] - The user who is being adding as a friend.

Wiki Page: The blog token

Jenny Jarrard — Wed, 17 Mar 2010 19:29:00 GMT

$blog.ExternalFeedUrl - string - URL to the external feed for the blog.
$blog.PostCount - int - Number of posts to the blog.
$blog.ArticleCount - int - Number of articles in the blog.
$blog.CommentCount - int - Number of comments in the blog.
$blog.TrackbackCount - int - Number of trackbacks to the blog.
$blog.Url - string - URL to the blog homepage.
$blog.MostRecentArticleAuthor - string - Username of most recent article author.
$blog.MostRecentArticleDate - DateTime - Date of most recent article.
$blog.MostRecentArticleName - string - Name of most recent article.
$blog.MostRecentArticleSubject - string - Subject of most recent article.

Site Root

Wiki: Telligent Evolution Platform and Applications Documentation

Wiki: Developer Documentation

Wiki: Community Server 2008 Documentation

Forum Post: CS 2007.1 to CS2008.5 Upgrade Issue

Wiki Page: Customization Guide

Forum Post: Re: download Enterprise Search

Wiki Page: Install a new community

Table of contents

Unzip and copy the installation package

Set up the Web server

Set up the database

Connect the Web site and database

Set up search

Connect Web site to search

Enable attachment indexing

Install additional IFilters to index additional attachment types

Optional components

Wiki Page: Mail Gateway Account Types

Wiki Page: Configure the Mail Gateway Service

Wiki Page: Install the Mail Gateway

Related information

Wiki Page: Mail Gateway

Wiki Page: The user invitation token

Wiki Page: The reply message token

Wiki Page: The post token

Wiki Page: The group token

Wiki Page: The profile message token

Wiki Page: The global term tokens

$capture

$globals

$helpers

$mg

$resources

$settings

$spam

$term

$urls

$viewable

Wiki Page: The follower token

Wiki Page: The friendship token

Wiki Page: The blog token