I'm currently developing a web based email system for eventual commercial usage. I have the basic goals for the system sketched out ( features, size limits, etc ). The problem(s) I am running into is as follow:

1) I have a fixed limit of physical mbox's available as dictated by my service provider ( media|temple ) and the only apparent solution is to use a catch all email address

2) security of using a single address to recieve mail ( ie. a catch-all account and the feasibility of implementing this as a long term solution with special consideration given to the max number of users that the server can support before purchasing additional servers is required

3) the moral/ethical concerns surrounding content-filtering based on community input (ie. spam/not spam on a per user basis ) and then setting up rules where content is being filtered at a single point in the process by group consensus ( greater than 50% ) and the per user choice to filter/not filter content based on community suggestion

4) including geolocation services and automatic spam reporting back to the originating server.



Any insight that the community could provide on this would be greatly appreciated. Thanks for your time

In reply to Email System Scalabilty by john.charles.aldrich

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.