81–90 of 110 posts
I'm wondering the legality of this... The emails in your mailbox aren't yours to do with as you please - they're all still owned by their original sender, who has given you an implicit license to read them, and store them for later re-reading. You don't really have rights to datamine, aggregate, train AI on, post stats about, etc. the data in those emails. Its a violation of the rights of the original sender to do it…
I'm wondering the legality of this... The emails in your mailbox aren't yours to do with as you please - they're all still owned by their original sender, who has given you an implicit license to read them, and store them for later re-reading. You don't really have rights to datamine, aggregate, train AI on, post stats about, etc. the data in those emails. Its a violation of the rights of the original sender to do it…
Earlier quoted context omitted.
Either way, I find the syntax of both to be extremely ugly. Arguably this may simply be me not getting JavaScript. Starting a line with ; is just plain weird and the last bit })() seems like German, where all the stuff that you technically not need to understand the sentence is at the end. Maybe someone can explain with JavaScript developers love anonymous functions so much. Why not just name your function and make t…
Not all JavaScript devs. Love the language, hate the popularity of anonymous functions and non-descriptive variable names. My production code as a sample. http://designbymobi.us/wp-content/uploads/2020/02/rabbitmq-c...
function someName(p1, p2) {}
and then when you need it for something, like a handler, just say:
handler: someName
Earlier quoted context omitted.
It always annoys me when some general purpose utility or script is written in JavaScript because I refuse to install node on my computer.
What would have been a shell script in the 1980s, a Perl script in the 1990s, a Python script in the 2000s, is now a JS bundled with an outdated Chromium build aka an Electron app.
Deliverability is a big marketing/selling point for all these providers & important selection criteria for their customers. So it'd be very interesting to see what % of emails for each provider landed in Inbox vs Promotions/Spam/Junk folder.
> So it'd be very interesting to see what % of emails for each provider landed in Inbox vs Promotions/Spam/Junk folder. Are those percentages really a good measure of deliverability? I mean, a significant portion of “one million dollars for you” scams in my Gmail spam folder are from @gmail.com addresses; that doesn’t say anything about gmail.com to gmail.com deliverability.
If you mess-up really bad you will have bad deliverability across the board.
The mistakes can be numerous:
* bad setup like broken DKIM
* bad sending parameters like opening too many connections by IP to a given provider
* bad content format like too many large images
* bad actual content
* bad recipient list management with lists containing lots of typos, none existent mailboxes, spam traps, etc
* miss-managing unsubscribes
* bad bounce handling
If this happens, you can have some if not all of your IPs blacklisted, maybe even your domain. In worst cases, a whole IPv4 range is blacklisted.
Then a second aspect to take into account is the open rate and the click through rate (people actually clicking a link in a marketing email), this one can vary depending on the company activities, and also the quality of their marketing content, but is generally in the range of a few percents at most. And then, you also have to take into account the actual impact in term of sells which will be even lower.
Deliverability is import, it's not rocket science, but it's a lot of small items various people at various stages (tech, creatives, marketers, etc) must be cautious about which makes it actually quite hard.
Earlier quoted context omitted.
Modern Perl is fine too
I haven't used Perl in about 12 years, has it changed much since then? Do you have any links to good examples/comparisons?
http://modernperlbooks.com/books/modern_perl_2016/index.html
I've mentioned it before, but reading this book and applying its concepts (along with judicial use Damian Conway's Perl Best Practices) changed my view of Perl from "well, I guess I'll use it since it's here," to "I really enjoy using Perl".
Mark Jason Dominus's Higher-Order Perl was another enjoyable read, for its advice on using Perl as a more functional programming language.
It's interesting that this is missing a lot of major enterprise marketing email providers. The author clearly isn't subscribing to things like Best Buy's weekly deal email, or Target cart reminders.
Who on earth, that knows how to unsubscribe, would ever subscribe to spam?
I must admit that I was a bit shocked when I realized that the author had used javascript for this task. At first I assumed that he was scripting some webmail interface but then I saw that he was using 'emailjs-imap-client'. I understand that people use what they're familiar with and there seems to be a vibrant ecosystem for JS outside of the browser but it'll never not be weird seeing it take over what would once ha…