Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 4D6362E2E52 for ; Mon, 11 Feb 2008 06:15:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 89726-01-5 for ; Mon, 11 Feb 2008 06:15:25 -0400 (AST) Received: from mail.mailpen.net (mail.mailpen.net [209.90.228.14]) by postgresql.org (Postfix) with ESMTP id 6B9622E2EE3 for ; Mon, 11 Feb 2008 05:30:04 -0400 (AST) Received: from [172.24.2.1] (pool-71-113-24-134.sttlwa.dsl-w.verizon.net [71.113.24.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mailpen.net (Postfix) with ESMTP id C652C2FE802 for ; Mon, 11 Feb 2008 01:30:01 -0800 (PST) Message-ID: <47B015CA.1030108@ultimeth.com> Date: Mon, 11 Feb 2008 01:30:50 -0800 From: "Dean Gibson (DB Administrator)" Organization: UltiMeth Systems User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: Bouncing replies Content-Type: multipart/alternative; boundary="------------030607060000080902080607" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/72 X-Sequence-Number: 30163 This is a multi-part message in MIME format. --------------030607060000080902080607 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit PostgreSQL list serve output has not been connecting from mail.postgresql.org for a LONG time (see the headers below). Currently they've been connecting from various hosts at the hub.org domain, but there have several other non-postgresql.org connecting domains in the past. Whenever I stop getting PostgreSQL mail, I go check my Postfix logs to see what the new hostname's domain is, and update my whitelist. While mail may originally come from a postgresql.org host, as I'm sure you know, the only information that a receiving SMTP server can trust is the connecting IP address and the hostname from a DNS reverse IP lookup. Everything else can be falsified. That's why virtually all SMTP-level spam filtering (including all DNS blacklist lookups) is based on the connecting IP address. -- Dean -------- Original Message -------- Return-Path: X-Original-To: *** Delivered-To: *** Received: from mail.mailpen.net (mail.mailpen.net [209.90.228.14]) by sc440a.internal.mailpen.net (Postfix) with ESMTP id 384105444E9 for <***>; Mon, 11 Feb 2008 00:56:14 -0800 (PST) Received: by mail.mailpen.net (Postfix) id D33062FE81D; Mon, 11 Feb 2008 00:56:13 -0800 (PST) Delivered-To: *** Received: from maia-1.hub.org (maia-1.hub.org [200.46.204.191]) by mail.mailpen.net (Postfix) with ESMTP id 952632FE802 for <***>; Mon, 11 Feb 2008 00:56:11 -0800 (PST) Received: from postgresql.org (postgresql.org [200.46.204.71]) by maia-1.hub.org (Postfix) with ESMTP id 6734DDB3A14; Mon, 11 Feb 2008 04:56:07 -0400 (AST) Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 14BEC2E030B for ; Mon, 11 Feb 2008 04:54:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 80826-05 for ; Mon, 11 Feb 2008 04:54:01 -0400 (AST) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by postgresql.org (Postfix) with ESMTP id 108552E0306 for ; Mon, 11 Feb 2008 04:54:04 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id r21so3723208wxc.28 for ; Mon, 11 Feb 2008 00:54:04 -0800 (PST) Received: by 10.151.144.4 with SMTP id w4mr905002ybn.199.1202720044201; Mon, 11 Feb 2008 00:54:04 -0800 (PST) Received: by 10.150.96.5 with HTTP; Mon, 11 Feb 2008 00:54:04 -0800 (PST) Message-ID: <937d27e10802110054h6538294bwcb8100665048bd57@mail.gmail.com> Date: Mon, 11 Feb 2008 08:54:04 +0000 From: Dave Page <***> To: Dean Gibson (DB Administrator) <***> Subject: Re: [SQL] Bouncing replies Cc: pgsql-sql@postgresql.org In-Reply-To: <47AFD7DD.2040000@ultimeth.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47AFA703.5060907@ultimeth.com> <15372.1202698673@sss.pgh.pa.us> <15505.1202699499@sss.pgh.pa.us> <47AFD7DD.2040000@ultimeth.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Mailing-List: pgsql-sql List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Status: O X-UID: 25516 Content-Length: 1252 X-Keywords: On Feb 11, 2008 5:06 AM, Dean Gibson (DB Administrator) wrote: > If mail to my list address doesn't come from one of your list > servers (and those seems to change much more often than any other list I > belong to), it gets rejected. Those must be some *really* long-lived lists. Our mailserver has been mail.postgresql.org for probably 7 or 8 years now. Many moons ago we did use some additional relay servers, but I don't think we've done that for 5+ years. --------------030607060000080902080607 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit PostgreSQL list serve output has not been connecting from mail.postgresql.org for a LONG time (see the headers below).  Currently they've been connecting from various hosts at the hub.org domain, but there have several other non-postgresql.org connecting domains in the past.  Whenever I stop getting PostgreSQL mail, I go check my Postfix logs to see what the new hostname's domain is, and update my whitelist.

While mail may originally come from a postgresql.org host, as I'm sure you know, the only information that a receiving SMTP server can trust is the connecting IP address and the hostname from a DNS reverse IP lookup.  Everything else can be falsified.  That's why virtually all SMTP-level spam filtering (including all DNS blacklist lookups) is based on the connecting IP address.

-- Dean

-------- Original Message --------
Return-Path: <pgsql-sql-owner+M30162@postgresql.org>
X-Original-To: ***
Delivered-To: ***
Received: from mail.mailpen.net (mail.mailpen.net [209.90.228.14]) by sc440a.internal.mailpen.net (Postfix) with ESMTP id 384105444E9 for <***>; Mon, 11 Feb 2008 00:56:14 -0800 (PST)
Received: by mail.mailpen.net (Postfix) id D33062FE81D; Mon, 11 Feb 2008 00:56:13 -0800 (PST)
Delivered-To: ***
Received: from maia-1.hub.org (maia-1.hub.org [200.46.204.191]) by mail.mailpen.net (Postfix) with ESMTP id 952632FE802 for <***>; Mon, 11 Feb 2008 00:56:11 -0800 (PST)
Received: from postgresql.org (postgresql.org [200.46.204.71]) by maia-1.hub.org (Postfix) with ESMTP id 6734DDB3A14; Mon, 11 Feb 2008 04:56:07 -0400 (AST)
Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 14BEC2E030B for <pgsql-sql-postgresql.org@postgresql.org>; Mon, 11 Feb 2008 04:54:09 -0400 (AST)
Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 80826-05 for <pgsql-sql-postgresql.org@postgresql.org>; Mon, 11 Feb 2008 04:54:01 -0400 (AST)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by postgresql.org (Postfix) with ESMTP id 108552E0306 for <pgsql-sql@postgresql.org>; Mon, 11 Feb 2008 04:54:04 -0400 (AST)
Received: by wx-out-0506.google.com with SMTP id r21so3723208wxc.28 for <pgsql-sql@postgresql.org>; Mon, 11 Feb 2008 00:54:04 -0800 (PST)
Received: by 10.151.144.4 with SMTP id w4mr905002ybn.199.1202720044201; Mon, 11 Feb 2008 00:54:04 -0800 (PST)
Received: by 10.150.96.5 with HTTP; Mon, 11 Feb 2008 00:54:04 -0800 (PST)
Message-ID: <937d27e10802110054h6538294bwcb8100665048bd57@mail.gmail.com>
Date: Mon, 11 Feb 2008 08:54:04 +0000
From: Dave Page <***>
To: Dean Gibson (DB Administrator) <***>
Subject: Re: [SQL] Bouncing replies
Cc: pgsql-sql@postgresql.org
In-Reply-To: <47AFD7DD.2040000@ultimeth.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47AFA703.5060907@ultimeth.com> <15372.1202698673@sss.pgh.pa.us> <15505.1202699499@sss.pgh.pa.us> <47AFD7DD.2040000@ultimeth.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Mailing-List: pgsql-sql
List-Archive: <http://archives.postgresql.org/pgsql-sql>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-sql.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@postgresql.org>
List-Post: <mailto:pgsql-sql@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-sql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org
Status: O
X-UID: 25516
Content-Length: 1252
X-Keywords: 


On Feb 11, 2008 5:06 AM, Dean Gibson (DB Administrator) wrote:
> If mail to my list address doesn't come from one of your list
> servers (and those seems to change much more often than any other list I
> belong to), it gets rejected.

Those must be some *really* long-lived lists. Our mailserver has been
mail.postgresql.org for probably 7 or 8 years now. Many moons ago we
did use some additional relay servers, but I don't think we've done
that for 5+ years.
--------------030607060000080902080607--