Skip to content
Snippets Groups Projects
Commit 39272597 authored by Mr. Evoltech's avatar Mr. Evoltech
Browse files

Updating to reflect the current patch level

parent efb95a6d
No related branches found
No related tags found
No related merge requests found
......@@ -27,5 +27,13 @@ we still need to disable listing of latest and active lists, since these operati
TODO; need to file a bug for this and press the issue upstream
06_2685_owner_address_set_to_special_address.patch
----------------------------
--------------------------------------------------
do_edit_list in wwsympa.fcgi needs to be patched to make sure that special list addresses can not be ued as list owner addresses. See https://labs.riseup.net/code/issues/2685 for more info
07_var-lock-subsys_missing_prevents_startup.patch
-------------------------------------------------
This fixes a bug in the init script for Debian Wheezy systems
08_2821_max_list_dispatch.patch
-------------------------------
Adds a feature to set hard limits on the size of lists that can send mail. This is controlled by max_list_dispatch and max_list_dispatch_from_subscriber. See https://labs.riseup.net/code/issues/2821 for more info.
This branch contains the patched sympa-6.1.20 source code along with the riseup patches.
This branch contains the patched sympa-6.1.22 source code along with the riseup patches.
The source code is located in sympa-6.1.20-src/. It is not compiled, which means that
to install or upgrade sympa, the INSTALL and UPGRADE files in the sympa-6.1.20-src/ directory
The source code is located in sympa-6.1.22-src/. It is not compiled, which means that
to install or upgrade sympa, the INSTALL and UPGRADE files in the sympa-6.1.22-src/ directory
can be followed.
The patches are located in 6.1.20/patches/. These patches have already been applied to the
sympa source code in sympa-6.1.20-src/.
The patches are located in 6.1.22/patches/. These patches have already been applied to the
sympa source code in sympa-6.1.22-src/.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment