For now I gave it my own email address, but it would make
more sense to have some service-specific mailboxes to use
for these things. What would you think about a git@osgeo.org
email, for example ?
The mail could go to the local mailbox for "git" user
on git.osgeo.org host, so that anyone with shell access
and sudo could use the ~git/.forward file to add her email
or something along those lines.
Is there any other service using this local approach ?
Even better, being a _local_ account, would be to use
"git@git.osgeo.org", but I'd still like then to be able
to receive mail from there (to eventually enable email-based
services to update tickets and the like). Any major drawback
with receiving mails that way ?
--strk;
On Tue, Apr 19, 2016 at 12:55:13PM +0200, Sandro Santilli wrote:
For now I gave it my own email address, but it would make
more sense to have some service-specific mailboxes to use
for these things. What would you think about a git@osgeo.org
email, for example ?
The mail could go to the local mailbox for "git" user
on git.osgeo.org host, so that anyone with shell access
and sudo could use the ~git/.forward file to add her email
or something along those lines.
Is there any other service using this local approach ?
An actual local account or just an alias? Perhaps even an email list
with multiple admins?
Guess I'm unclear on everything it needs to handle.
-Alex
On 04/19/2016 04:05 AM, Sandro Santilli wrote:
Even better, being a _local_ account, would be to use
"git@git.osgeo.org", but I'd still like then to be able
to receive mail from there (to eventually enable email-based
services to update tickets and the like). Any major drawback
with receiving mails that way ?
--strk;
On Tue, Apr 19, 2016 at 12:55:13PM +0200, Sandro Santilli wrote:
I'm registering an "osgeo-bot" user on gitlab.com to give it
push access for automating mirrors of code repositories
(see https://trac.osgeo.org/osgeo/ticket/1654)
For now I gave it my own email address, but it would make
more sense to have some service-specific mailboxes to use
for these things. What would you think about a git@osgeo.org
email, for example ?
The mail could go to the local mailbox for "git" user
on git.osgeo.org host, so that anyone with shell access
and sudo could use the ~git/.forward file to add her email
or something along those lines.
Is there any other service using this local approach ?
On Tue, Apr 19, 2016 at 09:43:57PM -0700, Alex Mandel wrote:
An actual local account or just an alias? Perhaps even an email list
with multiple admins?
Guess I'm unclear on everything it needs to handle.
I'm also unclear at the moment, thus the request for a local account.
An alias could also do, for a start, but I like the idea of anyone
being able to "impersonate" a given account (sudo users?) being
also able to read the email for that given account. Think mail
to the "git@git.osgeo.org" user, which may represent the git services
as per SAC:Git Service - OSGeo
On Tue, Apr 19, 2016 at 09:43:57PM -0700, Alex Mandel wrote:
An actual local account or just an alias? Perhaps even an email list
with multiple admins?
Guess I'm unclear on everything it needs to handle.
I'm also unclear at the moment, thus the request for a local account.
An alias could also do, for a start, but I like the idea of anyone
being able to "impersonate" a given account (sudo users?) being
also able to read the email for that given account. Think mail
to the "git@git.osgeo.org" user, which may represent the git services
as per https://wiki.osgeo.org/wiki/SAC:Git_Service
--strk;
I'm worried about no one remembering to check it...
On Wed, Apr 20, 2016 at 07:44:00AM -0700, Alex Mandel wrote:
On 04/20/2016 03:01 AM, Sandro Santilli wrote:
> On Tue, Apr 19, 2016 at 09:43:57PM -0700, Alex Mandel wrote:
>> An actual local account or just an alias? Perhaps even an email list
>> with multiple admins?
>>
>> Guess I'm unclear on everything it needs to handle.
>
> I'm also unclear at the moment, thus the request for a local account.
> An alias could also do, for a start, but I like the idea of anyone
> being able to "impersonate" a given account (sudo users?) being
> also able to read the email for that given account. Think mail
> to the "git@git.osgeo.org" user, which may represent the git services
> as per SAC:Git Service - OSGeo
I'm worried about no one remembering to check it...
I'm worried about setting a redirection now and then having
difficulty about changing it later. The whole point is giving
"redirectability" of the address the same permissions as the
service itself.
I'm not skilled enough with MTAs to know what's possible to do or
not for reducing the risk you're envisioning. How about a default
delivery to /dev/null UNLESS a ~user/.forward file exists ?
On Wed, Apr 20, 2016 at 07:44:00AM -0700, Alex Mandel wrote:
On 04/20/2016 03:01 AM, Sandro Santilli wrote:
On Tue, Apr 19, 2016 at 09:43:57PM -0700, Alex Mandel wrote:
An actual local account or just an alias? Perhaps even an email list
with multiple admins?
Guess I'm unclear on everything it needs to handle.
I'm also unclear at the moment, thus the request for a local account.
An alias could also do, for a start, but I like the idea of anyone
being able to "impersonate" a given account (sudo users?) being
also able to read the email for that given account. Think mail
to the "git@git.osgeo.org" user, which may represent the git services
as per https://wiki.osgeo.org/wiki/SAC:Git_Service
I'm worried about no one remembering to check it...
I'm worried about setting a redirection now and then having
difficulty about changing it later. The whole point is giving
"redirectability" of the address the same permissions as the
service itself.
I'm not skilled enough with MTAs to know what's possible to do or
not for reducing the risk you're envisioning. How about a default
delivery to /dev/null UNLESS a ~user/.forward file exists ?
--strk;
Well MTA is one thing, email forwarding is another and much simpler.
1. Please open a ticket asking to setup or confirm that a subdomain
mailing address works on osgeo.
2. Once that is done, put in a ticket to create a mailing list
(private), and an alias from that incoming address to the list. Then
subscribe all the admins that would need regular access to it.
On Wed, Apr 20, 2016 at 12:09:17PM -0700, Alex M wrote:
Well MTA is one thing, email forwarding is another and much simpler.
1. Please open a ticket asking to setup or confirm that a subdomain
mailing address works on osgeo.
2. Once that is done, put in a ticket to create a mailing list
(private), and an alias from that incoming address to the list. Then
subscribe all the admins that would need regular access to it.
To simplify things, I directly requested the mailing list.
Subdomain mailing address is not that important, if not for
directly receiving mail on the machine: