Define valid administrator email addresses 

Edit configuration property settings to change the default email addresses from which system notifications, such as a request to join a community, are sent. Notifications are sent from generic administrator email addresses if you do not take action.

Before starting

By default, automatic notifications are sent from a generic email address, such as blogs-admin@example.com. Edit the property to change this to a legitimate administrator email address that has access rights to send mail. Some of the notification messages sent automatically, such as the notifications used to handle blog postings that are flagged for containing inappropriate content, inform recipients that they can respond to the default administrative user email address from which the notification was sent. If you do not edit the default email address, recipients get a delivery failure notification when they try to respond to the automatic email.

Note:

• If you plan to prevent user email addresses from being displayed in the product, define a valid email address for the global administrator. When you hide emails, this global administrator address is specified as the sender even in emails generated by user actions that would normally specify that user as the sender. The global sender email address is only used if you configure IBM Connections to prevent emails from being displayed.

• If you provide additional administrator email addresses for the different types of notifications, those settings take precedence over the global address. If you want the global administrator address to be used for a specific notification, comment out the sender property currently specified for that notification type. For example:

  <!--<property name="sender">files_admin@example.com</property>-->

  
  

About this task

You can edit the following administrator email addresses:

• Global sender. Change the default email address of the global sender into one with the correct domain for your enterprise and a name that your users will recognize and trust.

• Specific notification types. Edit the administrator addresses used when different types of notifications are sent.

To define valid default email addresses...

Procedure

1. Start the wsadmin client from the following directory of the system on which you installed the deployment manager:
   
   app_server_root>\profiles\<dm_profile_root>\bin

   Note: You must start the client from this directory or subsequent commands that you try to run will not execute properly. See Starting the wsadmin client for more details.
   

2. Access the IBM Connections configuration files:
   

   execfile("connectionsConfig.py")

   If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
   

3. Check out the notification-config.xml file using the following command:
   

   LCConfigService.checkOutNotificationConfig("<temp_dir>","<cell_name>")

   where <temp_dir> is a temporary directory and <cell_name> is the WAS cell to which you installed Activities. When you specify a path to the working directory on a system running Microsoft Windows, use a forward slash for the directory. For example: "C:/temp".

   Note: AIX and Linux only: The directory you specify as the temporary directory must grant write permissions.
   

4. From the temporary directory to which you checked out the notification-config.xml file, open it in a text editor.

5. Specify a valid internet-style email address containing no spaces for the global sender by editing the globalSenderEmailAddress property in the following section of the notification-config.xml file:
   

   <properties>
     <property name="globalSenderName">IBM Connections Administrator</property>
     <property name="globalSenderEmailAddress">global-admin@example.com</property> 
   </properties>

   
   

6. Optional:  If you want to force the email address that you specify in the globalSenderEmailAddress to be used as the sender of all notifications, add the following property to the <properties> element listed above, and set it equal to true.
   

   <property name="alwaysUseGlobalSender">true</property>

   
   

7. Optional:  By default, the email address of the original sender is set as the reply-to address. If you do not want the original sender to appear as the reply-to address, then add the following property to the <properties> element listed above, and set it equal to false.
   

   <property name="includeOriginalSenderAsReplyTo">false</property>

   If the alwaysUseGlobalSender property is set to false, then the includeOriginalSenderAsReplyTo property is ignored. If the alwaysUseGlobalSender property is set to true, then the includeOriginalSenderAsReplyTo is optional. The default value for this property is true if the property is added, but no value is defined for it.
   

8. Optional: To specify different administrator email addresses for different notifications types per application, search for the notification types you want to change, and then change the value of the sender properties. If there is no sender property, add one.
   
   Note: If a type element is present, the email address specified for it is used instead of the global administrator address. If you want the global sender address to be used instead of the address specified here, comment out the associated type element. For example, if you want to change the address from which notifications that inform people that they have been added to an activity are sent, edit the value of the sender property in the following notification type:

   add-member

   For example:

   <type name="add-member">
     <channel name="email" enabled="true">
       <property name="sender">
   
   

   activities-admin@example.com </property> <property name="url"> {notification.source.url}/email/addMemberMail.jsp </property> </channel> </type>
   

   Note: No notifications are sent from the Home page application.
   

9. Save and close the notification-config.xml file.

10. Check in the configuration files using the following command:
    

    LCConfigService.checkInNotificationConfig("<temp_dir>","<cell-name>")

    
    

Parent topic

Configure notifications

Related concepts
Optional post-installation tasks

Related tasks

Enable email notifications
Starting the wsadmin client
Hiding email addresses
Specify an administrator email address for Blogs notifications

   

 

});

+

Search Tips   |   Advanced Search