Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1125A9FB837 for ; Tue, 16 Oct 2007 13:46:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 76410-01 for ; Tue, 16 Oct 2007 13:46:39 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 9C4519FB7EC for ; Tue, 16 Oct 2007 13:46:40 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 88A51DCC8C9; Tue, 16 Oct 2007 18:46:39 +0200 (CEST) Message-ID: <4714EAE4.6030004@hagander.net> Date: Tue, 16 Oct 2007 18:46:28 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: "Marc G. Fournier" CC: Andrew Sullivan , pgsql-www@postgresql.org Subject: Re: Mail setup broken (still/again?) References: <20071016085209.GD22159@svr2.hagander.net> <20071016140750.GF3255@crankycanuck.ca> <3509D6C66029EDED469CF3C0@ganymede.hub.org> In-Reply-To: <3509D6C66029EDED469CF3C0@ganymede.hub.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/107 X-Sequence-Number: 12694 Marc G. Fournier wrote: > > > --On Tuesday, October 16, 2007 10:07:50 -0400 Andrew Sullivan > wrote: > >> On Tue, Oct 16, 2007 at 10:52:09AM +0200, Magnus Hagander wrote: >>> 1) Tries to deliver to svr1.postgresql.org. This machine response that the >>> user is unknown, *but does so with a 450 error code indicating that this >>> is a temporary error*. This is of course wrong, it should be responding >>> with 550. >> This does appear to be an error. > > Changed ... postfix's default is 550, but we had: Great. > unknown_local_recipient_reject_code = 450 > > Funny thing is, looking on google, this isn't that particularly unusual: Yeah, IIRC there was a recommendation when this feature was added to postfix that you do this. And it is a good recommendation - you just have to remember to switch it back to 550 when you've tested :-) (yes, I've forgotten that on my servers as well a couple of times) >> Nit: it's not an alias; if it were (i.e. a CNAME or probably a >> DNAME), it would be an error, because MX records can't point to >> CNAMEs. It's just another name for the same address, which is >> perfectly acceptable. It does seem a little baroque. > > Fixed, now MX 0 == mail.postgresql.org, also an A record ... Good. >>> 2c) mx3 is then *graylisted* by svr1. A backup MX must *NOT* be graylisted >>> by the primary machine. I know I have mentioned this several times before >>> wrt other machines. >> Absolutely. > > Fixed ... I had missed the mx3 IP in the mynetworks file on postgresql.org ... > the other 3 mx servers should never have been affected, only the offsite one ... Ah, that's why it reappeared. Thanks for the quick fixes! //Magnus