@TitanEmail Heya - we filled out your partnership form a few weeks ago and never heard back. Just wanted to make we didn't miss a reply. I checked our spam filters and didn't see anything. ¯\_(ツ)_/¯
@Yahoo@AOL - ever since November 11th our users have had trouble emailing your users. The error doesn’t make much sense and we’re only getting boilerplate responses from your postmaster that don’t address the issue. How can we contact the right department at Yahoo/AOL?
We’ve been an email provider since 2007 and we scan every message leaving our network for spam. We do our best but we aren’t the ones creating the emails - our end users are - so most of the boilerplate responses don’t make sense.
The error given is “ temporarily deferred due to unexpected volume or user complaints”
Our volume hasn’t unexpectedly changed and we haven’t received any increase in complaints from other sources.
It’s a bit depressing that the AOL Feedback Loop is no more - replaced by a postmaster department that seems to only send out boilerplate messages.
If we were huge - like Gmail - we could get your attention but we’re a small provider hosting only 38,000 domains.
We’re happy to do whatever we can on our end but we need some guidance from your end.
I hate to go to Twitter but none of the official means of contact seem do do anything but reply with a boilerplate responses. I’m hoping maybe I can get to a real human to at least discuss this.
You can reach us at [email protected] - or by replying here.
Please, we need your help.
@HowellsMead You might be surprised how many “development agencies” don’t really have a clue what they’re doing. Not throwing anyone under the bus - but it is something I see regularly and we’re a tiny provider.
It’s frustrating for everyone involved - but regardless we do our best to help.
@henrywright @HowellsMead The problem is that often the user doesn’t know one way or another if it’s a plugin or theme issue. It’s really common to just assume it’s the server / host.
@DerekAshauer @HowellsMead 99.999% of the issues we resolve are issues that the user could have resolved themselves. We do our best to fix issues at the lowest access level and rarely is escalation necessary. That said - always happy to help regardless.
@HowellsMead Usually I would suggest cloning the site / creating a staging copy and testing there. Most sites that can’t bear downtime for testing or development should probably have a staging / non-production copy for the purpose.
This metric on our website updates automatically and is the real and actual average of our response times.
I don’t know anyone else that makes this information public especially when our competitors average hours not minutes.
We also have live chat!
Personally I've never understood how people can tolerate support that takes hours or even days to respond. It's even worse when the responses are not helpful.
That's not how we do things. Our average support ticket response time over the last 7 days is **8 minutes**.