It works just fine if I log in as root and use newlist, but if I try
to create a new list via the web admin interface, two things happen.
First, I get an error, whose text I do not have in front of me (I
know, I know, first rule of error reporting, report the exact error,
but you probably won't
12288 2012-03-28 19:07 aliases.db
-rw-rw 1 root list 5830 2012-03-28 19:07 virtual-mailman
-rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db
On Thu, 29 Mar 2012 01:52:45 +0900, you wrote:
On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote:
user unknown
12:28:27 -0700, you wrote:
Mark Sapiro wrote:
Steve Matzura wrote:
and
second, the aliases file is not updated, so if a subscriber tries to
send a message to the list, they receive an auto-reply telling them
user unknown in virtual mailbox table. My question is, why doesn't
the web interface
On Wed, 28 Mar 2012 12:46:48 -0700, you wrote:
You need to 'chmod 660 /var/lib/mailman/data/virtual-mailman.db' It
must be writable by the 'list group or it can't be updated by the web
server running the create CGI.
I did that and am still receiving the unknown virtual host error when
On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote:
On Wed, 28 Mar 2012, Steve Matzura wrote:
It would *never* be in my best interest not to give you all the info.
The problem is, I don't know exactly what info you need or want, and
what would be superfluous. Let's see if I can provide more
patronus.theglobalvoice.info, which may have something to do with why
the Web create doesn't work, but 'newlist' does.
On Wed, 28 Mar 2012 18:19:29 -0500, you wrote:
On Mar 28, 2012, at 4:40 PM, Steve Matzura wrote:
On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote:
How about the error message you get when
On Wed, 28 Mar 2012 19:37:42 -0700, you wrote:
Did I forget to check or report on anything?
Well, you never answered the questions I asked at
http://mail.python.org/pipermail/mailman-users/2012-March/073113.html
so we don't know what was wrong there, but presumably, you don't care
as you
I am a site admin for a system built on Debian version 7 (Wheezy). The
current available mailman package distribution version is 2.1.15 but I
want to use 2.1.18-1, which means, unless I miss my guess, it's got to
be built from source. If this isn't so, I'd greatly appreciate knowing
where and how
Thanks to Steve Turnbull's help and some intelligent manual-reading, I
have successfully built and installed version 2.1.18-1 on a Debian 7
(Wheezy) system. check_perms reports no problems, `version' reports
the right version number, I'm ready for the next step, which is to
move an entire
(which
is already underway) and then switch the DNS records after the new
environment has been thoroughly tested. I'll check the wiki's you
mentioned and report on progress when done.
On Thu, 05 Jun 2014 08:09:52 -0700, you wrote:
On 06/05/2014 04:27 AM, Steve Matzura wrote:
I'm ready for the next
On Thu, 05 Jun 2014 12:13:30 -0500, you wrote:
On Thu, 2014-06-05 at 12:43 -0400, Steve Matzura wrote:
This reply mechanism is driving me a little weird--the reply function
sends the messages to their individual authors, not the list. I hope
I'm not breeching etiquette by redirecting my reply
I'm setting up a new Mailman implementation on a new machine that's a
virtual copy of a running production machine. I'm expecting problems
because I'm trying to use the same domain name in two places, and I
absolutely understand that's not going to work, but the bottom line
is, the faster I get
Well, on a new implementation, I'm getting the same thing in 2.18-1.
What'd you do to fix it on your end?
On Tue, 1 Jul 2014 17:33:19 +0200, you wrote:
Mark Sapiro m...@msapiro.net wrote:
The above message indicates the traceback was written to some 'error' log,
just not the one you're
I just brought up a new 2.1.18-1 installation and am geting the we're
sorry but we encountered a bug page on theadmin interface.
/var/log/mail/error is 0-length. Should I turn stealth mode off to get
more info possibly?
--
Mailman-Users mailing
as it should be. All good now, and of
course, many thanks. It's always the little things.
On Sat, 10 Jan 2015 10:04:43 -0800, you wrote:
On 01/10/2015 07:01 AM, Steve Matzura wrote:
I just brought up a new 2.1.18-1 installation and am geting the we're
sorry but we encountered a bug page on theadmin
I have charge of a very mixed system--current OS (Fedora 20--OK 21's
out but I just haven't upgraded yet), current (or nearly so) Mailman
(2.1.18-1), Postfix 2.10 with a configuration file sfrom something a
lot older which I've run through the upgrade-configuration procedure,
and old Dovecot
On Wed, 13 May 2015 23:19:45 +0900, Steve Turnbull wrote:
Dovecot and Mailman should be mostly independent of each other, while
both depend crucially on Postfix. The first thing to do is to find
the log files for each application, and test that mail works for all
combinations of inside and
Mark:
On Thu, 02 Jul 2015 17:07:21 -0700, you wrote:
The smpt log is now clean. Newest message is ten minutes older than
the current date and time. I suspect running check_perms fixed
everything.
Does a 'subscribe' email get delivered to Mailman? That could have been
a permissions issue,
On Thu, 02 Jul 2015 16:46:00 -0700, you wrote:
On 07/02/2015 09:23 AM, Steve Matzura wrote:
On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
Mailman is sending a notice to the 'mailman' list and it's
undeliverable. That doesn't look like a 'bounce' log message. It looks
more like 'post' log
I have a new Mailman implementation connected to Postfix which is in
turn connected to Dovecot. These two components are working correctly,
as I have mailboxes set up with them and have created a test Mailman
mailing list and received confirmation that it has in fact been
created. Now I'm
If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
following:
Bug in Mailman version 2.1.18-1
Bug in Mailman version 2.1.18-1
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been
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 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
On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
On 07/02/2015 07:56 AM, Steve Matzura wrote:
I have a new Mailman implementation connected to Postfix which is in
turn connected to Dovecot. These two components are working correctly,
as I have mailboxes set up with them and have created a test
On Thu, 02 Jul 2015 08:23:23 -0700, you wrote:
Mailman is sending a notice to the 'mailman' list and it's
undeliverable. That doesn't look like a 'bounce' log message. It looks
more like 'post' log. What's in the 'smtp-failure' log?
Jul 02 16:12:13 2015 (1308)
On Thu, 02 Jul 2015 08:24:12 -0700, you wrote:
On 07/02/2015 07:56 AM, Steve Matzura wrote:
If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the
following:
Bug in Mailman version 2.1.18-1
Bug in Mailman version 2.1.18-1
We're sorry, we hit a bug!
Please inform
What's the best section of the standard documentation or the wiki to
consult in order to learn how to correctly use withlist?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman
On Thu, 02 Jul 2015 16:39:36 -0700, you wrote:
After check_perms fixed all problems, I re-ran it and got this:
Warning: Private archive directory is other-executable (o+x).
This could allow other users on your system to read private
archives.
If you're on a shared
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
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
On Sat, 04 Jul 2015 09:11:54 -0700, Mark Sapiro m...@msapiro.net
wrote:
In your case, the RedHat package has modified Mailman's crontab.in to be
a system crontab and already installed it in /etc/cron.d/.
It did, but the file is virtually empty (only three or four comment
lines warning not to
I'm now thinking none of the overnight cron jobs are running. I set
digest mode to a couple lists, posted to them, then modified the
digest job's run time from 12:00 every day to a minute or two from
current time, waited ten minutes, and got nothing in response. Then I
did the same for the monthly
With some excellent help, all my Mailman problems up to today have
been solved. and my mailing lists have been behaving normally. Since
it's a new month, mailpasswd ran earlier this morning. The email of
the cron job reported a permissions error on one of the config.pck
files for one of the lists.
On Sat, 08 Aug 2015 18:47:29 -0700, Mark Sapiro m...@msapiro.net
wrote:
On 08/08/2015 06:22 PM, Steve Matzura wrote:
On Sat, 08 Aug 2015 12:39:19 -0700, Mark asked:
What does
groups mailman
report? It should be 'mailman : mailman'. If so, and the crons are
getting permission problems
On Sun, 09 Aug 2015 08:44:56 -0700, Mark wrote:
On 08/09/2015 08:25 AM, Steve Matzura wrote:
No errors on the overnights, Things appear to be working correctly.
I'm trying to run the password reminder job now, /var/log/messages
shows it started twenty-three minutes ago, I haven't received
Every night, I get the following error at the bottom of a mail message
to my mailman list telling me that checkdbs, digest and disabled
failed:
IOError: [Errno 13] Permission denied:
'/usr/local/mailman/locks/mailman.lock.{my-FQDN}.{some-number}.0'
This also happened on the one and only password
On Sat, 08 Aug 2015 09:19:27 -0700, Mark Sapiro m...@msapiro.net
wrote:
On 08/08/2015 08:12 AM, Steve Matzura wrote:
Every night, I get the following error at the bottom of a mail message
to my mailman list telling me that checkdbs, digest and disabled
failed:
IOError: [Errno 13] Permission
On Sat, 08 Aug 2015 12:39:19 -0700, Mark asked:
What does
groups mailman
report? It should be 'mailman : mailman'. If so, and the crons are
getting permission problems, check if SELinux is enabled and if so, try
disabling it.
It's mailman : mailman postfix, and SELinux is disabled according to
After solving my cron confusions, I get these messages daily:
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/checkdbs
...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0'
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/disabled
On Thu, 09 Jul 2015 08:00:38 -0700, Mark wrote:
On 07/09/2015 06:48 AM, Steve Matzura wrote:
After solving my cron confusions, I get these messages daily:
Subject: Cron mailman@{mynode} /usr/lib/mailman/cron/checkdbs
...
IOError: [Errno 13] Permission denied:
'/var/lock/mailman
On Mon, 06 Jul 2015 19:17:23 -0700, you wrote:
RedHat's /etc/init.d/mailman copies the cron/crontab.in to
/etc/cron.d/mailman. So if you start Mailman via 'service mailman
start', the crontab in crontab.in will be installed.
At least that's the way I *think* it works. Ask RedHat or look at the
On Tue, 07 Jul 2015 07:11:40 -0400, Mark wrote:
RedHat's /etc/init.d/mailman copies the cron/crontab.in to
/etc/cron.d/mailman. So if you start Mailman via 'service mailman
start', the crontab in crontab.in will be installed.
It's done in the Mailman service definition, which means the crontab
I get Mailman job logs that look like this:
Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python
-S /usr/local/mailman/cron/checkdbs^M)
Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python
-S /usr/local/mailman/cron/disabled^M)
Sep 1 12:00:01 {my_node} atronus
On Tue, 1 Sep 2015 10:24:24 -0700, you wrote:
>On 09/01/2015 10:00 AM, Steve Matzura wrote:
>> I get Mailman job logs that look like this:
>>
>> Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python
>> -S /usr/local/mailman/cron/checkdbs^M)
>>
Well now I've seen everything. Why would Mailman send a return message
to a subscriber to a mailing list that says their message couldn't be
posted to the mailing list because "message may contain
administrivia"?
--
Mailman-Users mailing list
Guilty as charged. On several counts. Oy!
On Thu, 01 Oct 2015 08:56:57 +0200, you wrote:
>In a message of Thu, 01 Oct 2015 01:35:02 -0400, Steve Matzura writes:
>>Well now I've seen everything. Why would Mailman send a return message
>>to a subscriber to a mailing list that say
49 matches
Mail list logo
