[Mailman-Users] Removal of Line Breaks in Replies to Digest Messages

2020-11-17 Thread Michael Reeder LCPC -- Hygeia Regular 
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 thread.  I organize my email client by date and not by 
thread so I would not see this.  Apologizes to all if this is the case.


I'm told by my list subscriber the following:

a. He thinks that the Digest message formatting is messed-up as it 
originally comes from the list, but he is not sure (reply messages might 
be messing up the formatting).


b. He is using iPhone and Outlook for Apple email clients.

c. He is also experiencing quote marks (") and apostrophes (') being 
turned into question marks (?) throughout the text of digest messages.


Is this mess a function of his Apple email clients, or a problem that 
rests with the Mailman list management software?


Thanks,
Michael

*Michael Reeder, LCPC
*
*Hygeia Counseling Services : Baltimore / Mt. Washington Village location*
*410-205-2419 / michael(at)hygeiacounseling.com*
*http://www.hygeiacounseling.com - main website.
*

On 11/17/2020 9:21 PM, Michael Reeder LCPC -- Hygeia Regular wrote:
Mark -- I very much appreciate your answer below.  I'll work on the 
(nearly impossible) task of training users to respond to digests 
properly and also explain to people that the Mailman list mgmt 
software can't control formatting screw-ups by email client programs.


I agree with not hijacking threads...  What hijack?  Looks to me like 
I started a new topic.  Right??


Thanks,
Michael Reeder
mich...@hygeiacounseling.com


On 11/17/2020 2:32 PM, Mark Sapiro wrote:

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 2.1.23
on a Dream Host server (I assume UNIX).  I am encountering the 
following

problem:


Please see .



Replies to Digest messages (both MIME and plain text) sometimes have
line breaks stripped from them.  We have seen this so far with both a
version of Microsoft Outlook and an email client program for an Android
phone.  As far as I know, the digest messages themselves originally all
look fine when sent from the listserv.

Anyone know if there is anything I can do about this?


Use a different mail client that doesn't do this. Otherwse, there's
nothing you can do to control what users mail clients do.


Bonus Question:  I do not have command prompt access -- only admin 
panel
access (listserv software is implemented through Dream Host). 
Anything I

can do from the admin panel?  What would I ask Dream Host to change?


There is no change to the digests themselves that would mitigate this
issue without breaking the way the original digests render.

Further, people shouldn't be replying to a digest. For a MIME format
digest, they should open the individual message and reply to that. For
the plain digest, they should just copy/paste relevant context from the
digest into a new post to the list. Of course, training list members to
do that is probably not possible ...



--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: CPU %-usage surge associated with list archives

2020-11-17 Thread Mark Sapiro 
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 non-conformance is related to the OP's situation?


It's possible, but all we know is the OP moved lists from one server to
another - see
.

We have no idea how Mailman is installed on the new server.


> Are we FHS conformant?  If not, why would it be a bad idea to become
> FHS-conformant (aaside from the effort required)?


For Mailman 2.1, it requires RedHat's patch. See


For Mailman 3 putting

layout: fhs

in the [mailman] section of mailman.cfg should create an FHS compliant
layout.


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: CPU %-usage surge associated with list archives

2020-11-17 Thread Carl Zwanzig 

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 configure script if anyone 
wanted to go that route.


Later,

z!
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: CPU %-usage surge associated with list archives

2020-11-17 Thread Stephen J. Turnbull 
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?  If not, why would it be a bad idea to become
FHS-conformant (aaside from the effort required)?
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: CPU %-usage surge associated with list archives

2020-11-17 Thread Bill Cole 

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 there is a vulnerability in our distribution, and the
SELinux policy is pointing it out, we (I think I speak for all the
core devs here ;-) want to fix it.


Right. I agree that it is not a problem with anything Mailman is doing 
that is in any way dangerous or even that it is something that the base 
distribution should attempt to deal with.



FWIW:

1. SELinux doesn't know about specific security issues, it assumes 
that

nothing is safe unless explicitly allowed.


Yes, I was already aware that that is the "theoretically correct"
policy, and had guessed that SELinux follows it.

2. On RHEL7 and its derivatives, the default SELinux policy includes 
a
module for mailman's executable and data files which *in my 
experience*

just works without modification when mailman is installed from an
official RPM.


Aha.  Now *that* is *very* useful information!  So I assume that would
also apply to sufficiently recent CentOS, and most likely to Fedora.


Yes.


And it's something to look up on Debian and Ubuntu.


It seems that https://github.com/SELinuxProject/refpolicy is the 
upstream basis for the EL-family default policy and it appears to have 
build switches for other lineages. I believe that the EL family is the 
only one that has SELinux enabled and enforcing by default.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Removal of Line Breaks in Replies to Digest Messages

2020-11-17 Thread Mark Sapiro 
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 2.1.23
> on a Dream Host server (I assume UNIX).  I am encountering the following
> problem:


Please see .


> Replies to Digest messages (both MIME and plain text) sometimes have
> line breaks stripped from them.  We have seen this so far with both a
> version of Microsoft Outlook and an email client program for an Android
> phone.  As far as I know, the digest messages themselves originally all
> look fine when sent from the listserv.
> 
> Anyone know if there is anything I can do about this?


Use a different mail client that doesn't do this. Otherwse, there's
nothing you can do to control what users mail clients do.


> Bonus Question:  I do not have command prompt access -- only admin panel
> access (listserv software is implemented through Dream Host). Anything I
> can do from the admin panel?  What would I ask Dream Host to change?


There is no change to the digests themselves that would mitigate this
issue without breaking the way the original digests render.

Further, people shouldn't be replying to a digest. For a MIME format
digest, they should open the individual message and reply to that. For
the plain digest, they should just copy/paste relevant context from the
digest into a new post to the list. Of course, training list members to
do that is probably not possible ...

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Removal of Line Breaks in Replies to Digest Messages

2020-11-17 Thread Michael Reeder LCPC -- Hygeia Regular 

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 with both a 
version of Microsoft Outlook and an email client program for an Android 
phone.  As far as I know, the digest messages themselves originally all 
look fine when sent from the listserv.


Anyone know if there is anything I can do about this?

Bonus Question:  I do not have command prompt access -- only admin panel 
access (listserv software is implemented through Dream Host). Anything I 
can do from the admin panel?  What would I ask Dream Host to change?


Thanks,
Michael

*Michael Reeder, LCPC
*
*Hygeia Counseling Services : Baltimore / Mt. Washington Village location*
*410-205-2419 / michael(at)hygeiacounseling.com*
*http://www.hygeiacounseling.com - main website.
*


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/