This is a shortcoming of the existing quota infrastructure -- only a single email address can be specified (either via CLI or GUI, doesn't matter). Although one would think that something like "foo@bar.com;bar@baz.com" should work, it doesn't.
There's a bug filed for this in engineering already. The current workaround, as folks here have pointed out, is to use a distribution list. We recognize that this is not optimal.
If this issue is really disruptive, then I would suggest that you also work with your SE to get a feature request filed with Product Management. That will then affect the engineering bug in positive ways...
You can do this via the command line. I haven't done it with multiple individual addresses but I have pointed the notification to a mailing list address and that works fine. The notifications go to BOTH the quota domain owner and the mailing list.
We are running with 7.2.1 OneFS, We need the configuration like share level custom notification.
We tried configuring custom notification email for the individual share owner, It doesn't send the email to the individual owner's email address rather it sends to the distribution list.
Could you please update if this issue is fixed for any of the OneFS releases.
kipcranford
125 Posts
4120
0
Posted May 13th, 2015 08:00
This is a shortcoming of the existing quota infrastructure -- only a single email address can be specified (either via CLI or GUI, doesn't matter). Although one would think that something like "foo@bar.com;bar@baz.com" should work, it doesn't.
There's a bug filed for this in engineering already. The current workaround, as folks here have pointed out, is to use a distribution list. We recognize that this is not optimal.
If this issue is really disruptive, then I would suggest that you also work with your SE to get a feature request filed with Product Management. That will then affect the engineering bug in positive ways...