Advertisement
The two emails listed on the DDI website help-us page ( www.interpretivearson.com/ddi/h....shtml ) do NOT work:
550 5.1.1 <helping-hands@interpretivearson.com>... User unknown
550 5.1.1 <donated-stuff@interpretivearson.com>... User unknown
do you have a contact email that DOES work?
550 5.1.1 <helping-hands@interpretivearson.com>... User unknown
550 5.1.1 <donated-stuff@interpretivearson.com>... User unknown
do you have a contact email that DOES work?
Advertisement
Advertisement
-
Re: emails on DDI website don't work!
Tue, August 9, 2005 - 12:29 AMUrp....we seem to have had an internal miscommunication about email. To my surprise, there DON'T appear to be working emails listed on the site, we'll get that fixed pronto. Thanks for pointing it out. Meanwhile, we obsessively check tribe, so anything you post or message us here will get picked up fairly soon- at least on weekdays, when we're goofing off at work rather than building DDI! -
-
Re: emails on DDI website don't work!
Tue, August 9, 2005 - 12:53 AM> there DON'T appear to be working emails listed on the site
yeah, that was my impression too.
i just wanted to tell you that i have this photo from the Crucible FAF:
www.flickr.com/photos/lou...set-607413/ -
-
Re: emails on DDI website don't work!
Tue, August 9, 2005 - 9:14 AM>i just wanted to tell you that i have this photo from the Crucible FAF:
A great photo! Thanks for sharing. -
-
Re: emails on DDI website don't work!
Tue, August 9, 2005 - 11:03 AMthe comment posted on that photo is also great:
"We do this kind of stuff all the time in Texas, only its generally at a barbque, and we only wear cut-offs. Its a Darwin thing."
-
-
Re: emails on DDI website don't work!
Tue, August 9, 2005 - 11:50 AMOh *awesome*! That is a great photo - thanks for sharing.
Sorry about the email stuff.. as Matt said, it was a miscommunication thing. It should be fixed today, assuming our website/tech guys are awake & coherent :)
Thanks again! -
-
Re: emails on DDI website don't work!
Thu, August 11, 2005 - 12:18 PMYup, now it's fixed. Thanks again for the heads-up!
-
-
-