You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Mr Mr <dr...@gmail.com> on 2022/06/17 06:49:36 UTC

Fwd: confirm subscribe to dev@community.apache.org

---------- Forwarded message ---------
From: <de...@community.apache.org>
Date: Thu, Jun 16, 2022 at 10:15 PM
Subject:  http://www.apache.org/foundation/private-archives.
<http://www.apache.org/foundation/public-archives.html>aspx=
dev@community.apache.org
To: <dr...@gmail.com>


Hi! This is the ezmlm program. I'm managing the
dev@community.apache.org mailing list.

I'm working for my owner, who can be reached
at dev-owner@community.apache.org.

To confirm that you would like

   droski59@gmail.com

added to the dev mailing list, please send
a short reply to this address:

   dev-sc.1655442944.banjcpmkplagmgijelah-droski59=
gmail.com@community.apache.org

Usually, this happens when you just hit the "reply" button.
If this does not work, simply copy the address and paste it into
the "To:" field of a new message.

or click here:
        mailto:dev-sc.1655442944.banjcpmkplagmgijelah-droski59=
gmail.com@community.apache.org

This confirmation serves two purposes. First, it verifies that I am able
to get mail through to you. Second, it protects you in case someone
forges a subscription request in your name.

Please note that ALL Apache dev- and user- mailing lists are publicly
archived.  Do familiarize yourself with Apache's public archive policy at

    http://www.apache.org/foundation/public-archives.html

prior to subscribing and posting messages to dev@community.apache.org.
If you're not sure whether or not the policy applies to this mailing list,
assume it does unless the list name contains the word "private" in it.

Some mail programs are broken and cannot handle long addresses. If you
cannot reply to this request, instead send a message to
<de...@community.apache.org> and put the
entire address listed above into the "Subject:" line.


--- Administrative commands for the dev list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

To subscribe to the list, send a message to:
   <de...@community.apache.org>

To remove your address from the list, send a message to:
   <de...@community.apache.org>

Send mail to the following for info and FAQ for this list:
   <de...@community.apache.org>
   <de...@community.apache.org>

Similar addresses exist for the digest list:
   <de...@community.apache.org>
   <de...@community.apache.org>

To get messages 123 through 145 (a maximum of 100 per request), mail:
   <de...@community.apache.org>

To get an index with subject and author for messages 123-456 , mail:
   <de...@community.apache.org>

They are always returned as sets of 100, max 2000 per request,
so you'll actually get 100-499.

To receive all messages with the same subject as message 12345,
send a short message to:
   <de...@community.apache.org>

The messages should contain one line or word of text to avoid being
treated as sp@m, but I will ignore their content.
Only the ADDRESS you send to is important.

You can start a subscription for an alternate address,
for example "john@host.domain", just add a hyphen and your
address (with '=' instead of '@') after the command word:
<de...@community.apache.org>

To stop subscription for this address, mail:
<de...@community.apache.org>

In both cases, I'll send a confirmation message to that address. When
you receive it, simply reply to it to complete your subscription.

If despite following these instructions, you do not get the
desired results, please contact my owner at
dev-owner@community.apache.org. Please be patient, my owner is a
lot slower than I am ;-)

--- Enclosed is a copy of the request I received.

Return-Path: <dr...@gmail.com>
Received: (qmail 62074 invoked by uid 99); 17 Jun 2022 05:15:44 -0000
Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org)
(116.203.196.100)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2022 05:15:44 +0000
Received: from localhost (localhost [127.0.0.1])
        by spamproc1-he-de.apache.org (ASF Mail Server at
spamproc1-he-de.apache.org) with ESMTP id 493B71FF3D7
        for <de...@community.apache.org>; Fri, 17 Jun 2022 05:15:43
+0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.241
X-Spam-Level: **
X-Spam-Status: No, score=2.241 tagged_above=-999 required=6.31
        tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
        DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,
FREEMAIL_REPLY=1,
        HK_NAME_MR_MRS=0.999, HTML_MESSAGE=0.2, RCVD_IN_MSPIKE_H3=0.001,
        RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001,
T_SCC_BODY_TEXT_LINE=-0.01,
        URIBL_BLOCKED=0.001] autolearn=disabled
Authentication-Results: spamproc1-he-de.apache.org (amavisd-new);
        dkim=pass (2048-bit key) header.d=gmail.com
