IETF Logo Mail Archive

Re: [pim] Hello PIM, is there any configuration wrong in PIM list ?

Stig Venaas <stig@venaas.com> Fri, 17 July 2020 17:10 UTC

Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 179A33A084A for <pim@ietfa.amsl.com>; Fri, 17 Jul 2020 10:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venaas-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hs5UlkViOKX4 for <pim@ietfa.amsl.com>; Fri, 17 Jul 2020 10:10:27 -0700 (PDT)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6793F3A0858 for <pim@ietf.org>; Fri, 17 Jul 2020 10:10:27 -0700 (PDT)
Received: by mail-pj1-x1029.google.com with SMTP id a9so1209901pjd.3 for <pim@ietf.org>; Fri, 17 Jul 2020 10:10:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ZI2clY+1juQJlumPkt+yKSOM96VJFEDaBfZota1VSDs=; b=K6NNBuEQJryYNPx+Ilm0LYWR+Wg25Q/uHXoZv4pjIIsDIDwORXvsLnc1ZukVNY5BHe X1dc4nhCDnlXpmcuGlfYgJIJp9pE4yksi1HDDdow4OmzilXUAOP/U6UJv67o8JwllKk7 7abSTSGbbt41WGPnNQbu6Lnk0yKqY6znA3rxsLmkBmEdi/8NFh0EMtJPjZa5O/hjjwM1 GNoDDI+67QhjIU6TqQ6LJ5wia6fD/MSrNL6/bFyp1XYgp84h/NX6XFPUQ4nLT5LsH1u7 9devGcbf3ETvtEbIF+obqLDrPDX6RsCy4UEtKW3SYBOkB3s7yU+mhFJdoV8pOPLL+rVe mDHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ZI2clY+1juQJlumPkt+yKSOM96VJFEDaBfZota1VSDs=; b=AGOeiglRg7BWXpGESXv2KU2mx7Vey5a/+yHpVKAXHZ2jue6SamXf7Pm2KVRhsP8AmX fDbqcKkcmI3oFwDI4fny8R/pAWrp+gw7KPaxUGjXGgHgQZwP7TFBpNMi314zqHF59HwG ejYgFesgePKulO8xpa6YcCIGAEgugXZJwThgn6FniP2/oKv1gbrm4B1wCu6LfmYxd/in SUv35kKZKMTlTRe5EFq1GTIptTmu/vTBDa6v0TK+SZDzIV/0neH2/I2OS+gsf51hPdn2 pAjuIjrvAG+j3IwKjNSNQDht1PZBDUKAcKfauV9JaZCNSSA2954r7cl/lpJmKE5NZSb3 ++dQ==
X-Gm-Message-State: AOAM531ueqqqIjK1H5aaAzCDb3sZx1/OxZ3A/YqgCwvyAxHnfPkxBDst Lpdd0i460UKQKPguy9QjEf+F3AyKmBpwEAIdI0uuOA==
X-Google-Smtp-Source: ABdhPJxlc7G6N2kFYC8a4AyQb8so1dNC04qHQn4r8wdpoqbL1KpkdUpk4H1+u3AT7mBDmGW8XiQoe69fhRLFihJ08UM=
X-Received: by 2002:a17:90a:750:: with SMTP id s16mr4294006pje.218.1595005826801; Fri, 17 Jul 2020 10:10:26 -0700 (PDT)
MIME-Version: 1.0
References: <732604ad73d742928a56dceb24ec4f97@huawei.com>
In-Reply-To: <732604ad73d742928a56dceb24ec4f97@huawei.com>
From: Stig Venaas <stig@venaas.com>
Date: Fri, 17 Jul 2020 10:10:15 -0700
Message-ID: <CAHANBtLPT5gHpfZNmTBgtYJYz=+fcJ3BbiaoiZ4u3rK9NHiB8w@mail.gmail.com>
To: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
Cc: "pim@ietf.org" <pim@ietf.org>, "pim-chairs@ietf.org" <pim-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/cy1l3wVhr12KiZDq0rg0LuLwIKU>
Subject: Re: [pim] Hello PIM, is there any configuration wrong in PIM list ?
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2020 17:10:29 -0000

Hi

Your message was too large for the configured max for pim. I approved
it now, so it should be sent to the list now.
Regards,
Stig

On Fri, Jul 17, 2020 at 3:15 AM Xiejingrong (Jingrong)
<xiejingrong@huawei.com> wrote:
>
> Hello PIM,
>
>
>
> Is there any configuration wrong in PIM list ?
>
>
>
> I received the following message when I sent a message ccing the PIM list and SPRING list just now.
>
>
>
> I checked and find it failed on PIM list but succeed on SPRING list (https://mailarchive.ietf.org/arch/msg/spring/J4D2sk_oc91rNmdfYtcBmx_dxS4/).
>
>
>
> Don’t know why this happened and how to solve, so try this mail, and apologize if disturbs you.
>
>
>
> Thanks
>
> Jingrong
>
>
>
> ---------------------------- The message I received ------------------------------
>
>
>
> Your mail to 'pim' with the subject
>
>
>
>     RE: [spring] Understanding the replication draft
>
>
>
> Is being held until the list moderator can review it for approval.
>
>
>
> The reason it is being held:
>
>
>
>     Message body is too big: 46141 bytes with a limit of 40 KB
>
>
>
> Either the message will get posted to the list, or you will receive notification of the moderator's decision.  If you would like to cancel this posting, please visit the following URL:
>
>
>
>     https://www.ietf.org/mailman/confirm/pim/861d0e048976af6ec519b6dc16f5f633b4c6d35b
>
>
>
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

v2.23.0 | Report a Bug | By Email