easyDNS Blog - Comments

Mark Jeftovic: Bell Canada mail problems to easyDNS domains

nospam@example.com (Mark Jeftovic) — Tue, 29 Apr 2008 20:55:53 -0400

It has turned out to be nothing to do with anycast. The timing was unfortunate as it certainly looked to be the culprit initially.

Rest assured, we won't be rolling it out again until we're positive.

Brian K: Bell Canada mail problems to easyDNS domains

nospam@example.com (Brian K) — Tue, 29 Apr 2008 14:59:47 -0400

Anycast's ups and downs have been a nightmare for EasyDNS's customers. Can EasyDNS consider junking the project, and try it again after learning from the mistakes this time around?

Éric St-Jean: Bell Canada / Bellnexxia mail delivery problems return

nospam@example.com (Éric St-Jean) — Wed, 23 Apr 2008 17:02:26 -0400

Very strange...
out of curiosity, are they sending mail to A records of any random domain, or this is somehow only happening for random domains who's DNS info is served by easydns???
Does it consistently happen for a domain that's affected, or will some emails for an affected domain actually go to the MX?

(doesn't affect me as A==MX, but just wondering)

m.: Server monitoring now in beta

nospam@example.com (m.) — Sun, 20 Apr 2008 20:31:56 -0400

I second the motion! Tracking active servers and dynamically removing them from a round-robin pool when they fail a monitoring test is an exceptionally useful feature.

James Byers: NS2 now deployed as a second anycast strand

nospam@example.com (James Byers) — Wed, 16 Apr 2008 19:41:46 -0400

Great - glad to see you're moving towards anycast across the board!

Mark Jeftovic: easySPF: An SPF Wizard

nospam@example.com (Mark Jeftovic) — Tue, 08 Apr 2008 23:03:21 -0400

You could use DomainKeys now since it's just another type of data to load into a TXT record.

We can always look at adding DKIM support to easySPF so users could generate either/both.

Eliot Lear: easySPF: An SPF Wizard

nospam@example.com (Eliot Lear) — Sat, 08 Mar 2008 08:19:41 -0500

I wonder if EasyDNS could support DKIM, which has far more protection than SPF in any of its variants.

Joan Gobelns: Greylisting for email forwarded to "cox.net"

nospam@example.com (Joan Gobelns) — Thu, 31 Jan 2008 04:44:53 -0500

ok. thx for info.
spam must dead =)

Tim: Comcast silently discarding email containing URLs shortened via easyURL

nospam@example.com (Tim) — Sun, 27 Jan 2008 17:38:46 -0500

Chuck, in my case I'm a Comcast customer on their network. I was using my comcast email address to send messages through Comcast's authenticated SMTP server to non-comcast email addresses on my own mail servers. The comcast server never attempted to relay the mail to my mail server, and never bounced anything back to my comcast address either telling me the message had been discarded.

So I could plainly see that the comcast SMTP server accepted my message, but never delivered it beyond their server.

Thankfully it looks like someone at Comcast was listening-- as you saw starting this morning the filtering appears to have been lifted.

Chuck: Comcast silently discarding email containing URLs shortened via easyURL

nospam@example.com (Chuck) — Sun, 27 Jan 2008 09:23:21 -0500

I tested this morning (GMail to Comcast at 9AM Sunday), and it looks like the filtering has been lifted.

Comcast has a optional Screened-Mail folder (only accessible via web-mail), where it put likely spam. Could the easyurl-emails have been filtered to the Screened-Mail folder?

J. Bill: easySPF: An SPF Wizard

nospam@example.com (J. Bill) — Sun, 09 Sep 2007 17:26:27 -0400

Hi,

I set up an SPF record for my domain some years ago. Lately I've been hoping that having it might cut down on the amount of spam backscatter I get, much of which is from Microsoft Hotmail servers.

After several (typically inefficient) e-mail exchanges with Microsoft/Hotmail support, I came away with the idea--though I never could get them to admit it--that Microsoft/Hotmail doesn't even look at a domain's SPF record unless that domain has been signed up with their "Sender ID Program" at (the rather well-hidden):

http://support.msn.com/eform.aspx?productKey=senderid&page=support_senderid_options_form_byemail&ct=eformts

Anyone know if this is correct?

Anyway, I submitted my domain to the "program" and later got an e-mail, "we were unable to find any SPF record associated with this domain", even though everyone else seems to see it just fine. Hosers.

Jason: easySPF: An SPF Wizard

nospam@example.com (Jason) — Sun, 26 Aug 2007 11:40:31 -0400

EasySPF wizard - you guys rock

Better Search Engine Rankings: Four essential components of Search Engine Optimization

nospam@example.com (Better Search Engine Rankings) — Tue, 21 Aug 2007 01:14:59 -0400

I like the point you made about the meaningful anchor text... but I think it is important that there is variations in the anchor....... because it will look too spammy if there are none.... and you site can get hurt from that.

michael48: Server monitoring now in beta

nospam@example.com (michael48) — Wed, 13 Jun 2007 11:43:28 -0400

I second this, afr. What you describe is exactly what we are looking for in our organization.

I wonder if EasyDNS heard you.

Joe: Greylisting for email forwarded to "cox.net"

nospam@example.com (Joe) — Wed, 16 May 2007 14:36:58 -0400

I find it ironic that Cox.net is taking these efforts to avoid incoming spam, given how much spam I get from their subscribers.