30 Jul
2013
30 Jul
'13
11:43 p.m.
On 30/07/13 23:50, Martijn Grooten wrote:
On Tue, Jul 30, 2013 at 11:37 PM, Nigel Rantor wrote:
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.
So, I deleted all the spam messages and sent another...still being
classed as spam.
Bugger.
I am going to delete all email from the gmail test account I am using
and try again tomorrow maybe, just in case...I am worried though that it
will now have 'learned' that the domain is poisoned...
n
I may be on to something...examining the raw
message in gmail shows the
following;
This explains.
The -all in your SPF record says that you will only send email from
the domains (in your case the A and MX records) that are listed in
your SPF record and you give recipients implicit permission to discard
emails pretending to come from you that fail SPF.
Not many recipients do that, because many domains use -all
incorrectly, but it means your emails will get a lot of spam-points
added and they're going to be blocked unless there is a good reason
for not blocking them. A 19-year old domain with a good reputation
could be such a reason and that's likely what made the difference
here.
The simplest solution would be to add your IPv6 address (or, perhaps,
your /64) to your SPF record as
ip6:2001:ba8:1f1:f03f:216:
4eff:fe05:ae0f.
Or stop sending email over IPv6 of course.