It's a SPF problem, a misconfiguration at bitcointalk
Any mailserver will reject this emails if SPF (Sender Policy Framework) is enabled
current bitcointalk configuration:
v=spf1 mx a include:
amazonses.com -all
But last attempts in my mail.log from:
ec2-52-45-214-107.compute-1.
amazonaws.com
this does not match -> REJECT
May 1 14:30:25 mail1 policyd-spf[19143]: Fail; identity=helo; client-ip=52.45.214.107; helo=[Suspicious link removed]; receiver=xxx@xxx.xx
May 1 14:30:25 mail1 postfix/smtpd[19133]: NOQUEUE: reject: RCPT from ec2-52-45-214-107.compute-1.amazonaws.com[52.45.214.107]: 550 5.7.1 <
xxx@xxx.xx>: Recipient address rejected: Message rejected due to: SPF fail - not authorized
The domain name itself has nothing to do with the "include=" of the SPF record. Including amazonses.com just authorizes anything covered in the SPF/MX records of amazonses.com as being authorized, not the domain itself. The fact that it's coming from a server with amazonaws.com makes no difference as it is more about the IP address it's coming from.
The same IP address your listing in your SPF fail was passed by Gmail's SPF check not too long (April 20th is the last time I saw a message pass) my first SPF failure happened on the 27th but I don't have any messages to look at between those dates.
SPF's are failing for this IP as of right now but to my knowledge Amazon has only ever required including the amazonses.com in the SPF record to pull in those servers. (
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/spf.html)
Based on the dates, my only guess might be that theymos modified or removed an A record when dealing with recent DDoS issues here:
https://bitcointalk.org/index.php?topic=1880126.msg18689262#msg18689262And that maybe it included the IP that is now failing the SPF check? 52.45.214.107