Skip to main content

Always use Global Sender!

In Connections notification, I really don't like using dozens of different senders for every feature

That's why in notification-config.xml I always add the property for always using globalSenderName. You have to add it manually  here

 <?xml version="1.0" encoding="UTF-8"?><!-- Copyright IBM Corp. 2008, 2013  All Rights Reserved.              --><config buildlevel="LC4.0_20130311_1432" enabled="true" id="notification-config" version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="notification-config.xsd">
<properties>
<property name="globalSenderEmailAddress">global-admin@esprinet.com</property>
        <property name="alwaysUseGlobalSender">true</property>
        <property name="globalSenderName">Info Connections</property>
<!-- If true a link to Connections Mobile service will be included in 
Notifications (where applicable) -->
<property name="includeMobileLinksInNotifications">false</property>
<!-- If true no embedded experience mime parts will be included in notifications -->
<property name="disableEmbeddedAppsInNotifications">false</property>
</properties>
<handlers>

 























































Comments
















Tom Bosmans said…




I actually prefer to change the individual email addresses, because there seem to be or have been issues with the global sender .... 






3/26/2014 03:57:00 PM




















Post a Comment













Popular posts from this blog






















Multiple controllers with Spring Boot




























 Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work   So these two together will NOT work (or just one of them will work)         These two instead WILL work.        




















2 comments









Read more




























Can't use the newest npm when node is installed with brew (MacOs)




























    Even though I installed and reinstalled node with brew, with last versione 11.8.0, apparently it kept using the last version     fdecollibus$ npm install --global gatsby-cli   npm  WARN  npm  npm does not support Node.js v11.8.0   npm  WARN  npm  You should probably upgrade to a newer version of node as we   npm  WARN  npm  can't make any promises that npm will work with this version.   npm  WARN  npm  Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.   npm  WARN  npm  You can find the latest version at https://nodejs.org/   /usr/local/Cellar/node/11.8.0/bin/gatsby -> /usr/local/Cellar/node/11.8.0/lib/node_modules/gatsby-cli/lib/index.js   + gatsby-cli@2.4.8       npm -v gave me back version 5.6.0. I've therefore noticed that  /usr/local/lib/node_modules   had wrong permissions assigned to root:wheel. A chown did not fix the problem: I've had to manually delete the content of the folder (cd / usr/local/lib/node_modules and -careful - type rm -rf ...




















Post a Comment









Read more