There is a similar idea that Apache::SMTP/Apache2::Protocol::ESMTP surveyed - instead of munging the email address, munge the email hostname by setting up a wildcard domain and giving each email a different hostname. That way you could not only switch off an email address but also immediately stop all incoming traffic for that poisoned email address.

The problem with this setup is a human one (or so I gathered from the comments of the author) - people do not want their email addresses munged and can't stand that they're sending with a different email than what is on their business cards. But it seemed feasible for a small-scale, private/clueful email setup.

In reply to Re: RFC: Email 2.0: Segmail by Corion
in thread RFC: Email 2.0: Segmail by tomazos

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.