4 ms·
Seems to me there's two questions here: 1) do I need to secure this / does it matter if people get spammed? 2) how do I secure this I'd proceed until apprehend
by Travis 16y ago
Seems to me there's two questions here:
1) do I need to secure this / does it matter if people get spammed?
2) how do I secure this
I'd proceed until apprehended with #1. As long as it's simple to delete.
I like the confirmation idea, but which is more pleasing to the user (when a spam message is spoofed/sent in): to see dozens of emails coming in, or to see dozens of places suddenly added?
If it were me, I'd just implement a secret address code. If you're using gmail or something to host the email (and connecting via your web app), just use the '+' notation to extend a single email account. So submissions@app.com could be travis+submissions@app.com and go to the same mailbox (I'd change "travis" to a secret code... but the idea is the same)
- cullenking 16y agoI am not worried about spam since there isn't really any avenue for it. If there isn't a GPX/TCX/KML geo file attached to the email, the upload isn't processed. As a result, I don't expect this to be abused. I think I may just proceed and handle it if it becomes an issue, probably with a simple passphrase in the subject field. I am not using gmail, I actually setup a postfix transport layer, which runs a simple ruby script that just pipes the email through a unix socket to a r receiving server - the server has Resque loaded up and queues up jobs to be handled by my resque workers.