FAQ
Mailman 2.1.10 on OpenBSD 4.4 with Postfix 2.5.3

Checked the FAQ and searched Google but didn't see anything that
directly addressed this:

Most messages make it into the archives but a few do not. I've pasted
below a sample of a message that didn't make it to the archive. I
suspect that it might be related to Postfix's message handling but am
not sure what's missing from the offending messages.

Thanks in advance for clues on debugging this.

dn

((addresses, domains and IP addresses anonymized))

Return-Path: <user at example.com>
X-Original-To: myname at mydomain.tld
Delivered-To: myname at mydomain.tld
Received: from localhost (localhost [127.0.0.1])
by mail.mydomain.tld (Postfix) with ESMTP id 616F15B3159
for <myname at mydomain.tld>; Sun, 11 Jan 2009 10:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at localdomain
X-Spam-Flag: NO
X-Spam-Score: -1.671
X-Spam-Level:
X-Spam-Status: No, score=-1.671 tagged_above=-999 required=6.31
tests=[AWL=-0.929, BAYES_20=-0.74, SPF_PASS=-0.001]
Received: from mail.mydomain.tld ([127.0.0.1])
by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id kkMkBnOO63bs for <myname at mydomain.tld>;
Sun, 11 Jan 2009 10:16:19 -0800 (PST)
Received: from mx.otherdomain.net (blackhelicopters.otherdomain.net
[666.1.2.3])
by mail.mydomain.tld (Postfix) with ESMTP id 6BDC15B3157
for <myname at mydomain.tld>; Sun, 11 Jan 2009 10:16:19 -0800 (PST)
Received: from elvis.example.net (dsl1-2-3.yetanotherdomain.net [1.2.3.666])
(Authenticated sender: someuser at example.com)
by mx.otherdomain.net (Postfix) with ESMTP id 2A02D196841
for <myname at mydomain.tld>; Sun, 11 Jan 2009 10:16:18 -0800 (PST)
Message-Id: <23A25183-7F35-4D19-B528-53C0A6D4F73B at example.com>
From: someuser example <someuser at example.com>
To: myname <myname at mydomain.tld>
In-Reply-To: <4969A68C.8000900 at mydomain.tld>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: [myname members] Message size limits (was: (no subject))
Date: Sun, 11 Jan 2009 10:16:17 -0800
References: <0089FC87E3644D2895590076717851F9 at Wizardry>
<52F0A1B1F834C54DB1C0CF32182D6E9B03D7B307 at sagan.aperio.int>
<4969A68C.8000900 at mydomain.tld>
X-Mailer: Apple Mail (2.930.3)
On Jan 10, 2009, at 11:58 AM, myname wrote:

With due respect, I think it's a lousy idea
+1

-someuser

