| 129 |
|
|
| 130 |
o word-search: "identify" and "search" for |
o word-search: "identify" and "search" for |
| 131 |
|
|
| 132 |
|
o establish global "logs/" - like at http://moose.qx.net/logs/ |
| 133 |
|
|
| 134 |
|
o add redirecting page when someone wants to access |
| 135 |
|
o http://netfrag.org/~joko/phpChoPro/ or |
| 136 |
|
o http://netfrag.org/~joko/w2hfax/ |
| 137 |
|
|
| 138 |
|
o update mail-dispatching-rules |
| 139 |
|
o look at ilo.de/Inbox |
| 140 |
|
o marked message to Spam? Newsletters? |
| 141 |
|
o move: logs/cvs/quepasa.netfrag.org -> logs/netfrag.org |
| 142 |
|
o look at netfrag.org/Inbox |
| 143 |
|
o if subject eq "Cron <joko@quepasa> ~/.cronrc-hourly" set target "logs/netfrag.org/joko/cron" [push over cron] |
| 144 |
|
o if subject matches "quepasa daily usenet report" at begin set target "logs/netfrag.org/news" [push over inn] |
| 145 |
|
o if subject matches "[CVS" at begin set target "logs/netfrag.org/cvs" [push over CVSSpam] |
| 146 |
|
o if mail is from myself set target "netfrag.org/Info" |
| 147 |
|
o look at quepasa.netfrag.org/Inbox |
| 148 |
|
o [Multisync-users] |
| 149 |
|
o [Kroupware] |
| 150 |
|
|
| 151 |
|
o write parser and engine to handle above declaration: Mail::Audit::Dispatch::Interface::Script |
| 152 |
|
|
| 153 |
|
|
| 154 |
|
o release mail from above from joko - introduce another email-address |
| 155 |
|
- e.g. work@netfrag.org, event@netfrag.org or tracker@netfrag.org (like collector@netfrag.org) |
| 156 |
|
|
| 157 |
|
o Multisync & SyncML |
| 158 |
|
o post something to mailing-list...!? |
| 159 |
|
|
| 160 |
|
o the '.cvslink'-mechanism: |
| 161 |
|
o type: ln -s /home/joko/public_html/_web/_cvs.php . |
| 162 |
|
|
| 163 |
|
o LinkContainer |
| 164 |
|
- insert via drag & drop |
| 165 |
|
- shows links hierarchically |
| 166 |
|
|
| 167 |
|
o (Self)Info - mails to yourself |
| 168 |
|
o convert all "(Self)Info" mails to |
| 169 |
|
news-messages - use "formail" and ...? |
| 170 |
|
|
| 171 |
|
o h1.service.netfrag.org |
| 172 |
|
o base os-upgrade: suse X -> debian 3.0 |
| 173 |
|
|
| 174 |
|
o dispatchmail |
| 175 |
|
o are Mail-Headers already added? |
| 176 |
|
|
| 177 |
|
o workflow (PostThisLink) |
| 178 |
|
o drag link from done google-search ... |
| 179 |
|
o ... to container (at the current Task) |
| 180 |
|
o a news-post is created automagically |
| 181 |
|
o use this: |
| 182 |
|
[smtp-header-fields] |
| 183 |
|
From: expanded email-address resolved from Name|Nickname in Addressbook (via LDAP!) |
| 184 |
|
Subject: googled for "<search-request>" |
| 185 |
|
[body] |
| 186 |
|
o include into mime-part if not already included |
| 187 |
|
o fetch from web on demand |
| 188 |
|
|
| 189 |
|
o ssl/tls for inn? |
| 190 |
|
|
| 191 |
|
o dispatchmail |
| 192 |
|
o re-link as sub-/module-project under Torus::Content::Gateway |
| 193 |
|
o -> Torus::Content - a content delivery engine |
| 194 |
|
o -> additional idea: Torus::Content::Gateway is "just" the API to "Torus::Item::Router" in this case |
| 195 |
|
o 'Torus::Content::Gateway' would then route 'Torus::Item::RFC822'-objects using 'Torus::Item::Router' |
| 196 |
|
o look at sieve - jonen posted to nfo.links.computing: [r:Message-ID: <b0ppj7$7gv$1@quepasa.netfrag.org>] |
| 197 |
|
|
| 198 |
|
o finally: do actually establish 'Torus' at 'nfo/perl/libs' |
| 199 |
|
|
| 200 |
|
o pod: checkout how to make references which expand to html-urls |
| 201 |
|
o does pod handle this or do we need external link-expansion for this task? |
| 202 |
|
o how to make references to news-messages? |
| 203 |
|
e.g.: |
| 204 |
|
o Message-ID: <b0ppj7$7gv$1@quepasa.netfrag.org> |
| 205 |
|
o news://news.netfrag.org/nfo.links.computing |
| 206 |
|
o proposal(s): |
| 207 |
|
o http://news.netfrag.org/id=b0ppj7$7gv$1@quepasa.netfrag.org |
| 208 |
|
o http://news.netfrag.org/nfo.links.computing/subject=FilteringMailWithSieve of wiki |
| 209 |
|
o http://news.netfrag.org/nfo.links.computing/id=b0ppj7$7gv$1@quepasa.netfrag.org |
| 210 |
|
|
| 211 |
|
o what about the '.nws'-files on ms? (for news-messages) |
| 212 |
|
|
| 213 |
|
o display-mode: everything strictly hierarchical to get maximum overview!!! |
| 214 |
|
|
| 215 |
</pre> |
</pre> |
| 216 |
|
|
| 217 |
</body> |
</body> |
Parent Directory
| 
Revision Log
| 
Patch
