Hello
Upon a clean installation of Mailman 3.2.0a1, Without any additional configuration, nor custom footers, When accepting message from the list on Gmail client for example, The footer shows twice, also in the message source I see two identical footer parts, accept for the message barrier: --===============4363779446011731395== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Info mailing list -- info@mailman.sysbind.biz To unsubscribe send an email to info-leave@mailman.sysbind.biz
--===============4363779446011731395== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Info mailing list -- info@mailman.sysbind.biz To unsubscribe send an email to info-leave@mailman.sysbind.biz
--===============4363779446011731395==--
On 07/22/2018 06:23 AM, Asaf Ohayon wrote:
Hello
Upon a clean installation of Mailman 3.2.0a1, Without any additional configuration, nor custom footers, When accepting message from the list on Gmail client for example, The footer shows twice,
This may be <https://gitlab.com/mailman/mailman/issues/450> which was fixed by <https://gitlab.com/mailman/mailman/merge_requests/363> at commit 811b8ca.
There was no 3.2.0a1 release per se, so I don't know exactly what you installed and whether it contains that commit. Note that the current release on PyPI is 3.2.0 and contains this fix.
So the question is what did you install, and does it contain
- Message decoration has been removed from the posting pipeline and added to bulk delivery to avoid duplicate decoration of personalized and VERPed messages. (Closes #450)
in mailman/docs/NEWS.rst.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks Mark
What I was using is the rolling version of the docker deployment, which yielded 3.2.0a1.
However now I'm using 3.1.1, which I considered to be the last stable release, is it not? The double footer issue happens also here
How can I try 3.2.0 using the docker deployment ?
On 07/23/2018 12:27 AM, Asaf Ohayon wrote:
How can I try 3.2.0 using the docker deployment ?
You may have to wait for @maxking to deploy a new container.
Possibly the rolling releases
$ docker pull quay.io/maxking/mailman-web:rolling $ docker pull quay.io/maxking/mailman-core:rolling
will fix this issue. Also see <https://github.com/maxking/docker-mailman/blob/master/README.md> for how to determine the commit hashes of the Docker components.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Asaf Ohayon wrote:
Thanks Mark
What I was using is the rolling version of the docker deployment, which yielded 3.2.0a1.
However now I'm using 3.1.1, which I considered to be the last stable release, is it not? The double footer issue happens also here
How can I try 3.2.0 using the docker deployment ?
You cannot right now, but I hope I can fix that soon.
The images need to be updated to the stable 3.2 release and the rolling releases haven't gone out for about two weeks due to failing build scripts.
thanks, Abhilash
participants (3)
-
Abhilash Raj -
Asaf Ohayon -
Mark Sapiro