pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: Bouncing replies
4+ messages / 2 participants
[nested] [flat]
* Re: Bouncing replies
@ 2008-02-11 05:06 Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
0 siblings, 1 reply; 4+ messages in thread
From: Dean Gibson (DB Administrator) @ 2008-02-11 05:06 UTC (permalink / raw)
To: pgsql-sql
I'm open to suggestions. I've been a member of this list for several
years, but every time I post here, some scumbag harvests my eMail
address from it and I get hundreds of spam (most gets filtered by
postfix). I've gone through a half-dozen eMail addresses on this list
alone, and it's been a significant discouragement to posting questions,
let alone answering other people. I finally came up with the solution
below: 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. And boy, does that catch a lot of spam!
I'm curious as to why the list server defaults to using a sender's
address as the "Reply-to" address, rather than using the list address.
That means that, unless the user is careful to "reply all" (or even
better, just reply to the list address), any discussion immediately goes
private.
In fact, I don't understand why the sender's eMail address is visible at
all. Yahoo! is one of the stupidest Internet companies on the face of
the planet, and they seem to have been able to figure it out, as has
most of the free message board software. And yes, I've read
http://www.unicom.com/pw/reply-to-harmful.html -- a very long web page
that repeats the same fallacious arguments over and over. They had some
validity before spam became a problem, but not now.
Anyway, this list is not the place for that discussion. I appreciate
the support you give to not only me, but the entire mailing list. I've
white-listed you, and I'm open to other suggestions.
Sincerely, Dean
On 2008-02-10 19:11, Tom Lane wrote:
> BTW, bouncing mail sent to your advertised reply address is a good way to discourage people from ever answering you again.
>
> regards, tom lane
>
> ----- The following addresses had permanent fatal errors -----
> [postgresql.ultimeth.com]
> (reason: 550 <sss.pgh.pa.us[66.207.139.130]>: Client host rejected: Mail to a list member must be sent via the list)
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Bouncing replies
@ 2008-02-11 08:54 Dave Page <dpage@pgadmin.org>
parent: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dave Page @ 2008-02-11 08:54 UTC (permalink / raw)
To: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>; +Cc: pgsql-sql
On Feb 11, 2008 5:06 AM, Dean Gibson (DB Administrator)
<postgresql@ultimeth.com> 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.
> I'm curious as to why the list server defaults to using a sender's
> address as the "Reply-to" address, rather than using the list address.
> That means that, unless the user is careful to "reply all" (or even
> better, just reply to the list address), any discussion immediately goes
> private.
Because thats the convention on these lists that people are used to
and prefer in general.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Bouncing replies
@ 2008-02-11 09:30 Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
0 siblings, 1 reply; 4+ messages in thread
From: Dean Gibson (DB Administrator) @ 2008-02-11 09:30 UTC (permalink / raw)
To: pgsql-sql
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Bouncing replies
@ 2008-02-11 10:42 Dave Page <dpage@pgadmin.org>
parent: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dave Page @ 2008-02-11 10:42 UTC (permalink / raw)
To: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>; +Cc: pgsql-sql
On Feb 11, 2008 9:30 AM, Dean Gibson (DB Administrator)
<postgresql@ultimeth.com> wrote:
>
> 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.
Without wishing to sound pedantic, the list server itself which was
what you asserted kept changing has in fact not changed. Looking at
the headers I see the message has been relayed through the spam
filtering at hub.org as well which I didn't realise Marc was doing (I
thought he only checked incoming posts), but regardless, all mail
should be coming only from hub.org/postgresql.org machines. I'd be
interested to see where else you've seen it come from, and when.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2008-02-11 10:42 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-02-11 05:06 Re: Bouncing replies Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
2008-02-11 08:54 ` Dave Page <dpage@pgadmin.org>
2008-02-11 09:30 Re: Bouncing replies Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
2008-02-11 10:42 ` Dave Page <dpage@pgadmin.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox