<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for dominicsayers</title><link>https://disqus.com/by/dominicsayers/</link><description></description><atom:link href="https://disqus.com/dominicsayers/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 14 Oct 2020 11:50:54 -0000</lastBuildDate><item><title>Re: Moist flapjack with condensed milk</title><link>https://www.dominicsayers.com/flapjack/#comment-5110008297</link><description>&lt;p&gt;In this case I think you probably can, Yassar. Don't try this with Banoffee Pie though!&lt;/p&gt;&lt;p&gt;Let me know how it goes.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Wed, 14 Oct 2020 11:50:54 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-3583634849</link><description>&lt;p&gt;Thanks Matsuko. I don't think there's anything I can easily do about that because a slash is a valid part of a URL and there's no fancy routing software in front of this website. So at the moment it's just ignoring everything after the slash.&lt;/p&gt;&lt;p&gt;I'll have a think but I don't have much time to maintain this site, sorry.&lt;/p&gt;&lt;p&gt;Suggestions gratefully received.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Wed, 25 Oct 2017 04:29:08 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-2738645945</link><description>&lt;p&gt;Enter your address. Click "Test" and read the answer: &lt;a href="http://isemail.info/Wmflomo84.%40gmail.com" rel="nofollow noopener" target="_blank" title="http://isemail.info/Wmflomo84.%40gmail.com"&gt;http://isemail.info/Wmflomo...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Sun, 19 Jun 2016 03:43:45 -0000</pubDate></item><item><title>Re: The myth of the driverless cars revolution</title><link>http://www.christianwolmar.co.uk/2016/04/the-myth-of-the-driverless-cars-revolution/#comment-2716452053</link><description>&lt;p&gt;Actuaries will work out that cars are safer when they are driving themselves, so the insurance companies will offer lower premiums to drivers who use autopilot as much as possible. Paul Whitehouse will appear in adverts telling us he lets his car drive itself and saves money.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 07 Jun 2016 07:13:13 -0000</pubDate></item><item><title>Re: Running Ubuntu with DHCP on Hyper-V over WIFI — matt wrock's software development blog</title><link>http://www.hurryupandwait.io/blog/running-an-ubuntu-guest-on-hyper-v-assigned-an-ip-via-dhcp-over-a-wifi-connection#comment-2410667374</link><description>&lt;p&gt;Genius. Thank you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 15 Dec 2015 07:39:26 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-2341027603</link><description>&lt;p&gt;I'm very happy to merge a pull request if you'd like to make the necessary changes&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 03 Nov 2015 14:00:52 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-2049753916</link><description>&lt;p&gt;The validation is intended to be technically correct, and it's not really an end-user service. In a real-world app I'd expect you to punycode the user's input before validation, then use the information returned from is_email to provide a meaningful message to the user.&lt;/p&gt;&lt;p&gt;Many MTAs successfully pass on messages addressed to really strange email addresses. That doesn't mean those addresses are conformant. You should probably warn a user that he or she has entered an address that might not get sent reliably but allow them to use it if they insist. See &lt;a href="http://isemail.info/about" rel="nofollow noopener" target="_blank" title="http://isemail.info/about"&gt;http://isemail.info/about&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Thu, 28 May 2015 11:26:29 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-2042802022</link><description>&lt;p&gt;In order to transfer emails at international domains like this, the address has to be encoded so that it conforms to the standards. This encoding is called punycode and it's outside the scope of this validator. (I could add it but the validator is here to validate email addresses, not encode/decode them)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Sun, 24 May 2015 09:54:41 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-2026239887</link><description>&lt;p&gt;Read this &lt;a href="http://en.wikipedia.org/wiki/Robustness_principle" rel="nofollow noopener" target="_blank" title="http://en.wikipedia.org/wiki/Robustness_principle"&gt;http://en.wikipedia.org/wik...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;If it still isn't clear then ask again and I'll explain.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Fri, 15 May 2015 04:02:57 -0000</pubDate></item><item><title>Re: Three Colours Ped: A Trio Of Different Boris Bikes In One Photo</title><link>http://londonist.com/2015/03/three-colours-ped-a-trio-of-different-boris-bikes-in-one-photo.php#comment-1923248760</link><description>&lt;p&gt;Mudchute DLR this morning&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Mon, 23 Mar 2015 09:46:43 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1911848016</link><description>&lt;p&gt;The `Local-part` of the address is defined here: &lt;a href="https://tools.ietf.org/html/rfc5321#section-4.1.2" rel="nofollow noopener" target="_blank" title="https://tools.ietf.org/html/rfc5321#section-4.1.2"&gt;https://tools.ietf.org/html...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;It uses the definition of `atext` from RFC 5322 &lt;a href="https://tools.ietf.org/html/rfc5322#section-3.2.3" rel="nofollow noopener" target="_blank" title="https://tools.ietf.org/html/rfc5322#section-3.2.3"&gt;https://tools.ietf.org/html...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 17 Mar 2015 11:24:43 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1888853338</link><description>&lt;p&gt;Not sure why you'd pay for something that is available free but I have some magic beans you might be interested in...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Thu, 05 Mar 2015 04:18:47 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1687485960</link><description>&lt;p&gt;Thanks for perservering!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 11 Nov 2014 04:48:29 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1687483101</link><description>&lt;p&gt;Hi Matt,&lt;/p&gt;&lt;p&gt;I tried and failed to define a binary test for "valid" and "invalid" because there are contexts where a particular email is valid and other contexts where it isn't.&lt;/p&gt;&lt;p&gt;Look at the list of result codes here: &lt;a href="https://github.com/dominicsayers/isemail/blob/master/test/meta.xml" rel="nofollow noopener" target="_blank" title="https://github.com/dominicsayers/isemail/blob/master/test/meta.xml"&gt;https://github.com/dominics...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Each has a category, and you should use this rather than a numeric value to determine which addresses are valid in your context.&lt;/p&gt;&lt;p&gt;You might decide that ISEMAIL_VALID_CATEGORY, ISEMAIL_DNSWARN and &lt;br&gt;ISEMAIL_RFC5321 are your valid categories. This will allow TLD addresses and addresses at non-existent domains as well as "normal" addresses.&lt;/p&gt;&lt;p&gt;Hope this helps.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 11 Nov 2014 04:43:46 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1491068069</link><description>&lt;p&gt;Great question!&lt;/p&gt;&lt;p&gt;The standardized-tag has to be a member of the list held by IANA here: &lt;a href="http://www.iana.org/assignments/address-literal-tags/address-literal-tags.xhtml" rel="nofollow noopener" target="_blank" title="http://www.iana.org/assignments/address-literal-tags/address-literal-tags.xhtml"&gt;http://www.iana.org/assignm...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;At the moment this list has one member: "IPv6"&lt;/p&gt;&lt;p&gt;Anything else, therefore, is currently not a standardized-tag.&lt;/p&gt;&lt;p&gt;is_email has no means of checking whether any more members have been added to this list, but luckily the test is still valid :-)&lt;/p&gt;&lt;p&gt;You may have spotted a logical inconsistency here. I took the view that we shoudn't validate TLDs because more could be added at any time. Indeed many additional TLDs *have* been added since I last worked on this code. On the other hand, is_email validates against a snapshot of a standardized-tag list that might go out-of-date at any time. Just because it hasn't doesn't mean I was right!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Fri, 18 Jul 2014 04:44:35 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1438995908</link><description>&lt;p&gt;If you submit a pull request here I'd be very glad to consider it: &lt;a href="https://github.com/dominicsayers/isemail" rel="nofollow noopener" target="_blank" title="https://github.com/dominicsayers/isemail"&gt;https://github.com/dominics...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 17 Jun 2014 04:41:03 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1438995426</link><description>&lt;p&gt;Historically TLDs have always been 2 characters or more, but there's nothing to stop ICANN issuing a 1 character TLD if they choose to do so.&lt;/p&gt;&lt;p&gt;More detail: there's nothing in the RFCs to stop them doing it. The aim of isemail is to embody the principles of the RFCs. It's possible there is an ICANN policy document stating that they will never issue a 1 character TLD but that's outside the scope of isemail. If they submit their policy as an RFC then we would be inclined to add it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Tue, 17 Jun 2014 04:40:19 -0000</pubDate></item><item><title>Re: The kids are alright</title><link>http://www.daniellight.co.uk/the-kids-are-alright/#comment-1412117644</link><description>&lt;p&gt;Seconded&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Fri, 30 May 2014 10:15:00 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1374754780</link><description>&lt;p&gt;If you would like to add RFC 6531 compatibility then I'll happily accept a pull request here &lt;a href="https://github.com/dominicsayers/isemail" rel="nofollow noopener" target="_blank" title="https://github.com/dominicsayers/isemail"&gt;https://github.com/dominics...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;It may be some time before all the world's MTAs can handle non-ASCII email addresses though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Thu, 08 May 2014 04:27:48 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1374751829</link><description>&lt;p&gt;Your email address is valid. I have no idea why any other web site says it isn't.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Thu, 08 May 2014 04:23:11 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1303460688</link><description>&lt;p&gt;Why do you doubt it?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Wed, 26 Mar 2014 08:37:07 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1266452060</link><description>&lt;p&gt;Hi Will. You're right. I'll try to update the link when I can.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Sat, 01 Mar 2014 17:51:46 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1266451118</link><description>&lt;p&gt;Hi Colin. It would be helpful if you quoted the relevant RFC when you make assertions like "x is not allowed"&lt;/p&gt;&lt;p&gt;I agree the diagnostic message for this example is not perfect. It would be better to cite RFC 5321 section 4.1.2 where quoted-pairSMTP is defined as a backslash followed by any ASCII character in the range %d32-126. In other words, the diagnosis is correct: this is a valid email address.&lt;/p&gt;&lt;p&gt;&lt;a href="http://tools.ietf.org/html/rfc5321#section-4.1.2" rel="nofollow noopener" target="_blank" title="http://tools.ietf.org/html/rfc5321#section-4.1.2"&gt;http://tools.ietf.org/html/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Sat, 01 Mar 2014 17:50:35 -0000</pubDate></item><item><title>Re: NHS: What is the Hospital Closure Clause?</title><link>http://blog.38degrees.org.uk/2014/02/20/nhs-what-is-the-hospital-closure-clause/#comment-1264296902</link><description>&lt;p&gt;The link is still broken after 5 days. Seems there is little point commenting here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Fri, 28 Feb 2014 07:57:15 -0000</pubDate></item><item><title>Re: Is this email address valid?</title><link>http://isemail.info#comment-1264294847</link><description>&lt;p&gt;There seems little point supporting this RFC until there are a majority of servers in the wild that use SMTPUTF8 (&lt;a href="http://serverfault.com/questions/469990/are-there-any-smtp-servers-that-support-the-smtputf8-extension)" rel="nofollow noopener" target="_blank" title="http://serverfault.com/questions/469990/are-there-any-smtp-servers-that-support-the-smtputf8-extension)"&gt;http://serverfault.com/ques...&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Until then an address that uses non-ASCII characters will be transmitted on a best-efforts basis, so validation against a standard isn't really possible.&lt;/p&gt;&lt;p&gt;I would be very happy to accept a pull request that adds support for this RFC if anyone wants to make one here &lt;a href="https://github.com/dominicsayers/isemail" rel="nofollow noopener" target="_blank" title="https://github.com/dominicsayers/isemail"&gt;https://github.com/dominics...&lt;/a&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dominic Sayers</dc:creator><pubDate>Fri, 28 Feb 2014 07:54:44 -0000</pubDate></item></channel></rss>