From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Subject: gcc.gnu.org cronjobs mails do not make it to the lists
Date: Sat, 07 Jan 2012 09:30:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1201071027180.22517@zbenl.fvgr> (raw)
I was wondering why I had not seen GCC snapshot announcements for
a week or two, so I adjusted the script running in the gccadmin
account to also copy me directly.
And, voila, the copy in my personal inbox arrived (see below); the
one for the gcc@gcc.gnu.org list did not!
A spam filter gone awry?
Gerald
---------- Forwarded message ----------
Return-Path: <gccadmin@gcc.gnu.org>
Received: from sourceware.org (server1.sourceware.org [209.132.180.131])
by mailwash29.pair.com (Postfix) with SMTP id 8B85B30F3F
for <gerald@pfeifer.com>; Fri, 6 Jan 2012 17:48:38 -0500 (EST)
Comment: DKIM? See http://www.dkim.org
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;
d=gcc.gnu.org; s=default; x=1326494918; h=Comment:
DomainKey-Signature:Received:Date:Message-ID:From:To:Subject;
bh=q2eEfBEJTxKHexVjTHFf/FxHab4=; b=lYh5DMTpXNdQoKnTkm/stcfqN0E5P
2S1F1ZTAbyDRlc66zJ8hqBt3WEe67MVC1FnLk8mP6T2KdymMhXMQnGDpMkVvVewC
3/EgTxEY87GRCnxCiX3FOQ6zFAEflm//CJzxwZFz9My6+Ku5DLEQJvQlGYi1StiA
rlqY7MPWOVp320=
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=default; d=gcc.gnu.org;
h=Received:Date:Message-ID:From:To:Subject;
b=dh4vr5ortjZiggah7nvdb90J1Xl8tO9N2UI2rNALzlR/EeHY+9dFbiTT9lEGHQ
oRmsssDhdP3IZy5l82P9VDwVFMpAIiXIpEiGIBMCTrpth6zWQ13bivkNjYMSCvtI
KuLF99TwuqdjPJD66VodFz3nKaLK6QQKyet30y8RYfKwc=;
Received: (qmail 9412 invoked by uid 9160); 6 Jan 2012 22:48:36 -0000
Date: 6 Jan 2012 22:48:36 -0000
Message-ID: <20120106224836.9410.qmail@sourceware.org>
From: gccadmin@gcc.gnu.org
To: gcc@gcc.gnu.org, gerald@pfeifer.com
Subject: gcc-4.6-20120106 is now available
Snapshot gcc-4.6-20120106 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20120106/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch revision 182974
You'll find:
gcc-4.6-20120106.tar.bz2 Complete GCC
MD5=054f4098036cfd1d12a9c684a3ed766c
SHA1=0446510a33a4f9e51aeec0cf3b30a21c59758b19
Diffs from 4.6-20111230 are available in the diffs/ subdirectory.
When a particular snapshot is ready for public consumption the LATEST-4.6
link is updated and a message is sent to the gcc list. Please do not use
a snapshot before it has been announced that way.
next reply other threads:[~2012-01-07 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 9:30 Gerald Pfeifer [this message]
2012-01-15 11:23 ` Gerald Pfeifer
2012-01-15 18:17 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1201071027180.22517@zbenl.fvgr \
--to=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).