[Codematch-develop] [www.ietf.org/rt #198553] Re: CodeStand e-mail sender address

"Glen via RT" <ietf-action@ietf.org> Fri, 05 January 2018 17:05 UTC

Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: codematch-develop@ietf.org
Delivered-To: codematch-develop@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 1BBC5127419; Fri, 5 Jan 2018 09:05:33 -0800 (PST)
From: "Glen via RT" <ietf-action@ietf.org>
Reply-To: ietf-action@ietf.org
In-Reply-To: <rt-4.4.2-15725-1513779931-1436.198553-7-0@www.ietf.org/rt>
References: <RT-Ticket-198553@www.ietf.org/rt> <CAHbuEH6idTjeViwqj37GVW+omR0DUrifqt6jfNM5LStzXPRATA@mail.gmail.com> <3FFBDA46-0B36-451C-A3CE-5024A82191AF@isoc.org> <bc0bdca7-128c-f4c5-26cc-2de60fc09ea3@gmail.com> <D629EFBD-219A-4EF4-8D71-73BA23429427@inf.ufrgs.br> <CAHbuEH55SVx0pikt-82hqRYBkvcRakVLOu3_9sVQtPapdqX2yA@mail.gmail.com> <rt-4.4.2-19358-1513623655-394.198553-7-0@www.ietf.org/rt> <AFDA1CF4-601F-4190-80B6-351E4B82AA19@inf.ufrgs.br> <rt-4.4.2-27222-1513771521-1261.198553-7-0@www.ietf.org/rt> <rt-4.4.2-15725-1513779931-1436.198553-7-0@www.ietf.org/rt>
Message-ID: <rt-4.4.2-22873-1515171932-765.198553-7-0@www.ietf.org/rt>
X-RT-Loop-Prevention: www.ietf.org/rt
X-RT-Ticket: www.ietf.org/rt #198553
X-Managed-BY: RT 4.4.2 (http://www.bestpractical.com/rt/)
X-RT-Originator: glen@amsl.com
CC: oflaherty@isoc.org, nbbraga@inf.ufrgs.br, iesg-secretary@ietf.org, granville@inf.ufrgs.br, codematch-develop@ietf.org, carlos@lacnic.net, aretana@cisco.com
To: "OtherRecipients of www.ietf.org/rt Ticket #198553":;
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 05 Jan 2018 09:05:32 -0800
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/codematch-develop/afcF5UhmrXuBYlajFGCi00nPwBc>
Subject: [Codematch-develop] [www.ietf.org/rt #198553] Re: CodeStand e-mail sender address
X-BeenThere: codematch-develop@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" <codematch-develop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codematch-develop>, <mailto:codematch-develop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codematch-develop/>
List-Post: <mailto:codematch-develop@ietf.org>
List-Help: <mailto:codematch-develop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codematch-develop>, <mailto:codematch-develop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 17:05:33 -0000

All -

I apologize that this ticket got stalled.

Matt -

What they want is a send-only SMTP account on the IETF server. Please create
it, and send them the appropriate credentials and instructions.


On Wed Dec 20 06:25:31 2017, mlarson wrote:


  I am not clear on what you need from our end. Do you need an email account
  for codestand-noreply@ietf.org so you can send mail via SMTP through
  mail.ietf.org? Or do just need the IP addresses for the codestand server
  added to the IETF SPF record so you can send mail as ietf.org directly?


  On Wed Dec 20 04:05:22 2017, granville@inf.ufrgs.br wrote:

    Dear Matt At least at this moment, we don’t intend to use
    codestand@ietf.org (mailto:codestand@ietf.org) (or similar) to send AND
    receive e-mail. We need an e-mail address to be used in the
    notification messages that the CodeStand system generates itself. For
    example, once an important RFC is updated, the system should send a
    notification e-mail to all project leaders that have associated their
    projects to the RFC that has been just updated. In summary, it’s an
    e-mail address for sending messages only. Actually, the e-mail address
    could be codestand-noreply@ietf.org (mailto:codestand-noreply@ietf.org).
    Best regards, Lisandro

      Em 18 de dez de 2017, à(s) 17:00, Matt Larson via RT <
      ietf-action@ietf.org (mailto:ietf-action@ietf.org)> escreveu:

      We can take care of this, but I'll need a little more information.
      Is the
      intent to send and receive email for codestand@ietf.org (mailto:codestand@ietf.org)
      through the IETF
      server? Or would this be a forwarding alias for incoming mail with
      the outgoing
      mail departing directly from the codestand server?


      On Thu Dec 14 10:42:53 2017, kathleen.moriarty.ietf@gmail.com (mailto:kathleen.moriarty.ietf@gmail.com)


      Thanks for your work on this, Neimar! Let's loop in the
      as they will know who can assist.

      Best regards,

      On Thu, Dec 14, 2017 at 1:38 PM, Lisandro Zambenedetti Granville
      < granville@inf.ufrgs.br (mailto:granville@inf.ufrgs.br)> wrote:

        Dear all

        Neimar has been developing a notification subsistem for
        CodeStand, for example, to notify project authors about changes
        in drafts or RFCs of interest. Notifications are sent by
        e-mail. Neimar is using a Gmail account as the e-mail sender
        address. That works for development purposes, but it would not
        be appropriate after deploying the subsystem. Question: what is
        the process to request, for example, codestand@ietf.org (mailto:codestand@ietf.org)
        (or similar) e-mail address that we could use as the sender of
        CodeStand notifications?

        Best regards,


      Matthew Larson, Software Engineer
      Association Management Solutions
      Forum Management, Meeting and Event Planning

  Matthew Larson, Software Engineer
  Association Management Solutions
  Forum Management, Meeting and Event Planning