X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from mail-vw0-f46.google.com ([209.85.212.46] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.3.9f) with ESMTP id 61503471 for CGatePro@mail.stalker.com; Sun, 29 Aug 2010 04:04:37 -0700 Received-SPF: pass receiver=mail.stalker.com; client-ip=209.85.212.46; envelope-from=j.kohlmorgen@gmail.com Received: by vws3 with SMTP id 3so5146272vws.33 for ; Sun, 29 Aug 2010 04:04:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=juZ0sQIjnK7lRToVW0YLQBXsqvCLLRNNPlA4ZkS/oLc=; b=KtSbjXnjSngiU3r/jZF8skCWLZqZbucF11DglBxdFYumD5MN2zGWGj31jtcu5OMxUM 3LVlugIhKkrvhhrdbzeQ313LBGkLQchcJou76lC2N7ME04qAJodXvHUE3bP2MZGDBzyU 5I8nvtCzTqmQ6T7dAIYsMK38Qtv81nSgE5pFg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=F+q7CP11MwjxaaGsfq+/CWoHxXkLZQfchc/0f9+y0GGtuyctYjMZ/dxM7ycHQ4h9sy irghCM5jDXwI42+Y2ly4fPBsmJ+e02cXK4Q9I612ehqstDoP+6n7HVqkdG+aBzd9RDI4 q32OZQ7ED7/dzQwxM2MZyZ6qsIrC9Z937/roo= MIME-Version: 1.0 Received: by 10.220.49.204 with SMTP id w12mr1868391vcf.243.1283079887058; Sun, 29 Aug 2010 04:04:47 -0700 (PDT) Sender: j.kohlmorgen@gmail.com Received: by 10.220.84.195 with HTTP; Sun, 29 Aug 2010 04:04:47 -0700 (PDT) Date: Sun, 29 Aug 2010 13:04:47 +0200 X-Google-Sender-Auth: lYNzOxnThNMjIn0Rcaj3wUUEY0I Message-ID: Subject: IPv6 Problem - no DNS A-data returned From: jo To: CommuniGate Pro Discussions Content-Type: text/plain; charset=ISO-8859-1 While waiting for an expected mail from SixXS I had a look at the CGP log (5.3.8): 20:45:31.028 1 SMTPI-000972(nlams01.sixxs.net) failed to resolve 'sixxs.net' relay 'mx0.paphosting.net'. Error Code=no DNS A-data returned 20:45:31.028 1 SMTPI-000972(nlams01.sixxs.net) Return-Path 'www-data@sixxs.net' rejected: no DNS A-data returned and some further tries with same results. There really is no A Record for that MX, only AAAA however one of their three MX that has one. I'm not sure which party is not RFC-compliance in this case. Any suggestions how I can force CGPro to resolve alternative MX-servers if the first one has no A-Record? Or is this probably a bug? jo