From owner-freebsd-questions@FreeBSD.ORG Tue Feb 12 08:50:15 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E38DE16A417 for ; Tue, 12 Feb 2008 08:50:15 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9FC1413C447 for ; Tue, 12 Feb 2008 08:50:15 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.32] (a89-182-5-151.net-htp.de [89.182.5.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 9EF2DA44529; Tue, 12 Feb 2008 09:50:14 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-questions@freebsd.org Date: Tue, 12 Feb 2008 09:50:11 +0100 User-Agent: KMail/1.9.7 References: <402803274.21432@eyou.com> <200802120940.56386.wundram@beenic.net> In-Reply-To: <200802120940.56386.wundram@beenic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802120950.12120.wundram@beenic.net> Cc: Da Rock Subject: Re: FW: failure notice X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2008 08:50:16 -0000 Am Dienstag, 12. Februar 2008 09:40:55 schrieb Heiko Wundram (Beenic): > Am Dienstag, 12. Februar 2008 09:03:10 schrieb Da Rock: > > Anybody know why this would be happening to me? Every time I post I get > > this back, yet my post shows up on the list. > > You're sending from a hotmail.com address, without using a hotmail.com > server as outgoing mail relay. Ugh, I should have checked your mail headers before posting this. You are sending from a hotmail.com server. So, either hotmail has their SPF-records misconfigured (which I would guess isn't the case, because lots of people would complain in this case), or the final recipients SPF setup on their mailserver (mail.163.com) is broken (which I guess is most probably the case here). -- Heiko Wundram Product & Application Development