4 ms·
Here's my blog post: http://aws.typepad.com/aws/2011/01/introducing-the-amazon-simple-email-service.html http://aws.typepad.com/aws/2011/01/introducing-the-ama
by jeffbarr 16y ago
Here's my blog post:
http://aws.typepad.com/aws/2011/01/introducing-the-amazon-simple-email-service.html http://aws.typepad.com/aws/2011/01/introducing-the-amazon-si...
If you like to solve puzzles, be sure to read the PS!
- ronnier 16y agoJeff, join the HN phonetool page :-)
- jeffbarr 16y agoWill do!
- Lukeas14 16y agoYou forgot to mention this at your PHP Meetup talk last night. I'm enjoying your book by the way. Thanks.
- moeffju 16y agoHmm, you made me hungry.
- shadowpwner 16y agoI don't have time to solve it, but translated from binary to text is .zncf anug erggro fv abpno Anyone want to take up the mantle? :D
- ROFISH 16y agoThe bitstream converted to their ASCII value is ".zncf anug erggro fv abpno". When reversed and ROT-13ed, it is: "Bacon is better than spam."
- jeffbarr 16y agoIndeed it is!
- jollojou 16y agoJeff, are there any plans to support mailbox provisioning? At the moment I'm using Rackspace's REST API to create a mailbox for our new customers. I like their API, but I don't like the fact that we have to communicate with their IMAP and SMTP servers to receive and send email. It forces us to write a lot of bug-prone email handling code. Could Amazon help in this kind of a scenario?