[Masonmail-developers] template

[Tom A. <tal...@ta...>]

I have a few minutes and so I thought I would put together something for 
a template.  I'm not sure what other attributes we want to have, but it 
seems that if we do redirection using attributes we're going to have to 
include this attribute in every file.

The alternative is to use a filename test block redirection from turning
into an infinite loop from the autohandler.

Any problems with using an attribute?  I think it lends itself to being 
more flexible with the files that are accessable.

Any other thoughts on a basic template?

I've added a few preliminary tasks as corner stones to getting things 
started.  They are generic enough that anyone can pick them up without 
knowing too many of the details today.

I think we need to start with a combination of syshandler/autohandler 
(or just one?) that manages all the authentication from the point of 
view of:
grabbing cookies,
checking their validity (do they even exist?)
and redirecting to a login if False
and providing a $IMAP variable for the Mail::IMAPClient module that 
we'll need for the rest of the code.

This is the first of two core pieces that need to be done.  The second 
piece that is probably as important is the apache configuration file. 
This is going to be needed ASAP so we can get the right modules into 
play and be working off the same reference points (autohandler, and 
apache configuration)

Once these two are completed.......


<%doc>
$Id: $
$Log:$
</%doc>

<%attr>
   # Change this only for modules that do not require Authentication
   accept_all => 0
</%attr>