- Proper handling (and generation) of threading headers like "References" and "In-Reply-To". And, hence, a threaded view of my mail.
- The ability to just display the text/plain version of the mail. Just about every webmail I've used insists on trying to render the HTML version - and I don't want to see that.
- Virtual folders. The ability to put a mail into multiple folders. Maybe this can be achieved using tags (a bit like how Gmail does it).
- Multiple identities. I send mail that needs to appear to come from many different email addresses. Each different identity needs to potentially have different settings for From:, Reply-To:, SMTP server and signature (and probably other things). Identity should be able to be set automatically according to various attributes of the mail that I'm replying to (from:, to:, the current mailbox, etc) but I need to be able to override it when I'm composing the mail.
I guess I'm really looking for a web-based version of mutt :)
Oh, and in my opinion, Mail::Box is looking a bit old and over-complex. If I was you I'd look at the modules from the Perl Email Project.
--
< http://dave.org.uk>
"The first rule of Perl club is you do not talk about
Perl club."
-- Chip Salzenberg
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
