--- joko/doc/SampleTasks/joko_2003-01.html 2003/01/23 20:49:15 1.4
+++ joko/doc/SampleTasks/joko_2003-01.html 2003/01/23 22:49:17 1.5
@@ -137,17 +137,80 @@
o update mail-dispatching-rules
o look at ilo.de/Inbox
+ o marked message to Spam? Newsletters?
o move: logs/cvs/quepasa.netfrag.org -> logs/netfrag.org
o look at netfrag.org/Inbox
o if subject eq "Cron ~/.cronrc-hourly" set target "logs/netfrag.org/joko/cron" [push over cron]
o if subject matches "quepasa daily usenet report" at begin set target "logs/netfrag.org/news" [push over inn]
o if subject matches "[CVS" at begin set target "logs/netfrag.org/cvs" [push over CVSSpam]
o if mail is from myself set target "netfrag.org/Info"
+ o look at quepasa.netfrag.org/Inbox
+ o [Multisync-users]
+ o [Kroupware]
+
o write parser and engine to handle above declaration: Mail::Audit::Dispatch::Interface::Script
+
o release mail from above from joko - introduce another email-address
- e.g. work@netfrag.org, event@netfrag.org or tracker@netfrag.org (like collector@netfrag.org)
+
+o Multisync & SyncML
+ o post something to mailing-list...!?
+
+o the '.cvslink'-mechanism:
+ o type: ln -s /home/joko/public_html/_web/_cvs.php .
+
+o LinkContainer
+ - insert via drag & drop
+ - shows links hierarchically
+
+o (Self)Info - mails to yourself
+ o convert all "(Self)Info" mails to
+ news-messages - use "formail" and ...?
+
+o h1.service.netfrag.org
+ o base os-upgrade: suse X -> debian 3.0
+o dispatchmail
+ o are Mail-Headers already added?
+
+o workflow (PostThisLink)
+ o drag link from done google-search ...
+ o ... to container (at the current Task)
+ o a news-post is created automagically
+ o use this:
+ [smtp-header-fields]
+ From: expanded email-address resolved from Name|Nickname in Addressbook (via LDAP!)
+ Subject: googled for ""
+ [body]
+ o include into mime-part if not already included
+ o fetch from web on demand
+
+o ssl/tls for inn?
+
+o dispatchmail
+ o re-link as sub-/module-project under Torus::Content::Gateway
+ o -> Torus::Content - a content delivery engine
+ o -> additional idea: Torus::Content::Gateway is "just" the API to "Torus::Item::Router" in this case
+ o 'Torus::Content::Gateway' would then route 'Torus::Item::RFC822'-objects using 'Torus::Item::Router'
+ o look at sieve - jonen posted to nfo.links.computing: [r:Message-ID: ]
+
+o finally: do actually establish 'Torus' at 'nfo/perl/libs'
+
+o pod: checkout how to make references which expand to html-urls
+ o does pod handle this or do we need external link-expansion for this task?
+ o how to make references to news-messages?
+ e.g.:
+ o Message-ID:
+ o news://news.netfrag.org/nfo.links.computing
+ o proposal(s):
+ o http://news.netfrag.org/id=b0ppj7$7gv$1@quepasa.netfrag.org
+ o http://news.netfrag.org/nfo.links.computing/subject=FilteringMailWithSieve of wiki
+ o http://news.netfrag.org/nfo.links.computing/id=b0ppj7$7gv$1@quepasa.netfrag.org
+
+o what about the '.nws'-files on ms? (for news-messages)
+
+o display-mode: everything strictly hierarchical to get maximum overview!!!