Re: [Mailman-Users] HTML messages not passed, content filtering settings ignored

2009-11-27 Thread Christian Stalberg
   In looking at the output I may see the problem. I have been running
   Mailman and upgraded versions and moved Mailman from one server to
   another for years. Look at this output from my list wherein I see
   values like 'False' where the legals values are supposed to be either
   yes or no:

   # When you scrub attachments, they are stored in archive area and links
   # are made in the message so that the member can access via web
   browser.
   # If you want the attachments totally disappear, you can use content
   # filter options.
   #
   # legal values are:
   #0 = No
   #1 = Yes
   scrub_nondigest = False

   could this be the problem where an upgrade was not done properly where
   I have an old, out of date 'config' file whose values are unrecognized
   or ?


   On 11/25/2009 10:26 Mark Sapiro m...@[1]msapiro.net wrote ..

If filter_content is no, Mailman should not be doing any content
filtering or HTML to plain text conversion.
I can make a guess. Perhaps the message is multipart/alternative with
text/plain and text/html alternative parts and you are viewing the
received message  with an MUA (mail client) set to show you the plain
text, or perhaps you are seeing a 'scrubbed' message in a digest or
the archive or even the message from the list if Non-digest options -
scrub_nondigest is set to Yes.
If you really want to look 'under the hood' look at the output from
 bin/config_list -o - LISTNAME
or
 bin/dumpdb lists/LISTNAME/config.pck | grep filter_content
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Checking for Heartbeat

2009-11-27 Thread Rex Goode
First, thanks to Mark Sapiro for the great reply on Multiple List 
Pending Requests.


I host with jumpline.com, which generally does a good job with me. The 
Mailman installation is pretty good, but for some reason I can't track 
down, Mailman keeps going belly-up. Jumpline customer support doesn't 
know why. I have to stop it to turn off whatever qrunners are running 
and restart it. I don't mind doing that now and then. It doesn't happen 
that often.


Here's the problem. My users don't think to tell me when they haven't 
had any mail from the list for awhile. I just go along thinking all is 
well until someone tells me, Hey, Rex. We haven't had any email from 
the list for a week. I restart and old email mostly catches up.


I have an administrative page for all of my web sites and the various 
things they do. I am on that page several times each day. I would like 
to generate some message when Mailman isn't working, something I would 
see there. A lot of the command line scripts seem to work even if 
Mailman is not running. What can I use to check to see if it is alive?


Rex
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] HTML messages not passed, content filtering settings ignored

2009-11-27 Thread Mark Sapiro
Christian Stalberg wrote:

   In looking at the output I may see the problem. I have been running
   Mailman and upgraded versions and moved Mailman from one server to
   another for years. Look at this output from my list wherein I see
   values like 'False' where the legals values are supposed to be either
   yes or no:

   # When you scrub attachments, they are stored in archive area and links
   # are made in the message so that the member can access via web
   browser.
   # If you want the attachments totally disappear, you can use content
   # filter options.
   #
   # legal values are:
   #0 = No
   #1 = Yes
   scrub_nondigest = False

   could this be the problem where an upgrade was not done properly where
   I have an old, out of date 'config' file whose values are unrecognized
   or ?


This is not a problem. config_list says legal values are 0 and 1 for
False/True settings to accommodate older Pythons that didn't define
False and True, but False and True for these is actually fine.

Besides, if your issue were due to scrub_nondigest being True, you
could tell as the HTML wouldn't just disappear, it would be replaced
by a stanza saying an HTML attachment has been scrubbed with a link
to wher the HTML was stored.

Do the messages from the list contain a

X-Content-Filtered-By: Mailman/MimeDel 2.1.x

header? If not, Mailman's content filtering hasn't changed them.

What is the exact MIME structure of an HTML message to the list and of
the message received from the list?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Checking for Heartbeat

2009-11-27 Thread Mark Sapiro
Rex Goode wrote:

I host with jumpline.com, which generally does a good job with me. The 
Mailman installation is pretty good, but for some reason I can't track 
down, Mailman keeps going belly-up. Jumpline customer support doesn't 
know why. I have to stop it to turn off whatever qrunners are running 
and restart it. I don't mind doing that now and then. It doesn't happen 
that often.


