3,254
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + − {{Note box| It does not appear that this contrib works properly for virtual domains on SME 7.3+. This contrib functions as specified for the primary domain only. Additional work is required for this contrib to function properly for virtual domains.+ − + − Currently work on progress to port it on SME8+ − + − Line 13:
Line 13: − + + + + + + + + − * for sme9+ − yum install smeserver-mailman --enablerepo=stephdl+ − signal-event post-upgrade;signal-event reboot+ + + − You should now see a Mailman section under the Configuration section of the server-manager. Please see Known issues below to set up your mailman session. Keep in mind that the mailman administrator password is not the same as the SME Server one, [[Mailman#Error:_You_are_not_authorized_to_create_new_mailing_lists|Read the section below to see how find your password]].+ − === Configuration ===+ − Actually the administrator of SME Server isn't allowed to create Lists (even from the server-manager), here is how obtain the mailman administrator password. see [[bugzilla:7836]]+ − − version concerned − [root@sme8dev64 ~]# rpm -qa smeserver-mailman mailman − mailman-2.1.9-20.el5.sme − smeserver-mailman-1.3.0-42.el5.sme Line 51:
Line 55: − + − + Line 63:
Line 67: − + Line 106:
Line 110: − + − + − + Line 132:
Line 136: − + Line 139:
Line 143: − + Line 154:
Line 158: − + − + Line 163:
Line 167: + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 169:
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+ + + + + + + + + + +
→Import lists from ezmlm
{{Languages|Mailman}}
==Mailman==
==Mailman==
=== Maintainer ===
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br />
=== Version ===
}}
{{ #smeversion: smeserver-mailman }}
===Description===
===Description===
=== Installation ===
=== Installation ===
* for sme8
<tabs container><tab name="For SME 10">
yum install smeserver-mailman --enablerepo=smecontribs
</tab><tab name="For SME 9 and SME 8">
* for sme8, sme9
yum install smeserver-mailman --enablerepo=smecontribs
yum install smeserver-mailman --enablerepo=smecontribs
signal-event mailman-update
or if you want to restart your server
signal-event post-upgrade;signal-event reboot
signal-event post-upgrade;signal-event reboot
</tab>
</tabs>
You should now see a Mailman section under the Configuration section of the server-manager. Please see Known issues below to set up your mailman session. Keep in mind that the mailman administrator password is not the same as the SME Server one, [[Mailman#Error:_You_are_not_authorized_to_create_new_mailing_lists|Read the section below to see how find your password]].
=== 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 ====
===== Error: You are not authorized to create new mailing lists=====
===== Error: You are not authorized to create new mailing lists=====
The administrator of SME Server isn't allowed to create Lists (even from the server-manager), this is how obtain the mailman administrator password. see [[bugzilla:7836]]
{{Tip box|The mailman password is different of the admin password of SME Server, therefore to know the mailman Password you can issue the following command in a root terminal}}
{{Tip box|The mailman password is different of the admin password of SME Server, therefore to know the mailman Password you can issue the following command in a root terminal}}
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 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.
{{Note box|msg=Always use http://domain.name/mailman to create your list, where domain.name is the exact domain you want to be used after the "@". Failing to do so, will lead to denial to relay error. As an example do not go to http://hostname.domain.name/mailman to create a mailing list for mailinglist@domain.name but to http://domain.name/mailman. see [[Bugzilla:5976]]
{{Note box|msg=Always use http://domain.name/mailman to create your list, where domain.name is the exact domain you want to be used after the "@". Failing to do so, will lead to denial to relay error. As an example do not go to http://hostname.domain.name/mailman to create a mailing list for mailinglist@domain.name but to http://domain.name/mailman. see [[Bugzilla:5976]]
{{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...
and mailman is going to replace the string with the name the person used when he/she subscribed.
and mailman is going to replace the string with the name the person used when he/she subscribed.
</li></ol>
</li></ol>
===Import lists from ezmlm===
Get the script ezmlm2mbox from http://www.arctic.org/~dean/scripts/ezmlm2mbox
wget http://www.arctic.org/~dean/scripts/ezmlm2mbox -O
Get subscribers:
ezmlm-list /home/e-smith/files/ezmlm/lists/mylist > mylist.subscribers
Get denied subscribers:
ezmlm-list /home/e-smith/files/ezmlm/lists/mylist deny > mylist.deny
Convert the ezmlm list to an mbox-file:
./ezmlm2mbox /home/e-smith/files/ezmlm/lists/mylist > mylist.mbox
Backup the ezmlm list, just in case ...
tar -czf mylist.tgz /home/e-smith/files/ezmlm/lists/mylist
Then using the server-manager:
# Remove the ezmlm list, via the ezmlm web panel
# Create the new Mailman list, via the Mailman web panel
# Add subscribers to the new list, using the file you made in step 1. I prefer to do this in silence, without letting the subscribers know.
# Check the file mylist.deny from step 2, and - if needed - adjust the settings of your new list accordingly.
Import the mbox to Mailman
cp mylist.mbox /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox
/opt/mailman/bin/arch --wipe mylist
Check and fix ownerships and access rights
/opt/mailman/bin/check_perms -f
from : https://forums.contribs.org/index.php/topic,53230.0.html
=== For more information ===
=== For more information ===
=== Current Issues ===
=== Current Issues ===
=== Bugs ===
Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla]
and select the smeserver-mailman component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-mailman|title=this link}}.
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=smeserver-mailman|noresultsmessage="No open bugs found."}}
= Changelog =
Only released versions in smecontrib are listed here.
{{#smechangelog:smeserver-mailman}}
----
----
[[Category:Contrib]]
[[Category:Contrib]]
[[Category:Mail]]
[[Category:Mail]]
[[Category:Mail:Mailinglists]]