Edit configuration property settings to change the administrator email address for notifications. This is the address used to send system notifications, such as notifications sent to users who have posted inappropriate content.
Before you begin
To edit configuration files, you must use the wsadmin client. See Starting the wsadmin client
About this task
By default, automatic notifications are sent from a generic email address, such as firstname.lastname@example.org. If Connections is configured so that email addresses are not displayed, you can set a global sender email address for all notification templates, as described in the topic Defining a valid global sender email address
. If email addresses are displayed, the global sender is ignored. In either case, you should add a specific administrator email address that has access rights to send mail for several notification templates that are used in the workflows for managing content that is flagged as inappropriate. Some of the messages sent automatically instruct the recipient that they can respond to the administrative user email address from which the notification was sent. If you do not edit the default email address, the recipient gets a delivery failure notification when they try to respond to the automatic email.
To specify an administrator email address for managing flagged content, complete the following steps:
- Use the wsadmin client to access and check out the IBM Connections configuration files.
- Enter the following command to access the IBM Connections configuration file: 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, you must pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
- Enter the following command to check out the IBM Connections configuration files:
- <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft® Windows® operating system.
AIX® and Linux® only: The directory must grant write permissions or the command does not run successfully.
- <cell_name> is the name of the WebSphere® Application Server cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, type the following command while in the wsadmin command processor:print AdminControl.getCell()
- AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
- Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
- Check out the notification-config.xml file using the following command:
is a temporary directory and <cell_name>
is the WebSphere
Application Server cell where you installed Blogs.
- From the temporary directory to which you checked out the notification-config.xml file, open it in a text editor.
- Search for the <source name="Blogs" string to find the section that defines the notification settings for the Blogs application.
- To configure an administrative email address for handling flagged content in a blog, add or change the value of the sender attribute to a legitimate email address in the <type> elements that have the following name attribute values:
Save and close the notification-config.xml file.
Check in the configuration files using the following command:
<channel enabled="true" name="email">
Restart the Blogs server for the changes to take effect.
Parent topic: Administering Blogs using the wsadmin client
Managing content moderation and flagged content
Defining valid administrator email addresses
Moderating Blog comments