balug:mail_and_lists
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
balug:mail_and_lists [2017-09-21T10:19:34+0000] – status updates michael_paoli | balug:mail_and_lists [2018-05-22T22:10:41+0000] (current) – michael_paoli | ||
---|---|---|---|
Line 13: | Line 13: | ||
[Migration was fully completed off of DreamHost.com on 2017-09-18] | [Migration was fully completed off of DreamHost.com on 2017-09-18] | ||
High-level of migration strategy off of DreamHost.Com (to be implemented as feasible, but we do need to get off of DreamHost.Com): | High-level of migration strategy off of DreamHost.Com (to be implemented as feasible, but we do need to get off of DreamHost.Com): | ||
- | * create temp.balug.org (done - implemented | + | * (done) (temporarily) |
- | * create test list on temp.balug.org | + | * (done) |
- | * migrate lists - from lowest traffic/ | + | * (done) (initially) |
- | * fully prepare email infrastructure on @balug.org (e.g. for various aliases there) for migration (and test as feasible, etc.) | + | * (done) |
- | * copy/ | + | * (done - all relevant data copied) |
- | * pull the plug on DreamHost.Com (remove DNS delegation from it), move forward to cancel any relevant DreamHost.Com account(s) or services thereof | + | * (done) |
- | * temp.balug.org is intended to be // | + | * (done) |
- | Note also that presently | + | Note also that much of BALUG' |
===== List migration step-by-step ===== | ===== List migration step-by-step ===== | ||
(Work-in-progress, | (Work-in-progress, | ||
- | * temp.balug.org [created] | + | * temp.balug.org [created, moved to, moved from and deprecated, phased out, done] |
- | * temp.balug.org - any DNS records we need to create/add there? - notably not only what we need but implement as soon as feasible to avoid any DNS negative caching TTL issues [checked, done, more than sufficient] | + | * temp.balug.org - any DNS records we need to create/add there? - notably not only what we need but implement as soon as feasible to avoid any DNS negative caching TTL issues [checked, done, more than sufficient |
- | * archives - will want to get raw mbox of archives from DreamHost.Com if feasible, next best get rawest forms we can manage to get of archives | + | * archives - will want to get raw mbox of archives from DreamHost.Com if feasible, next best get rawest forms we can manage to get of archives |
- | * disable any email obfuscation of archives [checked and adjusted as feasible] - that may/will slightly aid quality of archive bits we can get - especially if we're not able to get raw mbox format.\\ | + | * disable any email obfuscation of archives [checked and adjusted as feasible] - that may/will slightly aid quality of archive bits we can get - especially if/ |
checked lists, BALUG-Talk and BALUG-Admin lists:\\ | checked lists, BALUG-Talk and BALUG-Admin lists:\\ | ||
< | < | ||
- | obscure_addresses (privacy): Show member addresses so they' | + | obscure_addresses (privacy): Show member addresses so they' |
Setting this option causes member email addresses to be transformed when they are presented on list web pages (both in text and as links), so they' | Setting this option causes member email addresses to be transformed when they are presented on list web pages (both in text and as links), so they' | ||
</ | </ | ||
changed from Yes to No (BALUG-Announce was already set to No).\\ | changed from Yes to No (BALUG-Announce was already set to No).\\ | ||
- | From walking the admin menus, the above seems the only setting of relevance to unobfuscate email addresses, but since they' | + | From walking the admin menus, the above seems the only setting of relevance to unobfuscate email addresses, but since they' |
- | * for our at migration time target operating system (Debian GNU/Linux 8.8 (jessie) amd64) to work with our desired anti-spam software/ | + | * for our at migration time target operating system (Debian GNU/Linux 8.8 (jessie) amd64) to work with our desired anti-spam software/ |
* So, for clean reinstall of exim4-daemon-heavy, | * So, for clean reinstall of exim4-daemon-heavy, | ||
< | < | ||
Line 50: | Line 50: | ||
</ | </ | ||
* We also notice it's //not// listening at all on IPv6 (not even \[::1\]:25, \[:: | * We also notice it's //not// listening at all on IPv6 (not even \[::1\]:25, \[:: | ||
- | * One or our existing key present design/ | + | * One or our existing key present design/ |
* Turns out our former MTA wasn't fully cleaned out - was unlinked but still running, SIGTERMed it, started exim, and rechecked our listening IPs for our ports:\\ | * Turns out our former MTA wasn't fully cleaned out - was unlinked but still running, SIGTERMed it, started exim, and rechecked our listening IPs for our ports:\\ | ||
< | < | ||
Line 62: | Line 62: | ||
* also installed: sa-exim (probably needed, and dependencies thereof) | * also installed: sa-exim (probably needed, and dependencies thereof) | ||
* also installed: clamav and libclamunrar7 (and dependencies thereof) - probably not required, but if the resource consumption isn't too great, very possibly a "good to have" - notably help us from being a (mostly immune) carrier. | * also installed: clamav and libclamunrar7 (and dependencies thereof) - probably not required, but if the resource consumption isn't too great, very possibly a "good to have" - notably help us from being a (mostly immune) carrier. | ||
- | * also added additional " | + | * also added additional " |
< | < | ||
238.194.144.198.in-addr.arpa. 10800 IN CNAME | 238.194.144.198.in-addr.arpa. 10800 IN CNAME | ||
Line 68: | Line 68: | ||
</ | </ | ||
* after much more configuration of eximconfig, exim4, and some adding of packages and further configuration also including clamav and spamassassin and spfd and related, got to semi-working configuration ... | * after much more configuration of eximconfig, exim4, and some adding of packages and further configuration also including clamav and spamassassin and spfd and related, got to semi-working configuration ... | ||
- | * also, clamav quite the (virtual) memory resource hog ... increased the host (virtual machine) RAM up from 512 MiB to 1 GiB - that seems sufficient for at least present - but clamav still consumes over 50% of RAM much of the time. At 512 MIB of system RAM, the OOM killer was kicking in. | + | * also, clamav quite the (virtual) memory resource hog ... increased the host (virtual machine) RAM up from 512 MiB to 1 GiB - that seems sufficient for at least present - but clamav still consumes over 50% of RAM much of the time. At 512 MiB of system RAM, the OOM killer was kicking in (later made some additional adjustments to prevent Apache RAM consumption from ballooning too big and triggering OOM killer). |
- | * send some initial test email messages to the domain - seemed to go relatively okay - at least after the RAM increase noted above - still much to (better) configure/ | + | * sent some initial test email messages to the domain - seemed to go relatively okay - at least after the RAM increase noted above - still (was) much to (better) configure/ |
* added AAAA record for our MX - not really any great reason not to at this point: | * added AAAA record for our MX - not really any great reason not to at this point: | ||
< | < | ||
mx.temp.balug.org. | mx.temp.balug.org. | ||
</ | </ | ||
- | * did set up BALUG-Test list, fixed some various issues, it seems at least (partially) working, but there are still various issues to correct and address, more to configure, etc. - but was at least able to successfully subscribe a non-local email address to it ... but still much more to do (and test). | + | * did set up BALUG-Test list, fixed some various issues, it seems it was at least (partially) working, but there are(were) |
- | * should probably create a bullet list of stuff to test on (test) list and confirm it's all working (sort' | + | * should probably create a bullet list of stuff to test on (test) list and confirm it's all working (sort' |
email/List stuff to (re)test - results (Y - good, N - failed, ? - to be tested) | email/List stuff to (re)test - results (Y - good, N - failed, ? - to be tested) | ||
Line 116: | Line 116: | ||
o Y (untested) mailman admin commands should work via email (need more complete list) | o Y (untested) mailman admin commands should work via email (need more complete list) | ||
o Y should accept legitimate email for legitimate @balug.org addresses | o Y should accept legitimate email for legitimate @balug.org addresses | ||
- | o Y default sending domain of host: @balug.org (for non-list email, list email updated to user @lists.balug.org) | + | o Y default sending domain of host: @balug.org (for non-list email, list email updated to use @lists.balug.org) |
- | o [Y/partial - need to phase out ~all soft-fail] | + | o Y add/ |
o Y lists should use URLs starting with: https:// | o Y lists should use URLs starting with: https:// | ||
o Y lists should use email addresses ending with: @lists.balug.org | o Y lists should use email addresses ending with: @lists.balug.org | ||
Line 132: | Line 132: | ||
o Y http[s]:// | o Y http[s]:// | ||
o Y http[s]:// | o Y http[s]:// | ||
- | o N (future) | + | o Y http[s]:// |
- | o ? (future ~2017-11-30) decommission temp.balug.org domain | + | o ? http:// |
+ | o Y decommission temp.balug.org domain | ||
+ | o Y add IPv6 to {www., | ||
+ | o [partially done] review/ | ||
+ | o [future] Mailman - review/ | ||
+ | o Y add DNSSEC for balug.org. | ||
</ | </ | ||
Line 162: | Line 167: | ||
Fix for: [[http:// | Fix for: [[http:// | ||
- | Added rewrite rules to remap old URLs to new - this will be useful most notably once we're hosting lists.balug.org away from DreamHost.com: | + | Added rewrite rules to remap old URLs to new - this will be useful most notably once we're hosting lists.balug.org away from DreamHost.com |
< | < | ||
RewriteRule " | RewriteRule " | ||
Line 179: | Line 184: | ||
</ | </ | ||
</ | </ | ||
+ | (and that's had lists.balug.org enabled, and temp.balug.org has been phased out) | ||
added mailman-loop alias - this may not be optimal handling, but the alias needs to exist (needs to always be deliverable), | added mailman-loop alias - this may not be optimal handling, but the alias needs to exist (needs to always be deliverable), | ||
< | < | ||
mailman-loop: | mailman-loop: | ||
</ | </ |
balug/mail_and_lists.1505989174.txt.bz2 · Last modified: 2017-09-21T10:19:34+0000 by michael_paoli