Define valid administrator e-mail addresses

Home

Define valid administrator e-mail addresses

Edit configuration property settings to change the default e-mail addresses from which system notifications, such as a request to join a community, are sent. Notifications are sent from generic administrator e-mail addresses if you do not take action.
By default, automatic notifications are sent from a generic e-mail address, such as blogs-admin@your-email-domain.com. Edit the property to change this to a legitimate administrator e-mail 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 e-mail address from which the notification was sent. If you do not edit the default e-mail address, recipients get a delivery failure notification when they try to respond to the automatic e-mail.

If you plan to prevent user e-mail addresses from being displayed in the product, define a valid e-mail address for the global administrator. When you hide e-mails, this global administrator address is specified as the sender even in e-mails generated by user actions that would normally specify that user as the sender. The global sender e-mail address is only used if you configure Lotus Connections to prevent e-mails from being displayed.
If you provide additional administrator e-mail 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:


You can edit the following administrator e-mail addresses:

Global sender. Change the default e-mail 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.

Define e-mail addresses
Start wsadmin
Access the Lotus Connections configuration files:

Single server:
execfile("connectionsConfig.py")

Cluster:
execfile("WAS_HOME/profiles/Dmgr01/config/bin_lc_admin/connectionsConfig.py")

Check out the notification-config.xml file...
LCConfigService.checkOutNotificationConfig("<temp_dir>", "cell_name")

where <temp_dir> is a temporary and cell_name is the WebSphere Application Server cell to which you installed Activities.
From the temporary to which you checked out the notification-config.xml file, open it in a text editor.
Specify a valid internet-style e-mail 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="globalSenderEmailAddress">
    global-admin@your-email-domain.com
  </property> 
</properties>
To specify e-mail addresses for different notifications types per feature, search for the following sections and change the value of the sender properties. If there is no sender property, add one.
If a type element is present, the e-mail 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.
In the <source name="Activities" section, which defines the notification settings for the Activities feature, edit the following notification types:
add-member
For example:
<type name="add-member">
  <channel name="email" enabled="true">
    <property name="sender">
      activities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/email/addMemberMail.jsp
    </property>
  </channel>
 </type>
autocomplete
For example:
<type name="autocomplete">
  <channel name="email" enabled="true">
    <property name="sender">
      activities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/email/autoCompleteActivityMail.jsp
    </property>
  </channel>
 </type>
You must specify a valid e-mail address in the sender attribute for this notification type.
create
For example:
<type name="create">
  <channel name="email" enabled="true">
    <property name="sender">
      activities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/email/createMail.jsp
    </property>
  </channel>
 </type>
error
For example:
<type name="error">
  <channel name="email" enabled="true">
    <property name="sender">
      activities-admin-error-address@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/email/errorMail.jsp
    </property>
  </channel>
 </type>
images-prefix
For example:
<type name="images-prefix">
  <channel name="email" enabled="true">
    <property name="url">
     {notification.source.url}/images/"
    </property>
  </channel> 
</type>
notify
For example:
<type name="notify">
  <channel name="email" enabled="true">
    <property name="sender">
      activities-admin-notify-address@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/email/notifyMail.jsp
    </property>
  </channel>
 </type>
In the <source name="Blogs" section, which defines the notification settings for the Blogs feature, edit the following notification types:
approvedmsg
Specifies the e-mail address from which comment approval notifications are sent. For example:
<type name="approvedmsg">
  <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/approvedmsg.jsp
    </property>
  </channel>
 </type>
confirmflagged
Specifies the e-mail address from which confirmations of content that has been flagged as inappropriate are sent. For example:
<type name="confirmflagged">
  <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/confirmflagged.jsp
    </property>
  </channel>
 </type>
notify
For example:
<type name="notify">
  <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/notify.jsp
    </property>
  </channel>
 </type>
notifyedit
Specifies the e-mail address from which edit notifications are sent. For example:
<type name="notifyedit">
  <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/notifyedit.jsp
    </property>
  </channel>
 </type>
notifyflagged
Specifies the e-mail address from which notifications about content that has been flagged as inappropriate are sent. For example:
<type name="notifyflagged">
  <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/notifyflagged.jsp
    </property>
  </channel>
</type>
notifyquarantined
Specifies the e-mail address from which entry quarantine notifications are sent. For example:
<type name="notifyquarantined">
  <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/notifyquarantined.jsp
    </property>
  </channel> 
</type>
ownermsg
Specifies the e-mail address from which comment notifications are sent. For example:
<type name="ownermsg">
 <channel name="email" enabled="true">
    <property name="sender">
      blogs-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/ownermsg.jsp
    </property>
  </channel>
</type>
In the <source name="Bookmarks" section, which defines the notification settings for the Bookmarks feature, edit the following notification types:
notify
For example:
<type name="notify">
    <channel name="email" enabled="true">
    <property name="sender">
      dogear-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/templates/notifytemplate.jsp
    </property>
  </channel>
