<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Smtp Headers on Evan Hoffman</title><link>https://evan.wtf/tags/smtp-headers/</link><description>Recent content in Smtp Headers on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Tue, 02 Aug 2011 14:39:45 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/smtp-headers/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon SES: "illegal headers" with ses-send-email.pl (followup)</title><link>https://evan.wtf/2011/08/02/amazon-ses-illegal-headers-with-ses-send-email-pl-followup/</link><pubDate>Tue, 02 Aug 2011 14:39:45 +0000</pubDate><guid>https://evan.wtf/2011/08/02/amazon-ses-illegal-headers-with-ses-send-email-pl-followup/</guid><description>&lt;p&gt;A few people have emailed me asking me to integrate &lt;a href="https://evan.wtf/2011/05/16/amazon-ses-illegal-header-errors/"&gt;the perl code snippet into I wrote to strip illegal headers&lt;/a&gt; when sending email via Amazon SES into something actually usable. I&amp;rsquo;ve done so! I haven&amp;rsquo;t really tested this beyond sending some test emails, but here it is. Use this at your own risk, I make no warranty, blah blah blah.&#10;This fix requires editing &lt;code&gt;ses-send-email.pl&lt;/code&gt;, so I&amp;rsquo;d advise making a backup copy, though I imagine you can always get a fresh version from Amazon if necessary.&lt;/p&gt;</description></item><item><title>Microsoft Office 2007's awful user interface</title><link>https://evan.wtf/2010/08/02/microsoft-office-2007s-awful-user-interface-2/</link><pubDate>Mon, 02 Aug 2010 12:48:49 +0000</pubDate><guid>https://evan.wtf/2010/08/02/microsoft-office-2007s-awful-user-interface-2/</guid><description>&lt;p&gt;Office 2007 is pretty old by now, and I know much has been written on the move from a &amp;ldquo;normal&amp;rdquo; looking app to the &amp;ldquo;Ribbon&amp;rdquo; UI. I personally hate the change and feel Microsoft just changed the UI as a way to make the application look &amp;ldquo;different&amp;rdquo; so that people will look at it and go &amp;ldquo;oooh, shiny!&amp;rdquo; and not feel as bad about being forced into another $400 upgrade of a word processor. Sure, Excel&amp;rsquo;s row limit was finally raised beyond 64k, and I&amp;rsquo;m sure there were some other tweaks, but .docx? .xlsx? Yet more file formats, ensuring most businesses will feel compelled to upgrade. If your clients are upgrading, you&amp;rsquo;re going to have to.&lt;/p&gt;</description></item><item><title>Microsoft Office 2007's awful user interface</title><link>https://evan.wtf/2010/08/02/microsoft-office-2007s-awful-user-interface/</link><pubDate>Mon, 02 Aug 2010 12:48:49 +0000</pubDate><guid>https://evan.wtf/2010/08/02/microsoft-office-2007s-awful-user-interface/</guid><description>&lt;p&gt;Office 2007 is pretty old by now, and I know much has been written on the move from a &amp;ldquo;normal&amp;rdquo; looking app to the &amp;ldquo;Ribbon&amp;rdquo; UI. I personally hate the change and feel Microsoft just changed the UI as a way to make the application look &amp;ldquo;different&amp;rdquo; so that people will look at it and go &amp;ldquo;oooh, shiny!&amp;rdquo; and not feel as bad about being forced into another $400 upgrade of a word processor. Sure, Excel&amp;rsquo;s row limit was finally raised beyond 64k, and I&amp;rsquo;m sure there were some other tweaks, but .docx? .xlsx? Yet more file formats, ensuring most businesses will feel compelled to upgrade. If your clients are upgrading, you&amp;rsquo;re going to have to.&lt;/p&gt;</description></item></channel></rss>