Hi Stephan,

there are two things that have to be set up:

1. in Cognos configuration on the Cognos server install configure the default sender's email address:
   
2. in the legacy admin console go to Configuration -> Dispatchers and Services -> [your-dispatcher] -> Delivery Service -> Properties -> Settings and edit the advanced settings:
   
   Create a new parameter "alwaysUseDefaultSender" and set it to true. 
3. Repeate these steps for the JobService

See https://www.ibm.com/support/pages/how-set-default-email-sender-specific-value-cognos-analytics-11

Your schedules can now be defined by multiple users and their credentials but the sender will be the one from Cognos Configuration. That's a global setting per dispatcher. If you have multiple dispatchers you may want to set up one for your central schedules (with the parameter) and others for individual schedules which will be sent by the users accounts (w/o the parameter).

One very important thing: dependent on your licenses (PVU vs. authorized user) it is strictly prohibited to share a user's login with more than one person in your organization. Of course, on person can have multiple users in your namespace (productive & test user) but not vice-versa. This could result in a license compliance violation.

Hi Robert,

Thank you for your reply! 

If I understand it right, In your solution, all replies will be sent to the same email adress. 

We want the replies to arrive at one of the generic department adresses (there are several departments), choosen by whoever creates the schedule.

kind regards,

Stephan

Hi Stephan,

there are two things that have to be set up:

1. in Cognos configuration on the Cognos server install configure the default sender's email address:
   
2. in the legacy admin console go to Configuration -> Dispatchers and Services -> [your-dispatcher] -> Delivery Service -> Properties -> Settings and edit the advanced settings:
   
   Create a new parameter "alwaysUseDefaultSender" and set it to true. 
3. Repeate these steps for the JobService

See https://www.ibm.com/support/pages/how-set-default-email-sender-specific-value-cognos-analytics-11

Your schedules can now be defined by multiple users and their credentials but the sender will be the one from Cognos Configuration. That's a global setting per dispatcher. If you have multiple dispatchers you may want to set up one for your central schedules (with the parameter) and others for individual schedules which will be sent by the users accounts (w/o the parameter).

One very important thing: dependent on your licenses (PVU vs. authorized user) it is strictly prohibited to share a user's login with more than one person in your organization. Of course, on person can have multiple users in your namespace (productive & test user) but not vice-versa. This could result in a license compliance violation.

Hi Stephan,

I'm not aware of any other solution to manipulate the sender of the emails so any reply would go to that specific email box. You could only use your suggested solution by using one email user per department, but keep the license topic in mind.

In my environment I use time zone specific users for schedules that have to be set up by different time zones. All technical users are my accounts so we don't have any license compliance violation. The con: I have to set up schedules for the corresponding departments/plants and their specific time zone.

Hi Robert,

Thank you for your reply! 

If I understand it right, In your solution, all replies will be sent to the same email adress. 

We want the replies to arrive at one of the generic department adresses (there are several departments), choosen by whoever creates the schedule.

kind regards,

Stephan

Hi Stephan,

there are two things that have to be set up:

1. in Cognos configuration on the Cognos server install configure the default sender's email address:
   
2. in the legacy admin console go to Configuration -> Dispatchers and Services -> [your-dispatcher] -> Delivery Service -> Properties -> Settings and edit the advanced settings:
   
   Create a new parameter "alwaysUseDefaultSender" and set it to true. 
3. Repeate these steps for the JobService

See https://www.ibm.com/support/pages/how-set-default-email-sender-specific-value-cognos-analytics-11

Your schedules can now be defined by multiple users and their credentials but the sender will be the one from Cognos Configuration. That's a global setting per dispatcher. If you have multiple dispatchers you may want to set up one for your central schedules (with the parameter) and others for individual schedules which will be sent by the users accounts (w/o the parameter).

One very important thing: dependent on your licenses (PVU vs. authorized user) it is strictly prohibited to share a user's login with more than one person in your organization. Of course, on person can have multiple users in your namespace (productive & test user) but not vice-versa. This could result in a license compliance violation.

Hi Robert,

Thank you for your reply! 

If I understand it right, In your solution, all replies will be sent to the same email adress. 

We want the replies to arrive at one of the generic department adresses (there are several departments), choosen by whoever creates the schedule.

kind regards,

Stephan

Hi Stephan,

there are two things that have to be set up:

1. in Cognos configuration on the Cognos server install configure the default sender's email address:
   
2. in the legacy admin console go to Configuration -> Dispatchers and Services -> [your-dispatcher] -> Delivery Service -> Properties -> Settings and edit the advanced settings:
   
   Create a new parameter "alwaysUseDefaultSender" and set it to true. 
3. Repeate these steps for the JobService

See https://www.ibm.com/support/pages/how-set-default-email-sender-specific-value-cognos-analytics-11

Your schedules can now be defined by multiple users and their credentials but the sender will be the one from Cognos Configuration. That's a global setting per dispatcher. If you have multiple dispatchers you may want to set up one for your central schedules (with the parameter) and others for individual schedules which will be sent by the users accounts (w/o the parameter).

One very important thing: dependent on your licenses (PVU vs. authorized user) it is strictly prohibited to share a user's login with more than one person in your organization. Of course, on person can have multiple users in your namespace (productive & test user) but not vice-versa. This could result in a license compliance violation.