1–10 of 11 posts
If the latter how do you avoid spam filters?
I don't know how to avoid spam filters other than what Googling for it gives me. It'd be interesting to hear what has worked from people who have actually had to do it.
Check out www.isipp.com for email whitelisting services.
Try lyris or ecelerity software for sending out emails. It costs about $1,000 for a license but it is worth the money for the bounce handling, error reporting, setting different time-between sending messages to particular hosts, etc.
Does any service actually let you send emails through a user's account via some sort of API? If you're just using their username and password to log into the service and send the email as them, that strikes me as considerably sketchy. Don't do it. Send the invite from your domain. I don't know how to avoid spam filters other than what Googling for it gives me. It'd be interesting to hear what has worked from people w…
I've seen both approaches - but it seems clear you'll get a better response using the individual's email.
Does any service actually let you send emails through a user's account via some sort of API? If you're just using their username and password to log into the service and send the email as them, that strikes me as considerably sketchy. Don't do it. Send the invite from your domain. I don't know how to avoid spam filters other than what Googling for it gives me. It'd be interesting to hear what has worked from people w…
The API you're talking about is authenticated SMTP. I think he's just talking about setting the From: header. I've seen both approaches - but it seems clear you'll get a better response using the individual's email.
If he's just talking about setting the From: header, wouldn't that make it even more likely to be marked as spam?
Earlier quoted context omitted.
The API you're talking about is authenticated SMTP. I think he's just talking about setting the From: header. I've seen both approaches - but it seems clear you'll get a better response using the individual's email.
Does anything other than GMail provide SMTP? If he's just talking about setting the From: header, wouldn't that make it even more likely to be marked as spam?
1 - Trust for the sender and recipient (we weren't masquerading as someone else, like NikePlus does)
2 - Trust for mail servers (so they're not receiving Gmail branded email from a non-Gmail server)
3 - Allowed integration with companies such as Exact Target who offer "deliverability" as a product (http://email.exacttarget.com/Services/Deliverability.html). This requires it to come from our domain
Facebook's approach seems like good etiquette; I've certainly never heard anyone complain about it...so I'm using a similar approach.
Earlier quoted context omitted.
Does anything other than GMail provide SMTP? If he's just talking about setting the From: header, wouldn't that make it even more likely to be marked as spam?
No mail provider is going to be stupid enough to let a client application relay mail without the user inputing a username/password combo, and I would hope that most users these days are not dumb enough to blindly hand their mail authentication credentials to some random website. This leaves two options, forging the From: header or sending from your own domain. The former will get marked as spam by anything honoring/u…