Re: OpenDKIM fails to sign IPv6 localhost originating email
SM skrev den 2013-01-05 11:14:
> I am not sure I understood what you said. Can you send me the
> headers of the message from the mailing list?
Authentication-Results: mx.elandsys.com; dkim=pass
reason="1024-bit key; insecure key"
header.d=junc.org header.i=_at_junc.org header.b=OBOj7TZo;
dkim-adsp=pass
this is when i send, all ok as it can be
Authentication-Results: duggi.junc.org; dkim=pass reason="1024-bit key"
header.d=opendkim.org
header.i=opendkim-users-bounce_at_lists.opendkim.org
header.b=eYcXBUvq; dkim-adsp=fail
when it comes back to duggi, adsp fails here since my opendkim does not
use my own signing ?, when it actuly is not removed ?
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=junc.org; s=mail;
t=1357374068; x=1357377668;
bh=IStQAa86QwT6kOYiRPEcHP83TgGxagnO+0rymiRueGY=;
h=Date:From:To:Subject:In-Reply-To:References;
z=Date:=20Sat,=2005=20Jan=202013=2009:21:07=20+0100|From:=20Benny=2
0Pedersen=20<me_at_junc.org>|To:=20<opendkim-users_at_lists.opendkim.org
>|Subject:=20Re:=20OpenDKIM=20fails=20to=20sign=20IPv6=20localhost
=20originating=20email|In-Reply-To:=20<alpine.BSF.2.00.13010407463
91.17133_at_medusa.blackops.org>|References:=20<68C5B4CD23E220C2493FE
6AD_at_[192.168.1.64]>=0D=0A=20<alpine.BSF.2.00.1301031453150.17133_at_m
edusa.blackops.org>=0D=0A=20<64AD7890FDAAD993E6C86F3F_at_[192.168.1.6
4]>=0D=0A=20<6.2.5.6.2.20130103152058.0a852500_at_resistor.net>=0D=0A
=20<7fd098a54abeb66dec67a2f05ab68038_at_junc.eu>=0D=0A=20<alpine.BSF.
2.00.1301040207390.17133_at_medusa.blackops.org>=0D=0A=20<3bb441b53f9
b64f82b014e807e389366_at_junc.eu>=0D=0A=20<alpine.BSF.2.00.1301040746
391.17133_at_medusa.blackops.org>;
b=OBOj7TZopV8PSWtK88g6+szUmzEBkD0f1EtCM+lJubXdR98M9XbfC4qFhrKY9439x
ndMI0xlDlx2bBocBoCdq2BFEJAsvjeXBZAXXxA1rEd/TDIXpahJXf+gPiOf7oLUguS
ptOODdAKCDpMOfEdJYWkgcUD/ETCQ1uomdz+O58Q=
i like to understand why its so
Received on Sat Jan 05 2013 - 11:36:02 PST
This archive was generated by hypermail 2.3.0
: Sat Jan 05 2013 - 11:45:02 PST