Re: [Mailman-Users] Old question, oft repeated
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 saving. I'll probably have to try and back up as much as I can, scrub it and start over. Thanks for the help, it saves me from doing much more floundering. Todd wrote: -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 it? Mandrake+Postfix+Mailman I don't know a lot about mandrake, but I happen to have a mandrake 9.0 install (VMware is great for testing, BTW). I installed the apache, mailman, and postfix rpms. I ran mmsitepass and then created a test list. Viewing the mailman listinfo page I got no errors. It does appear that a stock mandrake install works. Looking at the apache config, apache is set to run as user apache, which is uid 76 in /etc/passwd. That's odd because it's neither 48 nor 99 like in your error messages. One thing I don't know much about with mandrake is the security levels. Is it possible that the security level setting plays some role in this? I only have my test box set to the standard security level. As many on the list could tell you, the combo of apache, postfix, and mailman works very well together. The worst case scenario for you would be compiling mailman from source, as Jon pointed out already. But seeing as my default, mandrake install works well without any tweaking, it doesn't seem like the mandrake rpms are fundamentally broken. It's more likely that just a few tweaks are needed. Perhaps the mandrake lists have some useful clues in their archives? (The mailman-users archives might even have something helpful, but I'm guessing you might have already checked them. :) HTH - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe. -- Albert Einstein (1879-1955) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+cBF7uv+09NZUB1oRAsLRAKDowsJpGGVuWUumKyxsXxFiXhveEQCfS+dX 9KVDYYNqEXHvRjmHuNn4zFI= =Imn8 -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/chrisj%40joffecybernetics.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Old question, oft repeated
-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 it? > > Mandrake+Postfix+Mailman I don't know a lot about mandrake, but I happen to have a mandrake 9.0 install (VMware is great for testing, BTW). I installed the apache, mailman, and postfix rpms. I ran mmsitepass and then created a test list. Viewing the mailman listinfo page I got no errors. It does appear that a stock mandrake install works. Looking at the apache config, apache is set to run as user apache, which is uid 76 in /etc/passwd. That's odd because it's neither 48 nor 99 like in your error messages. One thing I don't know much about with mandrake is the security levels. Is it possible that the security level setting plays some role in this? I only have my test box set to the standard security level. As many on the list could tell you, the combo of apache, postfix, and mailman works very well together. The worst case scenario for you would be compiling mailman from source, as Jon pointed out already. But seeing as my default, mandrake install works well without any tweaking, it doesn't seem like the mandrake rpms are fundamentally broken. It's more likely that just a few tweaks are needed. Perhaps the mandrake lists have some useful clues in their archives? (The mailman-users archives might even have something helpful, but I'm guessing you might have already checked them. :) HTH - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe. -- Albert Einstein (1879-1955) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+cBF7uv+09NZUB1oRAsLRAKDowsJpGGVuWUumKyxsXxFiXhveEQCfS+dX 9KVDYYNqEXHvRjmHuNn4zFI= =Imn8 -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Old question, oft repeated
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 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-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 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 it? Mandrake+Postfix+Mailman Thanks -- Christopher T Joffe Joffe Cybernetics, Inc www.webgentools.com atl.unfranchise.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Old question, oft repeated
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-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 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 it? > > Mandrake+Postfix+Mailman > > Thanks > -- > Christopher T Joffe > Joffe Cybernetics, Inc > www.webgentools.com > atl.unfranchise.com > > > -- > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] sitewide list
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-12 at 17:12, Mark McEahern wrote: > [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. It seems to me this stuff should be in the > INSTALL file. Or in some documentation. > > Did I miss it? If it's not written down anywhere, what can I do to help > make that happen? > > Thanks, > > // mark > > - > -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Old question, oft repeated
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 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 it? Mandrake+Postfix+Mailman Thanks -- Christopher T Joffe Joffe Cybernetics, Inc www.webgentools.com atl.unfranchise.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newbe Headaches
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. :-) Did anyone see any bugs filed for this already? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman+Qmail+external subscribers
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, Jodie wrote: > 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 have one mailing list that is experiencing problems mailing out to CERTAIN > addresses on the membership list. When it sees this problem, it disables the > user. I have not confirmed whether this is the only list with this problem. > However, none of the other lists are complaining. > > Example: > > I am subscribed to the list using my email address [EMAIL PROTECTED] > (shreve.net being the default domain for the mail server hosting mailman). I > am also subscribed to the list with a yahoo address [EMAIL PROTECTED] > When I send a test message to the list, I get the test message at > [EMAIL PROTECTED] I never get the test message at the yahoo account. Many > of the other members who have non shreve.net addresses get disabled and the > admins get notifications that the emails bounced and these accounts were > disabled. Now, my yahoo account (which never received the test message) does > NOT get disabled. So, it seems that no external (non shreve.net) addresses > are receiving posts, but not all are bouncing (hence not all get disabled). > > The mail server is working properly as far as normal sending and receiving > email operations go...and it is listening on 127.0.0.1. > > I would be interested in looking at the actual bounce messages from the > MAILER-DAEMON. However, I don't know how I can get to these messages, if it > is even possible. I am hoping that these messages might shed some light on > the problem. > > If anyone has any suggestions, please let me know. Or, if I have provided too > little information, I will be glad to provide anything necessary to help > solve this issue. > > Thanks! > -- > Jodie E Crouch III > ShreveNet, Inc. > Asst. Network Administrator > > -- > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: sitewide list
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 - the default for Mailman in general seems to be public lists; is there a way for the install process to make the "mailman" list *default* to being a private list? When I added a "mailman" list in the course of upgrading Mailman, I forgot to check this, and realized a month or so later that it had been created as a public list. -- "Since when is skepticism un-American? Dissent's not treason but they talk like it's the same..." (Sleater-Kinney - "Combat Rock") -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman+Qmail+external subscribers
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 have one mailing list that is experiencing problems mailing out to CERTAIN addresses on the membership list. When it sees this problem, it disables the user. I have not confirmed whether this is the only list with this problem. However, none of the other lists are complaining. Example: I am subscribed to the list using my email address [EMAIL PROTECTED] (shreve.net being the default domain for the mail server hosting mailman). I am also subscribed to the list with a yahoo address [EMAIL PROTECTED] When I send a test message to the list, I get the test message at [EMAIL PROTECTED] I never get the test message at the yahoo account. Many of the other members who have non shreve.net addresses get disabled and the admins get notifications that the emails bounced and these accounts were disabled. Now, my yahoo account (which never received the test message) does NOT get disabled. So, it seems that no external (non shreve.net) addresses are receiving posts, but not all are bouncing (hence not all get disabled). The mail server is working properly as far as normal sending and receiving email operations go...and it is listening on 127.0.0.1. I would be interested in looking at the actual bounce messages from the MAILER-DAEMON. However, I don't know how I can get to these messages, if it is even possible. I am hoping that these messages might shed some light on the problem. If anyone has any suggestions, please let me know. Or, if I have provided too little information, I will be glad to provide anything necessary to help solve this issue. Thanks! -- Jodie E Crouch III ShreveNet, Inc. Asst. Network Administrator -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newbe Headaches
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 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 installing from source they could easily overlook the > placement of the smrsh directories... > > On Wed, 2003-03-12 at 13:02, Bob Sully wrote: > > > > 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 message as below; same thing with 8.12.8. The only way to get > > around this is to disable smrsh in sendmail.mc -> sendmail.cf. This is > > bothersome, as smrsh does have some (albeit minor?) security value. I'd > > like to see a fix for this soon. Perhaps we should alert the Sendmail > > developers. -- Bob Sully - Simi Valley, California, USA http://www.malibyte.net "The waiting is the hardest part." - T. Petty -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] configuring mailman with courier
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 did. ;-)
Courier setup
-
For starters, I'm using authpgsql as the authmodule for Courier. The domain
where I'm hosting Mailman is one of my hosteddomains.
Mailman
---
I did NOT have to create any accounts for Mailman, local or virtual. I do
everything with aliases. That, to me, seems like A Good Thing (tm). I
would have liked to use a single dot-courier file for each alias instead of
using the intermediate dummy aliases as described below, but I was unable to
get the [EMAIL PROTECTED]:com stuff to work.
After running bin/newlist, I copy the alias information it spits out into a
file (e.g., mylistname-list.aliases). I then run a Python script on this
file that does this:
1. Creates a file in /path/to/courier/etc/aliases/ named after the list. I
name the alias file after the list just to keep each list's aliases separate
and easily identifiable. In this file, I create intermediate aliases.
Suppose my list is named mailman and the hosted domain is domain.com. Then
I'd have:
[EMAIL PROTECTED]: mailman1
[EMAIL PROTECTED]: mailman2
...
The right-hand side is a dummy alias.
2. For each dummy alias, create a dot-courier file in
/path/to/courier/etc/aliasdir/. E.g.,
aliasdir/.courier-mailman1
aliasdir/.courier-mailman2
...
The contents of each dot-courier file look like this:
|/opt/mailman/mail/mailman post mailman
In other words, the contents of the dot-courier file are the same as the
right-hand side of what bin/newlist spits out for that alias, just without
the quotation marks.
I've attached the actual script below.
Cheers,
// mark
#!/usr/bin/env python
"""
Create the dot-courier files for the aliases listed in the specified file.
"""
import os
import sys
import pwd
class IncorrectUserError(Exception):pass
def require_user(username):
"""Exit if the current user is not username."""
current_username = pwd.getpwuid(os.getuid())[0]
if current_username != username:
template = 'Please run as %s (current user: %s).\n'
message = template % (username, current_username)
raise IncorrectUserError(message)
class Alias(object):
def __init__(self, alias, domain, command, counter):
self.alias = alias
self.domain = domain
self.command = command
self.counter = counter
def get_basename(self):
alias = self.alias
i = alias.find('-')
if i >= 0:
return alias[:i]
else:
return alias
def get_full_alias(self):
return '[EMAIL PROTECTED]' % (self.alias, self.domain)
def get_dummy_alias(self):
return '%s%d' % (self.get_basename(), self.counter)
def main():
program = os.path.basename(sys.argv[0])
usage = 'usage: %s listname filename etcdir [domain]\n' % (program,)
try:
listname = sys.argv[1]
filename = sys.argv[2]
etcdir = sys.argv[3]
except IndexError:
sys.stderr.write(usage)
sys.exit(1)
default_domain = 'yourlistdomain.com'
try:
domain = sys.argv[4]
except IndexError:
domain = default_domain
courier_username = 'courier'
try:
require_user(courier_username)
except IncorrectUserError, e:
message = str(e) + '\n'
sys.stderr.write(message)
sys.exit(2)
if not os.path.isdir(etcdir):
message = 'etcdir %s is not a directory.\n' % etcdir
sys.stderr.write(message)
sys.exit(2)
comment_char = '#'
separator = ':'
quote = '"'
aliases = []
counter = 0
for line in file(filename):
if line.startswith(comment_char):
continue
counter += 1
line = line.strip()
if not line:
continue
alias, command = line.split(separator)
alias = alias.strip()
command = command.strip()
if command.startswith(quote):
command = command[1:]
if command.endswith(quote):
command = command[:-1]
a = Alias(alias, domain, command, counter)
aliases.append(a)
# Write the intermediate aliases to $etcdir/aliases/.
filename = os.path.join(etcdir, 'aliases', listname)
f = file(filename, 'w')
for a in aliases:
f.write('%s: %s\n' % (a.get_full_alias(), a.get_dummy_alias()))
f.close()
# Write the dot-courier file to $etcdir/aliasdir/.
dirname = os.path.join(etcdir, 'aliasdir')
for a in aliases:
basename = '.courier-%s' % (a.get_dummy_alias(),)
filename = os.path.join(dirname, basename)
f = file(filename, 'w')
f.write(a.command + '\n')
f.close()
print 'You must run makealiase
RE: [Mailman-Users] sitewide list
[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. It seems to me this stuff should be in the INSTALL file. Or in some documentation. Did I miss it? If it's not written down anywhere, what can I do to help make that happen? Thanks, // mark - -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] A funny thing happened... (bug?)
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 the mm_cfg.py file the problem was corrected. Is there a known bug that DEFAULT_EMAIL_HOST= in the mm_cfg.py file is not being picked up correctly? Irwin -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] sitewide list
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 answered elsewhere. I've at least cursorily scanned the > obvious places. 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. > > Here are the questions I'm pondering... > > 1. When a subscriber to a normal list (i.e., something other than the > sitewide list) subscribes, are they implicitly subscribed to the site-wide > list? No. > 2. After the step for creating the site-wide list, the INSTALL file says, > "You should then subscribe yourself to the mailman list." Why? So if Mailman has an error to report, that error ends up in the Mailbox of someone who can handle it. > 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. > 4. Is there any reason to leave the archives public? (I guess you could > equally ask is there any reason to make them private?) I wouldn't save archives for error messages (unless you like to do that sort of thing). -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] sitewide list
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 obvious places. Here are the questions I'm pondering... 1. When a subscriber to a normal list (i.e., something other than the sitewide list) subscribes, are they implicitly subscribed to the site-wide list? 2. After the step for creating the site-wide list, the INSTALL file says, "You should then subscribe yourself to the mailman list." Why? 3. Is there any reason to display this site-wide list in the list of lists displayed by listinfo? 4. Is there any reason to leave the archives public? (I guess you could equally ask is there any reason to make them private?) I'm just trying to understand the purpose of the site-wide list. Any pointers would be helpful. Thanks, // m - -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
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 right, I should have been more precise. Best, elena -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
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 somehow the rest of sendmail (including listserv) was working fine, but mailman was pickier, and wanted the canonical domain of the host given there, in full. The canonical name was not there; instead, only the short name was given (it said "mafalda" instead of "mafalda.math.indiana.edu"). I edited sendmail.cf Dj$w.$m and now I can go back to having SMTPDirect. Nifty. Many thanks, best, elena -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
> 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.py. Kyle -- It is better to know nothing than to have learned nothing. -fortune cookie proverb -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
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 mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Different Errors this time
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 properly If you get the standard error that you see below "Group mismatch error. Mailman expected the mail wrapper script to be executed as group..." then you have a problem with Mailman's GroupID setting. On Wed, 2003-03-12 at 14:27, Joseph Smith wrote: > Yes > > I was worried that I had really fubared this up, so I rm'ed the whole > mailman dir and started from scratch > still getting the same error > > which is really wierd > > I mean I hate to ask stupid questions becuase the answer you gave me was > write there in the error. But it didn't fix it. Being new to freebsd and > not using Windows of any sort is making this hard to understand all the > little things that have gone wrong and I have no clue over. > > At 02:23 PM 3/12/2003 -0500, you wrote: > >Did you stop and restart "mailmanctl"? > > > >On Wed, 2003-03-12 at 13:57, Joseph Smith wrote: > > > Jon, > > > > > > > > > I have done exactly that with no change in the error msg. > > > > > > Would changing the GID of the user mailman to mailnull do anything > > positive? > > > > > > Joe > > > > > > At 01:52 PM 3/12/2003 -0500, you wrote: > > > >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 GroupID of "mailnull". This is because > > > >*your* mail-server runs as GroupID "mailnull" > > > > > > > >To set this up, you need to rerun the ./configure command (assuming you > > > >installed this from source): > > > > ./configure --with-mail-gid=mailnull > > > > make install > > > > > > > >Note: this will not hurt any of your current lists or list values > > > >(unless you modified the ~mailman/Mailman/Defaults.py file instead of > > > >the mm_cfg.py file). So fixing this should be a five minute job. > > > > > > > >Good Luck - Jon Carnes > > > > > > > >On Wed, 2003-03-12 at 13:02, Joseph Smith wrote: > > > > > 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. > > > > > > > > > > > > > > > - 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 tweaking the mail server to run the > > > > > script as group "mailman", or re-run configure, > > > > > providing the command line option `--with-mail-gid=mailnull'. > > > > > 554 5.3.0 unknown mailer error 2 > > > > > > > > > > > > > > > Any help is greatly appreciated. > > > > > Joe -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
-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 I changed DELIVERY_MODULE from SMTPDirect to Sendmail, > it worked just fine. That doesn't necessarily mean that the sendmail daemon was running. Changing DELIVERY_MODULE to Sendmail calls the sendmail binary directly so it would work even if sendmail was running in daemon mode. One way to tell if your MTA is listening for connections via SMTP is to use telnet, something like this: $ telnet localhost 25 You should get something like this: Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 localhost ESMTP Postfix > So, my problem (one of my many problems :-)) is that, I suppose, I > do not know what the hell is SMTPDirect, except that it is not something > standard in Solaris 8, because I have the full distribution. SMTPDirect isn't a program, it's a python module in mailman. That's what Sendmail is too, as used by the DELIVERY_MODULE setting. Using SMTPDirect tells mailman that it should try to deliver mail using the SMTP protocol. > Now, might mailman work if I just put SMTP instead of SMTPDirect? > Any comments? Unless you write a python module called SMTP, it would not. > As for all the warnings you cited, right, I read them. I read them > *after* I discovered what the problem was, which took me 24 hours... > My only point is that I would not see anything wrong if the README > file, the one we read when we install the thing, had said: > > "By the way, take a look at Defaults.py. It may well be that your > sistem does not use SMTPDirect bla bla bla." Since SMTPDirect merely tells mailman to use SMTP, and it's assumed that you're running an SMTP server (be it sendmail, postfix, exim, qmail, etc) it should be unnecessary to add such a warning. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp I always wanted to be a procrastinator, never got around to it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+b454uv+09NZUB1oRAmu/AJ4z6fpy68R7hqShOiaDrlC8IOFL5ACaAw5g O2OQZ8Z2s5pES7aGWVauVMI= =KxOm -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
-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 to be truly a newbie but... > > there is hope for me. I decided to look into the sendmail.cf You are a brave soul. I only edited sendmail.cf a few times before I switched to postfix, which uses plain english for it's config file (I know, what a weird idea :). > file, and it turns out that somehow the rest of sendmail (including > listserv) was working fine, but mailman was pickier, and wanted the > canonical domain of the host given there, in full. The canonical name was > not there; instead, only the short name was given (it said "mafalda" > instead of "mafalda.math.indiana.edu"). I edited sendmail.cf > > Dj$w.$m > > and now I can go back to having SMTPDirect. Nifty. Many thanks, > best, elena Cool. Glad it's working. Now you can enjoy playing with the more fun parts of mailman. Have a good time. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp A budget is just a method of worrying before you spend money, as well as afterward. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+b4+uuv+09NZUB1oRAvHWAJ4yxVeAhGWMMtj0ZO8/ReyR9Co6fgCfdPRS xJCJwOlaOHvT3QY+jjEkY3M= =JAQg -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newbe Headaches
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 installing from source they could easily overlook the placement of the smrsh directories... On Wed, 2003-03-12 at 13:02, Bob Sully wrote: > > 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 message as below; same thing with 8.12.8. The only way to get > around this is to disable smrsh in sendmail.mc -> sendmail.cf. This is > bothersome, as smrsh does have some (albeit minor?) security value. I'd > like to see a fix for this soon. Perhaps we should alert the Sendmail > developers. > > -- Bob -- > > > > On Wed, 12 Mar 2003, Jon Carnes wrote: > > > 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 expositions about Smrsh in the Archives that > > contain more info about Smrsh and its default settings. > > > > > > >- Transcript of session follows - > > > smrsh: "mailman" not available for sendmail programs (stat failed) > > > 554 5.0.0 Service unavailable > > -- > > Bob Sully - Simi Valley, California, USA > http://www.malibyte.net > > "The waiting is the hardest part." - T. Petty > > -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
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 do not understand this: First you wrote: That's a pretty strong warning against using this in production. And then you wrote: "There is nothing wrong with using sendmail as your MTA with mailman. Lots of people do this (despite sendmail's horrid .cf file, IMO ;)." So, my problem (one of my many problems :-)) is that, I suppose, I do not know what the hell is SMTPDirect, except that it is not something standard in Solaris 8, because I have the full distribution. Now, might mailman work if I just put SMTP instead of SMTPDirect? Any comments? As for all the warnings you cited, right, I read them. I read them *after* I discovered what the problem was, which took me 24 hours... My only point is that I would not see anything wrong if the README file, the one we read when we install the thing, had said: "By the way, take a look at Defaults.py. It may well be that your sistem does not use SMTPDirect bla bla bla." Best, elena -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Different Errors this time
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 GroupID of "mailnull". This is because *your* mail-server runs as GroupID "mailnull" To set this up, you need to rerun the ./configure command (assuming you installed this from source): ./configure --with-mail-gid=mailnull make install Note: this will not hurt any of your current lists or list values (unless you modified the ~mailman/Mailman/Defaults.py file instead of the mm_cfg.py file). So fixing this should be a five minute job. Good Luck - Jon Carnes On Wed, 2003-03-12 at 13:02, Joseph Smith wrote: > 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. > > > - 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 tweaking the mail server to run the > script as group "mailman", or re-run configure, > providing the command line option `--with-mail-gid=mailnull'. > 554 5.3.0 unknown mailer error 2 > > > Any help is greatly appreciated. > Joe > > > -- > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Proper Editing of Welcome Message
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 a way that it would effect all of the lists. Is there a correct way in which to do this? Thanks, DAM -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Proper Editing of Welcome Message
-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 don't > want indiscriminately to edit files in such a way that it would effect all > of the lists. > > Is there a correct way in which to do this? If you're using 2.1 you should copy the template file from ~mailman/templates/ to ~mailman/lists// Then edit subscribeack.txt to remove the reference to posting. If you're using 2.0 you can't do this without patching mailman to look in the list dirs for templates. I did this fairly easily using some suggestions I found in the list archives. But moving to 2.1 is much easier and has many other benefits, so that'd be the ideal solution. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp No man will ever bring out of the Presidency the reputation which carried him into it. -- Thomas Jefferson -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+b382uv+09NZUB1oRAtLfAJ97Adv8GmoCz8CP3Fglfo83860MIwCgss99 aKUxnT+UqPbFklm2r9IPKXc= =SSDT -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Different Errors this time
-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 tweaking the mail server to run the > script as group "mailman", or re-run configure, > providing the command line option `--with-mail-gid=mailnull'. > 554 5.3.0 unknown mailer error 2 > > > Any help is greatly appreciated. Just rerun ./configure adding --with-mail-gid=mailnull to any other options you used previously. Then do make and make install and that should get you over that hurdle. Don't forget to restart mailmanctl if it's running, I would imagine that's necessary. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp It is not who governs, but what government is entitled to do, that is the essential problem. -- Charles G. Bragg -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+b34Buv+09NZUB1oRAh+iAJ95JZ1wIO9UJqWgF94cvIz7KTX1JQCgv+jb LET+bYAdNgP2eCv+HG0Ie6o= =E2Vt -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem solved: it was the MTA
-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 this somewhere in the INSTALL docs. There isn't a warning because you the Sendmail DELIVERY_MODULE is not supposed to be used in a production environment. The comments in Default.py direct you to read Mailman/Handlers/Sendmail.py if you want to use it. When you read that file, you see this: WARNING WARNING WARNING: This module is provided for example purposes only. It should not be used in a production environment for reasons described below. Because of this, you must explicitly enable it with by editing the code. See the WARN section in the process() function. This module delivers the message via the command line interface to the sendmail program. It should work for sendmail clones like Postfix. It is expected that sendmail handles final delivery, message queueing, etc. The recipient list is only trivially split so that the command line is less than about 3k in size. SECURITY WARNING: Because this module uses os.popen(), it goes through the shell. This module does not scan the arguments for potential exploits and so it should be considered unsafe for production use. For performance reasons, it's not recommended either -- use the SMTPDirect delivery module instead, even if you're using the sendmail MTA. DUPLICATES WARNING: Using this module can cause duplicates to be delivered to your membership, depending on your MTA! E.g. It is known that if you're using the sendmail MTA, and if a message contains a single dot on a line by itself, your list members will receive many duplicates. That's a pretty strong warning against using this in production. > I do know about the security problems with Sendmail, and I am > applying myself to patching my installation this afternoon. There is nothing wrong with using sendmail as your MTA with mailman. Lots of people do this (despite sendmail's horrid .cf file, IMO ;). The DELIVERY_MODULE setting simply changes the method by which mail gets from mailman to your MTA. The default (and preferred) way is to use SMTP to talk to your MTA. Changing the DELIVERY_MODULE to Sendmail.py uses the command line interface to any sendmail compatible MTA (like Postfix). > But, from the point of view of mailman, once the correct > Delivery_Module was specified in Defaults.py, it works fast > as a whistle. I might not understand completely what problems you were having, but if the default DELIVERY_MODULE setting wasn't working, is it possible that you didn't have your MTA running or configured to accept mail from mailman? > I am glad: the work paid off. I am mad: I hate it when something > as basic as 'Sendmail' is commented out because "You shouldn't be > running sendmail in the first place." Fine, but tell me about it > in the README file. I say it here in case another newbie writes > in the future with the same difficulty. It's not in the README because it's considered experimental and unsecured. The mailman developers aren't trying to be mean or shove their views down users throats. In fact, the developers I've seen all seem like really nice folks. :) - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp Ammunition beats persuasion when you are looking for freedom. -- Will Rogers -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+b3Youv+09NZUB1oRAkAPAJ9hz9bQlzaNR0SRM4KHYCtJx1T1oQCg9zrj XGWCC30btIl81W2KkNWaNog= =3NF2 -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newbe Headaches
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 message as below; same thing with 8.12.8. The only way to get around this is to disable smrsh in sendmail.mc -> sendmail.cf. This is bothersome, as smrsh does have some (albeit minor?) security value. I'd like to see a fix for this soon. Perhaps we should alert the Sendmail developers. -- Bob -- On Wed, 12 Mar 2003, Jon Carnes wrote: > 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 expositions about Smrsh in the Archives that > contain more info about Smrsh and its default settings. > > > >- Transcript of session follows - > > smrsh: "mailman" not available for sendmail programs (stat failed) > > 554 5.0.0 Service unavailable -- Bob Sully - Simi Valley, California, USA http://www.malibyte.net "The waiting is the hardest part." - T. Petty -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Different Errors this time
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. - 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 tweaking the mail server to run the script as group "mailman", or re-run configure, providing the command line option `--with-mail-gid=mailnull'. 554 5.3.0 unknown mailer error 2 Any help is greatly appreciated. Joe -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] let me clarify
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 months ago so I could just be hallucinating) Sorry, I did not quote enough to get context. The issue here is not the GID's but the permissions on directories that run CGI. As far as I can tell Ensim will not run CGI if the directory or script has permissions over 755. This conflicts with what mailman wants. Will changing the permissions on the mailman cgi-bin to 755 kill mail man? - su as the local chrooted user that runs the webserver (generally the admin of the chroot) - run the admin cgi from the command line: ~mailman/cgi-gin/admin This should dump out the source of a web-page to the command line (like when you look at a web-page and click on "View Source". It's a simple check. If that works then your Mailman install is working fine and the problems must be in the Chroot web-server setup. Ah, another problem. 'Mailman expected the CGI wrapper script to be executed as group "apache", but the system's web server executed the CGI script as group "admin". ' That I can fix by rerunning configure I think! That plain Red Hat box is looking cheaper and cheaper! Don't mess with me, I know how to change my laser printer from stun to kill! <>< Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem solved: it was the MTA
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. All that is fine, except that there should be a warning about this somewhere in the INSTALL docs. I do know about the security problems with Sendmail, and I am applying myself to patching my installation this afternoon. But, from the point of view of mailman, once the correct Delivery_Module was specified in Defaults.py, it works fast as a whistle. I am glad: the work paid off. I am mad: I hate it when something as basic as 'Sendmail' is commented out because "You shouldn't be running sendmail in the first place." Fine, but tell me about it in the README file. I say it here in case another newbie writes in the future with the same difficulty. Many thanks to all who bothered with my problem. Best, elena -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newbe Headaches
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 expositions about Smrsh in the Archives that contain more info about Smrsh and its default settings. - Original Message - From: "Joseph Smith" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 12, 2003 12:48 AM Subject: [Mailman-Users] Newbe Headaches > Good Evening folks, > > I have just reinstalled Mailman for the third time and I am obviously doing > something wrong. > > I have freebsd 4.7 running with sendmail > > The list is setup and only a few test users are added. Mailman sends out > the subscription notification to the users. > > As soon as I send a post to Mailman here is my error. > >- Transcript of session follows - > smrsh: "mailman" not available for sendmail programs (stat failed) > 554 5.0.0 Service unavailable > > Now I have added the link as stated in the reading material provided. I > know I am missing something real smapp but it seem that the wrapper is not > handling this task properely or its not working with smrsh right. > > Any and all help is greatly appreciated. > > Thanks > Joe > > > -- > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 14 hours and still not there
- 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 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. Interesting, because I remember using UID and GID's that were in the 1000+ range for the chroot (but that was six months ago so I could just be hallucinating) > As for lack of web pages, I assume that is because the cgi programs > don't run? Are the web pages real or created on the fly? And if real, > where are they supposed to reside? I tried manually creating pages and > could not get to them, apparently a redirect was sending me else where. I > have not dissected it yet, but any hints would be appreciated. > The web-pages are generated via the GGI's, but you can check them out simply: - Chroot yourself - su as the local chrooted user that runs the webserver (generally the admin of the chroot) - run the admin cgi from the command line: ~mailman/cgi-gin/admin This should dump out the source of a web-page to the command line (like when you look at a web-page and click on "View Source". It's a simple check. If that works then your Mailman install is working fine and the problems must be in the Chroot web-server setup. Good Luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] no discernable addresses?
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 the bounces log: Mar 12 10:38:35 2003 (3705) bounce message w/no discernable addresses: <[EMAIL PROTECTED] u> Mar 12 10:38:35 2003 (3705) forwarding unrecognized, message-id: <[EMAIL PROTECTED]> Now, at some point "[EMAIL PROTECTED]" got converted to "[EMAIL PROTECTED]". Any advice? Many thanks, best, elena P.D. This is today's behavior, after recompiling and re-installing anew. It seems to be an improvement on yesterday. At least I now have something to work on. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: mailman + spamassassin
"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 through spamassassin. I found this patch at sourceforge, but if I > add SpamAssassin.py to mailman/Mailman/Handlers/, and patch > mailman/Mailman/Handlers/HandlerAPI.py, mailman gives errors. What did I > wrong? Is there any step-by-step howto? The SpamAssassin code needs to be compiled, I think, before it will activate. If you just put the py file in the installed location, it doesn't get compiled (into a pyc file). I implemented the SA patch without a problem, but I put the patch in the source directory and reinstalled the whole thing. david -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] How does MM 2.1.1 catch bounces? -- too many"Uncaught.."
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 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] How does MM 2.1.1 catch bounces? -- too many"Uncaught.."
> "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 that aren't John> really "bounce" messages. I.e., they don't indicate a John> problem delivering the mail. John> My theory is that when I have time I will try and filter out the most John> common ones with procmail or the like. John> But you certainly don't want someone's account John> disabled because of some of these messages. agreed. But here I give an example of one where I think mailman should have figured it out: From: [EMAIL PROTECTED] (Mail Delivery Subsystem) To: <[EMAIL PROTECTED]> Subject: Returned mail: User unknown Date: Wed, 12 Mar 2003 12:58:45 +0100 (MET) The original message was received at Wed, 12 Mar 2003 12:58:44 +0100 (MET) from hypatia.ethz.ch [129.132.58.23] - The following addresses had permanent fatal errors - <[EMAIL PROTECTED]> - Transcript of session follows - ... while talking to akasolvr.vub.ac.be.: >>> RCPT To:<[EMAIL PROTECTED]> <<< 553 <[EMAIL PROTECTED]>... User mathie.roelants unknown at vub.ac.be 550 <[EMAIL PROTECTED]>... User unknown - Message header follows - John> Martin Maechler wrote: >> 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 somehow do things automagically. >> Now that I've read the related info more carefully, I realize >> these are just the bounces that mailman is *not* able to deal >> with automatically. >> I've looked at some and really wondered _why_ mailman couldn't >> figure out the E-mail address that bounced when it looked very >> obvious to the human eye. >> >> - Hints? >> - To whom could I forward examples of these? John> -- John> John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] How does MM 2.1.1 catch bounces? -- too many"Uncaught.."
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 the most common ones with procmail or the like. But you certainly don't want someone's account disabled because of some of these messages. Martin Maechler wrote: 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 somehow do things automagically. Now that I've read the related info more carefully, I realize these are just the bounces that mailman is *not* able to deal with automatically. I've looked at some and really wondered _why_ mailman couldn't figure out the E-mail address that bounced when it looked very obvious to the human eye. - Hints? - To whom could I forward examples of these? -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] customizing text and layout
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 is located which this message prints. Can anybody perhaps help me with this by telling where I can find this text? Another problem I'm facing; I'm trying to include a CSS-file in listinfo.html. Therefore, I've added the line to the file, like I always do with these lines. In my editor, the results of this include do show, but they do not on the server (when I open the page on the web). I've ofcourse uploaded the mailman.css file to the same folder as the listinfo.html is in. Anybody knows what I'm doing wrong? Thanks in advance for any answers. With kind regards, Thijs Koetsier -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] How does MM 2.1.1 catch bounces? -- too many "Uncaught.."
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 somehow do things automagically. Now that I've read the related info more carefully, I realize these are just the bounces that mailman is *not* able to deal with automatically. I've looked at some and really wondered _why_ mailman couldn't figure out the E-mail address that bounced when it looked very obvious to the human eye. - Hints? - To whom could I forward examples of these? Thank you, Martin Maechler <[EMAIL PROTECTED]> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
