From owner-freebsd-questions@FreeBSD.ORG Tue Feb 12 09:06:35 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 A017316A41B for ; Tue, 12 Feb 2008 09:06:35 +0000 (UTC) (envelope-from michael.ross@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id DF0C213C45E for ; Tue, 12 Feb 2008 09:06:34 +0000 (UTC) (envelope-from michael.ross@gmx.net) Received: (qmail invoked by alias); 12 Feb 2008 09:06:32 -0000 Received: from e176154133.adsl.alicedsl.de (EHLO localhost) [85.176.154.133] by mail.gmx.net (mp015) with SMTP; 12 Feb 2008 10:06:32 +0100 X-Authenticated: #11429267 X-Provags-ID: V01U2FsdGVkX19RCjpdV8hRQhzDVnGQ2caTHP+jEB8ZZ4auv5NM0H 4BBs36LMGaBY9t Date: Tue, 12 Feb 2008 10:06:31 +0100 To: "Heiko Wundram (Beenic)" , freebsd-questions@freebsd.org From: "Michael Ross" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 References: <402803274.21432@eyou.com> <200802120940.56386.wundram@beenic.net> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <200802120940.56386.wundram@beenic.net> User-Agent: Opera Mail/9.25 (FreeBSD) X-Y-GMX-Trusted: 0 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 09:06:35 -0000 Am 12.02.2008, 09:40 Uhr, 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. > I am getting this messages, too, for the address of kugua065315@163.com, as OP. And I _am_ using the gmx.net smtp as outgoing relay (just double-checked). My bet is 163.com screwed their setup.