<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
</div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">It would be very hard to improve it to be smarter than simply looking for the use of `@`. But I need to add some way for the user to “whitelist” names.</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">Yes, whitelisting would be very good — perhaps at both the address and even at the domain level. I have several clients using MailMate who love it greatly — but the skull at first really creeped them out, and now it just annoys them because they happen to deal regularly with correspondents whose email names <em>by corporate policy</em> are their own email addresses:</p>
<pre style="background-color:#F7F7F7; border-radius:5px 5px 5px 5px; margin-left:15px; margin-right:15px; max-width:90vw; overflow-x:auto; padding:5px" bgcolor="#F7F7F7"><code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0" bgcolor="#F7F7F7">robert@example.com <robert@example.com>
</code></pre>
<p dir="auto">Blech, to be sure! What an awful idea! But apparently it’s relatively common. And it’s MailMate that gets the blame, at least in my clients’ minds.</p>
<p dir="auto">Anyway, being able to suppress the warnings for all of (say) example.com would be very handy for folks who have to deal with such organizations.</p>
<p dir="auto">Cheers,</p>
<p dir="auto">— Erik</p>
</div>
</div>
</body>
</html>