| 1 |
<html> |
| 2 |
<body> |
| 3 |
|
| 4 |
<pre> |
| 5 |
|
| 6 |
joko@netfrag.org - sample stack: |
| 7 |
|
| 8 |
o [task by joko] introduced "dispatchmail" to add mail2news-functionality to "recieveMail" (collector@netfrag.org) |
| 9 |
x [task by joko] migrated joko_mail from "receiveMail" to "dispatchmail" |
| 10 |
x [bug from joko] what about mailing from the cli / mails sent from the system (e.g. via CVSSpam): |
| 11 |
mail is sent out coming from <username>@quepasa.netfrag.org |
| 12 |
--> how to configure just having <username>@netfrag.org right here??? |
| 13 |
x [resolved by jonen] CVSSpam: janosch@netfrag.org: |
| 14 |
x cd /etc/mail |
| 15 |
x nano sendmail.mc |
| 16 |
x add/replace line: MASQUERADE_AS(`netfrag.org') |
| 17 |
x make |
| 18 |
x /etc/init.d/sendmail reload |
| 19 |
o [bug from joko] "su root" is needed sometimes |
| 20 |
else PATH is not set correctly |
| 21 |
and maybe something other |
| 22 |
compiling fails always |
| 23 |
x [task by joko] these items already have been refactored into other Tasks, Notes and/or Bug Requests - this Note is just FYI. |
| 24 |
o [task by joko] dispatchmail - project work |
| 25 |
x README.pod -> README.html |
| 26 |
x link with "topics.html" properly |
| 27 |
x write something about data-/control-flow to README.pod |
| 28 |
|
| 29 |
o look (in detail) at Cyrus Netnews |
| 30 |
[...] |
| 31 |
The IMAP server can export netnews newsgroups as IMAP mailboxes. |
| 32 |
[...] |
| 33 |
o collectnews, rmnews, syncnews |
| 34 |
x seems to make an external web-based newsreader unneccessary!!! |
| 35 |
|
| 36 |
o tie together mail, news and html |
| 37 |
o write mini-howto |
| 38 |
|
| 39 |
o link with erfrakon |
| 40 |
|
| 41 |
o sieve? |
| 42 |
|
| 43 |
o post some old mails to news.netfrag.org! |
| 44 |
|
| 45 |
o what about "dev@netfrag.org"? |
| 46 |
|
| 47 |
o nfo/perl/libs |
| 48 |
x ts |
| 49 |
x outlook2ldap |
| 50 |
x dispatchmail |
| 51 |
o get the essence (project- and development work - the whole workflow) out of it! write it down! in detail! |
| 52 |
|
| 53 |
o netfrag.org-workflow: |
| 54 |
o technical questions to support@netfrag.org? |
| 55 |
o publish them via news! |
| 56 |
o queue them into / integrate with TUTOS somehow!!! |
| 57 |
|
| 58 |
o new threads@news.netfrag.org: |
| 59 |
x ctlinnd newgroup nfo.support.queue |
| 60 |
x ctlinnd newgroup nfo.support.faq |
| 61 |
|
| 62 |
x new account for janosch@news.netfrag.org |
| 63 |
x nano /etc/news/nnrp.access |
| 64 |
x added line: *:Read Post:janosch:janosch:* |
| 65 |
|
| 66 |
o check out from cvs-repository: |
| 67 |
o joko/doc -> /home/joko/public_html/computing/overview/topics/ |
| 68 |
o leaded to (A, B and C): see <a href="../topics/home2web.html">home2web</a> |
| 69 |
|
| 70 |
o added user@netfrag.org: |
| 71 |
x adduser: collector/col§$ |
| 72 |
|
| 73 |
o about: some sample items occoured 2003-01-17 until 2003-01-26. |
| 74 |
what to do with that? |
| 75 |
o have all items stored in other applications conveniently. |
| 76 |
o be able to have items or references to them *archived* centrally |
| 77 |
o be able to access informations via *one* interface. |
| 78 |
actually *multiple* interfaces should be possible |
| 79 |
- the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?) |
| 80 |
|
| 81 |
o refactor topics: |
| 82 |
o make global-accessible@netfrag.org |
| 83 |
o introduce subtopics |
| 84 |
o sysadmin tasks |
| 85 |
o janosch's, jonen's and joko's tasks |
| 86 |
|
| 87 |
o start project "admintools" @ nfo/perl/scripts - including |
| 88 |
o getip.pl |
| 89 |
o notify.pl |
| 90 |
x on uml-event: up/down/reboot |
| 91 |
o on news-post (dispatchmail: mail2news) |
| 92 |
o on cvs-checkout (done on interval with joko/doc - see above) |
| 93 |
o on build (build.pl) |
| 94 |
o some tools from dispatchmail |
| 95 |
o dispatchmail itself! |
| 96 |
o |
| 97 |
|
| 98 |
o [idea] ;-) for symbols (in general) |
| 99 |
- o = Open Task |
| 100 |
- x = Closed Task |
| 101 |
(- [<TopicName>] = name of topic - fixed/proposed) |
| 102 |
- [<TopicType> by|for <UserName>] = |
| 103 |
- type of topic - fixed/proposed |
| 104 |
- username who submitted this item / should this item be assigned to |
| 105 |
- this could become a language for describing the workflow |
| 106 |
- this proposal should be the shortcut-form in wiki-style: (e.g. make 'tiki-workflow' from that?) |
| 107 |
- more verbose (e.g. XML) - forms could/should become possible (e.g. 'WFML') (WorkFlow Markup|Modeling Language) |
| 108 |
- TODO: refactor this document after further commits to show off refactoring process through cvs-revisioning! |
| 109 |
o required for this: link to a page which shows the history of a document not as verbose as (e.g.) chora does |
| 110 |
- d = from 'tbd': to-be-discussed |
| 111 |
- c = cancelled |
| 112 |
|
| 113 |
o [idea] ;-) for symbols (in _this_ document here) (parser|engine behaviour modification) |
| 114 |
- R = from 'tbr': to-be-refactored |
| 115 |
- r = already refactored elsewhere |
| 116 |
- an "r" may also mean "reference" ;-) |
| 117 |
- make 'r-http://netfrag.org/to/another/reference/wrapped/via/http/' possible in documentation |
| 118 |
- also the shortcut form: [r:/to/another/reference/wrapped/via/http/] |
| 119 |
- this - and only this - should be the minimalst requried definition of a "reference" |
| 120 |
- an internet "link" - however needs some more metadata around it: an "url" and a "caption" - what about these? |
| 121 |
- either fetch them from archive-metadata of this reference ... |
| 122 |
- ... or use the name directly as caption and build the url against a known redirector handler which |
| 123 |
accesses the archive-metadata |
| 124 |
|
| 125 |
o rename "thread" to "newsgroup" in all scripts! |
| 126 |
|
| 127 |
o what about: |
| 128 |
Torus::Xyz - solution to reuse concepts of Apache 2 and Cyrus 2!!! (and OpenLDAP???) for building an open collaboration server? |
| 129 |
|
| 130 |
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> |
| 216 |
|
| 217 |
</body> |
| 218 |
</html> |
Parent Directory
| 
Revision Log
