From: Geoff Keating <geoffk@geoffk.org>
To: overseers@gcc.gnu.org
Subject: mailman commands bouncing because they have an empty body?
Date: Tue, 25 Mar 2008 12:08:00 -0000 [thread overview]
Message-ID: <1A5F0CCE-B692-4EDF-BE6A-864B38BBCA55@geoffk.org> (raw)
In-Reply-To: <20080325021315.7AFA633D01E@dragaera.releasedominatrix.com>
[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]
I don't think spam filtering should apply to subscribe confirmation
messages, even if they do look like spam because they have an empty
body.
The full message I sent is also attached below.
Begin forwarded message:
> From: MAILER-DAEMON@releasedominatrix.com (Mail Delivery System)
> Date: 24 March 2008 7:13:15 PM
> To: geoffk@geoffk.org
> Subject: Undelivered Mail Returned to Sender
>
> This is the mail system at host dragaera.releasedominatrix.com.
>
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to <postmaster>
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
> The mail system
>
> <gcc-announce-sc.1206410750.egcomjjibejicoooclhe-geoffk=geoffk.org@gcc.gnu.org
> >:
> host gcc.gnu.org[209.132.176.174] said: 552 spam score exceeded
> threshold
> (in reply to end of DATA command)
> Reporting-MTA: dns; dragaera.releasedominatrix.com
> X-Postfix-Queue-ID: C1ECC33CFA1
> X-Postfix-Sender: rfc822; geoffk@geoffk.org
> Arrival-Date: Tue, 25 Mar 2008 02:12:47 +0000 (UTC)
>
> Final-Recipient: rfc822; gcc-announce-sc.1206410750.egcomjjibejicoooclhe-geoffk=geoffk.org@gcc.gnu.org
> Original-Recipient: rfc822;gcc-announce-sc.1206410750.egcomjjibejicoooclhe-geoffk=geoffk.org@gcc.gnu.org
> Action: failed
> Status: 5.0.0
> Remote-MTA: dns; gcc.gnu.org
> Diagnostic-Code: smtp; 552 spam score exceeded threshold
>
> From: Geoff Keating <geoffk@geoffk.org>
> Date: 24 March 2008 7:12:46 PM
> To: gcc-announce-sc.1206410750.egcomjjibejicoooclhe-geoffk=geoffk.org@gcc.gnu.org
> Subject: Re: confirm subscribe to gcc-announce@gcc.gnu.org
>
>
>
>
>
I originally sent something very much like:
> Message-Id: <3B24B3A3-41D1-4631-9D98-2CA4C0FB6D66@geoffk.org>
> From: Geoff Keating <geoffk@geoffk.org>
> To: gcc-announce-sc.1206410750.egcomjjibejicoooclhe-geoffk=geoffk.org@gcc.gnu.org
> In-Reply-To: <1206410750.606.ezmlm@gcc.gnu.org>
> Content-Type: text/plain;
> charset=US-ASCII;
> format=flowed
> X-Smtp-Server: mail.releasedominatrix.com:geoffk
> Content-Transfer-Encoding: 7bit
> Mime-Version: 1.0 (Apple Message framework v919.2)
> Subject: Re: confirm subscribe to gcc-announce@gcc.gnu.org
> Date: Mon, 24 Mar 2008 19:12:46 -0700
> References: <1206410750.606.ezmlm@gcc.gnu.org>
>
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2460 bytes --]
next parent reply other threads:[~2008-03-25 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080325021315.7AFA633D01E@dragaera.releasedominatrix.com>
2008-03-25 12:08 ` Geoff Keating [this message]
2008-03-25 15:38 ` Frank Ch. Eigler
2008-03-26 16:32 ` 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=1A5F0CCE-B692-4EDF-BE6A-864B38BBCA55@geoffk.org \
--to=geoffk@geoffk.org \
--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).