build:lists
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
build:lists [2018/05/28 03:00] SLUUG Administration [Mailman TODO:] |
build:lists [2018/05/28 03:17] SLUUG Administration [Mailman TODO:] |
||
|---|---|---|---|
| Line 524: | Line 524: | ||
| * We should probably SSL-require the administrative pages for mailman. | * We should probably SSL-require the administrative pages for mailman. | ||
| - | + | * We need to test mailman with some of the majordomo archives from michelob. | |
| - | * We need to test mailman with some of the majordomo archives from | + | |
| - | michelob. | + | |
| * We need to set up mailman to handle lists for all of sluug.org | * We need to set up mailman to handle lists for all of sluug.org | ||
| - | + | * /usr/local/mailman/bin/add_members should be run on a list of current subscribers to ANNOUNCE, DISCUSS, SYSADMIN, and STEERCOM. I'm not quite sure how passwords, if any, will be handled. | |
| - | * /usr/local/mailman/bin/add_members should be run on a list of current | + | * We need to copy the archives from michelob to bud and index them via htdig. I'm not sure how htdig and/or apache will handle the compressed files as currently configured. |
| - | subscribers to ANNOUNCE, DISCUSS, SYSADMIN, and STEERCOM. I'm not quite | + | |
| - | sure how passwords, if any, will be handled. | + | |
| - | + | ||
| - | * We need to copy the archives from michelob to bud and index them via | + | |
| - | htdig. I'm not sure how htdig and/or apache will handle the compressed files as currently configured. | + | |
| === Spam Subscriptions === | === Spam Subscriptions === | ||
| Line 572: | Line 564: | ||
| === GENERAL MAIL TODO: === | === GENERAL MAIL TODO: === | ||
| - | * We need to get virtual users set up in some way. Craig and I discussed | + | * We need to get virtual users set up in some way. Craig and I discussed this, and two options are postfix maps and a mysql database. We didn't make any decisions. Two particular challenges will be copying existing passwords for POP3/IMAP access and mail filtering (procmail/maildrop/whatever). Once we get users set up, we'll need to migrate their mail spools. |
| - | this, and two options are postfix maps and a mysql database. We didn't | + | * We need to get spamassassin working. We particularly need to take a look at the performance impact of scanning list mail. This should probably be done incoming list mail only. |
| - | make any decisions. Two particular challenges will be copying existing | + | * We need to get some form of webmail up and running. I'm partial to Horde becauses it has a powerful interface and a ton of cool modules. I haven't used the password module, but it might be particularly useful for us. See http://www.horde.org/accounts/screenshots/accounts.png. If we use horde, we'll be using mysql, so that might be the way to go for virtual users. |
| - | passwords for POP3/IMAP access and mail filtering (procmail/maildrop/whatever). Once we get users set up, we'll need to migrate their mail spools. | + | |
| - | + | ||
| - | * We need to get spamassassin working. We particularly need to take a | + | |
| - | look at the performance impact of scanning list mail. This should | + | |
| - | probably be done incoming list mail only. | + | |
| - | + | ||
| - | * We need to get some form of webmail up and running. I'm partial to | + | |
| - | Horde becauses it has a powerful interface and a ton of cool modules. I | + | |
| - | haven't used the password module, but it might be particularly useful | + | |
| - | for us. See http://www.horde.org/accounts/screenshots/accounts.png. If | + | |
| - | we use horde, we'll be using mysql, so that might be the way to go for | + | |
| - | virtual users. | + | |
| That should do it for now - enjoy the rest of the weekend. | That should do it for now - enjoy the rest of the weekend. | ||
build/lists.txt · Last modified: 2018/05/28 03:34 by SLUUG Administration
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
