FAQ
It's a server running only postfix and mailman, with an apache frontend
for mailman. It runs multiple lists, and this is the only problem it
seems to have, so it gets blocked by some recipients.
This doesn't look like a Mailman list. Return-Path: reflects the
envelope sender of the mail and if it is the Apache user, that
indicates this is something like phplist or some other web based list
manager.
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Thanks,
Cameron

Search Discussions

  • Mark Sapiro at Dec 24, 2008 at 12:35 am

    Cameron Camp wrote:
    It's a server running only postfix and mailman, with an apache frontend
    for mailman. It runs multiple lists, and this is the only problem it
    seems to have, so it gets blocked by some recipients.

    Mailman sends mail with an envelope sender (Return-Path:) of
    LISTNAME-bounces at example.com.

    Mailman doesn't rewrite From: headers unless the list is configured as
    anonymous in which case the From: is rewritten to LISTNAME at example.com.

    If you are sure these messages are coming from Mailman, post the
    complete raw headers of a message here, and we'll try to figure out
    what's going on.

    Note other headers you will always find in messages from Mailman

    X-BeenThere: LISTNAME at example.com
    X-Mailman-Version: x.x.x
    Precedence: list

    And headers you may find depending on list configuration

    List-Id:
    List-Unsubscribe:
    List-Archive:
    List-Post:
    List-Help:
    List-Subscribe:

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedDec 24, '08 at 12:21a
activeDec 24, '08 at 12:35a
posts2
users2
websitelist.org

2 users in discussion

Cameron Camp: 1 post Mark Sapiro: 1 post

People

Translate

site design / logo © 2022 Grokbase