3,250
edits
Changes
Jump to navigation
Jump to search
Line 27:
Line 27: + + + + + + + Line 48:
Line 55: − + Line 60:
Line 67: − + Line 103:
Line 110: − + − + − + Line 129:
Line 136: − + Line 136:
Line 143: − + Line 151:
Line 158: − + − + Line 169:
Line 176: − + Line 193:
Line 200: − * Check submitted bugs in the bug tracker under the contrib component "smeserver-mailman"+ − * Current mailman release is 2.1.9 − * [[Bugzilla:2411]]: /usr/lib/mailman/aliases and /var/lib/mailman are not currently backed up Line 203:
Line 208: − +
→Import lists from ezmlm
=== Configuration ===
=== Configuration ===
==== Configure access ====
By default only listing public lists is enabled from outside the LAN. Admin is reserved for LAN access, and also Archive browsing.
Option setting is also attached to the public listing access, so external users can modify their preferences.
To modify those setting just go to server-manager and modify according to your needs.
==== Creating lists ====
==== Creating lists ====
If your SMEServer has multiple domains configured, do not prepend www. before the virtual domain.
If your SMEServer has multiple domains configured, do not prepend www. before the virtual domain.
For example: go to http:// virtualdomain.name/mailman to create lists for that domain name.
For example: go to http://virtualdomain.name/mailman to create lists for that domain name.
Keep in mind that '''no list can have the same name as an ibay, group or an user''' so choose the name carefully.
Keep in mind that '''no list can have the same name as an ibay, group or an user''' so choose the name carefully.
{{Tip box|Further more You have to define the concerned domain in the server-manager's domain panel. You can select whether this domain is resolved locally, passed to the corporate DNS servers, or resolved by the Internet DNS servers, otherwise you will have the message: '''Error: Unknown virtual host: xxxxxx'''}}
{{Tip box|Further more You have to define the concerned domain in the server-manager's domain panel. You can select whether this domain is resolved locally, passed to the corporate DNS servers, or resolved by the Internet DNS servers, otherwise you will have the message: '''Error: Unknown virtual host: xxxxxx'''}}
===== "www" instead of "apache =====
===== "www" instead of "apache" =====
But if you are not running the contribs compiled version, Mailman's management interface shows up with a CGI error message. It complains about group mismatch error between "www" and "apache". Login as root and apply the following workaround, which was suggested in [[bugzilla:6425]]:
But if you are not running the contribs compiled version, Mailman's management interface shows up with a CGI error message. It complains about group mismatch error between "www" and "apache". Login as root and apply the following workaround, which was suggested in [[bugzilla:6425]]:
|-
|-
| /usr/lib/mailman/bin/list_owners
| /usr/lib/mailman/bin/list_owners
| will list all owners of mailling lists or will list all mailling list
| will list all owners of mailling lists or will list all mailling lists
|}
|}
Running the script with --help will display the options available
Running the script with --help will display the options available.
==== Transferring Lists ====
==== Transferring Lists ====
You can transfer lists from another server and keep everything in tact. It's an easy process but the Mailman FAQ and info seems to be sparse and complicated. This simplifies everything.
You can transfer lists from another server and keep everything intact. It's an easy process but the Mailman FAQ and info seems to be sparse and complicated. This simplifies everything.
OLD SERVER
OLD SERVER
Extract/untar/unzip the tar/zip file.
Extract/untar/unzip the tar/zip file.
tar -xvzf /var/lib/mailman.tar.gz
tar -xvzf /var/lib/mailman.tar.gz
The lists are transferred but the SME SERVER doesn't know about them. Let the server know about the list:
The lists are transferred but the SME SERVER doesn't know about them. Let the server know about the lists:
signal-event mailman-addlist <listname>
signal-event mailman-addlist <listname>
=== Personalization ===
=== Personalization ===
{{Note box|Be warned that personalization is going to stress your server a lot as every mail is sent individually, not in batches as mailman usually do, so test this option before using in a production server}}
{{Note box|Be warned that personalization is going to stress your server a lot as every mail is sent individually, not in batches as mailman usually do, so test this option before using in a production server.}}
If you want to enable personalization in mailman (make every mail sent with the name of the recipient in the to: field as example or add the name of the user on the text) you do this:
If you want to enable personalization in mailman (make every mail sent with the name of the recipient in the to: field as example or add the name of the user on the text) you do this:
/etc/e-smith/templates-custom/usr/lib/mailman/Mailman/mm_cfg.py/30hostname
/etc/e-smith/templates-custom/usr/lib/mailman/Mailman/mm_cfg.py/30hostname
</li><li>
</li><li>
To refelct your changes we need to regenerate the file using the following commands:
To reflect your changes we need to regenerate the file using the following commands:
expand-template /usr/lib/mailman/Mailman/mm_cfg.py
expand-template /usr/lib/mailman/Mailman/mm_cfg.py
signal-event reboot
signal-event smeserver-mailman-update
</li><li>
</li><li>
After the server comes back up again enter your mailing list admin and go to non-digest and in "Should Mailman personalize each non-digest delivery?" choose either yes or full personalization. Test both to see wich one do you like more...
After the server comes back up again enter your mailing list admin and go to non-digest and in "Should Mailman personalize each non-digest delivery?" choose either yes or full personalization. Test both to see wich one do you like more...
ezmlm-list /home/e-smith/files/ezmlm/lists/mylist deny > mylist.deny
ezmlm-list /home/e-smith/files/ezmlm/lists/mylist deny > mylist.deny
Convert the ezmlm list to an mbox-file:
Convert the ezmlm list to an mbox-file:
./ezmlm2mbox /home/e-smith/files/ezmlm/lists/mylist > mylist.mbox
./ezmlm2mbox /home/e-smith/files/ezmlm/lists/mylist > mylist.mbox
Backup the ezmlm list, just in case ...
Backup the ezmlm list, just in case ...
tar -czf mylist.tgz /home/e-smith/files/ezmlm/lists/mylist
tar -czf mylist.tgz /home/e-smith/files/ezmlm/lists/mylist
=== Current Issues ===
=== Current Issues ===
=== Bugs ===
=== Bugs ===
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]
= Changelog =
= Changelog =
Only released version in smecontrib are listed here.
Only released versions in smecontrib are listed here.
{{#smechangelog:smeserver-mailman}}
{{#smechangelog:smeserver-mailman}}