top | item 3627608

MailerJS: Send email with client-side JavaScript

52 points| unignorant | 14 years ago |mailerjs.com | reply

29 comments

order
[+] bcrescimanno|14 years ago|reply
Flagging for an incredibly misleading topic / tagline. This isn't actually "sending email with client-side javascript;" it's simply a script that allows you to send a message to a service that will generate an email for you. Seriously, it's basically a scripted email form--how this at all interesting?
[+] patsantre|14 years ago|reply
You can also ask how HTML forms are interesting? (Answer is WuFoo)
[+] wvl|14 years ago|reply
Interesting idea. This could be useful for signup and contact forms from a static website.

It's amusing to me that the contact link is just a mailto. Why not use MailerJS?

[+] kijin|14 years ago|reply
> It's amusing to me that the contact link is just a mailto. Why not use MailerJS?

In case someone wants to complain that MailerJS doesn't work in their browser, I guess?

[+] the_bear|14 years ago|reply
I don't see any pricing info on their site. If this is intended to be free for life, then I guess it's pretty nifty. But it would take about 30 minutes for any web developer to duplicate this functionality, so I hope they don't plan on charging for it.
[+] chromedude|14 years ago|reply
It's hidden until you sign up: - Free - 5 emails/day - Basic ($5/month) - 50 emails/day - Big ($29/month) - 500 emails/day - Huge ($99/month) - 5000 emails/day
[+] jrockway|14 years ago|reply
You need to tell Mailer.js about your API key

What exactly stops me from stealing someone else's API key and using it to send spam? You can't trust the client.

[+] wvl|14 years ago|reply
That was my first thought, however, from the docs:

MailerJS will send mail to the address you enter on your account page. You can't specify the receiver dynamically, as client-side JavaScript is publicly accessible by definition, and we want to protect you from spammers.

Why steal someone's api key just so you can send them email?

[+] nilved|14 years ago|reply
You need to input the domains you'll be running Mailer.js on[1], so perhaps API keys only work on those domains? This is just from preliminary reading, so I could be wrong. :)

[1] https://www.mailerjs.com/documentation

[+] thomasjoulin|14 years ago|reply
This is terrible. Overpriced web service that sends emails to a single address, 20-lines script calling the API using jQuery $.ajax (why the dependency ?!) and sends the request with GET instead of PUT or POST...
[+] JRambo|14 years ago|reply
Indeed. Why would you pay for, and be dependent on, a service like this when you could quite easily make something like this? Running on your own server where you have full control.
[+] riffraff|14 years ago|reply
Isn't GET in place to allow cross site ajax?
[+] tauv|14 years ago|reply
This is great but ridiculously overpriced that 1 months delivery is how much I would tack onto a clients bill for building a customer form or implementing this service.

This is just bad value for money

[+] le_isms|14 years ago|reply
Cool. I can think of many reasons it would be bad to have a mailer on the client side, but a big pro w/ this is that you can send mail easily when you only have file access to say, a client's website.
[+] mardiros|14 years ago|reply
Oh, collect email in an html form ?
[+] drivebyacct2|14 years ago|reply
Why email? It seems like an inefficient method to deal with bug reports. Not to mention it seems like this would be really open to abuse.
[+] cleverjake|14 years ago|reply
My guess would be because email is universal, bugtracking platforms are not. It would be easier for me to script a mail filter to auto create bug tickets than wait for them to support my specific kind.
[+] zackattack|14 years ago|reply
I agree, it's overpriced. I would rather just put a snippet in that tracked javascript errors somehow, and also grabbed all of the user's browser information etc. And bonus points if it takes a screenshot (doable with HTML5) and copies over everything from console.log. Would really help with debugging.

P.S. They should have put the pricing information on the home page. Didn't realize they were a YC company either.

[+] josscrowcroft|14 years ago|reply
Open source it. I know, I know, but just do it. Charge for support or something.