From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55837 invoked by alias); 8 Aug 2018 10:31:29 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 55709 invoked by uid 89); 8 Aug 2018 10:31:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=ruan, Ruan, emails, visit X-HELO: mail-it0-f52.google.com Received: from mail-it0-f52.google.com (HELO mail-it0-f52.google.com) (209.85.214.52) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Aug 2018 10:31:27 +0000 Received: by mail-it0-f52.google.com with SMTP id g141-v6so2870204ita.4 for ; Wed, 08 Aug 2018 03:31:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aI3AfQwPi7DkG5ulEBA7O3Dh53x6NzMROTk1nSzAKKQ=; b=AR21pohZKrV4z4uQePd+q/CsxS0SQ89/SyT9+iKi8nwdPL83Mml4MfM4nwmYtL2XI+ zy54HlyDuibwyI1OA+42itjS0zICyPxxAbcleb8PZuBO3viMpRIOQhr0Fted/S8x2L6N 0sOUmWhAITpbrcnSvuXoiwwPrdFoU1GM4j238yHFHGISCAgiEgV5QiR/+Pp2fPl9cpxX yJICQirukSEdEyzOZ25RSrQyCxOCF7GX2zBTxwIKvkGwow8Tikv7RDQm1DeQ29FTiI/d AZd4nCC2ku6cYc0B/aT27pNkgUVFDWOCA4wrbBCohOM24R+3i2K6mTNWpK24cSB01ReO cN+g== MIME-Version: 1.0 References: <1533450048.58449.ezmlm-warn@gcc.gnu.org> <10925af5-122e-ad85-63ae-67e2e0412999@winterflaw.net> <20180805214658.GC31204@gate.crashing.org> <7172ce35-7132-8254-2f10-f86c2fe6c375@aol.com> In-Reply-To: From: Jonathan Wakely Date: Wed, 08 Aug 2018 10:31:00 -0000 Message-ID: Subject: Re: ezmlm warning To: Yubin Ruan Cc: tprince@intelretiree.com, n8tm@aol.com, gcc-help Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-08/txt/msg00025.txt.bz2 On Wed, 8 Aug 2018 at 02:31, Yubin Ruan wrote: > Now I understand why I am always receiving these emails. Is it OK to > just ignore them all ? I've never seen one that informed me of a mail I actually wanted to read, but I wouldn't say in general it's *always* safe to ignore them all. Sometimes it could be a problem with your mail server. As a gmail user, you can probably assume that bounces are due to gmail policies, not due to their servers being down. You can look at the bounce message to see the reason. For the recent example it said this: Remote host said: 552-5.7.0 This message was blocked because its content presents a potential 552-5.7.0 security issue. Please visit 552-5.7.0 https://support.google.com/mail/?p=BlockedMessage to review our 552 5.7.0 message content and attachment content guidelines. j10-v6si6866809pgq.503 - gsmtp That seems pretty clear it was intentionally rejected by gmail, and so if you trust google to filter your mail, you can ignore it. If you want to know what you missed you can send an email to gcc-index@gcc.gnu.org and look for the message ID given in the bounce notification. If the subject line looks like spam, ignore it. But I don't bother doing that.