I can't help on the technical side, but I volunteer to be a Guinea pig 'receiver' for any tests you might want to run
So... I've tried everything I can think of... I cannot for the life of me get outgoing email to not be seen as spam from this server. This means that many new users verification emails are not being received, as well as subscription notices and birthday notices and so on.
This is also why I haven't put together any newsletters because what would be the point if they don't get received or accepted by the isp's.
At this point I'd like to reach out to anyone who has any experience running an smtp only server (postfix) to help me out and maybe even take a look at things. I'd prefer someone who's been a member here for a long time that I can trust, but I'll take what I can get. If you have any experience with smtp and anti spam measures, please either post here, pm me, or use the contact us link at the bottom of the page.
PR folks please feel free to tweet/fb this request for maximum visibility.
Sent from my m8wl using Tapatalk
I can't help on the technical side, but I volunteer to be a Guinea pig 'receiver' for any tests you might want to run
Free parchments | Free seamless textures | Battle tiles / floor patterns | Room 1024 - textures for CC3 | GUILD CITY INDEX
No one is ever a failure until they give up trying
Have you checked the blacklists? The IP may have ended up on one accidentally.
I just set some notification to 'on' and have received email from this server. I have looked through the headers and can't see anything indicating it may be spam. In fact it verifies that the outgoing server is a permitted sender. Also it verifies that the DKIM sig is valid.
One of the mx nameservers is blacklisted on Backscatterer.
Oh, which one? I'm unable to log on right now.
Sent from my m8wl using Tapatalk
I've sent the info via PM
If you are running SMTP on a send only basis on the web server then I don't think you need a mx record for it. Your incoming mail goes to a different server? That's all you need mx records for so unless the ISP is using the mx records as one of its checks then the blacklist doesn't make sense as I'd have thought the valid SPF record would override this anyway. It seems like an overzealous anti-spam measure, especially as it's probably not the done thing to make a send only server a mx. It could mess up the routing.