• Roadmap for 2.9
• Other/long term items to do in the future

Roadmap for 2.9

( all tentative )

• Work on Archiving Abilities
  The archiving part of Mojo Mail is showing it's age. I'm guessin' it hasn't been heavily updated since the 2.2, 2.3 days.

  Some problems with it at the moment:

  • Archives don't handle HTML mail that well
    This is especially true when you send a webpage.

  • Generally, the archive DB does't save enough information
    For example, if you send a message with both a plain text and HTML version, only the plain text version is saved.

    No header information is saved at all, any shown is sort of made up. Since no header information is saved, you can't do something cool, such as sort by thread.

• Bounce Handler
  The bounce handler is pretty pathetic at the moment, since it'll unsubscribe EVERY email address it finds in a message that gets sent to it. What would be better is to create a rule system. For example, I could make a rule that says that any message with a subject of: Returned mail: User unknown will have it's message body scanned to find the line that says:

  550 <someaddress@somewherethatdoesnt.exist>... User unknown

  and have that address removed from the list that sent it, or hey, any list that's Mojo'd.

  This is probably easy enough to do without having to use a package of modules like MIME::Tools, but maybe it would be a good idea to make MIME::Tools usage optional. (are required, I'm not sure yet...)

  I believe the bounce handler is a part of the magic book distro, and this ain't changin'

• Templating
  As with the archiving part of Mojo Mail, it's ``Templating'' (cough) part is in need of a rewrite. At the moment, it's very simple. Some things I want to work on for 2.9:
  • It may be a good idea to have list be able to create more than one template per list and perhaps use this template in specific functions. Say, use template #1 when someone tries to subscribe, template #2 when the see archives, etc.
    
  • The actual content, not the wrapper, for various screens should be able to be customizable. Some screens I'm thinking of include the Mojo Mail main screen, the list screen and the archive screens.
    
  • Create xHTML compatible default archives
    You know, get with the program on those.

• Add subscription size limitations
  

Other/long term items to do in the future

• Add Multiple Fields Support
  It seems that just saving an email address is quickly not enough for some people. Multiple Fields support needs to be added, the problem is that Mojo Mail was rewritten totally almost 3 years ago and since then, has slowly been rewritten in pieces. This leads to the problem of some of the code being new and well maintainted, and some of the code being old and crufty.

• Make all HTML printed out by Mojo Mail xHTML compatible
  The default templates need a redesign and MOJO::Template::HTML needs a total rewrite as it's one of the least touched modules and is slowly getting dusty with age. This will most likely be done by taking advantage of the HTML::Template CPAN module

• Installer
  A automatic installer needs to be created that can be executed via the command line, or using a program like CPanel. This will help adoptation of the program.

• Make Mojo Mail mod_perl compatible
  Making Mojo Mail mod_perl compatible will make it more appealing to larger organizations and businesses. There are relatively few barriers to make this happen. There are some exit() function calls in Mojo Mail that will have to be either removed. Mojo Mail also forks off mailings; an alternative to this will have to be found.

  http://perl.apache.org/guide/porting.html

  I currently DO NOT have access to mod_perl enabled box. If anyone wants to ``donate'' a a account, I would be very grateful.

  More testing on different servers/OS's
  
  Windows Servers currently aren't tested at all. This is because I don't have access to a server on a Windows machine. This could be a job for someone else.

  If anyone wants to be in charge of porting Mojo to any OS, just let me know

  Allow Mojo Mail to run in Taint mode.
  Taint mode forces you to make special security considerations in the Perl program. Knowing a program can be run in taint mode will appeal to larger organisations. You can test if Mojo Mail can run in Taint mode by adding the '-T' flag in the shebang line in mojo.cgi:

  #!/usr/bin/perl -T

  Recently, Mojo Mail has been known to work with this flag on in most functions, but this needs much, much more testing.

  Version 2.8 works almost perfectly with the -T flag enabled, but I haven't tested it enough.

  mojo_send.pl needs a Mother
  I currently am not interested in supporting mojo_send.pl, and someone else needs to take the reigns for its development. Why am I not interested? Because I don't use it.