</type>
In the <source name="Communities" section, which defines the notification settings for the Communities feature, edit the following notification types:
broadcastMail
For example:
<type name="broadcastMail"> 	
  <channel name="email" enabled="true">
    <property name="sender">
      communities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/broadcast
    </property>
  </channel> 
 </type>
memberAdded
For example:
<type name="memberAdded">
		<channel name="email" enabled="true">
    <property name="sender">
      communities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/memberAdded
    </property>
  </channel>
 </type>
memberRemoved
For example:
<type name="memberRemoved">
	<channel name="email" enabled="true">
    <property name="sender">
      communities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/memberRemoved
    </property>
  </channel>
</type>
requestToJoin
For example:
<type name="requestToJoin">
		<channel name="email" enabled="true">
    <property name="sender">
      communities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/requestToJoin
    </property>
  </channel>
</type>
forumTopicCreated
For example:
<type name="forumTopicCreated">
		<channel name="email" enabled="true">
    <property name="sender">
      communities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/topicCreated
    </property>
  </channel>
</type>
topicReplyCreated
For example:
<type name="topicReplyCreated">
		<channel name="email" enabled="true">
    <property name="sender">
      communities-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/replyCreated
    </property>
  </channel>
</type>
In the <source name="Files" section, which defines the notification settings for the Files feature, edit the following notification types:
commentAdd
<type name="commentAdd">
  <channel enabled="true" name="email">
    <property name="sender">
     files_admin@your-email-domain.com
    </property>
		<property name="file">
     {notification.source.url}/files/email/commentAddMail.xml
    </property>
	</channel>
</type>
mediaEdit
For example:
<type name="mediaEdit">
  <channel enabled="true" name="email">
    <property name="sender">
     files_admin@your-email-domain.com
    </property>
    <property name="file">
     {notification.source.url}/files/email/mediaEditMail.xml
    </property>
	</channel>
</type>
mediaShare
For example:
<type name="mediaShare">
  <channel enabled="true" name="email">
    <property name="sender">
    files_admin@your-email-domain.com
    </property>
		<property name="file">
     {notification.source.url}/files/email/shareMail.xml
    </property>
	</channel>
</type>
In the <source name="Profiles" section, which defines the notification settings for the Profiles feature, edit the following notification types:
notify
For example:
<type name="notify">
   <channel name="email" enabled="true">
    <property name="sender">
      profiles-admin@your-email-domain.com
    </property>
    <property name="url">
     {notification.source.url}/mail/sendInvitation
    </property>
  </channel>
 </type>
notifyBoardOwnerForComment
Notifications sent to the board owner when someone makes a comment on any board entry.
  <type name="notifyBoardOwnerForComment">
     <channel enabled="true" name="email">
		   <property name="sender">
        profiles-admin@your-email-domain.com
       </property>
		   <property name="url">
        {notification.source.url}/mail/notifyBoardOwnerForComment
       </property>
     </channel>
  </type>
notifyBoardOwnerForEntry
Notifications sent to the board owner when a new message is posted.
  <type name="notifyBoardOwnerForEntry">
     <channel enabled="true" name="email">
		   <property name="sender">
         profiles-admin@your-email-domain.com
       </property>
		   <property name="url">
         {notification.source.url}/mail/notifyBoardOwnerForEntry
       </property>
     </channel>
  </type>
notifyEntryOwnerForComment
Notifications sent to the board entry owner when someone makes a comment on the entry.
  <type name="notifyEntryOwnerForComment">
     <channel enabled="true" name="email">
		   <property name="sender">
         profiles-admin@your-email-domain.com
       </property>
		   <property name="url">
         {notification.source.url}/mail/notifyEntryOwnerForComment
       </property>
     </channel>
  </type>
In the <source name="Wikis" section, which defines the notification settings for the Wikis feature, edit the following notification types:
commentAdd
<type name="commentAdd">
  <channel enabled="true" name="email">
    <property name="sender">
     wikis_admin@your-email-domain.com
    </property>
		<property name="file">
     {notification.source.url}/wikis/email/commentAddMail.xml
    </property>
	</channel>
</type>
mediaEdit
For example:
<type name="mediaEdit">
  <channel enabled="true" name="email">
    <property name="sender">
     wikis_admin@your-email-domain.com
    </property>
    <property name="file">
     {notification.source.url}/wikis/email/mediaEditMail.xml
    </property>
	</channel>
</type>
No notifications are sent from the Home page feature.
Save and close the notification-config.xml file.
Check in the configuration files...
LCConfigService.checkInNotificationConfig("<temp_dir>","<cell-name>")
Related tasks
Configure notifications
Enable e-mail notifications
Start the wsadmin client
Hiding e-mail addresses
Specify an administrator e-mail address for Blogs notifications

+
Search Tips | Advanced Search