I'm guessing you have a VPS or similar hosting arrangement where you
actually have access to the Maulman installation.

When Mailman 'dies' are one or more qrunners missing? If so, look in
Mailman's error and qrunner logs to try to find out why. If not, maybe
there is a lock issue of some sort. See the FAQ at
http://wiki.list.org/x/A4E9.


Here's the problem. My users don't think to tell me when they haven't 
had any mail from the list for awhile. I just go along thinking all is 
well until someone tells me, Hey, Rex. We haven't had any email from 
the list for a week. I restart and old email mostly catches up.

I have an administrative page for all of my web sites and the various 
things they do. I am on that page several times each day. I would like 
to generate some message when Mailman isn't working, something I would 
see there. A lot of the command line scripts seem to work even if 
Mailman is not running. What can I use to check to see if it is alive?


I suggest you look at the mmdsr script. I don't know what you have
available in your installation, but if you have a Mailman contrib/
directory, you'll find it there. If not, go to
http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head%3A/contrib/
where you can download mmdsr and README.mmdsr.

mmdsr is designed to be run by cron at 23:59 daily and mail you a
report summarizing Mailman's logs, queues, etc. This is very helpful
in spotting problems.

If mailmanctl and some qrunners are running when mailman is not
working, and you want to check right now, you can look at

find /path/to/qfiles -print -name \*.pck

to see if any queues are backed up, and you can do

ps -u mailman --no-headers | wc -l

which should return '9' in a standard installation (mailmanctl and 8
qrunners).

You could incorporate one of these or something similar in your
administrative page.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] rejecting messages *to* non-members

2009-11-27 Thread LuKreme
On 26-Nov-2009, at 16:26, Shop at Just Brits wrote:
 Another prob I ran into early on was folks just blindly
 using the Reply-All function therefore if I had made
 the orginal post I would get TWO replies.  I nipped THAT
 in the bud VERY quickly.


I'd much rather get two replies than what some lists do which is not send me a 
copy if they see I 'already got one' in the Cc or To headers. I REALLY hate 
that.

This list, for example.

-- 
Over 3,500 gay marriages and, what, no hellfire? I was promise
hellfire. And riots. What gives? -- Mark Morford

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] rejecting messages *to* non-members

2009-11-27 Thread Mark Sapiro
LuKreme wrote:

I'd much rather get two replies than what some lists do which is not send me a 
copy if they see I 'already got one' in the Cc or To headers. I REALLY hate 
that.

This list, for example.


It's a user option (at least on Mailman lists) -

Avoid duplicate copies of messages?

When you are listed explicitly in the To: or Cc: headers of a list
message, you can opt to not receive another copy from the mailing
list. Select Yes to avoid receiving copies from the mailing list;
select No to receive copies. 

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] rejecting messages *to* non-members

2009-11-27 Thread Mark Sapiro
Ed wrote:
 Another prob I ran into early on was folks just blindly
 using the Reply-All function therefore if I had made
 the orginal post I would get TWO replies. 


In some cases at least, this is a good thing. E.g.,

- The poster is not a list member and would not otherwise see the reply.

- The poster is a digest member and wouldn't otherwise see the reply for
some time.

The typical list member is not able to know whether a poster is a
regular or digest member or even a list member at all.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Checking for Heartbeat

2009-11-27 Thread LuKreme
On 27-Nov-2009, at 08:56, Mark Sapiro wrote:
 http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head%3A/contrib/
 where you can download mmdsr and README.mmdsr

Hmm.. the readme and internal docs where not that useful.

# Arguments for your mktemp command to specify directory and/or create file.
# For example, HPUX mktemp requires -c; FreeBSD doesn't accept -p dir.
 ###
TMPDIR=-p /tmp

OK, since freeBSD doesn't like the -p option, what should this be? setting it 
to just /tmp generates an error. Setting it to -d /tmp/mmdsr also generates 
the same basic errors. Yes, the script is running as root.

