Ask HN: Facebook emails as facebookmail.com. Should I?
If I'm startup.com, is it advisable to have my corporate email come from [email protected], and user notifications come from [email protected]?
I assume facebook has both [email protected] and [email protected] so that their employees don't get their own outgoing emails blocked as spam the same way that "Bob sent you a message on Facebook!" messages might.
However, I am guessing that my notifications might be likely to be tagged as spam if notifications come from startupmail.com and those notifications contain links to startup.com (or a reply-to: to [email protected]).
Any experienced insights much appreciated!
EDIT: Any thoughts on the variant of having [email protected] and [email protected], and the effect of a spam rating of the subdomain on the main domain?
(
11 comments
| 12 points
| on HN
)
That panic didn’t last that long (I have some capacity for logical deduction and Google helped) but I do think that it’s not really a very clever idea to send out your mail from a domain you are not normally using. There might be technical reasons but I think the user experience is just not great. I’m not sure, though. Most people probably wouldn’t even notice.
I mean, why not use @startupmail.com for your personal addresses and have your app use @startup.com? You can set up aliases like [email protected] so the obvious guess-address still works, but this way your users don't end up asking "is this legit?", your corp emails still won't get blocked for spam, etc.
I really dislike the UI of sending app related emails from a different domain. It's an ugly solution to what may be a non-problem, and if there really is a need to separate corp from app addresses, treat your app as the number one priority. Use gmail for your corp correspondence if you have to.
Because then people might wonder if I really did represent startup.com when I emailed them about a biz dev deal.
I agree with you regarding the trust/user experience issue with sending notifications from startupmail.com.
Well yeah, but I'd argue that that's better than having your users wonder if they're really getting emailed by startup.com or not.
I've got dozens of "your friends are waiting for you on Facebook" notifications to email addresses that are not even linked on Facebook. I can see where people would mark these as spam.
Also given the less savvy end of the computer user spectrum, I can see where people will just click 'spam' as a quicker alternative to clicking delete and then 'Yes I want to delete'
Finally with the sheer volume of notifications generated, I can see where some overly sensitive mail servers may block the sending domain for too many messages.
And if it is already an issue, providing more details about the type and quantity of emails you are sending, and the blocking you are experiencing, will help you get better answers.
I'm mostly worried about signup/+3 day/+7 day notifications to new users from damaging the spam reputation of [email protected] when I attempt to email important people to discuss e.g. biz dev deals.
I wonder if the issues of needing to send out mail from multiple IP addresses and per-ISP rate throttling are as important as they say. I guess I'll find out if I'm lucky enough to ever hit those limits.