My 2 cents on the idea of the 'monk-to-monk' email system is that it might not be a good idea unless adequate controls were in place to prevent spamming. I'm on a chat system that does email redirects to your real address that you gave when registering (and is in your profile) so I could send an email to "user@chatboard.com" and it would get to them even if I didn't know their real address (providing they kept a valid email address in their profile). The problem is that this got out somehow and as a result, spam levels increased significantly. I ended up setting up a filter that trashes anything sent that comes in with "myuser@chatboard.com" anywhere in the headers. I don't miss much in the way of email because no one really uses the redirection much. Probably because of the spamming. Perhaps include something (if this were ever implemented) that would allow an individual to select not to receive these sorts of emails. While this might not be quite the same as your suggestion, there could still be problems. To paraphrase one of Murphey's Laws of Programming: It Is Impossible to Make Anything Spam-proof, Because Spammers are so Ingenious. ;-)


"Ex libris un peut de tout"

In reply to Re: Whatever happened to Node2Email? by nimdokk
in thread Whatever happened to Node2Email? by xenchu

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.