BLOG

Links for 1/7

Chris K. at Bronto blogs about in-store address collection and delivery issues. Chris is right, the Spamhaus issue isn’t going away any time soon. And companies collecting addresses in store / at point of sale really need to figure out how to make sure that their data capture is accurate. That means addressing everything from customers giving the wrong address to typos and other transcription errors.

Gene M. at Forbes asks Is Constant Contact the Best E-Mail Marketing Service?. I’m not sure Constant Contact is the best, but it’s nice to see that some people do realize that the occasional compliance incident just means that the ISP is actually monitoring things.

Matt B from Return Path posts his predictions for the new year. While I don’t always do predictions, I agree with all of his.

The Next Web says that Yahoo users are being compromised by an XSS exploit. I have noticed a lot more virus from Yahoo users over the last 2 days, including one person who said their account was broken into while she was on the ski slopes. It may not be exactly an XSS hack, but something is broken at Yahoo and the spammers seem to be somehow getting around Yahoo’s outbound filters.

Comment:

Your email address will not be published. Required fields are marked *

  • ReturnPath on DMARC+Yahoo

    Over at ReturnPath Christine has an excellent non-technical summary of the DMARC+Yahoo situation, along with some solid recommendations for what actions you might take to avoid the operational problems it can cause.No Comments


  • AOL problems

    Lots of people are reporting ongoing (RTR:GE) messages from AOL today.  This indicates the AOL mail servers are having problems and can't accept mail. This has nothing to do with spam, filtering or malicious email. This is simply their servers aren't functioning as well as they should be and so AOL can't accept all the mail thrown at them. These types of blocks resolve themselves. 1 Comment


  • Fixing discussion lists to work with new Yahoo policy

    Al has some really good advice on how to fix discussion lists to work with the new Yahoo policy. One thing I would add is the suggestion to actually check dmarc records before assuming policy. This will not only mean you're not having to rewrite things that don't need to be rewritten, but it will also mean you won't be caught flat footed if (when?) other free mail providers start publishing p=reject.No Comments


Archives