Search Discussions

  • Mark Sapiro at Mar 26, 2009 at 3:05 pm

    David Newman wrote:
    Most messages make it into the archives but a few do not. I've pasted
    below a sample of a message that didn't make it to the archive. I
    suspect that it might be related to Postfix's message handling but am
    not sure what's missing from the offending messages.

    The message below wasn't posted to the list. It is an off-list reply to
    you only.

    ((addresses, domains and IP addresses anonymized))

    Return-Path: <user at example.com>
    X-Original-To: myname at mydomain.tld
    Delivered-To: myname at mydomain.tld
    Received: from localhost (localhost [127.0.0.1])
    by mail.mydomain.tld (Postfix) with ESMTP id 616F15B3159
    for <myname at mydomain.tld>; Sun, 11 Jan 2009 10:16:21 -0800 (PST)
    X-Virus-Scanned: amavisd-new at localdomain
    X-Spam-Flag: NO
    X-Spam-Score: -1.671
    X-Spam-Level:
    X-Spam-Status: No, score=-1.671 tagged_above=-999 required=6.31
    tests=[AWL=-0.929, BAYES_20=-0.74, SPF_PASS=-0.001]
    Received: from mail.mydomain.tld ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id kkMkBnOO63bs for <myname at mydomain.tld>;
    Sun, 11 Jan 2009 10:16:19 -0800 (PST)
    Received: from mx.otherdomain.net (blackhelicopters.otherdomain.net
    [666.1.2.3])
    by mail.mydomain.tld (Postfix) with ESMTP id 6BDC15B3157
    for <myname at mydomain.tld>; Sun, 11 Jan 2009 10:16:19 -0800 (PST)
    Received: from elvis.example.net (dsl1-2-3.yetanotherdomain.net [1.2.3.666])
    (Authenticated sender: someuser at example.com)
    by mx.otherdomain.net (Postfix) with ESMTP id 2A02D196841
    for <myname at mydomain.tld>; Sun, 11 Jan 2009 10:16:18 -0800 (PST)
    Message-Id: <23A25183-7F35-4D19-B528-53C0A6D4F73B at example.com>
    From: someuser example <someuser at example.com>
    To: myname <myname at mydomain.tld>
    In-Reply-To: <4969A68C.8000900 at mydomain.tld>
    Content-Type: text/plain; charset=US-ASCII; format=flowed
    Content-Transfer-Encoding: 7bit
    Mime-Version: 1.0 (Apple Message framework v930.3)
    Subject: Re: [myname members] Message size limits (was: (no subject))
    Date: Sun, 11 Jan 2009 10:16:17 -0800
    References: <0089FC87E3644D2895590076717851F9 at Wizardry>
    <52F0A1B1F834C54DB1C0CF32182D6E9B03D7B307 at sagan.aperio.int>
    <4969A68C.8000900 at mydomain.tld>
    X-Mailer: Apple Mail (2.930.3)
    On Jan 10, 2009, at 11:58 AM, myname wrote:

    With due respect, I think it's a lousy idea
    +1

    -someuser

    ------------------------------------------------------
    Mailman-Users mailing list
    Mailman-Users at python.org
    http://mail.python.org/mailman/listinfo/mailman-users
    Mailman FAQ: http://wiki.list.org/x/AgA3
    Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
    Unsubscribe: http://mail.python.org/mailman/options/mailman-users/mark%40msapiro.net

    Security Policy: http://wiki.list.org/x/QIA9
    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • David Newman at Mar 26, 2009 at 8:57 pm

    On 3/26/09 8:05 AM, Mark Sapiro wrote:
    David Newman wrote:
    Most messages make it into the archives but a few do not. I've pasted
    below a sample of a message that didn't make it to the archive. I
    suspect that it might be related to Postfix's message handling but am
    not sure what's missing from the offending messages.

    The message below wasn't posted to the list. It is an off-list reply to
    you only.
    Well, that will teach me not to post before finishing morning coffee. Sorry.

    Here's another message that actually was cc:'d to a list but didn't make
    it into the archives. This subscriber is a frequent poster and other
    messages of his exist in the archives.

    It's HTML mail but then so is all this subscriber's other mail.

    Thanks again for any clues on what caused this not to get archived.

    dn


    ((addresses, domains and IP addresses anonymized))


    Return-Path: <members-bounces+user=example.org at example.org>
    X-Original-To: user at example.org
    Delivered-To: user at example.org
    Received: from localhost (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id 4F3335B31A7
    for <user at example.org>; Tue, 24 Mar 2009 21:54:21 -0700 (PDT)
    X-Virus-Scanned: amavisd-new at mail.example.org
    X-Spam-Flag: NO
    X-Spam-Score: -2.597
    X-Spam-Level:
    X-Spam-Status: No, score=-2.597 tagged_above=-999 required=6.31
    tests=[AWL=0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
    Received: from mail.example.org ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id UqCM5fJ2cnnr for <user at example.org>;
    Tue, 24 Mar 2009 21:54:20 -0700 (PDT)
    Received: from mail.example.org (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id 99DB35B3221
    for <user at example.org>; Tue, 24 Mar 2009 21:53:02 -0700 (PDT)
    X-Original-To: members at example.org
    Delivered-To: members at mail.example.org
    Received: from localhost (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id CF2CE5B31A5
    for <members at example.org>; Tue, 24 Mar 2009 21:52:36 -0700 (PDT)
    X-Virus-Scanned: amavisd-new at mail.example.org
    Received: from mail.example.org ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id xitN3rRm3SCk for <members at example.org>;
    Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
    Received: from obfuscatedhost.hotmail.com (obfuscatedhost.hotmail.com
    [666.1.2.3])
    by mail.example.org (Postfix) with ESMTP id C6F295B3161
    for <members at example.org>; Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
    Received: from COL113-W22 ([65.55.34.200]) by obfuscatedhost.hotmail.com
    with Microsoft SMTPSVC(6.0.3790.3959);
    Tue, 24 Mar 2009 21:52:29 -0700
    Message-ID: <COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl>
    Content-Type: multipart/mixed;
    boundary="_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_"
    X-Originating-IP: [98.149.111.105]
    From: George Washington <gw at msn.com>
    Date: Tue, 24 Mar 2009 21:52:29 -0700
    Importance: Normal
    In-Reply-To: <2868DBC10E894FC7B7CF953D5BCAF832 at Wizardry>
    References: <2868DBC10E894FC7B7CF953D5BCAF832 at Wizardry>
    MIME-Version: 1.0
    X-OriginalArrivalTime: 25 Mar 2009 04:52:29.0023 (UTC)
    FILETIME=[7FF8E6F0:01C9AD05]
    Subject: [members] the subject of my message '09
    X-BeenThere: members at example.org
    X-Mailman-Version: 2.1.10
    Precedence: list
    Cc: user member list <members at example.org>
    List-Id: user member list <members.example.org>
    List-Unsubscribe: <https://mail.example.org/mailman/options/members>,
    <mailto:members-request at example.org?subject=unsubscribe>
    List-Archive: <https://mail.example.org/mailman/private/members>
    List-Post: <mailto:members at example.org>
    List-Help: <mailto:members-request at example.org?subject=help>
    List-Subscribe: <https://mail.example.org/mailman/listinfo/members>,
    <mailto:members-request at example.org?subject=subscribe>
    To: user webmaster <user at example.org>
    Sender: members-bounces+user=example.org at example.org
    Errors-To: members-bounces+user=example.org at example.org

    --_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_
    Content-Type: multipart/alternative;
    boundary="_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_"

    --_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_
    Content-Type: text/plain; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable



    ((message text omitted))

    --_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_
    Content-Type: text/html; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable


    <html>
    <head>
    <style>
    .hmmessage P
    {
    margin:0px;
    padding:0px
    }
    body.hmmessage
    {
    font-size: 10pt;
    font-family:Verdana
    }
    </style>
    </head>
    <body class='hmmessage'>

    ((html version omitted))


    </body>
    </html>
    --_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_--

    --_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_
    Content-Type: text/plain
    Content-Transfer-Encoding: base64
    Content-Disposition: attachment; filename="ATT00000"

    X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1lbWJlcnMg
    bWFpbGluZyBsaXN0DQptZW1iZXJzQGN2Y2Jpa2Uub3JnDQpodHRwczovL21haWwuY3ZjYmlrZS5v
    cmcvbWFpbG1hbi9saXN0aW5mby9tZW1iZXJzDQo
    --_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_
    Content-Type: text/plain; charset="us-ascii"
    MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Disposition: inline

    _______________________________________________
    members mailing list
    members at example.org
    https://mail.example.org/mailman/listinfo/members

    --_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_--
  • Mark Sapiro at Mar 26, 2009 at 9:49 pm

    David Newman wrote:
    Here's another message that actually was cc:'d to a list but didn't make
    it into the archives. This subscriber is a frequent poster and other
    messages of his exist in the archives.

    It's HTML mail but then so is all this subscriber's other mail.

    Thanks again for any clues on what caused this not to get archived.

    dn

    OK. This one came from the list. There are only a few reasons why a
    particular post would not be archived, assuming archiving is working
    in general.

    1) There could be something in this particular post that throws an
    exception in ArchRunner. This is unlikely, but check Mailman's error
    log to be sure.

    2) If a post contains an "X-Archive: No" or an "X_No_Archive:" header,
    it won't be archived. This doesn't seem to be the case here.

    3) If the post's Message-ID is the same as that of an already archived
    post, it will be in the LISTNAME.mbox file, but it won't be in the
    pipermail archive. grep Mailman's post log for this post's Message-ID

    grep "<COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl>" /path/to/logs/post

    and see if there is more than one post with this Message-ID (don't
    forget to check rotated logs as well if any). You can also see if this
    post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will
    tell you that Mailman tried to archive it. Note that two different
    messages should never have the same Message-ID, but ...


    ((addresses, domains and IP addresses anonymized))


    Return-Path: <members-bounces+user=example.org at example.org>
    X-Original-To: user at example.org
    Delivered-To: user at example.org
    Received: from localhost (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id 4F3335B31A7
    for <user at example.org>; Tue, 24 Mar 2009 21:54:21 -0700 (PDT)
    X-Virus-Scanned: amavisd-new at mail.example.org
    X-Spam-Flag: NO
    X-Spam-Score: -2.597
    X-Spam-Level:
    X-Spam-Status: No, score=-2.597 tagged_above=-999 required=6.31
    tests=[AWL=0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
    Received: from mail.example.org ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id UqCM5fJ2cnnr for <user at example.org>;
    Tue, 24 Mar 2009 21:54:20 -0700 (PDT)
    Received: from mail.example.org (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id 99DB35B3221
    for <user at example.org>; Tue, 24 Mar 2009 21:53:02 -0700 (PDT)
    X-Original-To: members at example.org
    Delivered-To: members at mail.example.org
    Received: from localhost (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id CF2CE5B31A5
    for <members at example.org>; Tue, 24 Mar 2009 21:52:36 -0700 (PDT)
    X-Virus-Scanned: amavisd-new at mail.example.org
    Received: from mail.example.org ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id xitN3rRm3SCk for <members at example.org>;
    Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
    Received: from obfuscatedhost.hotmail.com (obfuscatedhost.hotmail.com
    [666.1.2.3])
    by mail.example.org (Postfix) with ESMTP id C6F295B3161
    for <members at example.org>; Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
    Received: from COL113-W22 ([65.55.34.200]) by obfuscatedhost.hotmail.com
    with Microsoft SMTPSVC(6.0.3790.3959);
    Tue, 24 Mar 2009 21:52:29 -0700
    Message-ID: <COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl>
    Content-Type: multipart/mixed;
    boundary="_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_"
    X-Originating-IP: [98.149.111.105]
    From: George Washington <gw at msn.com>
    Date: Tue, 24 Mar 2009 21:52:29 -0700
    Importance: Normal
    In-Reply-To: <2868DBC10E894FC7B7CF953D5BCAF832 at Wizardry>
    References: <2868DBC10E894FC7B7CF953D5BCAF832 at Wizardry>
    MIME-Version: 1.0
    X-OriginalArrivalTime: 25 Mar 2009 04:52:29.0023 (UTC)
    FILETIME=[7FF8E6F0:01C9AD05]
    Subject: [members] the subject of my message '09
    X-BeenThere: members at example.org
    X-Mailman-Version: 2.1.10
    Precedence: list
    Cc: user member list <members at example.org>
    List-Id: user member list <members.example.org>
    List-Unsubscribe: <https://mail.example.org/mailman/options/members>,
    <mailto:members-request at example.org?subject=unsubscribe>
    List-Archive: <https://mail.example.org/mailman/private/members>
    List-Post: <mailto:members at example.org>
    List-Help: <mailto:members-request at example.org?subject=help>
    List-Subscribe: <https://mail.example.org/mailman/listinfo/members>,
    <mailto:members-request at example.org?subject=subscribe>
    To: user webmaster <user at example.org>
    Sender: members-bounces+user=example.org at example.org
    Errors-To: members-bounces+user=example.org at example.org
    <body snipped>

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • David Newman at Mar 27, 2009 at 5:30 am

    On 3/26/09 2:49 PM, Mark Sapiro wrote:
    There are only a few reasons why a
    particular post would not be archived, assuming archiving is working
    in general.
    Archiving is working in general.
    1) There could be something in this particular post that throws an
    exception in ArchRunner. This is unlikely, but check Mailman's error
    log to be sure.

    2) If a post contains an "X-Archive: No" or an "X_No_Archive:" header,
    it won't be archived. This doesn't seem to be the case here.

    3) If the post's Message-ID is the same as that of an already archived
    post, it will be in the LISTNAME.mbox file, but it won't be in the
    pipermail archive. grep Mailman's post log for this post's Message-ID

    grep "<COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl>" /path/to/logs/post

    and see if there is more than one post with this Message-ID (don't
    forget to check rotated logs as well if any).
    Went 0 for 3 on these.
    You can also see if this
    post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will
    tell you that Mailman tried to archive it. Note that two different
    messages should never have the same Message-ID, but ...
    And the message is the LISTNAME.mbox file.

    Another post from this same subscriber today also failed to make it into
    the archive. Any other places to check?

    Many thanks

    dn


    ((addresses, domains and IP addresses anonymized))


    Return-Path: <members-bounces+user=example.org at example.org>
    X-Original-To: user at example.org
    Delivered-To: user at example.org
    Received: from localhost (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id 4F3335B31A7
    for <user at example.org>; Tue, 24 Mar 2009 21:54:21 -0700 (PDT)
    X-Virus-Scanned: amavisd-new at mail.example.org
    X-Spam-Flag: NO
    X-Spam-Score: -2.597
    X-Spam-Level:
    X-Spam-Status: No, score=-2.597 tagged_above=-999 required=6.31
    tests=[AWL=0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
    Received: from mail.example.org ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id UqCM5fJ2cnnr for <user at example.org>;
    Tue, 24 Mar 2009 21:54:20 -0700 (PDT)
    Received: from mail.example.org (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id 99DB35B3221
    for <user at example.org>; Tue, 24 Mar 2009 21:53:02 -0700 (PDT)
    X-Original-To: members at example.org
    Delivered-To: members at mail.example.org
    Received: from localhost (localhost [127.0.0.1])
    by mail.example.org (Postfix) with ESMTP id CF2CE5B31A5
    for <members at example.org>; Tue, 24 Mar 2009 21:52:36 -0700 (PDT)
    X-Virus-Scanned: amavisd-new at mail.example.org
    Received: from mail.example.org ([127.0.0.1])
    by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id xitN3rRm3SCk for <members at example.org>;
    Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
    Received: from obfuscatedhost.hotmail.com (obfuscatedhost.hotmail.com
    [666.1.2.3])
    by mail.example.org (Postfix) with ESMTP id C6F295B3161
    for <members at example.org>; Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
    Received: from COL113-W22 ([65.55.34.200]) by obfuscatedhost.hotmail.com
    with Microsoft SMTPSVC(6.0.3790.3959);
    Tue, 24 Mar 2009 21:52:29 -0700
    Message-ID: <COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl>
    Content-Type: multipart/mixed;
    boundary="_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_"
    X-Originating-IP: [98.149.111.105]
    From: George Washington <gw at msn.com>
    Date: Tue, 24 Mar 2009 21:52:29 -0700
    Importance: Normal
    In-Reply-To: <2868DBC10E894FC7B7CF953D5BCAF832 at Wizardry>
    References: <2868DBC10E894FC7B7CF953D5BCAF832 at Wizardry>
    MIME-Version: 1.0
    X-OriginalArrivalTime: 25 Mar 2009 04:52:29.0023 (UTC)
    FILETIME=[7FF8E6F0:01C9AD05]
    Subject: [members] the subject of my message '09
    X-BeenThere: members at example.org
    X-Mailman-Version: 2.1.10
    Precedence: list
    Cc: user member list <members at example.org>
    List-Id: user member list <members.example.org>
    List-Unsubscribe: <https://mail.example.org/mailman/options/members>,
    <mailto:members-request at example.org?subject=unsubscribe>
    List-Archive: <https://mail.example.org/mailman/private/members>
    List-Post: <mailto:members at example.org>
    List-Help: <mailto:members-request at example.org?subject=help>
    List-Subscribe: <https://mail.example.org/mailman/listinfo/members>,
    <mailto:members-request at example.org?subject=subscribe>
    To: user webmaster <user at example.org>
    Sender: members-bounces+user=example.org at example.org
    Errors-To: members-bounces+user=example.org at example.org
    <body snipped>
  • Mark Sapiro at Mar 27, 2009 at 4:07 pm

    David Newman wrote:
    On 3/26/09 2:49 PM, Mark Sapiro wrote:

    You can also see if this
    post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will
    tell you that Mailman tried to archive it. Note that two different
    messages should never have the same Message-ID, but ...
    And the message is the LISTNAME.mbox file.

    Another post from this same subscriber today also failed to make it into
    the archive. Any other places to check?

    You can look in the archives/private/LISTNAME/yyyy-mmmm.txt file and
    see if it is there. In fact you can do
    grep "COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl" archives/private/LISTNAME/*.txt
    And see if you can find it in any month's .txt file.

    The archiving code first appends the message to the LISTNAME.mbox file
    and then adds it to the pipermail archive which includes the periodic
    .txt file. If the message gets as far as being appended to
    LISTNAME.mbox, only a processing exception (which should be logged) or
    the message-id already existing in the archive should prevent it's
    being added.

    In fact, you could grep the LISTNAME.mbox for the message-id to see if
    there's a duplicate there.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • David Newman at Mar 30, 2009 at 4:47 am

    On 3/27/09 9:07 AM, Mark Sapiro wrote:
    David Newman wrote:
    On 3/26/09 2:49 PM, Mark Sapiro wrote:

    You can also see if this
    post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will
    tell you that Mailman tried to archive it. Note that two different
    messages should never have the same Message-ID, but ...
    And the message is the LISTNAME.mbox file.

    Another post from this same subscriber today also failed to make it into
    the archive. Any other places to check?

    You can look in the archives/private/LISTNAME/yyyy-mmmm.txt file and
    see if it is there. In fact you can do
    grep "COL113-W22FAD79423AE3666EAAE42CC900 at phx.gbl" archives/private/LISTNAME/*.txt
    And see if you can find it in any month's .txt file.

    The archiving code first appends the message to the LISTNAME.mbox file
    and then adds it to the pipermail archive which includes the periodic
    .txt file. If the message gets as far as being appended to
    LISTNAME.mbox, only a processing exception (which should be logged) or
    the message-id already existing in the archive should prevent it's
    being added.

    In fact, you could grep the LISTNAME.mbox for the message-id to see if
    there's a duplicate there.
    Pilot error. This poster's messages are in the archive, just not where I
    expected them to be in the threaded display. Possibly this is because
    the poster replied to some other message and just changed the subject,
    but in any event the messages are there.

    Thanks/sorry

    dn

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedMar 26, '09 at 2:59p
activeMar 30, '09 at 4:47a
posts7
users2
websitelist.org

2 users in discussion

David Newman: 4 posts Mark Sapiro: 3 posts

People

Translate

site design / logo © 2022 Grokbase