Okay, upon reflection I think I figured out what happened here. I
replied to an existing thread but deleted the entirety of the message
thread and changed the subject entirely. I thought that started a new
message thread but perhaps the list software registers that as a reply
to an existing
On 11/17/20 8:30 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
>
> > And several years ago (in the 2.1.5 timeframe), RedHat modified their
> > Mailman package to be FHS compliant for the specific purpose of avoiding
> > SELinux security violations.
>
> Is it possible FHS
On 11/17/2020 8:30 PM, Stephen J. Turnbull wrote:
Are we FHS conformant? If not, why would it be a bad idea to become
FHS-conformant (aaside from the effort required)?
I don't think so and that would probably break non linux systems (e.g.
xBSD). Might be OK to add FHS as an option to the
Mark Sapiro writes:
> And several years ago (in the 2.1.5 timeframe), RedHat modified their
> Mailman package to be FHS compliant for the specific purpose of avoiding
> SELinux security violations.
Is it possible FHS non-conformance is related to the OP's situation?
Are we FHS conformant?
On 16 Nov 2020, at 2:17, Stephen J. Turnbull wrote:
Bill Cole writes:
On 15 Nov 2020, at 22:18, Stephen J. Turnbull wrote:
I don't see why access to archives would cause a security issue,
Thanks for the reply!
Also FWIW, I'm explaining here why I don't think this is a Mailman
issue. If
On 11/16/20 10:36 PM, Michael Reeder LCPC -- Hygeia Regular wrote:
> Hello All,
Please don't hijack threads. When you want to post a new topic, don't do
it by replying to another post, just compose a ney message to the list.
> I am running a listserv which was recently moved to GNU Mailman
Hello All,
I am running a listserv which was recently moved to GNU Mailman 2.1.23
on a Dream Host server (I assume UNIX). I am encountering the following
problem:
Replies to Digest messages (both MIME and plain text) sometimes have
line breaks stripped from them. We have seen this so far