# mmdsr
mktemp: mkstemp failed on /tmp: File exists
mktemp: mkstemp failed on /tmp: File exists
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory
/usr/local/bin/mmdsr: cannot create : No such file or directory

The script then sits there for far long than a minute seemingly doing nothing. 
(I know it has a sleep 60 in it because it's intended to run at 23:59, but that 
does seem an odd way to go to me). Still, wanting to see the output it 
generated I ran it, but it seems to just stall.


-- 
Conservatives want live babies so they can raise them to be 
dead soldiers ~Carlin

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] rejecting messages *to* non-members

2009-11-27 Thread LuKreme
On 27-Nov-2009, at 11:37, Mark Sapiro wrote:
 LuKreme wrote:
 
 I'd much rather get two replies than what some lists do which is not send me 
 a copy if they see I 'already got one' in the Cc or To headers. I REALLY 
 hate that.
 
 This list, for example.
 
 
 It's a user option (at least on Mailman lists) -
 
 Avoid duplicate copies of messages?

Yep, but I've set it at least twice for this list and I still find it getting 
set back. But that said, some Mailman lists have a setting that lets you set 
the Reply-To: on your posts so that when people reply, it goes ONLY to the 
list, as $DEITY intended.


-- 
Love seekest only self to please, To bind another to its delight
Joys in another's loss of ease And builds a hell in Heaven's
despite!

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Checking for Heartbeat

2009-11-27 Thread Mark Sapiro
LuKreme wrote:

On 27-Nov-2009, at 08:56, Mark Sapiro wrote:
 http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head%3A/contrib/
 where you can download mmdsr and README.mmdsr

Hmm.. the readme and internal docs where not that useful.

# Arguments for your mktemp command to specify directory and/or create file.
# For example, HPUX mktemp requires -c; FreeBSD doesn't accept -p dir.
 ###
TMPDIR=-p /tmp

OK, since freeBSD doesn't like the -p option, what should this be? setting it 
to just /tmp generates an error. Setting it to -d /tmp/mmdsr also generates 
the same basic errors. Yes, the script is running as root.


The equivalent option in FreeBSD is -t /tmp, at least according to
http://www.gsp.com/cgi-bin/man.cgi?section=1topic=mktemp.


(I know it has a sleep 60 in it because it's intended to run at 23:59, but 
that does seem an odd way to go to me).


It runs at 23:59 and sleeps for a minute after getting the current date
to use in filtering the logs. It sleeps to get the last minute in the
logs, and it gets the date before midnite so it doesn't have to figure
out the correct date for 'yesterday'. Granted, it could just run at
midnight and use the -d yesterday option for the date command, but
a) I didn't write that part; b) I don't know if -d yesterday or
equivalent is universally available in implementations of date, and c)
the impact of a change at this point on existing users makes such a
change problematic.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] rejecting messages *to* non-members

2009-11-27 Thread Mark Sapiro
LuKreme wrote:

Yep, but I've set it at least twice for this list and I still find it getting 
set back.


I don't know why that would happen.


But that said, some Mailman lists have a setting that lets you set the 
Reply-To: on your posts so that when people reply, it goes ONLY to the list, 
as $DEITY intended.


Our recommendations are to not strip the poster's Reply-To: if any and
to not add any other Reply-To: addresses. This list is set that way so
you can add your own Reply-To: and it will be passed through.

List owners can set these as they see fit, but I don't see why anyone
would choose to strip the poster's Reply-To: if they weren't adding
one of their own.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Checking for Heartbeat

2009-11-27 Thread Mark Sapiro
LuKreme wrote:

Hmm.. the readme and internal docs where not that useful.

# Arguments for your mktemp command to specify directory and/or create file.
# For example, HPUX mktemp requires -c; FreeBSD doesn't accept -p dir.
 ###
TMPDIR=-p /tmp


I have changed the comment to

# Arguments for your mktemp command to specify directory and/or create
file.
# For example, HPUX mktemp requires -c -d dir; FreeBSD requires -t
dir.

Hopefully, that will be more clear. I would prefer not to have this
setting at all, but there needs to be something because without the
'-c' option HPUX won't create the file, and none of the others accept
'-c'.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org