You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Roy T. Fielding (JIRA)" <ji...@apache.org> on 2007/01/30 02:25:49 UTC

[jira] Closed: (INFRA-1045) moderation mail seems to have had no effect

     [ https://issues.apache.org/jira/browse/INFRA-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roy T. Fielding closed INFRA-1045.
----------------------------------

    Resolution: Fixed

There are a few possibilities:

  1) you sent the message to the allow address only (as indicated by your queue), in which case the person would have been added to the allow list (for future messages) but the current message would not have been approved;

  2) you sent the message with a sender field other than the address you have as moderator;

  3) you sent an empty message and it was blocked as spam.

I think (1) is most likely.  In any case, the system does seem to be working in general.


> moderation mail seems to have had no effect
> -------------------------------------------
>
>                 Key: INFRA-1045
>                 URL: https://issues.apache.org/jira/browse/INFRA-1045
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mailing Lists
>            Reporter: Justin Mason
>
> Yesterday, someone posted a mail to our PMC list, it was bounced to moderators as a non-subscriber post, I approved it -- but it never appeared.
> I dug out the moderation message from my mail-backup archive, checked the logs, and verified that the "approve" mail went out:
> /var/log/mail.info.0:Nov 20 10:59:27 dogma postfix/smtp[21774]:
> EF333310225: to=<pr...@spamassassin.apache.org>, relay=herse.apache.org[140.211.11.133], delay=29, status=sent (250 Queued! <20...@radish.jmason.org> (Queue-Id: D08B910FB017))
> so the failure was somewhere between the ASF's MX and my MUA.  Asking other subscribers on the "private" list, they didn't see the approved mail either, so it seems unlikely that it made it past the ASF's list software at all.
> Could it have been because the mail was sent to pmc<AT>spamassassin.apache.org instead of private<AT>spamassassin.apache.org, and the forwarding breaks the approval in some way?
> Here are the headers of the moderation mail, and the headers of the held message:
> Return-Path: <pr...@spamassassin.apache.org>
> X-Original-To: jm@jmason.org
> Delivered-To: jm@dogma.boxhost.net
> Received: from minotaur.apache.org (minotaur.apache.org [140.211.11.9])
>         by dogma.boxhost.net (Postfix) with SMTP id 2981B3101E4
>         for <jm...@jmason.org>; Sun, 19 Nov 2006 21:42:32 +0000 (GMT)
> Received: (qmail 35160 invoked by uid 1833); 19 Nov 2006 21:42:26 -0000
> Delivered-To: jm@locus.apache.org
> Received: (qmail 34850 invoked from network); 19 Nov 2006 21:42:16 -0000
> Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
>   by minotaur.apache.org with SMTP; 19 Nov 2006 21:42:16 -0000
> Received: (qmail 6495 invoked by uid 500); 19 Nov 2006 21:38:31 -0000
> Delivered-To: apmail-jm@apache.org
> Received: (qmail 6478 invoked by uid 500); 19 Nov 2006 21:38:31 -0000
> Mailing-List: contact private-help@spamassassin.apache.org; run by ezmlm
> Date: 19 Nov 2006 21:38:31 -0000
> Message-ID: <11...@spamassassin.apache.org>
> From: private-reject-1163972311.6476.eaopghofgbimhbfplhbl@spamassassin.apache.org
> Reply-To: private-accept-1163972311.6476.eaopghofgbimhbfplhbl@spamassassin.apache.org
> Cc: private-allow-tc.1163972311.hmdjpkppnbihifmmdbln-mkettler_sa=verizon.net@spamassa
> ssin.apache.org
> To: Recipient list not shown: ;
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
>         boundary=bidkhiboljmgbgpffohl
> Subject: MODERATE for private@spamassassin.apache.org
> --bidkhiboljmgbgpffohl
> Content-Type: text/plain; charset=us-ascii
> To approve:
>    private-accept-1163972311.6476.eaopghofgbimhbfplhbl@spamassassin.apache.org
> To reject:
>    private-reject-1163972311.6476.eaopghofgbimhbfplhbl@spamassassin.apache.org
> To give a reason to reject:
> %%% Start comment
> %%% End comment
> --bidkhiboljmgbgpffohl
> Content-Type: message/rfc822
> Return-Path: <mk...@verizon.net>
> Delivered-To: moderator for private@spamassassin.apache.org
> Received: (qmail 6461 invoked by uid 500); 19 Nov 2006 21:38:31 -0000
> Delivered-To: apmail-spamassassin-pmc@spamassassin.apache.org
> Received: (qmail 6453 invoked by uid 99); 19 Nov 2006 21:38:31 -0000
> Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
>     by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Nov 2006 13:38:31 -0800
> X-ASF-Spam-Status: No, hits=1.9 required=10.0
>         tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_PASS
> X-Spam-Check-By: apache.org
> Received-SPF: pass (herse.apache.org: domain of mkettler_sa@verizon.net designates 206.46.252.42 as permitted sender)
> Received: from [206.46.252.42] (HELO vms042pub.verizon.net) (206.46.252.42)
>     by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Nov 2006 13:38:18 -0800
> Received: from [192.168.1.3] ([72.81.220.46])
>  by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0J...@vms042.mailsrvcs.net> for
>  pmc@spamassassin.apache.org; Sun, 19 Nov 2006 15:37:40 -0600 (CST)
> Date: Sun, 19 Nov 2006 16:37:40 -0500
> From: Matt Kettler <mk...@verizon.net>
> Subject: [.......]
> In-reply-to: <74...@talk.nabble.com>
> To: pmc@spamassassin.apache.org
> Message-id: <45...@verizon.net>
> MIME-version: 1.0
> Content-type: text/plain; charset=ISO-8859-1
> Content-transfer-encoding: 7bit
> References: <74...@talk.nabble.com> <74...@talk.nabble.com>
> User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
> X-Virus-Checked: Checked by ClamAV on apache.org

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.