Changeset 316:e108bea0d05c
- Timestamp:
- 08/20/11 01:32:45 (9 months ago)
- Branch:
- default
- Files:
-
- 1 modified
-
doc/Lancelot-HOWTO.txt (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/Lancelot-HOWTO.txt
r303 r316 28 28 ''alias'' such as 29 29 {{{ 30 test: "|/usr/local/bin/pl-incoming test@example.com"30 test: "|/usr/local/bin/pl-incoming --user alfred test@example.com" 31 31 }}} 32 32 in your system's alias database (usually /etc/aliases). You will probably … … 40 40 take care of them. 41 41 42 '''Note (for Our-ISP users):''' On Our-ISP, use the pfixadm(1) command to43 create a mailbox ('''NOT''' a pfixadm-style mailinglist) for the desired44 address:45 {{{46 $ pfixadm mailbox add test@example.com foobar47 }}}48 (The password, "foobar" here, is of no consequence.) Then invoke49 pl-init(1) as above, but giving the '''--our-isp''' command line option:50 {{{51 $ pl-init --our-isp test@example.com alfred@example.com52 }}}53 This will create the list configuration database in54 $HOME/domains/DOMAIN/LOCAL, or $HOME/domains/example.com/test in our55 example. (Note that this is the mailbox's "home directory" from the56 point of view of the mail delivery mechanism.)57 58 To deliver mail to Project Lancelot on Our-ISP; create a file called59 $HOME/domains/DOMAIN/LOCAL/.mailfilter (here,60 $HOME/domains/example.com/test/.mailfilter) containing a recipe like61 {{{ to "|/usr/bin/pl-incoming test@example.com" }}} The good news is62 that Project Lancelot does this for you unless you specify the63 '''--nomailfilter''' option.64 65 66 42 == Configuring the new list == 67 43 … … 109 85 == Managing Subscribers == 110 86 111 Like most mailing list management programs, Lancelot allows users87 Like most mailing list management programs, Project Lancelot allows users 112 88 to subscribe or unsubscribe themselves by sending messages to 113 addresses such as ''test -subscribe@example.com''. But you can still89 addresses such as ''test+subscribe@example.com''. But you can still 114 90 change the subscription database manually. Here's how to add subscribers: 115 91 {{{ … … 117 93 }}} 118 94 This will add Joe Blow's and Sue Foo's addresses to the subscriber 119 database. pl-subscribe(1) takes arbitrarily many (well almost) 95 database. Project Lancelot uses the same code to parse the address 96 arguments to pl-subscribe(1) that it uses to pass ''From'' headers in 97 e-mail, so you can say 98 {{{ 99 $ pl-subscribe test@example.com "Joe Blow <joe.blow@example.org>" 100 }}} 101 and "Joe Blow" will be noted as the name going with the address, 102 ''joe.blow@example.org''. 103 104 pl-subscribe(1) takes arbitrarily many (well almost) 120 105 addresses on the command line, but if you do not give any, pl-subscribe(1) 121 will read standard input instead:106 will read its standard input instead: 122 107 {{{ 123 108 $ pl-subscribe test@example.com <members-list.txt … … 139 124 }}} 140 125 126 == List Aliases == 127 128 It is extremely tedious to have to type command lines like 129 {{{ 130 $ pl-subscribe foobar-announce@lists.marketing.example.com ... 131 }}} 132 so (fortunately) there is a helpful shortcut. A command like 133 {{{ 134 $ pl-conf --alias foobar-announce@lists.marketing.example.com fba 135 }}} 136 lets you use ''fba'' in place of the long address in commands: 137 {{{ 138 $ pl-subscribe fba ... 139 }}} 140 This form of "aliasing" applies to all Project Lancelot command-line 141 tools. The command 142 {{{ 143 $ pl-conf --alias foobar-announce@lists.marketing.example.com 144 }}} 145 (without an alias) will enumerate the current alias (or aliases -- 146 you can have as many as you like) for that list. If you're ever unsure 147 exactly what list an alias points to, use a command like 148 {{{ 149 $ pl-conf -qh fba list.address 150 }}} 151 152 Project Lancelot maintains an "automatic" alias to the last list 153 address you used in a Project Lancelot command. In 154 {{{ 155 $ pl-subscribe test@example.org joe.blow@example.org 156 $ pl-subscribe . sue.foo@example.net 157 }}} 158 the second ''pl-subscribe'' command also applies to 159 ''test@example.org''. (You will be relieved to hear that this works 160 for all Project Lancelot command-line tools except pl-incoming(1), 161 which deals with incoming mail, and pl-janitor(1), which performs 162 periodic cleanups. These commands will be invoked at various times 163 either from the mail system or cron, and it would be confusing for 164 them to reset Project Lancelot's notion of the "current list" while 165 you may be typing interactive commands. 166 167 List aliases are really just symbolic links in the ''.pl'' directory. 168 If you want to remove an alias, simply delete the symbolic link in 169 question. (The "." alias is really a symbolic link called 170 ''.default-list''.) 171 141 172 142 173 == Incoming Mail == 143 174 144 175 Here's what happens when Project Lancelot receives a message to the 145 list submission address ( test@example.com, right?). At least this is176 list submission address (''test@example.com'', right?). At least this is 146 177 what happens unless you change things completely, which you are 147 178 absolutely free to do but probably shouldn't until you have learned … … 162 193 * Checking whether the message looks reasonable from a MIME point 163 194 of view, i.e., has significant plain-text content and does not contain 164 fishy-looking attachments such as viruses. This step also gets rid165 of everything that is not plain text.195 fishy-looking attachments, which might harbour spam or viruses. 196 This step also gets rid of everything that is not plain text. 166 197 * Adding RFC2919 and (optionally) RFC2369 headers to the message. 167 198 * Optionally adding a "tag" to the message's ''Subject:'' header. … … 212 243 213 244 Project Lancelot is very much a work in progress, and we hope that its 214 obvious major problems, such as the complete lack of e-mail-based 215 subscription handling, will very shortly be either removed or replaced 245 obvious major problems will very shortly be either removed or replaced 216 246 with new major problems. Stay tuned.
