That actually tells me the worst answer, thanks. This system has
been running for a LONG time and has been through many os upgrade
cycles. I think it's a victim of genetic drift. Other things act
a bit weird at times also. I continually try to rectify these things,
but I think it may be beyond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher T Joffe wrote:
> Failure to exec script. WANTED gid 48, GOT gid 99. (Reconfigure to take
> 99?)
>
> when trying to access it from the browser. Are there any runtime
> configuration changes to make, or must I get the sources and recompile
I've been out of the *nix world for long enough for some of this
stuff to be fuzzy. Sorry. The apache group is 48, but apache (httpd)
and most of the /var/www tree seem to root/root. I hesitate to
run around changing stuff, as this is a running server.
Jon Carnes wrote:
You might want to check a
You might want to check around for a different rpm (or install from
source). Of course you could always reset Apache to run using a GroupID
of 48 (instead of the 99 it is currently using).
Good Luck.
On Wed, 2003-03-12 at 22:30, Christopher T Joffe wrote:
> Sorry for the obvious from a mailman-n
You can always send Barry a note and volunteer to do some documentation.
Other than that, you can add an entry into the FAQ
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
It's self-service so feel free to add an entry or two!
Thanks for volunteering to help - Jon Carnes
On Wed, 2003-03-1
Sorry for the obvious from a mailman-newbie, but I can't
seem to find the correct answer elsewhere. I'm running
Mandrake9.0 and have just installed Mailman from the
included RPMs. I now get:
Mailman CGI error!!!
This entry is being stored in your syslog:
Failure to exec script. WANTED gid 48, GOT
On Wed, 2003-03-12 at 17:41, Bob Sully wrote:
>
> Jon: I did install from source but paid special attention to the smrsh
> directories. Everything is where it should be. Still didn't work.
>
> -- Bob --
Oh well... I guess it was a good thing (tm) that I moved over to Postfix
last year. :-)
As an experiment, grab one of the messages that you got locally but not
via yahoo, and send it to your yahoo account from the server.
You could also clone the list (using ~mailman/bin/config_list) and
simply add a few test users, then test using that.
Good Luck!
On Wed, 2003-03-12 at 12:08, Jod
On Wed, Mar 12, 2003 at 04:21:45PM -0500, Jon Carnes wrote:
> On Wed, 2003-03-12 at 15:48, Mark McEahern wrote:
> > 3. Is there any reason to display this site-wide list in the list of lists
> > displayed by listinfo?
> No. This should always be a private list.
I was wondering about this - th
I have been searching for days for an answer to this, so please forgive me if
you know of some document or web site that addresses this problem. Point me
to that document and I will be glad to read for myself.
I am currently running RH 7.3 with Qmail 1.03+patches-19 with Mailman
2.0.13-1.
I h
Jon: I did install from source but paid special attention to the smrsh
directories. Everything is where it should be. Still didn't work.
-- Bob --
On 12 Mar 2003, Jon Carnes wrote:
> Most of these (I think) were from folks upgrading their Sendmail due to
> the recent vulnerability and subs
I just spent a considerable amount of time getting Mailman to work with
Courier as the MTA.
I'm sure there's probably more than one way to do it, but here's an outline
of what I did. I offer this here in the hopes that anyone trying to do this
in the future won't have to pursue all the deadends I
[Jon Carnes [mailto:[EMAIL PROTECTED]
> This list should only be for you and other system/list admins that are
> in charge of the whole Mailman install. It is for Mailman errors and
> list warnings.
[snip other helpful background information about the site-wide list]
Jon, thanks for the reply.
On the overview pages, listinfo and admin, the email address was appearing as
[EMAIL PROTECTED] instead of [EMAIL PROTECTED] In both the
Defaults.py and mm_cfg.py files, the DEFAULT_EMAIL_HOST was correct as
DEFAULT_EMAIL_HOST='domain.com'
By removing the DEFAULT_EMAIL_HOST='domain.com' from
On Wed, 2003-03-12 at 15:48, Mark McEahern wrote:
> The INSTALL file recommends creating a site-wide list called mailman, but
> aside from saying this is where password reminders appear to come from, it
> seems short on details as to the purpose of this list. I apologize if these
> questions are a
The INSTALL file recommends creating a site-wide list called mailman, but
aside from saying this is where password reminders appear to come from, it
seems short on details as to the purpose of this list. I apologize if these
questions are answered elsewhere. I've at least cursorily scanned the
ob
No, it was not a typo, just an ellipsis :-)
I am very careful when it comes to changing things. I read
that changes are not to go into Defaults, and I made the
changes in mm_cfg.py. I just omitted the gory details :-)
(that what I put in mm_cfg.py in the end becomes Defaults).
But you are rig
Thank you, Todd, for acting so irate ;-) about my bypassing
the warnings and setting up sendmail "in the raw" as opposed
to going to it via SMTPDirect.
I guess I have demonstrated to be truly a newbie but...
there is hope for me. I decided to look into the sendmail.cf
file, and it turns out that
> But, from the point of view of mailman, once the correct
> Delivery_Module was specified in Defaults.py, it works fast
> as a whistle.
That was a typo, right? There is ample warning in the documentation
(and, IIRC, in the Defaults.py file itself) that changes go in
mm_cfg.py, not in Defaults.
So, I got this:
#telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mafalda.math.indiana.edu ESMTP Sendmail bla bla bla versions
Well, let me play with the fun parts :-) Best, elena
--
Mailman-Users
Are you running your MTA in a chroot?
Is there a group called mailnull in /etc/group?
You can check on the error manually by su-ing as a user with the GroupID
"mailnull" and then running:
/usr/local/mailman/mail/mailman owner
If it says:
"mailowner got no listname."
then Mailman is working p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Elena Fraboschi wrote:
> ugh, you must be a developer... :-)
Not even close. (I don't even play one on TV. :)
> My problem was that mailman received all fine, queued all fine,
> and never delivered a thing. Obviously my sendmail was running.
> When
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Elena Fraboschi wrote:
> Thank you, Todd, for acting so irate ;-) about my bypassing the warnings
> and setting up sendmail "in the raw" as opposed to going to it via
> SMTPDirect.
I guess that's like 'tough love.' ;-)
> I guess I have demonstrated
Most of these (I think) were from folks upgrading their Sendmail due to
the recent vulnerability and subsequent update release. I would hope
that folks using package management (like rpm or apt-get) would have no
problems if they used the updated packages for their distributions.
If folks are ins
ugh, you must be a developer... :-) (just in case, here comes
another one ;-))
My problem was that mailman received all fine, queued all fine,
and never delivered a thing. Obviously my sendmail was running.
When I changed DELIVERY_MODULE from SMTPDirect to Sendmail,
it worked just fine.
Now, I
Please see the FAQ
In a nutshell it will tell you that Mailman's CGI's are setup with a
security feature during the install. The feature only allows someone
with the proper GroupID to run the CGI's.
The scripts that are run via your MTA (mail-server) should be set to
only run for someone with a
Greetings, Mailman users.
I would like to tweak the welcome message of one of the lists on our list
server in such a way that it would not invite the users to post to the list.
I do not see an interface for this in the Mailman web interface, and I don't
want indiscriminately to edit files in such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David A. Mason wrote:
> I would like to tweak the welcome message of one of the lists on our list
> server in such a way that it would not invite the users to post to the list.
> I do not see an interface for this in the Mailman web interface, and I do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joseph Smith wrote:
> - Transcript of session follows -
> Group mismatch error. Mailman expected the mail
> wrapper script to be executed as group "mailman", but
> the system's mail server executed the mail script as
> group "mailnull". Try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Elena Fraboschi wrote:
> and there I learned that the makers of mailman, in an over-protective
> move, commented out "Sendmail" as the Delivery_Module, and put
> "SMTPDirect" instead. All that is fine, except that there should
> be a warning about thi
Jon:
You've seen the flurry of these over the past couple of weeks. I firmly
believe that the problem lies with some mod to smrsh in the latest
versions of Sendmail. I had previously been running 2.0.13 with
Sendmail 8.12.3 without a problem...after upgrading to 8.12.7 I got the
same messag
Hello again,
I corrected and followed the information from an earlier post to solve the
smrsh issue and now I get the following msg back when sending to the list.
I can read what it ways but for someone new this is a headache. I need to
understand more then just receive and answer.
- Tr
I wrote:
> I've seen this mentioned on a number of Ensim lists, it just won't
> work with anything over 755. When I get far enough it matters, I'll dig
> into it more.
Jon said:
Interesting, because I remember using UID and GID's that were in the 1000+
range for the chroot (but that was six mont
Well, I reasoned that mailman was working just fine, save for
the fact that it was not delivering any messages. I went to
Mailman/Defaults.py
and there I learned that the makers of mailman, in an over-protective
move, commented out "Sendmail" as the Delivery_Module, and put
"SMTPDirect" instead.
Well, you could disable the Smrsh control from within Sendmail - or - you
could look up on your system where Smrsh's link directory should be located.
You may have to create the directory and then create your links to the
Mailman executables.
Good Luck - Jon Carnes
BTW: there are some recent expo
- Original Message -
From: "Paul H Byerly" <[EMAIL PROTECTED]>
> Thee:
> >I don't think this is exactly true. Your chroot environment has a
> >limited amount of UserID's and GroupID's that are available to be used
> >inside (and really outside as well) the Chroot.
>
> I've seen this
I believe I have pinpointed the root of the problem, which was,
in a nutshell, that mailman received the messages from subscribed
members, and queued them, but failed to deliver to the list
because, it would appear from the bounces log, it does not
recognize the addresses at some point. Here is th
"Jonas Meurer" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello,
> I asked already two times, but no answer, now the third try ;)
> I have mailman set up from debian/testing (2.0.13), and spamassassin
> also. Now I would like to configure mailman to filter every incoming
> mail t
Martin,
I would submit this as a bug and include the messages that you think
should be caught, especially "user unknown".
This URL tells you how to submit a bug report:
http://mailman.sourceforge.net/bugs.html
--
John DeCarlo, My Views Are My Own
---
> "John" == John DeCarlo <[EMAIL PROTECTED]>
> on Wed, 12 Mar 2003 09:55:53 -0500 writes:
John> Martin,
John> Have you read through these messages?
yes, (of course)!
John> Some of the ones I get include "out of office"
John> messages or other auto-generated messages
Martin,
Have you read through these messages? Some of the ones I get include
"out of office" messages or other auto-generated messages that aren't
really "bounce" messages. I.e., they don't indicate a problem
delivering the mail.
My theory is that when I have time I will try and filter out t
Hello all,
I'm trying to customize the Mailman interface pages, mainly translating
the text. I've done so with the files located in /mailman/lists/listname
(listinfo.html, options.html, etc.) However, in the listinfo page other
text is placed by including . I cannot seem to
find out where the text
We have upgraded to 2.1.1 about 2 weeks ago.
We have about 20 mailing lists, totalling about 70-100 messages
a day -- although mainly from one 1-3 lists.
I've been getting half a dozen "Uncaught bounce notification"
messages a day, and had been ignoring them more or less --
hoping mailman would so
43 matches
Mail list logo