Received: from mx1-ec2-va.apache.org ([116.203.227.195])
        by localhost (spamproc1-he-de.apache.org [116.203.196.100])
(amavisd-new, port 10024)
        with ESMTP id zEV1LiDHqs2w for <de...@community.apache.org>;
        Fri, 17 Jun 2022 05:15:42 +0000 (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.216.44;
helo=mail-pj1-f44.google.com; envelope-from=droski59@gmail.com;
receiver=<UNKNOWN>
Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com
[209.85.216.44])
        by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org)
with ESMTPS id 3B513BD45D
        for <de...@community.apache.org>; Fri, 17 Jun 2022 05:15:42
+0000 (UTC)
Received: by mail-pj1-f44.google.com with SMTP id f16so2105817pjj.1
        for <de...@community.apache.org>; Thu, 16 Jun 2022 22:15:42
-0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;

h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=bApGHcLz1Q8rGBoAng2tJM+uTecUjbpVqk9iLVdBx0M=;
        b=b8bwPRnBZkngHwMnEy75gR2IGRREqiPNyjLFpm8BltPfUrl5WK/qpWFk0O/0pBNbkJ

 qy8LWdcmqBhJThVm7z+88N3Qg5jg17ypAycCSQEJL+rXO9cqQcMN48BnZoYQbFf3o0gj

 Ja45QdOktmYQiIFgPLk/+lUpCZLn+59Df0yMKKNrsGnqKn8pS4NVg0xlVVENgYATM/Yz

 n0I9w6oNZJUhE0QXTQuIQnT8zpD/xcFBSOF7qvjlVL3gDUtzndxA5ndVNRCEVq0Ni+65

 yOyX1vU9qVP7attU0cvWnoA6Kj0EWCNuYU6oLqJz8hoVcvpYP4po6RCpW4wzlQdCzdlj
         w7xA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=bApGHcLz1Q8rGBoAng2tJM+uTecUjbpVqk9iLVdBx0M=;
        b=4nxeowz1vfDDKidXbql0BycxrFZOcJQKYOxUE9f4vCiIgQtmN3exYDqY4MqETHeD9l

 EiLpITmbs6mCQ/e2MxyW48ey2FABPrNWlbG4KixMJ/mjpurylJcwleCm4sXgE/SaMvaj

 CrY4hogJpYLulGeajpwTo4/igwMnWHCCmKZYec5QzVZ3haqLPzaoNUyPqg+aIkwWD5rm

 pGTQlLpSofGTREZfp7Nmx1AJKZHJcL8rJcYzgsA//1tnq7LkfcZeEja4/u0nDNXwvwCp

 duc5yywHpnU5t0+s60HcFmrWTDv5S5pDuCx1JTOS2rfYSudaD4KleWYwb+lxyFbooi+B
         wfgw==
X-Gm-Message-State: AJIora8kXXS6+CCLElC5hdeIWSxAI9CJlXZieiAFGWdpxBcK0ZwGL16S
        c21WsJIyu3DlWKLveZN7lETEoDizuxvtVrjXKg==
X-Google-Smtp-Source:
AGRyM1vuuwULwMBeK6u7hPlsyR6Q0mC2naOMetx+tNQ0QyEReyZr5Q92hamsZBi/fu/qFvxslqb6nGF1jHVWOZmvgWg=
X-Received: by 2002:a17:902:7884:b0:167:4d5b:7a2f with SMTP id
 q4-20020a170902788400b001674d5b7a2fmr8415706pll.18.1655442941326; Thu, 16
Jun
 2022 22:15:41 -0700 (PDT)
MIME-Version: 1.0
References: <88...@mail.uber.com>
In-Reply-To: <88...@mail.uber.com>
From: Mr Mr <dr...@gmail.com>
Date: Thu, 16 Jun 2022 22:15:29 -0700
Message-ID: <CAHAbSh_6a+Hr=
mge_RoOkRrU_VWFt0-QCns9pEBkEUOgpC3VgA@mail.gmail.com>
Subject: Re: I lost access to my phone number or email
To: noreply@uber.com
Cc: Facebook <in...@support.facebook.com>,
        dev-subscribe@community.apache.org, no-reply@uber.com
Content-Type: multipart/alternative; boundary="00000000000076bb0705e19dd887"