Re: [Mailman-Users] Unable to post to list - Command died with status 2

2016-09-12 Thread Mark Sapiro
On 09/12/2016 06:45 AM, Jewel Brueggeman-Makda wrote: > Good Morning, > I am in the process of setting up a replacement mailman server and so far > things are going well. I did have 2.1.22 and upgraded to 2.1.23. The point > where I am stuck is when I try to post to the mailman list I receive the

Re: [Mailman-Users] What does "Possible malformed path attack" actually mean?

2016-09-12 Thread Mark Sapiro
On 09/12/2016 12:02 PM, Sebastian Hagedorn wrote: > > So far I haven't been able to understand what is going on. I can't find > any questionable requests in Apache's access log from the GSA. Any ideas > what could be causing this? It is caused by an attempt to get a mailman URL that contains spa

[Mailman-Users] What does "Possible malformed path attack" actually mean?

2016-09-12 Thread Sebastian Hagedorn
Hi, today I updated our installation of Mailman to version 2.1.23. Prior to the upgrade there were "Possible malformed path attack" log entries, but without any further details I never bothered to look for their cause. After the update I can now see where they are coming from, and it's our own

[Mailman-Users] Unable to post to list - Command died with status 2

2016-09-12 Thread Jewel Brueggeman-Makda
Good Morning, I am in the process of setting up a replacement mailman server and so far things are going well. I did have 2.1.22 and upgraded to 2.1.23. The point where I am stuck is when I try to post to the mailman list I receive the following error below. When I setup mailman I used the foll