David Cottle: > Content-Description: Undelivered Message > Content-Type: message/rfc822 > Content-Transfer-Encoding: 8bit > > Received: from server.engineering.idb (unknown [127.0.0.1]) > by server.engineering.idb (Postfix) with ESMTP id C3F5B13C002D > for <webmas...@aus-city.com>; Sun, 11 Jan 2009 23:43:36 +0000 (UTC) > Received-SPF: none (no valid SPF record) > Received: from hosting.mgapi.edu (unknown [82.179.217.2]) > by server.engineering.idb (Postfix) with SMTP > for <webmas...@aus-city.com>; Sun, 11 Jan 2009 23:43:35 +0000 (UTC) > Received: from dpkpyv (181.138.153.218) > by hosting.mgapi.edu; Mon, 12 Jan 2009 02:43:44 +0300
This is your problem. If webmas...@aus-city.com is invalid, then hosting.mgapi.edu MUST NOT ACCEPT MAIL FOR THAT RECIPIENT. To learn more about blocking invalid recipients on an inbound transit mail server, see the archives, as this is discussed here about every other week. See also: http://www.postfix.org/postconf.5.html#relay_recipient_maps http://www.postfix.org/postconf.5.html#relay_domains http://www.postfix.org/ADDRESS_VERIFICATION_README.html Wietse
