mlmmj-rbarchiver 0.0.1

data/README.md

@@ -0,0 +1,151 @@
+mlmmj-rbarchive
+===============
+
+Small Ruby program for properly archiving a mlmmj-managed
+mailinglist.
+
+Requirements
+------------
+
+* [Ruby](http://ruby-lang.org) 1.9.3+
+* [MHonArc](http://mhonarc.org)
+* The `mail` gem
+* The `paint` gem
+
+Usage
+-----
+
+You can choose between using mlmmj-rbarchive as a library or as a
+commandline program.
+
+### Commandline ###
+
+The `mlmmj-rbarchiver` program allows to process any given mlmmj ML
+directory directly into a browsable HTML mailinglist archive. It is
+intended to be run regularly from Cron so it is able to cumulatively
+add any new messages delivered to your ML to the HTML archive.
+
+An example call may look like this:
+
+```
+$ mlmmj-rbarchiver -i /var/spool/mlmmj/mymailinglist -o /var/www/mlarchive
+```
+
+This will take all mails found in
+`/var/spool/mlmmj/mymailinglist/archive` and output them to
+`/var/www/mlarchive/mymailinglist` in a month-year-ordered
+format. Note you still have to provide a toplevel `index.html`
+yourself.
+
+The program features a good number of commandline options; run it with
+`-h` to get a summary. For styling you might especially be interested
+in the `-s` option. You might also use a configuration file with `-c`
+that allows you to specify some options once and for all; see the
+`rbarchiver.conf` file in the `extra/` directory for an example of how
+it could look like.
+
+### Library ###
+
+To use it as a library, first create a new archiver:
+
+``` ruby
+require "mlmmj-archiver"
+
+a = MlmmjArchiver::Archiver.new("output", # Target directory for all the messages
+                                header: "<p>My ML archive</p>", # HTML to display at the top
+                                stylefile: "/stylesheets/archive.css") # CSS stylesheet to reference from the HTML files
+```
+
+This will create an archiver that places the resulting HTML files
+below a directory `output` below the current directory. To actually
+add an mlmmj ML do the following:
+
+``` ruby
+a << "/var/spool/mlmmj/my-ml
+```
+
+Note you don’t have to specify the "archive" directory below `my-ml`
+manually. Next, create an empty file `my-ml/control/webarchive`. This
+signals mlmmj-rbarchive that you really want this ML to be processed;
+without this file, the directory is skipped even though you have added
+it to the archiver.
+
+You can now preprocess the mails into a hierarchical year-month
+directory structure so that before the messages get passed to MHonArc
+they are already nicely sorted:
+
+``` ruby
+a.preprocess_mlmmj_mails!
+```
+
+After having prepared all existing mail, you can now watch the ML’s
++archive+ directories for changes rather than running the
+Archiver#preprocess_mlmmj_mails! method periodically:
+
+``` ruby
+a.watch_mlmmj_mails!
+```
+
+Note that the above only works if you have the `rb-inotify` gem
+installed. Finally, start the conversion process:
+
+``` ruby
+a.archive!
+```
+
+You can run this periodically if you want, already processed
+messages will not be processed again, only new messages are
+added to the web archive.
+
+#### I want more output! ####
+
+Do this before you start adding mailinglists to the
+archiver:
+
+``` ruby
+a.debug_mode = true
+```
+
+Docs?
+-----
+
+To get a more thorough documentation, run this:
+
+```
+$ rdoc archiver.rb
+```
+
+You will then end up with some more detailed docs in a directory `doc`
+below the current working directory.
+
+Links
+-----
+
+* [Online docs](http://quintus.github.io/mlmmj-rbarchiver)
+* [Repository](https://github.com/Quintus/mlmmj-rbarchiver)
+* [Issue tracker](https://github.com/Quintus/mlmmj-rbarchiver/issues)
+
+License
+-------
+
+mlmmj-rbarchive makes a web archive from your mlmmj-archive.
+Copyright (C) 2013-2014  Marvin Gülker
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+The MHonArc template file is based on mlmmj-archiver by Andreas Schneider,
+which can be found here: http://git.cryptomilk.org/projects/mlmmj-webarchiver.git.
+It is GPL-copyrighted free software, hence this is also GPL’ed free software.
+
+You can contact me at quintus ät quintilianus döt eu.

data/bin/mlmmj-rbarchiver

@@ -0,0 +1,102 @@
+#!/usr/bin/env ruby
+# -*- coding: utf-8 -*-
+# This file is part of mlmmj-rbarchive.
+#
+# mlmmj-rbarchive makes a web archive from your mlmmj-archive.
+# Copyright (C) 2014  Marvin Gülker
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+
+require "optparse"
+require_relative "../lib/mlmmj-archiver"
+
+########################################
+# Helpers
+
+def info(str)
+  puts(str)
+end
+
+def warn(str)
+  puts Paint[str, :yellow]
+end
+
+def error(str)
+  puts Paint[str, :red]
+end
+
+def error!(exception)
+  error(exception.to_s)
+  raise(exception)
+end
+
+########################################
+# Argument parsing
+
+options = {}
+
+OptionParser.new do |op|
+  op.banner =<<-EOF
+This program archives mlmmj mailinglists into HTML archives.
+
+Usage: mlmmj-rbarchiver [Options] -i MLDIR -o OUTDIR
+  EOF
+
+  op.separator ""
+  op.separator "Options:"
+
+  op.on("-a", "--admin EMAIL", "E-Mail address of the administrator"){ |addr| options[:archiveadmin] = addr }
+  op.on("-c", "--config-file FILE", "Read configuration from FILE"){ |path| options[:configfile] = Pathname.new(path).expand_path }
+  op.on("-C", "--cachedir DIR", "Sorted cache directory"){ |path| options[:cachedir] = Pathname.new(path).expand_path }
+  op.on("-h", "--help", "Print this help and exit."){ puts(op); exit }
+  op.on("-H", "--header STRING", "HTML code shown above everyhing"){ |str| options[:header] = str }
+  op.on("-i", "--indir PATH", "mlmmj mailinglist to archive"){ |path| options[:indir] = Pathname.new(path).expand_path }
+  op.on("-l", "--levels NUM", Integer, "Maxmimum message nest before flattening"){ |num| options[:tlevels] = num }
+  op.on("-m", "--mhonarc PATH", "Path to the mhonarc executable"){ |path| options[:mhonarc] = Pathname.new(path).expand_path }
+  op.on("-o", "--outdir PATH", "Target directory for the output HTML files"){ |path| options[:outdir] = Pathname.new(path).expand_path }
+  op.on("-s", "--style STRING", "Path to a CSS file referenced from the HTML.", "This is copied as-is!"){ |str| options[:stylefile] = str }
+  op.on("-S", "--search URL", "Search target location"){ |url| options[:searchtarget] = url }
+  op.on("-v", "--version", "Print version number and exit"){ puts(MlmmjArchiver::VERSION); exit }
+  op.on("-V", "--[no-]verbose", "Turn on verbose mode"){ |bool| options[:verbose] = bool }
+  op.on("-x", "--[no-]checknoarchive", "Check the mails' X-No-Archive header"){ |bool| options[:checknoarchive] = bool }
+end.parse!(ARGV)
+
+########################################
+# Configfile
+
+if options[:configfile]
+  confighash = Hash[YAML.load_file(options[:configfile].to_s).map{|k, v| [k.to_sym, v]}]
+  options.update(confighash){|k, v1, v2| v1}
+end
+
+########################################
+# Checking
+
+error!("Required option -i missing") unless options[:indir]
+error!("Required option -o missing") unless options[:outdir]
+
+if options[:verbose]
+  puts "Specified options:"
+  options.each{|k, v| puts("#{k}: #{v}")}
+end
+
+########################################
+# Start of program
+
+archiver = MlmmjArchiver::Archiver.new(options.delete(:outdir), options)
+archiver.debug_mode = true if options[:verbose]
+archiver << options.delete(:indir)
+archiver.preprocess_mlmmj_mails!
+archiver.archive!

data/data/mhonarc-rc.erb

@@ -0,0 +1,465 @@
+<!-- Autogenerated MHonArc RC file, do not touch -->
+<!-- ------------------------------------------------------------------	-->
+<!-- TLEVELS:								-->
+<!--									-->
+<!-- TLEVELS defines the maximum number of nested listings in a thread	-->
+<!-- index. Any threads that go over TLEVELS in depth are flattened to	-->
+<!-- the value of TLEVELS. This resource is helpful in preventing huge	-->
+<!-  indentations in deep threads which may cause text to be squished	-->
+<!-- on the right-side of an HTML viewer.				-->
+<!--									-->
+
+<TLEVELS>
+<%= tlevels %>
+</TLEVELS>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- MIMEExcs:							-->
+<!--									-->
+<!-- we don't want HTML messages at all. -->
+
+<MIMEExcs>
+text/html
+text/x-html
+</MIMEExcs>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- NOMAILTO:								-->
+<!--									-->
+<!-- If the MAILTO resource is on, mail addresses in message headers	-->
+<!-- will be converted into mailto URL links as defined by the		-->
+<!-- MAILTOURL resource.						-->
+<!--									-->
+
+<NOMAILTO>
+</NOMAILTO>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- MHPATTERN:								-->
+<!--									-->
+<!-- This is needed to have MHonArc grok maildir folders		-->
+<!--									-->
+
+<MHPATTERN>
+^[^\.]
+</MHPATTERN>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- TIDXFNAME:								-->
+<!--									-->
+<!-- Name of the threads index file					-->
+<!--									-->
+
+<TIDXFNAME>
+index.html
+</TIDXFNAME>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- IDXFNAME:								-->
+<!--									-->
+<!-- Name of the message index file					-->
+<!--									-->
+
+<IDXFNAME>
+seq.html
+</IDXFNAME>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- MSGPREFIX:								-->
+<!--									-->
+<!-- Prefix for message files						-->
+<!--									-->
+
+<MSGPREFIX>
+00
+</MSGPREFIX>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- NODOC:								-->
+<!--									-->
+<!-- Remove link to MHonArc documentation from bottom of pages		-->
+<!--									-->
+
+<NODOC>
+</NODOC>
+
+<SPAMMODE>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- CHECKNOARCHIVE:							-->
+<!--									-->
+<!-- If CHECKNOARCHIVE is set, MHonArc will check each message for the	-->
+<!-- "no archive" flag. If present, MHonArc will not add the message to	-->
+<!-- the archive. MHonArc looks for one of the following in a message	-->
+<!-- header to determine if message should not be archived:		-->
+<!--									-->
+<!--     X-no-archive: yes						-->
+<!--     Restrict: no-external-archive					-->
+<!--									-->
+<!-- If either header field is present with the given value, and	-->
+<!-- CHECKNOARCHIVE is set, MHonArc will skip the message.		-->
+<!--									-->
+
+<%= checknoarchive %>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- FIELDORDER:							-->
+<!--									-->
+<!-- The FIELDORDER resource allows you to control the order the	-->
+<!-- message header fields appear in the HTML output.			-->
+<!--									-->
+<!-- If -extra- is not specified, then only the fields listed will be	-->
+<!-- displayed.								-->
+
+<FIELDORDER>
+subject
+from
+reply-to
+date
+to
+cc
+</FIELDORDER>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- MIMEArgs -->
+<!-- Define options for the MIME filters in use. We want to wrap -->
+<!-- long lines of text automatically. -->
+
+<MIMEArgs>
+m2h_text_plain::filter; maxwidth=80 fancyquote quoteclass=mlquote
+</MIMEArgs>
+
+<!-- ------------------------------------------------------------------	-->
+<!-- HTMLEXT:								-->
+<!--									-->
+<!-- HTMLEXT defines the extension for all HTML files generated by	-->
+<!-- MHonArc.								-->
+<!--									-->
+
+<HTMLEXT>
+html
+</HTMLEXT>
+
+
+<!-- ------------------------------------------------------------------ -->
+<!-- MSGPGBEGIN, MSGPGEND:                                              -->
+<!--                                                                    -->
+<!-- MSGPGBEGIN defines the beginning markup of each message page. It   -->
+<!-- allows you to redefine the opening HTML element, HEAD element,     -->
+<!-- TITLE element, opening BODY element, etc.                          -->
+<!--                                                                    -->
+<!-- MSGPGEND defines the ending markup of each message page.           -->
+<!--                                                                    -->
+
+<MSGPGBEGIN>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+<head>
+ <title>$SUBJECTNA$</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <link rel="stylesheet" type="text/css" media="screen" href="<%= stylefile %>">
+</head>
+<body>
+ <div id="banner">
+  <div id="header">
+   <%= header %>
+  </div>
+  <div id="toplinks">
+  $BUTTON(PREV)$ $BUTTON(NEXT)$ $BUTTON(TPREV)$ $BUTTON(TNEXT)$ [<a
+  href="$IDXFNAME$#$MSGNUM$">Date Index</a>] [<a
+  href="$TIDXFNAME$#$MSGNUM$">Thread Index</a>]
+<% if searchtarget %>
+  [<a href="<%= searchtarget %>">Search</a>]
+<% end %>
+  </div>
+ </div>
+ <div id="mailinglists">
+  <div id="main">
+</MSGPGBEGIN>
+
+<MSGPGEND>
+   <!-- FIXME <address>Archive administrator: postmaster@mlmmj-webarchiver</address> -->
+  </div>
+ </div>
+</body>
+</html>
+</MSGPGEND>
+
+
+<!-- ------------------------------------------------------------------ -->
+<!-- IDXPGBEGIN, IDXPGEND:                                              -->
+<!--                                                                    -->
+<!-- The IDXPGBEGIN resource defines the beginning markup for the main  -->
+<!-- index page. I.e. You can control the opening <HTML> tag, the HEAD  -->
+<!-- element contents, the opening <BODY> tag, etc. Therefore, if you   -->
+<!-- are not satisfied with the default behavior of how the TITLE       -->
+<!-- resource is used, or have other needs that require control over    -->
+<!-- the beginning markup, you can set the IDXPGBEGIN resource to what  -->
+<!-- you desire.                                                        -->
+<!--                                                                    -->
+<!-- The IDXPGEND resource defines the end markup for the main index    -->
+<!-- page.                                                              -->
+
+<IDXPGBEGIN>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+<head>
+ <title>$IDXTITLE$</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <link rel="stylesheet" type="text/css" media="screen" href="<%= stylefile %>">
+</head>
+<body>
+</IDXPGBEGIN>
+
+<IDXPGEND>
+</body>
+</html>
+</IDXPGEND>
+
+
+<!-- ------------------------------------------------------------------ -->
+<!-- TIDXPGBEGIN, TIDXPGEND                                             -->
+<!--                                                                    -->
+<!-- The TIDXPGBEGIN resource defines the beginning markup for the      -->
+<!-- thread index pages. I.e. You can control the opening <HTML> tag,   -->
+<!-- the HEAD element contents, the opening <BODY> tag, etc. Therefore, -->
+<!-- if you are not satisfied with the default behavior of how the      -->
+<!-- TTITLE resource is used, or have other needs that require control  -->
+<!-- on the beginning markup, you can set the TIDXPGBEGIN resource to   -->
+<!-- what you desire.                                                   -->
+<!--                                                                    -->
+<!-- The TIDXPGEND resource defines the end markup for the thread index -->
+<!-- pages.                                                             -->
+<!--                                                                    -->
+
+<TIDXPGBEGIN>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+<head>
+ <title>$TIDXTITLE$</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <link rel="stylesheet" type="text/css" media="screen" href="<%= stylefile %>">
+</head>
+<body>
+</TIDXPGBEGIN>
+
+<TIDXPGEND>
+</body>
+</html>
+</TIDXPGEND>
+
+<!-- ------------------------------------------------------------------ -->
+<!-- LISTBEGIN, LITEMPLATE, LISTEND:                                    -->
+<!--                                                                    -->
+<!-- The LISTBEGIN resource specifies the markup to begin the message   -->
+<!-- list. This resource works in conjuction with LITEMPLATE and        -->
+<!-- LISTEND resources to format the main index page(es).               -->
+<!--                                                                    -->
+<!-- The LITEMPLATE resource specifies the markup for an entry in the   -->
+<!-- main index message list. This resource works in conjuction with    -->
+<!-- LITEMPLATE and LISTEND resources to format the main index page(es) -->
+<!-- http://www.mhonarc.org/MHonArc/doc/resources/litemplate.html       -->
+<!--                                                                    -->
+<!-- The LISTEND resource specifies the markup to end the message list  -->
+<!-- in the main index. This resource works in conjuction with          -->
+<!-- LISTBEGIN and LITEMPLATE resources to format the main index        -->
+<!-- page(es).                                                          -->
+<!--                                                                    -->
+
+<LISTBEGIN>
+ <div id="banner">
+  <div id="header">
+    <%= header %>
+  </div>
+  <div id="topnav">
+   <a href="/">Home</a>
+   |
+   <a href="../..">Month and Year Index</a>
+   |
+   <a href="$TIDXFNAME$">Thread Index</a>
+   |
+   <a href="$IDXFNAME$">Date Index</a>
+<% if searchtarget %>
+   |
+   <a href="<%= searchtarget %>">Search</a>
+<% end %>
+  </div>
+ </div>
+ <div id="mailinglists">
+  <div id="main">
+<h1>Date Index</h1>
+<div id="didx">
+<ul>
+</LISTBEGIN>
+
+<LITEMPLATE>
+<li><strong>$SUBJECT$</strong> $MSGLOCALDATE(CUR;%Y-%m-%d %H:%M)$
+<ul>
+<li><em>From</em>: $FROM$</li></ul>
+</li>
+</LITEMPLATE>
+
+<LISTEND>
+</ul>
+</div>
+   <!-- FIXME <address>Archive administrator: postmaster@mlmmj-webarchiver</address> -->
+  </div>
+ </div>
+</LISTEND>
+
+
+<!-- ------------------------------------------------------------------ -->
+<!-- THEAD, TFOOT                                                       -->
+<!--                                                                    -->
+<!-- THEAD defines the header markup of thread index pages. It is also  -->
+<!-- responsible for defining the opening markup for the thread         -->
+<!-- listings.                                                          -->
+<!--                                                                    -->
+<!-- TFOOT defines the footer markup of thread index pages. It is also  -->
+<!-- responsible for defining the closing markup for the thread listing -->
+<!--                                                                    -->
+
+<THEAD>
+ <div id="banner">
+  <div id="header">
+    <%= header %>
+  </div>
+  <div id="topnav">
+   <a href="/">Home</a>
+   |
+   <a href="../..">Month and Year Index</a>
+   |
+   <a href="$TIDXFNAME$">Thread Index</a>
+   |
+   <a href="$IDXFNAME$">Date Index</a>
+<% if searchtarget %>
+   |
+   <a href="<%= searchtarget %>">Search</a>
+<% end %>
+  </div>
+ </div>
+ <div id="mailinglists">
+  <div id="main">
+<h1>Thread Index</h1>
+<div id="tidx">
+<ul>
+</THEAD>
+
+<TFOOT>
+</ul> 
+</div>
+   <address>Archive administrator: <%= archiveadmin %></address>
+  </div>
+ </div>
+</TFOOT>
+ 
+<!-- ------------------------------------------------------------------ -->
+<!-- BOTLINKS                                                           -->
+<!--                                                                    -->
+<!-- BOTLINKS defines the markup for the links at the bottom of a       -->
+<!-- message page. Its usage is analagous to the TOPLINKS resource, but -->
+<!-- tends to be more verbose. However, you can define the resource     -->
+<!-- anyway you desire.                                                 -->
+<!--                                                                    -->
+
+<BOTLINKS>
+<!-- No BOTLINKS -->
+</BOTLINKS>
+
+<!-- ------------------------------------------------------------------ -->
+<!-- FOLUPBEGIN, FOLUPLITXT and FOLUPEND                                -->
+<!--                                                                    -->
+<!-- FOLUPBEGIN defines the markup to start the explicit follow-up      -->
+<!-- links after the message body on a message page.                    -->
+<!--                                                                    -->
+<!-- FOLUPLITXT defines the markup for an entry in the explicit         -->
+<!-- follow-up links list after the message body on a message page.     -->
+<!--                                                                    -->
+<!-- FOLUPEND defines the ending markup for the the explicit follow-up  -->
+<!-- links after the message body on a message page.                    -->
+<!--                                                                    -->
+
+<FOLUPBEGIN>
+<div class="followups">
+<h2>Followups:</h2>
+<ul>
+</FOLUPBEGIN>
+
+<FOLUPLITXT>
+<li><strong>$SUBJECT$</strong> (<em>$FROM$</em>)</li>
+</FOLUPLITXT>
+
+<FOLUPEND>
+</ul>
+</div>
+</FOLUPEND>
+
+<!-- ------------------------------------------------------------------ -->
+<!-- REFSBEGIN, REFSLITXT and REFSEND                                   -->
+<!--                                                                    -->
+<!-- REFSBEGIN defines the markup to start the explicit reference links -->
+<!-- after the message body on a message page.                          -->
+<!--                                                                    -->
+<!-- REFSLITXT defines the markup for an entry in the explicit          -->
+<!-- reference links list after the message body on a message page.     -->
+<!--                                                                    -->
+<!-- REFSEND defines the ending markup for the the explicit reference   -->
+<!-- links after the message body on a message page.                    -->
+<!--                                                                    -->
+
+<REFSBEGIN>
+<div class="references">
+<h2>References:</h2>
+<ul>
+</REFSBEGIN>
+
+<REFSLITXT>
+<li><strong>$SUBJECT$</strong> (<em>$FROM$</em>)</li>
+</REFSLITXT>
+
+<REFSEND>
+</ul>
+</div>
+</REFSEND>
+
+<!-- ------------------------------------------------------------------ -->
+<!-- SUBJECTHEADER:                                                     -->
+<!--                                                                    -->
+<!-- SUBJECTHEADER defines the markup for the main subject line above   -->
+<!-- the message header of message pages.                               -->
+<!--                                                                    -->
+ 
+<SUBJECTHEADER>
+<h1>$SUBJECTNA$</h1>
+</SUBJECTHEADER>
+
+<!-- Thread element -->
+<!-- Add dates to every line in the thread view -->
+<TLiTxt>
+<li><strong>$SUBJECT$</strong>,
+<em>$FROMNAME$</em>, $MSGLOCALDATE(CUR;%Y-%m-%d %H:%M)$
+</TLiTxt>
+
+<TTopBegin>
+<li><strong>$SUBJECT$</strong>,
+<em>$FROMNAME$</em>, $MSGLOCALDATE(CUR;%Y-%m-%d %H:%M)$
+</TTopBegin>
+
+<TSingleTxt>
+<li><strong>$SUBJECT$</strong>,
+<em>$FROMNAME$</em>, $MSGLOCALDATE(CUR;%d.%m %H:%M)$
+</TSingleTxt>
+
+<!-- ------------------------------------------------------------------ -->
+
+<FieldsBeg>
+<ul class="message-headers">
+</FieldsBeg>
+
+<FieldsEnd>
+</ul>
+</FieldsEnd>
+
+<TopLinks>
+<div></div>
+</TopLinks>