31 Jul
2013
31 Jul
'13
5:49 a.m.
On 31/07/13 00:43, Nigel Rantor wrote:
[snip]
Yeah, the easiest for me was to tell exim not to use
ipv6 for now.
First email I tried via mail client got through okay.
First email I tried through the automated system that runs behind
alertferret.com failed but the message displayed in gmail as to why this
message was marked as spam was different, it now says it is spam because
it is like other messages that have been marked as spam.
I recently had much the same problem and for the same reason. Gmail -
having been very good about not mis-classifying e-mail as spam -
suddenly started filing all stuff from my domain as spam. The reason as
it turned out was because the e-mail was indeed going via IPv6 and my
SPF record didn't list my IPv6 address.
In the course of investigating I found a very useful site. Send an
e-mail to check-auth(a)verifier.port25.com and you get back an automated
acknowledgement telling you how well it did in security checks. It
covers SPF, DKIM and other bits.
I both fixed my SPF (by adding an IPv6 record to my host name) and added
DKIM signing to my outgoing e-mails. Google is now a happy bunny again.
$ host -t txt sinodun.org.uk
sinodun.org.uk descriptive text "v=spf1 a:ntp.sinodun.org.uk
a:nimbus.sinodun.org.uk ~all"
$ host nimbus.sinodun.org.uk
nimbus.sinodun.org.uk has address 85.119.83.78
nimbus.sinodun.org.uk has IPv6 address 2001:ba8:1f1:f187::2
nimbus.sinodun.org.uk mail is handled by 10 nimbus.sinodun.org.uk.
$
HTH
John