pith. sign in

arxiv: 1907.01423 · v1 · pith:6BCZ4B2Znew · submitted 2019-07-02 · 💻 cs.HC · cs.SE

Enhancing Email Functionality using Late Bound Content

Haojian Jin , Vita Chen , Ritwik Rajendra , Jason Hong This is my paper

Pith reviewed 2026-05-25 10:53 UTC · model grok-4.3

classification 💻 cs.HC cs.SE
keywords emaillate bound contentHTML emailsimage lazy-loadingdynamic email contentemail updatesthird party servicesemail functionality
0
0 comments X

The pith

Late bound content defers email parts to external images so they can be updated after delivery.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper introduces a technique that converts sections of an email into external images placed inside HTML snippets. Email clients then delay loading those images until the recipient opens the message. This deferral lets the original sender or a third-party service replace the image content even after the email has already been delivered. A reader would care because email has long lacked ways to change messages post-delivery without new infrastructure. The method relies only on standard HTML image behavior already present in most clients.

Core claim

Email late bound content converts parts of an email into external images embedded in HTML code snippets, making it so that email clients will defer the image download until the moment users open the email. This late bound content allows email senders and third party services to update delivered emails.

What carries the argument

Late bound content, which defers message content binding through image lazy-loading by embedding external images in HTML code snippets.

If this is right

  • Senders can replace content in already-delivered emails.
  • Third-party services can alter email content without involving the original sender.
  • Dynamic features such as live data or post-send corrections become possible inside ordinary emails.
  • Four concrete example features are demonstrated to illustrate the approach.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • Widespread use would require email clients to maintain consistent external-image loading behavior.
  • Security filters that already suppress external images could limit the technique's reach.
  • The same deferral pattern might be tested in other message formats that support embedded HTML.

Load-bearing premise

Email clients will reliably fetch and display the external images when the user opens the message, and this behavior can be used without breaking existing email standards or client security policies.

What would settle it

An observation that major email clients consistently block or fail to load external images in HTML messages would show the technique cannot reliably update delivered emails.

Figures

Figures reproduced from arXiv: 1907.01423 by Haojian Jin, Jason Hong, Ritwik Rajendra, Vita Chen.

