infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-14566) Add cronjob to send list of .qmail ids to whimsy-vm4
Date Fri, 14 Jul 2017 00:29:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-14566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086644#comment-16086644
] 

Chris Lambertus commented on INFRA-14566:
-----------------------------------------

I'm just thinking out loud here - I have not done any due diligence on feasibility. Since
existing aliases for "real" accounts already exist in LDAP, the purpose of this tool is to
provide differential output between LDAP and hermes, so whimsy can know what qmail IDs exist
outside of LDAP. I have no problems with this cronjob as specified once the minor tech details
are hashed out, but I would like to suggest that we consider what a wholesale migration of
this data into LDAP would look like. Various hermes replacement solutions have been discussed,
and while nothing has been decided on, it would be useful to begin the machinations of thought
as to how this might look in the face of a possible hermes replacement that does not use qmail
dot-files.

> Add cronjob to send list of .qmail ids to whimsy-vm4
> ----------------------------------------------------
>
>                 Key: INFRA-14566
>                 URL: https://issues.apache.org/jira/browse/INFRA-14566
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Identity Management, Mail (qmail)
>            Reporter: Sam Ruby
>
> Add a cronjob to hermes to extract list of taken qmail ids:
> ls -a | sed -n '/^\.qmail-[a-z0-9]*$/ s/.qmail-//p' | ssh whimsy-vm4.apache.org 'cat
> /srv/subscriptions/qmail.ids'
> See https://issues.apache.org/jira/browse/WHIMSY-113 for rationale.
> The resolution of https://issues.apache.org/jira/browse/WHIMSY-114 may affect the actual
regular expression used.  sed doesn't support '+', but a tighter regular expression can be
used, for example: /^[a-z][a-z0-9][a-z0-9][a-z0-9]*$/
> Note: with this JIRA, I'm merely looking for review/approval.  The code is available
for review above, and I can do the deployment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message