From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: overseers@gcc.gnu.org
Subject: Re: gcc-patches: Spam filter?
Date: Thu, 25 Sep 2014 04:26:00 -0000 [thread overview]
Message-ID: <20140925042555.GA22897@lug-owl.de> (raw)
In-Reply-To: <20140924181325.GA2126@ednor.casa.cgf.cx>
[-- Attachment #1.1: Type: text/plain, Size: 1124 bytes --]
On Wed, 2014-09-24 14:13:25 -0400, Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> wrote:
> On Wed, Sep 24, 2014 at 02:31:02PM +0200, Jan-Benedict Glaw wrote:
> > In July, I discussed the problem of re-encoding PGP-MIME messages
> > (which may break signatures.) Yesterday, it seems one of my
> > emails didn't get through some (spam?) filter at all.
>
> It's hard to say why you would have been blocked without the
> original email but I've super-whitelisted you so you should now
> bypass all spam checking (except for html-based email).
>
> If you still have the original email, I wouldn't mind seeing it, If
> you can gzip it and send it here
Sure, it's properly saved. I'll attach it to this email and re-send it
later on.
Thanks for the help,
Jan-Benedict
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: "really soon now": an unspecified period of time, likly to
the second : be greater than any reasonable definition
of "soon".
[-- Attachment #1.2: MAINTAINERS-patch.mbox.gz --]
[-- Type: application/octet-stream, Size: 14386 bytes --]
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-09-25 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 12:31 Jan-Benedict Glaw
2014-09-24 18:13 ` Christopher Faylor
2014-09-25 4:26 ` Jan-Benedict Glaw [this message]
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=20140925042555.GA22897@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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).