EEVblog Forum Email Problems - Page 1
Forum section: electronics / general

author: EEVblog
author_rank: Unknown
timestamp: February 08, 2016, 04:09:41 am
content: As many know, there has been an ongoing issue with people who use hotmail, Yahoo and several others email domains not getting login info etc.I got a lead on this that perhaps this domain is being blacklistd by Microsoft.I was advised:To get your reputation cleaned up go tohttps://support.live.com/eform.aspx?productKey=edfsmsbl3&ct=eformts&wa=wsignin1.0.So I've filled in that forum in that link and we'll see what happenes.Anyone know if it's possible to check if the site is actually being blacklisted?

author: Brumby
author_rank: Unknown
timestamp: February 08, 2016, 04:16:44 am
content: There are tools out there which are easily found (Google) - but I don't know how good or bad they are.Here's the link for one I tried...http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3aeevblog.com&run=toolpageNothing listed there.

author: EEVblog
author_rank: Unknown
timestamp: February 08, 2016, 04:56:56 am
content: I got a reply:QuoteSo perhaps fixed now?

author: Brumby
author_rank: Unknown
timestamp: February 08, 2016, 05:07:36 am
content: Sounds like it.Server must behave though, or it won't last.

author: tautech
author_rank: Super Contributor
timestamp: February 14, 2017, 08:10:56 am
content: Using the new Reply button.A couple of times since this thread started I've tried to email members and it doesn't work.I'd expect it to open a new email with a members email address already filled in and ready to go.Using Outlook as default email.

author: Unknown
author_rank: Unknown
timestamp: February 14, 2017, 08:52:11 am
content: Sometimes forged spam will end up lowering your domain's reputation (i.e. spammers who send mail "from" eevblog.com). This seems to affect popular domains more; I would guess eevblog.com shows up in enough places to qualify.For larger mail domains I have had to roll out SPF, DKIM, and DMARC to try and aid with the domain reputation issue. It doesn't stop people from forging mail from the domain, but people who implement DMARC on the receiving end will at least reject the forged mail. That ends up being, on the receiving side, the major e-mail providers (e.g. Microsoft), so it can help if you end up having reputation issues with them.I noticed you already have SPF rolled out though, which covers a lot of the concern. If you run your own mail server, which it looks like you do, rolling out the DKIM part requires some configuration. Or you could just outsource the problem to something like Amazon SES.Really for deliverability issues it seems like using a 3rd party service (e.g. Amazon SES, Sendgrid, Mailgun) is the easiest thing to do these days, vs. running a single mail server yourself. If you're in the average shared hosting environment, it may even be an IP reputation issue from your neighbors in the same ASN, allocation or surrounding /24, which is hard to do anything about. Sometimes that will show up on the RBLs (like with the mxtoolbox link above) if it gets bad enough, sometimes it is just the receiving provider's own analytics that canned you.The free e-mail providers (Microsoft, Yahoo, AOL, etc.) are generally cagey about telling you why, or even if, you have been canned. Many anecdotes about it if you go look around. The easiest thing to do is to sign up with an account from each and test manually.DMARC resources:http://blog.endpoint.com/2014/04/spf-dkim-and-dmarc-brief-explanation.htmlhttps://dmarc.org/resources/deployment-tools/http://www.kitterman.com/dmarc/assistant.htmlhttps://dmarcian.com/dmarc-inspector/3rd party mail services:https://aws.amazon.com/ses/details/https://sendgrid.com/http://www.mailgun.com/