On 07/03/2015 06:52 AM, Steve Matzura wrote:
Oh boy. Not good. Here's what I'm after finding: I want to find
something I can use to look at a list's properties in order to
possibly determine what is wrong with my setup that's generating the
smtp-failure messages and generally inhibiting or
On 07/04/2015 08:23 AM, Steve Matzura wrote:
Because that's the only one I knew of. Blame Red Hat for this one. :-)
The RedHat/Centos package is even more complex. See the FAQ at
http://wiki.list.org/x/8486953.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San
This should have gone to the list instead of where it went.
On Sat, 04 Jul 2015 07:45:07 -0700, Mark Shapiro m...@msapiro.net
wrote:
These occur because you have installed a crontab which has been
formatted as a system crontab and intended to be installed in a place
like /etc/cron.d/mailman as a
On Sat, 04 Jul 2015 07:22:43 -0700, Mark wrote:
Mailman has two main configuration paths, $prefix for immutable code,
etc. and $var_prefix for mutable data. By default, $var_prefix =
$prefix, but in your case, you or the packager whose package you
installed configured mailman with
On 4 Jul 2015 at 8:22, Mark Sapiro wrote:
On 07/03/2015 09:03 AM, Bernie Cosell wrote:
I have a spam filter set to 'hold':
X-Spam-Level:\s*\*\*\*
I would use
^X-Spam-Level:\s*\*\*\*
but yours should match any with 3 or more stars, in particular the one
above.
Is it possible
On 07/03/2015 03:59 PM, Steve Matzura wrote:
Interesting: My $prefix is /usr/lib/mailman. However, there is a
/var/lib/mailman as that's where archives is. It's owned and grouped
properly, and it does have the 1-bit set in the 'other' portion of its
permissions mask. I can definitely fix
On Sat, 04 Jul 2015 08:54:44 -0700, Mark Sapiro m...@msapiro.net
wrote:
The RedHat/Centos package is even more complex. See the FAQ at
http://wiki.list.org/x/8486953.
Thanks. Noted and saved for future reference.
--
Mailman-Users mailing list
On Sat, 04 Jul 2015 09:11:54 -0700, you wrote:
On 07/04/2015 08:27 AM, Steve Matzura wrote:
On Sat, 04 Jul 2015 07:45:07 -0700, Mark Sapiro m...@msapiro.net
wrote:
These occur because you have installed a crontab which has been
formatted as a system crontab and intended to be installed in
On 07/03/2015 09:03 AM, Bernie Cosell wrote:
I've looked through the FAQs and the archives and my spam filters *OUGHT*
to work. But it seems they're not and I don't know why.
I have a spam filter set to 'hold':
X-Spam-Level:\s*\*\*\*
And a message with these headers just got blasted
On 07/04/2015 08:27 AM, Steve Matzura wrote:
On Sat, 04 Jul 2015 07:45:07 -0700, Mark Sapiro m...@msapiro.net
wrote:
These occur because you have installed a crontab which has been
formatted as a system crontab and intended to be installed in a place
like /etc/cron.d/mailman as a user
On 07/04/2015 06:36 AM, Steve Matzura wrote:
I guess things are getting better with my new mailman implementation,
as I received nine messages overnight I've never gotten before. four
are Errno 13 permission denied, five only contain one line:
/bin/sh: mailman: command not found
The
On 07/04/2015 06:45 PM, JB via Mailman-Users wrote:
Is there an ETA on when a migration path from MM 2.x to 3.x will be ready or
is there even a plan in place to develop such an animal?
The short answer is yes, there is a plan and it is one of the things we
plan to include with Mailman 3.1,
On 07/04/2015 10:19 AM, Steve Matzura wrote:
Right. And it was wrong of RH not to tell me that up front, or if it
does, it didn't jump up and tell me. Sometimes there's just so much to
read and digest, and much of it has to be done after the fact. I'll
comb their docs and if it's not
Is there an ETA on when a migration path from MM 2.x to 3.x will be ready or is
there even a plan in place to develop such an animal?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
On 07/04/2015 10:32 AM, Bernie Cosell wrote:
I've looked through the headers and it appears that my service provider
only runs spam assassin *AFTER* the message goes through mailman -- the
spam assassin headers come *after* all the mailman headers. I don't
know if I can fix/change that
I guess things are getting better with my new mailman implementation,
as I received nine messages overnight I've never gotten before. four
are Errno 13 permission denied, five only contain one line:
/bin/sh: mailman: command not found
The subject fields of these five all begin with the same text
I've looked through the FAQs and the archives and my spam filters *OUGHT*
to work. But it seems they're not and I don't know why.
I have a spam filter set to 'hold':
X-Spam-Level:\s*\*\*\*
And a message with these headers just got blasted out to the list:
X-Spam-Checker-Version: SpamAssassin
On Fri, 03 Jul 2015 06:50:58 -0700, you wrote:
$prefix/archives and the private/ and public/ sub-directories thereof
are created on installation, and if Mailman is running there must be a
'mailman' site list and thus $prefix/archives/private/mailman/ and
$prefix/archives/private/mailman.mbox/
On Fri, 03 Jul 2015 06:38:49 -0700, you wrote:
If you mean what can you do interactively after invoking withlist on a
list and have a '' prompt, see
https://wiki.python.org/moin/BeginnersGuide#Learning_Python for the
Python part. For the Mailman specific stuff, You need to understand what
list
19 matches
Mail list logo
