Apologies for the top post but sometimes it is in order. Stuart, you
need to contact custhelp.com rather than blockbuster.com. They are the
ones who really get their ox gored. If you make them aware of the
issue and also communicate that your next step will be contacting
blockbuster, they have a very strong incentive for getting it
resolved. I'd give them a call... it would probably end up being less
of your time than emailing over the transom.
There really are potentially multiple correct solutions. Custhelp.com
could include Blockbusters IPs in their record (Do ya really trust me?
Really really?). Problem solved. Another alternative would be to
delegate a subdomain to Blockbuster and only have Blockbuster IPs
listed for that subdomain.
It may be that bounces are actually what is driving the situation.
Someone might not know enough to use aliases and redirects to get
(delayed) bounces and response (even when you tell people not to use
that email address) to the correct place. Just doing a little guessing
here.
In any event, it's likely they don't even know they have a problem. It
amazes me how few people actually look at their bounces.
When you reach someone offer to point them to this email thread.
Consider how many people follow this list. Would you want to be known
as the clueless ones?
As usual, just my 2 cents.
Mike
On Apr 4, 2005 5:30 PM, Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com> wrote:
I signed up with blockbuster.com online rentals. Unfortunately, the
email from their service always fails SPF:
2005Apr04 16:29:19 [15795] connect from smtp2.online.blockbuster.com at
('129.33.92.80', 50671) EXTERNAL
2005Apr04 16:29:20 [15795] hello from smtp2.online.blockbuster.com
2005Apr04 16:29:20 [15795] mail from <blockbuster(_at_)custhelp(_dot_)com>
('SIZE=1705',)
2005Apr04 16:29:20 [15795] Received-SPF: fail (mail.bmsi.com: domain of
custhelp.com does not designate 129.33.92.80 as permitted sender)
client-ip=129.33.92.80; envelope-from=blockbuster(_at_)custhelp(_dot_)com;
helo=smtp2.online.blockbuster.com;
2005Apr04 16:29:20 [15795] rcpt to <dvd(_at_)gathman(_dot_)org> ()
2005Apr04 16:29:20 [15795] Subject: Blockbuster has shipped Children of Heaven
2005Apr04 16:29:21 [15795] CBV: blockbuster(_at_)custhelp(_dot_)com (cached)
2005Apr04 16:29:21 [15795] dspam
custhelp.com text "v=spf1 ip4:63.240.89.0/24 ip4:63.240.103.0/26
ip4:216.136.162.64/26 ip4:216.136.229.0/24 ip4:216.136.168.64/27
ip4:206.17.168.0/25 ip4:64.79.35.0/24 -all"
The custhelp.com SPF record is beautiful, by Radu's standards. Unfortunately,
Blockbuster doesn't seem to have a clue about forging the custhelp.com
domain on their email. I have repeatedly submitted problem reports,
and have configured pymilter to send frequent DSNs complaining about the
problem when they send me the forged email (instead of rejecting it), but they
never even respond to my problem reports. (I suppose that would be a plug for
NetFlix, but Blockbuster includes 2 in-store rentals/month - although I am
getting frustrated enough to think about switching.)
So, how does one go about getting big lazy corps to fix serious email
problems?