I've set up a new mailing list for monitoring notifications that relate
to the project infrastructure, to make sure they don't only go to one
person.
This will eventually include things like Rackspace monitoring
notifications, scheduled maintenance notifications from suppliers etc.
It's potentially high traffic, so it's separate to ensure that
foreman-dev isn't flooded with automated messages.
> I've set up a new mailing list for monitoring notifications that relate
> to the project infrastructure, to make sure they don't only go to one
> person.
>
> This will eventually include things like Rackspace monitoring
> notifications, scheduled maintenance notifications from suppliers etc.
> It's potentially high traffic, so it's separate to ensure that
> foreman-dev isn't flooded with automated messages.
>
> The list is foreman-infra-notifications@googlegroups.com. To subscribe,
> e-mail foreman-infra-notifications+subscribe@googlegroups.com. If you
> have SSH access to our servers, then you should be subscribed.
>
Sorry, I don't know why that would be. The address is working for me
(it replies to say I'm already subbed), and a number of people did
subscribe to the list successfully.
···
On 10/02/16 19:18, Eric D Helms wrote:
>
>
> On Wed, Feb 10, 2016 at 3:57 AM, Dominic Cleal > wrote:
>
> I've set up a new mailing list for monitoring notifications that relate
> to the project infrastructure, to make sure they don't only go to one
> person.
>
> This will eventually include things like Rackspace monitoring
> notifications, scheduled maintenance notifications from suppliers etc.
> It's potentially high traffic, so it's separate to ensure that
> foreman-dev isn't flooded with automated messages.
>
> The list is foreman-infra-notifications@googlegroups.com
> . To subscribe,
> e-mail foreman-infra-notifications+subscribe@googlegroups.com
> .
> If you
> have SSH access to our servers, then you should be subscribed.
>
>
> I am hitting mail delivery errors when I try to email:
> foreman-infra-notifications+subscribe@googlegroups.com
>
For anyone else that may hit this, turns out the issue was the email
address I was sending the email with. I was using the shortened version of
my email address instead of the full. That is I was using: ericdhelms@gmai.com instead of using eric.d.helms@gmail.com.
Eric
···
On Thu, Feb 11, 2016 at 3:23 AM, Dominic Cleal wrote:
I've set up a new mailing list for monitoring notifications that
relate
to the project infrastructure, to make sure they don't only go to one
person.
This will eventually include things like Rackspace monitoring
notifications, scheduled maintenance notifications from suppliers
etc.
It's potentially high traffic, so it's separate to ensure that
foreman-dev isn't flooded with automated messages.
The list is foreman-infra-notifications@googlegroups.com
<mailto:foreman-infra-notifications@googlegroups.com>. To
subscribe,
e-mail foreman-infra-notifications+subscribe@googlegroups.com
<mailto:foreman-infra-notifications%2Bsubscribe@googlegroups.com>.
If you
have SSH access to our servers, then you should be subscribed.
Sorry, I don’t know why that would be. The address is working for me
(it replies to say I’m already subbed), and a number of people did
subscribe to the list successfully.