Figure 1
Figure 1. Figure 1: The concept of content late binding. The presentation of Late Bound Content can be integrated into any emails. Email recipients are not required to install any software to view the content. Extensions [18, 19, 20, 30, 32] have also been developed to support additional email delivery protocols. However, it is difficult to make changes like these, in large part due to the strong need for backward compatibili… view at source ↗
Figure 3
Figure 3. Figure 3: Animated image visualizations of Kinetic Typography. The static images are mapped to the corresponding timestamp in the animation. Self-destruct KT examples (left) illustrate two examples at 3 days and 1 day before expiration, respectively). The continuous editing KT example (right) illustrates the modification history described in [PITH_FULL_IMAGE:figures/full_fig_p003_3.png] view at source ↗
Figure 4
Figure 4. Figure 4: Reusable weekly electricity report. The chart and the numbers are bound to a corresponding RESTful services. The RESTful service specifies the refresh rate and content updates. convey affective content with high levels of arousal, such as excitement or anger. Applying KT on late bound content further expand the email feature space. The self-destruct KT extension ( [PITH_FULL_IMAGE:figures/full_fig_p003_4.png] view at source ↗
Figure 6
Figure 6. Figure 6: Example of Continuous Editing. A Gmail user writes an email to a Hotmail user with a typo in the recipient’s name. and edit sent messages. WeChat lets senders retract messages in the first 2 minutes after sending. Late bound content offers the ability to continuously edit regular emails after being sent (e.g., short mobile email replies and self-emails). Senders can click late bound content to enter the ed… view at source ↗
read the original abstract

Email is one of the most successful computer applications yet devised. Communication features in email, however, have remained relatively static in years. We investigate one way of expanding email functionality without modifying the existing email infrastructure. We introduce email late bound content, a simple and generalizable technique that defers message content binding through image lazy-loading. Parts of an email are converted into external images embedded in HTML code snippets, making it so that email clients will defer the image download (i.e. content binding) until the moment users open the email. This late bound content allows email senders and third party services to update delivered emails. To illustrate the utilities of late bound content, we present four new example features and discuss the tradeoffs of email content late binding.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 1 minor

Summary. The paper introduces 'late bound content' as a technique that converts email message parts into external <img> references within HTML snippets. This defers content binding until the recipient opens the message, allowing senders or third-party services to update the served image data post-delivery without modifying email infrastructure. Four example features are presented to illustrate utilities, along with a discussion of tradeoffs.

Significance. If the mechanism functions as described, it offers a lightweight way to add dynamic, updatable elements to email without protocol changes, which could support features like live updates or third-party integrations. The approach is simple and generalizable, with explicit discussion of tradeoffs providing a balanced view. However, its practical impact hinges on whether the deferred binding reliably occurs across clients.

major comments (2)
  1. [Abstract and technique description] Abstract and description of the technique: The central claim that converting parts to external <img> references enables post-delivery updates assumes email clients will automatically fetch and render the external images on open. This is contradicted by the default behavior of major clients (Gmail, Outlook, Apple Mail), which suppress external images to prevent tracking and reduce attack surface; the binding therefore occurs only in the subset of clients where images are explicitly enabled by the user.
  2. [Example features and tradeoffs discussion] Discussion of tradeoffs and example features: The paper presents four features relying on late binding, but does not provide evidence or analysis showing how the mechanism would operate when external content is blocked (the common case). Without addressing this, the examples demonstrate functionality only under non-default client configurations.
minor comments (1)
  1. The manuscript would benefit from explicit clarification on whether the proposed features are intended only for the minority of clients that permit external images or if additional mechanisms are suggested to handle blocked content.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for the thoughtful comments, which highlight important practical considerations for the proposed technique. We address each major comment below and will revise the manuscript accordingly to improve clarity on client behaviors and limitations.

read point-by-point responses

  1. Referee: [Abstract and technique description] Abstract and description of the technique: The central claim that converting parts to external <img> references enables post-delivery updates assumes email clients will automatically fetch and render the external images on open. This is contradicted by the default behavior of major clients (Gmail, Outlook, Apple Mail), which suppress external images to prevent tracking and reduce attack surface; the binding therefore occurs only in the subset of clients where images are explicitly enabled by the user.

    Authors: We agree that the technique's effectiveness depends on clients fetching external images, which is suppressed by default in major clients such as Gmail, Outlook, and Apple Mail for privacy and security reasons. The late binding occurs only when image loading is permitted. We will revise the abstract and technique description to explicitly state this dependency and qualify the conditions under which post-delivery updates are possible. revision: yes

  2. Referee: [Example features and tradeoffs discussion] Discussion of tradeoffs and example features: The paper presents four features relying on late binding, but does not provide evidence or analysis showing how the mechanism would operate when external content is blocked (the common case). Without addressing this, the examples demonstrate functionality only under non-default client configurations.

    Authors: We concur that the tradeoffs section should address the blocked external content case more directly. We will expand this discussion to analyze operation when images are blocked, noting that the example features would not activate under default client settings and outlining the resulting scope and limitations of the approach. revision: yes

Circularity Check

0 steps flagged

No circularity: descriptive proposal without derivations or fitted results

full rationale

The paper presents a technique for deferring email content binding via external image references in HTML. No equations, parameters, predictions, or derivation chains appear in the provided text or abstract. The central claim is an engineering proposal whose correctness rests on external client behavior rather than any self-referential reduction. This is a standard non-derivational systems paper; the default finding of no circularity applies.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 1 invented entities

The central claim depends on the domain assumption that email clients will load external images on open and that this can be leveraged for content updates.

axioms (1)
  • domain assumption Email clients support and will execute HTML image lazy-loading when a message is opened.
    The late-binding mechanism relies entirely on this client behavior.
invented entities (1)
  • late bound content no independent evidence
    purpose: Mechanism to defer and allow post-delivery updates to email message parts.
    New named concept introduced to describe the image-based deferral technique.

pith-pipeline@v0.9.0 · 5650 in / 1095 out tokens · 30994 ms · 2026-05-25T10:53:21.150359+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

37 extracted references · 37 canonical work pages

  1. [1]

    https://blog

    Bringing the power of AMP to Gmail. https://blog. google/products/g-suite/bringing-power-amp-gmail/ . (????). (Accessed on 04/05/2018)

    work page 2018

  2. [2]

    http://stylecampaign

    Building a dynamic SVG timer. http://stylecampaign. com/blog/2016/04/building-a-dynamic-svg-timer/ . (????). (Accessed on 04/05/2018)

    work page 2016

  3. [3]

    http://stylecampaign.com/ blog/2010/12/dynamic-time-based-images/

    Dynamic time-based images. http://stylecampaign.com/ blog/2010/12/dynamic-time-based-images/ . (????). (Accessed on 04/05/2018)

    work page 2010

  4. [4]

    HTML Email: The Poll | scot hacker’s foobar blog

    2006. HTML Email: The Poll | scot hacker’s foobar blog. http: //blog.birdhouse.org/2006/01/15/html-email-the-poll/ . (2006). (Accessed on 09/19/2017)

    work page 2006

  5. [5]

    Why HTML in E-Mail is a Bad Idea

    2006. Why HTML in E-Mail is a Bad Idea. http://archive.birdhouse.org/etc/evilmail.html. (2006). (Accessed on 09/18/2017)

    work page 2006

  6. [6]

    Tab Discarding in Chrome: A Memory-Saving Experiment

    2015. Tab Discarding in Chrome: A Memory-Saving Experiment. https://developers.google.com/web/updates/ 2015/09/tab-discarding. (2015). (Accessed on 09/17/2017)

    work page 2015

  7. [7]

    Nir Ailon, Zohar S Karnin, Edo Liberty, and Yoelle Maarek. 2013. Threading machine generated email. In Proceedings of the sixth ACM international conference on Web search and data mining. ACM, 405–414

    work page 2013

  8. [8]

    Patti Bao, Jeffrey Pierce, Stephen Whittaker, and Shumin Zhai. 2011. Smart phone use by non-mobile business users. In Proceedings of the 13th international conference on human computer interaction with mobile devices and services. ACM, 445–454

    work page 2011

  9. [9]

    Victoria Bellotti, Nicolas Ducheneaut, Mark Howard, and Ian Smith. 2003. Taking email to task: the design and evaluation of a task management centered email tool. In Proceedings of the SIGCHI conference on Human factors in computing systems. ACM, 345–352

    work page 2003

  10. [10]

    Frank Bentley, Nediyana Daskalova, and Nazanin Andalibi. 2017. If a person is emailing you, it just doesn’t make sense: Exploring Changing Consumer Behaviors in Email. In Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems. ACM, 85–95

    work page 2017

  11. [11]

    Julie E Boland and Robin Queen. 2016. If You’re House Is Still Available, Send Me an Email: Personality Influences Reactions to Written Errors in Email Messages. PloS one 11, 3 (2016), e0149885

    work page 2016

  12. [12]

    Horatiu Bota, Paul N Bennett, Ahmed Hassan Awadallah, and Susan T Dumais. 2017. Self-Es: The Role of Emails-to-Self in Personal Information Management. In Proceedings of the 2017 Conference on Conference Human Information Interaction and Retrieval . ACM, 205–214

    work page 2017

  13. [13]

    ARA Bouguettaya and MY Eltoweissy. 2003. Privacy on the Web: Facts, challenges, and solutions. IEEE Security & Privacy 99, 6 (2003), 40–49

    work page 2003

  14. [14]

    Vitor R Carvalho and William W Cohen. 2007. Preventing information leaks in email. In Proceedings of the 2007 SIAM International Conference on Data Mining . SIAM, 68–77

    work page 2007

  15. [15]

    Marta E Cecchinato, Abigail Sellen, Milad Shokouhi, and Gavin Smyth. 2016. Finding email in a multi-account, multi-device world. In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems . ACM, 1200–1210

    work page 2016

  16. [16]

    Nicolas Ducheneaut and Victoria Bellotti. 2001. E-mail as habitat: an exploration of embedded personal information management. interactions 8, 5 (2001), 30–38

    work page 2001

  17. [17]

    Shannon Ford, Jodi Forlizzi, and Suguru Ishizaki. 1997. Kinetic typography: issues in time-based presentation of text. In CHI’97 extended abstracts on Human factors in computing systems. ACM, 269–270

    work page 1997

  18. [18]

    Simson L Garfinkel, David Margrave, Jeffrey I Schiller, Erik Nordlander, and Robert C Miller. 2005. How to make secure email easier to use. In Proceedings of the SIGCHI conference on human factors in computing systems. ACM, 701–710

    work page 2005

  19. [19]

    Google. 2017. End-to-end: End-To-End is a library and a chrome extension that helps you encrypt, decrypt, digital sign, and verify signed messages within the browser using OpenPGP. https://github.com/google/end-to-end. (Apr 2017)

    work page 2017

  20. [20]

    Mike Hanson, Graham Miller, and Brian Axe. 2003. Method for communicating information among a group of participants. (Jan. 7 2003). US Patent 6,505,233

    work page 2003

  21. [21]

    Chris Hoffman. 2017. Why You Can’t Undo Sending an Email (and When You Can). https://www.howtogeek.com/161762/ why-you-cant-undo-sending-an-email-and-when-you-can/ . (Apr 2017)

    work page 2017

  22. [22]

    Huawei Technologies. 2009. SMTP Service Extension for Message Recall. https://tools.ietf.org/id/ draft-leiba-morg-message-recall-00.html . (July 2009)

    work page 2009

  23. [23]

    HubSpot. 2017. Inbound Marketing & Sales Software. https://www.hubspot.com/. (Apr 2017)

    work page 2017

  24. [24]

    Suguru Ishizaki. 1998. On kinetic typography. Statements, the newsletter for the American Center for Design 12, 1 (1998), 7–9

    work page 1998

  25. [25]

    Farshad Kooti, Luca Maria Aiello, Mihajlo Grbovic, Kristina Lerman, and Amin Mantrach. 2015. Evolution of conversations in the age of email overload. In Proceedings of the 24th International Conference on World Wide Web. International World Wide Web Conferences Steering Committee, 603–613

    work page 2015

  26. [26]

    Johnny C Lee, Jodi Forlizzi, and Scott E Hudson. 2002. The kinetic typography engine: an extensible system for animating expressive text. In Proceedings of the 15th annual ACM symposium on User interface software and technology. ACM, 81–90. 6

    work page 2002

  27. [27]

    Luke McDowell, Oren Etzioni, Alon Halevy, and Henry Levy. 2004. Semantic email. In Proceedings of the 13th international conference on World Wide Web. ACM, 244–254

    work page 2004

  28. [28]

    You’ve got e-mail!

    Karen Renaud, Judith Ramsay, and Mario Hair. 2006. " You’ve got e-mail!"... shall I deal with it now? Electronic mail from the recipient’s perspective. International Journal of Human-Computer Interaction 21, 3 (2006), 313–332

    work page 2006

  29. [29]

    Peter W Resnick. 2008. Internet message format. (2008)

    work page 2008

  30. [30]

    Scott Ruoti, Jeff Andersen, Travis Hendershot, Daniel Zappala, and Kent Seamons. 2016. Private Webmail 2.0: Simple and Easy-to-Use Secure Email. In Proceedings of the 29th Annual Symposium on User Interface Software and Technology (UIST ’16). ACM, New York, NY , USA, 461–472. DOI: http://dx.doi.org/10.1145/2984511.2984580

    work page doi:10.1145/2984511.2984580 2016

  31. [31]

    Scrubadub. 2017. Clean personally identifiable information from dirty dirty text. https://github.com/datascopeanalytics/scrubadub. (Apr 2017)

    work page 2017

  32. [32]

    Snapmail. 2017. Self-destructing emails for Gmail. https://snapmail.co/. (Apr 2017)

    work page 2017

  33. [33]

    Agnieszka Matysiak Szóstek. 2011. ‘Dealing with My Emails’: Latent user needs in email management. Computers in Human Behavior 27, 2 (2011), 723–729

    work page 2011

  34. [34]

    The Radicati Group. 2017. Email statistics report, 2017-2021. http://www.radicati.com/?p=14588, (Feb 2017)

    work page 2017

  35. [35]

    Gail Fann Thomas, Cynthia L King, Brian Baroni, Linda Cook, Marian Keitelman, Steve Miller, and Adelia Wardle. 2006. Reconceptualizing e-mail overload. Journal of Business and Technical Communication 20, 3 (2006), 252–287

    work page 2006

  36. [36]

    Joshua R Tyler and John C Tang. 2003. When can I expect an email response? A study of rhythms in email usage. In ECSCW 2003. Springer, 239–258

    work page 2003

  37. [37]

    Yesware. 2017. Email Tracking. http://www.yesware.com/email-tracking. (Apr 2017). 7

    work page 2017