Ricardo Signes, profile picture
Uploaded byRicardo Signes
1,084 views

i <3 email

The document discusses various libraries and tools for sending emails in Perl, contrasting their features and usability. It covers the intricacies of using these libraries, such as email::send and email::sender, and problem-solving techniques for sending structured and templated emails. Key topics include transport options, failure handling, and building MIME email messages with attachments and HTML content.

Embed presentation

Download to read offline
1 / 107
2 / 107
3 / 107
4 / 107
5 / 107
6 / 107
7 / 107
8 / 107
9 / 107
10 / 107
11 / 107
12 / 107
13 / 107
14 / 107
15 / 107
16 / 107
17 / 107
18 / 107
19 / 107
20 / 107
21 / 107
22 / 107
23 / 107
24 / 107
25 / 107
26 / 107
27 / 107
28 / 107
29 / 107
30 / 107
31 / 107
32 / 107
33 / 107
34 / 107
35 / 107
36 / 107
37 / 107
38 / 107
39 / 107
40 / 107
41 / 107
42 / 107
43 / 107
44 / 107
45 / 107
46 / 107
47 / 107
48 / 107
49 / 107
50 / 107
51 / 107
52 / 107
53 / 107
54 / 107
55 / 107
56 / 107
57 / 107
58 / 107
59 / 107
60 / 107
61 / 107
62 / 107
63 / 107
64 / 107
65 / 107
66 / 107
67 / 107
68 / 107
69 / 107
70 / 107
71 / 107
72 / 107
73 / 107
74 / 107
75 / 107
76 / 107
77 / 107
78 / 107
79 / 107
80 / 107
81 / 107
82 / 107
83 / 107
84 / 107
85 / 107
86 / 107
87 / 107
88 / 107
89 / 107
90 / 107
91 / 107
92 / 107
93 / 107
94 / 107
95 / 107
96 / 107
97 / 107
98 / 107
99 / 107
100 / 107
101 / 107
102 / 107
103 / 107
104 / 107
105 / 107
106 / 107
107 / 107
the 2009 PEP talk!!!
...I work there!
YAPC::NA 2006
PEP: Thoughts from Pobox YAPC::NA 2006
YAPC::NA 2007
How I Learned To Stop Worrying and Love Email YAPC::NA 2007
YAPC::NA 2008
Email hates the living! YAPC::NA 2008
What’s the best way to deal with horrible code?
Write more code! ...so I did! The last year has been really productive. Lots of obnoxious problems were sorted out. I’m really happy with what we got accomplished, and so finally I can with a straight face...
rjbs <3 email the 2009 PEP talk!!!
sending email
MIME::Lite Mail::Send Mail::Sender Mail::Sendmail so, here are some of the libraries for sending mail. these all let you specify subject, to/from, and content -- so you can’t actually make an email just hwo you want and pass it in. worthless for any real use
Mail::Mailer this lets you send mail through pluggable backends, and you provide the mail message. not bad, but not great; it has this weird API where it isa IO::Handle and you print to it like a filehandle to send your message. subclassing is a pain because it’s a blessed globref
Email::Send Email::Send simplifies by expecting a string, being a hashref, and being in theory easier to extend (by using Module::Pluggable) unfortunately, this pluggability (and some other oddities) ends up making extending things harder and can cause it to silently lose mail. for real.
this is probably about about as good as a number of them.
system(“sendmail @opts < $tempfile”) && die sprintf “sendmail died: %s”, errstr($?); this is probably about about as good as a number of them.
Mail::Transport So, Mail::Transport isn’t bad. It’s part of the Mail-Box distro, which means it tends to get things right, but it also tends to be confusing and overwhelming for new users. If you’re already using it happily, that’s great! We weren’t, though, and so we wrote something new, built using just the ideas we liked from Email::Send, and
Email::Sender
Email::Sender
Email::Sender Email-Sender uses Møøse
Email::Sender Email-Sender uses Møøse Email::Sender is a role
Email::Sender Email-Sender uses Møøse Email::Sender is a role you use Email::Sender::Simple
Email::Sender::Simple use Email::Sender::Simple qw(sendmail); my $email = $customer->build_welcome_email; sendmail($email); Yup. That’s about it. That will try to send mail with either sendmail or SMTP, depending on what’s available. If it can’t send the message, it will throw.
Email::Sender::Simple use Email::Sender::Simple qw(sendmail); my $email = $customer->build_welcome_email; sendmail( $email, { to => @rcpts, from => $sender, } ); In other words, you can specify the envelope separately from the header. This is of *vital* importance to real email work. VERP, mailing lists, especially.
Email::Sender::Simple my $smtp = Email::Sender::Transport::SMTP->new({ host => ‘sasl.pobox.com’, port => 26, }); sendmail($email, { transport => $smtp }); If you don’t like the auto-detected transport, you can specify one. Transports are really easy to write, and a bunch already exist:
Transports SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail SMTP SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail SMTP Persist. SMTP SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail SMTP Persist. SMTP Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail DevNull SMTP Persist. SMTP Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail DevNull SMTP Print Persist. SMTP Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail DevNull SMTP Print Persist. SMTP Test Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Transports Sendmail DevNull SMTP Print Persist. SMTP Test Maildir, Mbox SQLite SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
Email::Sender::Simple my $smtp = Email::Sender::Transport::SMTP->new({ host => ‘sasl.pobox.com’, port => 26, }); sendmail($email, { transport => $smtp }); so, you can do this, that’s fine, and you can use any of those cool transports when you call sendmail... but what about if you want to change the whole default?
Email::Sender::Simple walrus!rjbs:~$ EMAIL_SENDER_TRANSPORT=Maildir my-awesome-program --auden now *every* call to Email::Sender::Simple->send will deliver to ./Maildir so you can see exactly what it would have sent
Programmable Failure so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
Programmable Failure ::Failable transport so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
Programmable Failure ::Failable transport wrap any transport so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
Programmable Failure ::Failable transport wrap any transport make it fail when you want so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
Other Random Senderisms
Other Random Senderisms structured failure
Other Random Senderisms structured failure partial successes
making email messages
Email::Simple
Email::MIME
these are pretty low level
you probably want to send only a few messages (but with differences)
MIME Crap to Deal With
MIME Crap to Deal With header encoding
MIME Crap to Deal With header encoding content encoding
MIME Crap to Deal With header encoding content encoding building html & plain parts
MIME Crap to Deal With header encoding content encoding building html & plain parts attaching files
Other Crap to Deal With
Other Crap to Deal With templated documents
Other Crap to Deal With templated documents validate parameters
Other Crap to Deal With templated documents validate parameters reusable hunks of content
hate!
Existing Solutions
Existing Solutions none?
Existing Solutions none? horrible hacks
Existing Solutions none? horrible hacks make a template in TT
Existing Solutions none? horrible hacks make a template in TT render to html
Existing Solutions none? horrible hacks make a template in TT render to html html-to-text
Existing Solutions none? horrible hacks make a template in TT render to html html-to-text hope you guess right at headers
Email::MIME::Kit
Email::MIME::Kit
Email::MIME::Kit a bunch of files
Email::MIME::Kit a bunch of files with instructions on how to assemble them
Email::MIME::Kit a bunch of files with instructions on how to assemble them and some other data
Kit Manifest { "renderer" : "TT", "header" : [ { "Subject": "Hello [% user.name %]" }, { "From": "Test Sender <test@test.com>" }, { "To": "[% user.email %]" } ], "alternatives": [ { "type": "text/plain", "path": "body.txt" }, { "type": "text/html", "path": "body.html" } ], "attachments": [ { "path": "demands.rtf" } ] }
Assembling the Kit my $kit = Email::MIME::Kit->new({ source => ‘msg.mkit’ }); my $email = $kit->assemble({ user => $user_object }); sendmail($email);
Dear , Thank you for being a customer since . Your account has been due to . Please contact before at or we will be forced to your lovely wife Tracy’s head. Cheers, Anonymous Ugh. Our $user_object was undef. Now we get crap that looks like mail but stinks and makes us look like idiots. We can plug in a validator pretty easily, though...
Kit Manifest { "renderer" : "TT", “validator”: “Rx”, "header" : [ { "Subject": "Hello [% user.name %]" }, { "From": "Test Sender <test@test.com>" }, { "To": "[% user.email %]" } ], "alternatives": [ { "type": "text/plain", "path": "body.txt" }, { "type": "text/html", "path": "body.html" } ], "attachments": [ { "path": "demands.rtf" } ] }
rx.json { “type”: “//rec”, “required”: { “user”: { “type”: “/perl/obj”, “isa” : “User::Account” } } }
Assembling the Kit my $kit = Email::MIME::Kit->new({ source => ‘msg.mkit’ }); my $email = $kit->assemble({ user => undef }); undefined value tag: [ “/err/nil” ], data path: [ “user” ], schema path: [ “user” ] at slide 42, line 3
Annoying Crap: Dealt With
Annoying Crap: Dealt With if user.name is Ævar...
Annoying Crap: Dealt With if user.name is Ævar... if attachments are binary...
Annoying Crap: Dealt With if user.name is Ævar... if attachments are binary... text-only (singlepart) mail...
Annoying Crap: Dealt With if user.name is Ævar... if attachments are binary... text-only (singlepart) mail... HTML with images as attachments...
...so what’s still annoying?
Some Kits... so, you love mkits and you’re writing them all the time... now you start having this problem...
Some Kits... ./body.html ./body.txt ./logo.jpg ./background.jpg ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json ./body.html ./body.txt ./logo.jpg ./background.jpg ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json those files are identical everywhere. blaugh! duplication baaaaaaaaaad
The Kit Reader
The Kit Reader EMKit gets at its contents with the kit reader
The Kit Reader EMKit gets at its contents with the kit reader normally, just looks for files in the kit directory
SWAK! /fs (can be chrooted) /dist /kit (default, too)
SWAK! you can write your own kit reader /fs (can be chrooted) /dist /kit (default, too)
SWAK! you can write your own kit reader SWAK: Path::Resolver /fs (can be chrooted) /dist /kit (default, too)
SWAK! you can write your own kit reader SWAK: Path::Resolver /kit/body.html /fs (can be chrooted) /dist /kit (default, too)
SWAK! you can write your own kit reader SWAK: Path::Resolver /kit/body.html body.html /fs (can be chrooted) /dist /kit (default, too)
SWAK! you can write your own kit reader SWAK: Path::Resolver /kit/body.html body.html /fs/usr/share/app/body.html /fs (can be chrooted) /dist /kit (default, too)
SWAK in Use ./body.html ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json So, we can take those common files and put them in our dist’s shared resources, and reference them with the “/dist/” prefix, which finds stuff in share-dirs. So, awesome! What’s still annoying?
SWAK in Use ./body.html ./body.txt ./manifest.json ./body.html /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json So, we can take those common files and put them in our dist’s shared resources, and reference them with the “/dist/” prefix, which finds stuff in share-dirs. So, awesome! What’s still annoying?
SWAK in Use ./body.html ./body.txt ./manifest.json ./body.html /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json almost certainly, the html and text parts are (a) really close to each other within one kit (b) contain really different parts between kits (c) contain common boilerplate between kits
EMK::Assembler::Markdown ./body.mkdn ./manifest.json /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.mkdn ./manifest.json ./body.mkdn ./manifest.json So, let’s fix that, too. We replace the text and html parts with a single Markdown document. We’ll use the Markdown itself for the plaintext part and we’ll turn it into HTML to use in the HTML part. Of course, this still needs work. We want wrapper stuff and copyright and so on in both parts.
EMK::Assembler::Markdown ./body.mkdn ./manifest.json /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.mkdn /dist/YourApp/wrapper.html ./manifest.json /dist/YourApp/wrapper.text ./body.mkdn ./manifest.json
Thank you!

More Related Content

PPT
Lecture19
byChâu Thanh Chương
 
PDF
Fighting XMPP abuse and spam with ejabberd - ejabberd Workshop #1
byMickaël Rémond
 
ZIP
Elegant Systems Integration w/ Apache Camel
byPradeep Elankumaran
 
PPTX
TechNet Webcast: Exchange 2010 Outlook Web Access
byMicrosoft TechNet
 
PDF
Kafka Technical Overview
bySylvester John
 
PDF
XMPP Intro 1101 - 2008
bySteffen Larsen
 
DOCX
Azure Service Bus Performance Checklist
bySalim M Bhonhariya
 
PDF
Real life XMPP Instant Messaging
byMickaël Rémond
 
Lecture19
byChâu Thanh Chương
 
Fighting XMPP abuse and spam with ejabberd - ejabberd Workshop #1
byMickaël Rémond
 
Elegant Systems Integration w/ Apache Camel
byPradeep Elankumaran
 
TechNet Webcast: Exchange 2010 Outlook Web Access
byMicrosoft TechNet
 
Kafka Technical Overview
bySylvester John
 
XMPP Intro 1101 - 2008
bySteffen Larsen
 
Azure Service Bus Performance Checklist
bySalim M Bhonhariya
 
Real life XMPP Instant Messaging
byMickaël Rémond
 

What's hot

PDF
NATS + Docker meetup talk Oct - 2016
bywallyqs
 
PPT
Implementing WebServices with Camel and CXF in ServiceMix
byAdrian Trenaman
 
ODP
Art Of Message Queues
byMike Willbanks
 
PDF
Better CSV processing with Ruby 2.6
byKouhei Sutou
 
ODP
Apache Kafka Demo
byEdward Capriolo
 
PPT
24 Hours Of Exchange Server 2007 ( Part 9 Of 24)
byHarold Wong
 
PDF
Kafka zero to hero
byAvi Levi
 
PPTX
Kafka tutorial
bySrikrishna k
 
PPTX
Apache kafka
bySrikrishna k
 
PPTX
Codefresh + BlazeMeter Webinar: Continuous Testing for Containerized Applicat...
byBrittany Ingram
 
PPTX
Apache kafka
bynatashasweety7
 
PDF
GopherFest 2017 - Adding Context to NATS
bywallyqs
 
KEY
The Real Time Web with XMPP
byJack Moffitt
 
PDF
Queues queues queues — How RabbitMQ enables reactive architectures
byMartin Tajur
 
PPTX
Using message enricher
bySon Nguyen
 
PPTX
Groovy example in mule
byMohammed246
 
PDF
Rabbitmq, amqp Intro - Messaging Patterns
byJavier Arias Losada
 
DOCX
Unit 59 diary
byinwill12
 
NATS + Docker meetup talk Oct - 2016
bywallyqs
 
Implementing WebServices with Camel and CXF in ServiceMix
byAdrian Trenaman
 
Art Of Message Queues
byMike Willbanks
 
Better CSV processing with Ruby 2.6
byKouhei Sutou
 
Apache Kafka Demo
byEdward Capriolo
 
24 Hours Of Exchange Server 2007 ( Part 9 Of 24)
byHarold Wong
 
Kafka zero to hero
byAvi Levi
 
Kafka tutorial
bySrikrishna k
 
Apache kafka
bySrikrishna k
 
Codefresh + BlazeMeter Webinar: Continuous Testing for Containerized Applicat...
byBrittany Ingram
 
Apache kafka
bynatashasweety7
 
GopherFest 2017 - Adding Context to NATS
bywallyqs
 
The Real Time Web with XMPP
byJack Moffitt
 
Queues queues queues — How RabbitMQ enables reactive architectures
byMartin Tajur
 
Using message enricher
bySon Nguyen
 
Groovy example in mule
byMohammed246
 
Rabbitmq, amqp Intro - Messaging Patterns
byJavier Arias Losada
 
Unit 59 diary
byinwill12
 

Similar to i &lt;3 email

PPS
Linux10 sendmail
byJainul Musani
 
PPT
4. SMTP.ppt
byDEEPAK948083
 
PPT
Electronic Mail on Solaris 2 Configuration
bypankajvanisdr4
 
DOC
vishal_sharma: python email sending software
byvishal sharma
 
PDF
Lecture 9 electronic_mail_representation_and_transfer
bySerious_SamSoul
 
PPTX
Exchange Server 2013 Architecture Deep Dive, Part 2
byMicrosoft TechNet - Belgium and Luxembourg
 
PDF
Postfix, Imap e Pop3
byCarlos Eduardo
 
PDF
Dbmail
bySandino Araico Sánchez
 
PPTX
7_Chapter 7_Email.pptx
byhoangdinhhanh88
 
PPTX
Email/Ad/Marketing 20100130
bydsoprea
 
PPT
Spam Filter
bySanjeev Kumar Jaiswal
 
PDF
Mail server on Ubuntu Server 12.04 (Postfix, Courier, SSL, SpamAssassin, Clam...
byMohd Khairulazam
 
KEY
Sending email with perl
byapeiron
 
PDF
Linux instalação e-conf postfix - pop3 eimap
byCarlos Eduardo
 
KEY
Itch Scratching
byRubyX
 
PDF
Qpsmtpd
byFred Moyer
 
PDF
Email plugin for_cakephp
byTakahiro Fujiwara
 
PPT
Web 2.0: Making Email a Useful Web App
byAndy Denmark
 
PDF
Protecting Plone from the Big, Bad Internet
byErik Rose
 
PDF
Tripit Ajaxworld V5
byrajivmordani
 
Linux10 sendmail
byJainul Musani
 
4. SMTP.ppt
byDEEPAK948083
 
Electronic Mail on Solaris 2 Configuration
bypankajvanisdr4
 
vishal_sharma: python email sending software
byvishal sharma
 
Lecture 9 electronic_mail_representation_and_transfer
bySerious_SamSoul
 
Exchange Server 2013 Architecture Deep Dive, Part 2
byMicrosoft TechNet - Belgium and Luxembourg
 
Postfix, Imap e Pop3
byCarlos Eduardo
 
Dbmail
bySandino Araico Sánchez
 
7_Chapter 7_Email.pptx
byhoangdinhhanh88
 
Email/Ad/Marketing 20100130
bydsoprea
 
Spam Filter
bySanjeev Kumar Jaiswal
 
Mail server on Ubuntu Server 12.04 (Postfix, Courier, SSL, SpamAssassin, Clam...
byMohd Khairulazam
 
Sending email with perl
byapeiron
 
Linux instalação e-conf postfix - pop3 eimap
byCarlos Eduardo
 
Itch Scratching
byRubyX
 
Qpsmtpd
byFred Moyer
 
Email plugin for_cakephp
byTakahiro Fujiwara
 
Web 2.0: Making Email a Useful Web App
byAndy Denmark
 
Protecting Plone from the Big, Bad Internet
byErik Rose
 
Tripit Ajaxworld V5
byrajivmordani
 

More from Ricardo Signes

PDF
Writing Modular Command-line Apps with App::Cmd
byRicardo Signes
 
PDF
How I Learned to Stop Worrying and Love Email::: The 2007 PEP Talk!!
byRicardo Signes
 
PDF
Dist::Zilla - Maximum Overkill for CPAN Distributions
byRicardo Signes
 
PDF
Crafting Custom Interfaces with Sub::Exporter
byRicardo Signes
 
PDF
Perl 5.10 for People Who Aren't Totally Insane
byRicardo Signes
 
PDF
Perl 5: Today, Tomorrow, and Christmas
byRicardo Signes
 
PDF
Dist::Zilla
byRicardo Signes
 
PDF
Perl 5.14 for Pragmatists
byRicardo Signes
 
PDF
What's New in Perl? v5.10 - v5.16
byRicardo Signes
 
PDF
Perl 5.12 for Everyday Use
byRicardo Signes
 
PDF
Antediluvian Unix: A Guide to Unix Fundamentals
byRicardo Signes
 
Writing Modular Command-line Apps with App::Cmd
byRicardo Signes
 
How I Learned to Stop Worrying and Love Email::: The 2007 PEP Talk!!
byRicardo Signes
 
Dist::Zilla - Maximum Overkill for CPAN Distributions
byRicardo Signes
 
Crafting Custom Interfaces with Sub::Exporter
byRicardo Signes
 
Perl 5.10 for People Who Aren't Totally Insane
byRicardo Signes
 
Perl 5: Today, Tomorrow, and Christmas
byRicardo Signes
 
Dist::Zilla
byRicardo Signes
 
Perl 5.14 for Pragmatists
byRicardo Signes
 
What's New in Perl? v5.10 - v5.16
byRicardo Signes
 
Perl 5.12 for Everyday Use
byRicardo Signes
 
Antediluvian Unix: A Guide to Unix Fundamentals
byRicardo Signes
 

Recently uploaded

PPTX
AI: Beyond Generative AI and LLM | Harrie de Groot (harrie.dev)
byHarrie de Groot
 
PDF
Supervised Machine Learning Approaches for Log-Based Anomaly Detection: A Cas...
byMohammed BEKKOUCHE
 
PDF
Oracle MySQL HeatWave - Complete - Version 3
byLuca Bonesini
 
PDF
Building a Multi-Tenant OpenShift Platform with HyperShift
byTosin Akinosho
 
PDF
IDSECCONF2025 - Aan Wahyu - Maze–Malware Analysis Platform.pdf
byidsecconf
 
PDF
Build an AI/ML-driven image archive processing workflow: Image archive, analy...
bywesley chun
 
PDF
Introduction to Shell Scripting - RHCSA+.pdf
byLinuxCert Guru
 
PDF
Beyond Basics: How to Build Scalable, Intelligent Imagery Pipelines
bySafe Software
 
PDF
Linux Professional Institute LPIC-1 Exam.pdf
byLinuxCert Guru
 
PDF
Mutation Testing for Industrial Robotic Systems (FMAS 2025)
bySylvain Hallé
 
PDF
Command Line Text Processing - RHCSA +.pdf
byLinuxCert Guru
 
PPTX
The power of Slack and MuleSoft | Bangalore MuleSoft Meetup #60
byshyamraj55
 
PDF
THE THREATS OF INSTABILITY IN BRAZIL'S INTERCONNECTED ELECTRICAL SYSTEM AND H...
byFaga1939
 
PDF
AI in Food Production (Foodwell) - AI Solutions Supporting Operations
bybyteLAKE
 
PDF
SELinux Policy Management in RHEL - RHCSA+.pdf
byLinuxCert Guru
 
PDF
IDSECCONF2025 - Nosa Shandy - Discovering and Disclosing Privacy Vulnerabilit...
byidsecconf
 
PDF
Building Powerful Web Apps to Improve Productivity and Engagement - Esri UK W...
byEsri UK
 
PPTX
Neo4j Fraud GraphTalk Singapore Nov 2025
bygourisachdeva2
 
PPTX
Redcentric Data Centres: vision, mission and values
byRedcentric
 
PPTX
Explaining ourselves – people, computers and AI
byAlan Dix
 
AI: Beyond Generative AI and LLM | Harrie de Groot (harrie.dev)
byHarrie de Groot
 
Supervised Machine Learning Approaches for Log-Based Anomaly Detection: A Cas...
byMohammed BEKKOUCHE
 
Oracle MySQL HeatWave - Complete - Version 3
byLuca Bonesini
 
Building a Multi-Tenant OpenShift Platform with HyperShift
byTosin Akinosho
 
IDSECCONF2025 - Aan Wahyu - Maze–Malware Analysis Platform.pdf
byidsecconf
 
Build an AI/ML-driven image archive processing workflow: Image archive, analy...
bywesley chun
 
Introduction to Shell Scripting - RHCSA+.pdf
byLinuxCert Guru
 
Beyond Basics: How to Build Scalable, Intelligent Imagery Pipelines
bySafe Software
 
Linux Professional Institute LPIC-1 Exam.pdf
byLinuxCert Guru
 
Mutation Testing for Industrial Robotic Systems (FMAS 2025)
bySylvain Hallé
 
Command Line Text Processing - RHCSA +.pdf
byLinuxCert Guru
 
The power of Slack and MuleSoft | Bangalore MuleSoft Meetup #60
byshyamraj55
 
THE THREATS OF INSTABILITY IN BRAZIL'S INTERCONNECTED ELECTRICAL SYSTEM AND H...
byFaga1939
 
AI in Food Production (Foodwell) - AI Solutions Supporting Operations
bybyteLAKE
 
SELinux Policy Management in RHEL - RHCSA+.pdf
byLinuxCert Guru
 
IDSECCONF2025 - Nosa Shandy - Discovering and Disclosing Privacy Vulnerabilit...
byidsecconf
 
Building Powerful Web Apps to Improve Productivity and Engagement - Esri UK W...
byEsri UK
 
Neo4j Fraud GraphTalk Singapore Nov 2025
bygourisachdeva2
 
Redcentric Data Centres: vision, mission and values
byRedcentric
 
Explaining ourselves – people, computers and AI
byAlan Dix
 

i &lt;3 email

  • 1.
    the 2009 PEPtalk!!!
  • 2.
  • 3.
  • 4.
    PEP: Thoughts fromPobox YAPC::NA 2006
  • 5.
  • 6.
    How I LearnedTo Stop Worrying and Love Email YAPC::NA 2007
  • 7.
  • 8.
  • 9.
    What’s the bestway to deal with horrible code?
  • 10.
    Write more code! ...soI did! The last year has been really productive. Lots of obnoxious problems were sorted out. I’m really happy with what we got accomplished, and so finally I can with a straight face...
  • 11.
    rjbs <3 email the 2009 PEP talk!!!
  • 12.
  • 13.
    MIME::Lite Mail::Send Mail::Sender Mail::Sendmail so, here are some of the libraries for sending mail. these all let you specify subject, to/from, and content -- so you can’t actually make an email just hwo you want and pass it in. worthless for any real use
  • 14.
    Mail::Mailer this lets yousend mail through pluggable backends, and you provide the mail message. not bad, but not great; it has this weird API where it isa IO::Handle and you print to it like a filehandle to send your message. subclassing is a pain because it’s a blessed globref
  • 15.
    Email::Send Email::Send simplifies byexpecting a string, being a hashref, and being in theory easier to extend (by using Module::Pluggable) unfortunately, this pluggability (and some other oddities) ends up making extending things harder and can cause it to silently lose mail. for real.
  • 16.
    this is probablyabout about as good as a number of them.
  • 17.
    system(“sendmail @opts <$tempfile”) && die sprintf “sendmail died: %s”, errstr($?); this is probably about about as good as a number of them.
  • 18.
    Mail::Transport So, Mail::Transport isn’tbad. It’s part of the Mail-Box distro, which means it tends to get things right, but it also tends to be confusing and overwhelming for new users. If you’re already using it happily, that’s great! We weren’t, though, and so we wrote something new, built using just the ideas we liked from Email::Send, and
  • 20.
  • 21.
  • 22.
  • 23.
  • 24.
    Email::Sender Email-Sender uses Møøse Email::Senderis a role you use Email::Sender::Simple
  • 25.
    Email::Sender::Simple use Email::Sender::Simple qw(sendmail); my $email = $customer->build_welcome_email; sendmail($email); Yup. That’s about it. That will try to send mail with either sendmail or SMTP, depending on what’s available. If it can’t send the message, it will throw.
  • 26.
    Email::Sender::Simple use Email::Sender::Simple qw(sendmail); my $email = $customer->build_welcome_email; sendmail( $email, { to => @rcpts, from => $sender, } ); In other words, you can specify the envelope separately from the header. This is of *vital* importance to real email work. VERP, mailing lists, especially.
  • 27.
    Email::Sender::Simple my $smtp = Email::Sender::Transport::SMTP->new({ host => ‘sasl.pobox.com’, port => 26, }); sendmail($email, { transport => $smtp }); If you don’t like the auto-detected transport, you can specify one. Transports are really easy to write, and a bunch already exist:
  • 28.
    Transports SQLite is especiallyhandy because you can dump all mail from a forking program into an easy-to-test database.
  • 29.
    Transports Sendmail SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 30.
    Transports Sendmail SMTP SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 31.
    Transports Sendmail SMTP Persist. SMTP SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 32.
    Transports Sendmail SMTP Persist. SMTP Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 33.
    Transports Sendmail DevNull SMTP Persist. SMTP Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 34.
    Transports Sendmail DevNull SMTP Print Persist. SMTP Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 35.
    Transports Sendmail DevNull SMTP Print Persist. SMTP Test Maildir, Mbox SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 36.
    Transports Sendmail DevNull SMTP Print Persist. SMTP Test Maildir, Mbox SQLite SQLite is especially handy because you can dump all mail from a forking program into an easy-to-test database.
  • 37.
    Email::Sender::Simple my $smtp = Email::Sender::Transport::SMTP->new({ host => ‘sasl.pobox.com’, port => 26, }); sendmail($email, { transport => $smtp }); so, you can do this, that’s fine, and you can use any of those cool transports when you call sendmail... but what about if you want to change the whole default?
  • 38.
    Email::Sender::Simple walrus!rjbs:~$ EMAIL_SENDER_TRANSPORT=Maildir my-awesome-program --auden now *every* call to Email::Sender::Simple->send will deliver to ./Maildir so you can see exactly what it would have sent
  • 39.
    Programmable Failure so, forexample, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
  • 40.
    Programmable Failure ::Failable transport so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
  • 41.
    Programmable Failure ::Failable transport wrap any transport so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
  • 42.
    Programmable Failure ::Failable transport wrap any transport make it fail when you want so, for example, we have a system that distributes mail across a cluster of hosts with various mechanisms to cope with failure Failable lets me test them by using a mailer that always works wrapped in predictable failure, easily
  • 43.
  • 44.
    Other Random Senderisms structured failure
  • 45.
    Other Random Senderisms structured failure partial successes
  • 46.
  • 47.
  • 48.
  • 49.
  • 50.
    you probably wantto send only a few messages (but with differences)
  • 51.
    MIME Crap toDeal With
  • 52.
    MIME Crap toDeal With header encoding
  • 53.
    MIME Crap toDeal With header encoding content encoding
  • 54.
    MIME Crap toDeal With header encoding content encoding building html & plain parts
  • 55.
    MIME Crap toDeal With header encoding content encoding building html & plain parts attaching files
  • 56.
    Other Crap toDeal With
  • 57.
    Other Crap toDeal With templated documents
  • 58.
    Other Crap toDeal With templated documents validate parameters
  • 59.
    Other Crap toDeal With templated documents validate parameters reusable hunks of content
  • 61.
  • 62.
  • 63.
  • 64.
  • 65.
  • 66.
    Existing Solutions none? horrible hacks make a template in TT render to html
  • 67.
    Existing Solutions none? horrible hacks make a template in TT render to html html-to-text
  • 68.
    Existing Solutions none? horrible hacks make a template in TT render to html html-to-text hope you guess right at headers
  • 70.
  • 71.
  • 72.
  • 73.
    Email::MIME::Kit a bunch offiles with instructions on how to assemble them
  • 74.
    Email::MIME::Kit a bunch offiles with instructions on how to assemble them and some other data
  • 75.
    Kit Manifest { "renderer" : "TT", "header" : [ { "Subject": "Hello [% user.name %]" }, { "From": "Test Sender <test@test.com>" }, { "To": "[% user.email %]" } ], "alternatives": [ { "type": "text/plain", "path": "body.txt" }, { "type": "text/html", "path": "body.html" } ], "attachments": [ { "path": "demands.rtf" } ] }
  • 76.
    Assembling the Kit my$kit = Email::MIME::Kit->new({ source => ‘msg.mkit’ }); my $email = $kit->assemble({ user => $user_object }); sendmail($email);
  • 77.
    Dear , Thank you for being a customer since . Your account has been due to . Please contact before at or we will be forced to your lovely wife Tracy’s head. Cheers, Anonymous Ugh. Our $user_object was undef. Now we get crap that looks like mail but stinks and makes us look like idiots. We can plug in a validator pretty easily, though...
  • 78.
    Kit Manifest { "renderer" : "TT", “validator”: “Rx”, "header" : [ { "Subject": "Hello [% user.name %]" }, { "From": "Test Sender <test@test.com>" }, { "To": "[% user.email %]" } ], "alternatives": [ { "type": "text/plain", "path": "body.txt" }, { "type": "text/html", "path": "body.html" } ], "attachments": [ { "path": "demands.rtf" } ] }
  • 79.
    rx.json { “type”: “//rec”, “required”: { “user”: { “type”: “/perl/obj”, “isa” : “User::Account” } } }
  • 80.
    Assembling the Kit my$kit = Email::MIME::Kit->new({ source => ‘msg.mkit’ }); my $email = $kit->assemble({ user => undef }); undefined value tag: [ “/err/nil” ], data path: [ “user” ], schema path: [ “user” ] at slide 42, line 3
  • 81.
  • 82.
    Annoying Crap: DealtWith if user.name is Ævar...
  • 83.
    Annoying Crap: DealtWith if user.name is Ævar... if attachments are binary...
  • 84.
    Annoying Crap: DealtWith if user.name is Ævar... if attachments are binary... text-only (singlepart) mail...
  • 85.
    Annoying Crap: DealtWith if user.name is Ævar... if attachments are binary... text-only (singlepart) mail... HTML with images as attachments...
  • 86.
  • 87.
    Some Kits... so, youlove mkits and you’re writing them all the time... now you start having this problem...
  • 88.
    Some Kits... ./body.html ./body.txt ./logo.jpg ./background.jpg ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
  • 89.
    Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
  • 90.
    Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json ./body.html ./body.txt ./logo.jpg ./background.jpg ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
  • 91.
    Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json so, you love mkits and you’re writing them all the time... now you start having this problem...
  • 92.
    Some Kits... ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json ./body.html ./body.html ./body.txt ./body.txt ./logo.jpg ./logo.jpg ./background.jpg ./background.jpg ./manifest.json ./manifest.json those files are identical everywhere. blaugh! duplication baaaaaaaaaad
  • 93.
  • 94.
    The Kit Reader EMKitgets at its contents with the kit reader
  • 95.
    The Kit Reader EMKitgets at its contents with the kit reader normally, just looks for files in the kit directory
  • 96.
    SWAK! /fs (can be chrooted) /dist /kit (default, too)
  • 97.
    SWAK! you can write your own kit reader /fs (can be chrooted) /dist /kit (default, too)
  • 98.
    SWAK! you can write your own kit reader SWAK: Path::Resolver /fs (can be chrooted) /dist /kit (default, too)
  • 99.
    SWAK! you can write your own kit reader SWAK: Path::Resolver /kit/body.html /fs (can be chrooted) /dist /kit (default, too)
  • 100.
    SWAK! you can write your own kit reader SWAK: Path::Resolver /kit/body.html body.html /fs (can be chrooted) /dist /kit (default, too)
  • 101.
    SWAK! you can write your own kit reader SWAK: Path::Resolver /kit/body.html body.html /fs/usr/share/app/body.html /fs (can be chrooted) /dist /kit (default, too)
  • 102.
    SWAK in Use ./body.html ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json So, we can take those common files and put them in our dist’s shared resources, and reference them with the “/dist/” prefix, which finds stuff in share-dirs. So, awesome! What’s still annoying?
  • 103.
    SWAK in Use ./body.html ./body.txt ./manifest.json ./body.html /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json So, we can take those common files and put them in our dist’s shared resources, and reference them with the “/dist/” prefix, which finds stuff in share-dirs. So, awesome! What’s still annoying?
  • 104.
    SWAK in Use ./body.html ./body.txt ./manifest.json ./body.html /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.txt ./manifest.json ./body.html ./body.txt ./manifest.json almost certainly, the html and text parts are (a) really close to each other within one kit (b) contain really different parts between kits (c) contain common boilerplate between kits
  • 105.
    EMK::Assembler::Markdown ./body.mkdn ./manifest.json /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.mkdn ./manifest.json ./body.mkdn ./manifest.json So, let’s fix that, too. We replace the text and html parts with a single Markdown document. We’ll use the Markdown itself for the plaintext part and we’ll turn it into HTML to use in the HTML part. Of course, this still needs work. We want wrapper stuff and copyright and so on in both parts.
  • 106.
    EMK::Assembler::Markdown ./body.mkdn ./manifest.json /dist/YourApp/logo.jpg /dist/YourApp/background.jpg ./body.mkdn /dist/YourApp/wrapper.html ./manifest.json /dist/YourApp/wrapper.text ./body.mkdn ./manifest.json
  • 107.