On Wed, Dec 5, 2012 at 5:39 AM, Terry (1stKMH) <terry@???> wrote:
> +++ 1TgF4f-0005mY-29 has not completed +++
> 2012-12-05 13:31:41 1TgF4f-0005mY-29 DKIM: d=msgfocus.com s=msgf
> c=relaxed/relaxed a=rsa-sha256 [verification succeeded]
> 2012-12-05 13:34:02 1TgF4f-0005mY-29 IPv6 socket creation failed: Protocol
> not supported
> 2012-12-05 13:34:07 1TgF4f-0005mY-29 H=relay134.msgfocus.com [86.54.102.134]
> Warning: spam-score-int: -48 (----). spamreject: 100.
This second message that you posted shows that there was a 2:20 second
pause here between the final dot (DKIM is computed at that point) and
when _something_ attempts to connect to an ipv6 address. Then your
spam score happens quickly after that point, just 5 seconds. So the
problem you need to figure out is what is attempting to connect out to
something using ipv6.
To narrow it down, run:
exim -bh 86.54.102.134
EHLO relay134.msgfocus.com
MAIL FROM:<investmentweek.cqcjtnewktcpeonmibc@???>
RCPT TO:<admin@???>
DATA
(paste a simple, but full, email header and body here)
.
Then look at the output and see if you can spot something that is
pausing for a very long time. It won't actually deliver the email,
but it will spam scan it and do everything that it would do for a
regular inbound email.
Did your provider recently enable raw ipv6 to you or did you recently
setup an ipv6 to a tunnel provider and set up an RA (Router
Advertisement)? Likely you can fix this by just disabling ipv6 in
exim.
...Todd
--
The total budget at all receivers for solving senders' problems is $0.
If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine
