ilman-*/INSTALL.REDHAT for documentation on the
directory structure, you may not have copied the old list data into the
locations currently used.
--
John Dennis
Red Hat Software
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.p
o mm_cfg.py files. Something to do
> with your 'package' I suppose. Does one import from the other?
They are the same file. The mm_cfg.py in /etc/mailman is a sym link
to /usr/lib/mailman/Mailman/mm_cfg.py.
--
John Dennis <[EMAIL PROTECTED]>
---
Thomas Waters wrote:
><[EMAIL PROTECTED]>: Command died with status 2:
> "/usr/share/mailman/mail/mailman post rxtesttuesday". Command
>output: Group
> mismatch error. Mailman expected the mail wrapper script to be
>executed as
> group "mailman", but the system's mail server execu
Ben wrote:
>>The underlying problem here is Windows lack of support for
>>setting effective user and group ids. This breaks all kinds
>>of things that Mailman assumes about its environment.
>>
>>
>
>Yes, that's clear :) The question remaining is, is there any hope of
>getting around it :(
>
it should have no problems reading the driver script, but
that is what is failing, go figure, seems like it should work.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mai
what does
ls -l /home/mailman/domains/chuckie.co.uk/scripts/driver
say?
what does
/usr/sbin/getenforce
say?
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/m
eneral was not a prime design point for mailman, a limitation which is
recognized and hopefully will be better addressed in MM 3.0. If you have
very sensitive information in your archives you may want to consider an
alternate solution.
--
John Dennis <[EMAIL PROTECTED]>
---
n this one.
Essentially you have two choices:
1) The php script executes as a member of the mailman group
2) The php script invokes a wrapper just like the CGI does. This is
preferred for a variety of security reasons. It would not be hard to
create a new wrapper from
On Thu, 2005-12-08 at 17:50 -0800, Mark Sapiro wrote:
> John Dennis wrote:
> >
> >If your MTA can only handle one, or a small number of client connections
> >then each connection will be busy handling SMTP_MAX_RCPTS and other
> >client connections will queue up. If you
tain a connection from the SMTP
connection pool because mailman will cycle through connections in a
serial manner leaving the rest of the SMTP client connection pool
available for other SMTP clients.
HTH,
--
John Dennis <[EMAIL PROTECTED]>
--
mailman specific uid/gid then when those
aliases instruct postfix to run a command (e.g. the wrapper) then it
will do so with the uid/gid of the mailman alias file.
In your case you ended up with a mixed bag of aliases and depending on
which bag the alias was found in first you got the uid/gid of t
ot;turn off" the old
name, you can't have two machines trying to answer service requests for
the same name without a very complex scheme which is probably far beyond
what you want to get involved with. Mailman's involvement with the name
change is minimal, it effects all inte
ed so that mailman is replaced by the cgi location and executed.
In this case the cgi location is /usr/local/lib/mailman/cgi-bin, it will
try to find the script "listinfo" in that directory because that is the
next part of the path and it will pass "mylist" as a p
as any further
> troubleshooting ideas about this I'd appreciate hearing them. Thanks a lot...
And did you restart Apache so it would reread its configuration?
Are you getting a 404 "Not Found" error?
Do you have any rewriting rules enabled which might rewrite the mailman
URL by mistake?
-
-users%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-users/jdennis%40redhat.com
>
> Security Policy:
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
--
John Dennis <[EMAIL PROTECTED]>
-
SER then remove the file manually because most likely
someone during initial testing/setup ran it in some other way. You
should then be fine.
Do verify the values of mm_cfg.MAILMAN_GROUP, mm_cfg.MAILMAN_USER.
--
John Dennis <[EMAIL PROTECTED]>
cron jobs? In particular the "senddigests"
cron job needs to be scheduled to run periodically.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/m
w set
of aliases.
Please read the file /usr/share/doc/mailman-*/INSTALL.REDHAT for Red Hat
specific tips and to learn that 2.1 has a different way of being run
than 2.0 did, you'll now start mailman as a regular service. Cron will
be taken care of automati
27;t be changed readily.
Thus Rule #2 follows from Corollary #1:
Don't use sendmail :-)
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
to go to the
new address right where he won't see it (or were you planning on
aliasing these as well?).
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/list
ve that is
not a huge issue, but you should be aware it is a limitation.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.
east you haven't
indicated why you need to map a non-existant domain. The postfix site
has good documentation on virtual domains
(http://www.postfix.org/VIRTUAL_README.html), reading that might shed
some light.
HTH,
--
John Dennis <[EMAIL PROTECTED]>
-
code, you don't have to explicitly set it in mm_cfg. However, if you
created a list and then changed the hostname you'll have to fix the
lists you already created because that information is embedded in the
list after creation. The mailman FAQ
to a new name and edit it so that it
calls AddMember instead of AddApprovedMember. See
Mailman/Cgi/subscribe.py for an example of how to do this and the
various exceptions you'll have to catch and handle.
--
John Dennis <[EMAIL PROTECTED]>
on) that you almost certainly would not have access to.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-
's are encouraged not to use an important password for
mailman.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.p
ssword() to be a no-op. You would
also want to configure the site defaults to never send password
reminders.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo
nclude $alias_maps in the
local_recipient_maps parameter in postfix's main.cf. This is very
clearly documented in the comments in main.cf and the
LOCAL_RECIPIENTS_README file that is part of the postfix distribution
and available on www.postfix.org. You need the alia
DN
it sets the domans to the string you see above (which I had hoped would
be more or less self explanatory as an indicator you have to manually
edit the file).
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@py
is craft a rule which first attempts to
match /lists/mailman and if that matches terminate the rule processing
outputting the matched URL, else continue to process and rewrite the URL
to the per list URL.
BTW, rewrite != redirect
--
John Dennis <[EMAIL PROTECTED]>
On Thu, 2005-09-29 at 14:23 -0400, John Dennis wrote:
> I suspect the problem is the http configuration for the directory that
> was originally posted omitted the "Options ExecCGI" which is required to
> tell the http server it is permissible to execute cgi scripts in this
>
your installation:
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
AllowOverride None
Options ExecCGI
Order allow,deny
Allow from all
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
You probably want to use the fix_url utility. Look in
PREFIX/bin/fix_url.py, you will find documentation at the top of the
file. Note, you don't run fix_url directly, its invoked by running
PREFIX/bin/with_list, the doc explains this.
--
John Dennis <[EMAIL P
file called extend.py in the list directory ($prefix/lists/NAME where
NAME is the name of one of your lists).
Sorry, I realize this is a very python'ic answer but its the best I can
do given the info.
--
John Dennis <[EMAIL PROTECTED]>
---
ying and SMTP configuration are outside the scope of the
mailman-users list. You will need to learn what the SMTP server is on
proxiad.com and configure it correctly. Or, locate everything on one
server.
--
John Dennis <[EMAIL PROTECTED]>
--
M
e its running
on the same machine as the receiving SMTP server and the aliaes are
correct. I suspect what actually occurred is those are examples from
mail sent on the machine mailman is running on where everything will
resolve correctly.
--
John Dennis <[EMAIL PROTECTED]>
ag to prevent a sender from receiving their own post, if you send
the mail from the same address you're expecting to see it returned in
from the list, you won't.
Have you looked in /var/log/maillog for SMTP messages?
Have you reloaded you
On Wed, 2005-09-21 at 13:44 -0400, Darren G Pifer wrote:
> On Wed, 2005-09-21 at 12:13, John Dennis wrote:
>
> > > I tried testing with:
> > >
> > > $ pwd
> > > /usr1/mailman/mailman/cron
> > >
> > > $ runas -u mailman ./mailpass
s its password reminder flag set to
yes under general options and that the per user option to receive
reminders is enabled for at least some members of the list?
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Us
FAQ
3.11. How do I create a newsletter/announcement/one-way list?
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.011.htp
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
htt
n as
a distributor of messages is ignorant of them.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cg
On Mon, 2005-09-19 at 11:12 -0400, John Dennis wrote:
> > This is on Redhat Enterprise w/ Plesk - I suspect a nightly
> > up2date hosed something that mailman cares about.
> >
> > Any thoughts on what to do to correct this problem?
One more suggestion: If up2date instal
your apache configuration (I know very little about how Plesk works
but I suspect it has a very strong interaction with apache configuration
which is why since Plesk is in the picture you need to consider Plesk
interaction).
--
John Dennis <[EMAIL PROTECTED]>
-
; errors in /var/log/messages
or /var/log/audit/audit.log?
* Do you have SELinux enabled? Try turning it off
setenforce 0
* Can you create the list via the command line (mailman/bin/newlist)
but not the Web UI?
--
John Dennis <[EMAIL PROTECTED]>
--
or /usr/lib/mailman/cgi-bin/rmlist
checking set-gid for /usr/lib/mailman/cgi-bin/create
checking set-gid for /usr/lib/mailman/cgi-bin/edithtml
checking set-gid for /usr/lib/mailman/cgi-bin/options
--
John Dennis <[EMAIL PROTECTED]>
--
x 1 root mailman 18349 Mar 7 2005 private
-rwxr-sr-x 1 root mailman 18349 Mar 7 2005 rmlist
-rwxr-sr-x 1 root mailman 18349 Mar 7 2005 roster
-rwxr-sr-x 1 root mailman 18353 Mar 7 2005 subscribe
--
John Dennis <[EMAIL PROTECTED]>
-
#x27;t help because they are
not in the group "list". Make sense?
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://ww
oth mail and cgi have to line
up with how your MTA and web server respectively execute sub-programs.
Also, being a bit more specific with how the web interface is not
working properly would help solve your problem.
--
John Dennis <[EMAIL PROTECTED]>
--
is telling you that is not what is happening, its being executed
as group mail.
>
> ##
> #MAIN CONFIGURATION SETTINGS #
> ##
>
> exim_user = mail
hmm... very suspicious, looks l
m playing a little loose and fast here, but thats
the idea in a nutshell). This probably only happens via an exim
configuration parameter tied to mailman invocation.
HTH,
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
n mapping when you re-route
to the primary server. If the alias lookup's include domain information
you may fail the local_recipient_maps lookup because although the user
part of the address is correct it may include a domain part not
recognized by the server fielding the request. I would use the
. Try this as root:
% chown mailman database
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/fa
e mail wrapper to
accept a message but not log it. I wonder if your mail wrapper is
actually executing. You can try piping a dummy message into the wrapper
with the same args as the user your postfix program runs as. Pay
particular attention in any of the logs to "grou
you could install the mbox file and
run mailman/bin/arch to rebuild mailmans archive from the mbox file.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mail
On Fri, 2005-08-19 at 12:47 -0400, Julian C. Dunn wrote:
> On Fri, 2005-08-19 at 12:37 -0400, John Dennis wrote:
> > On Fri, 2005-08-19 at 11:46 +0300, [EMAIL PROTECTED] wrote:
> > > Hello All,
> > >
> > > 1) I'm implementing web-cyradm installation to
#
> ScriptAlias /mailman/ "/usr/lib/mailman/cgi-bin/"
>
> AllowOverride None
> Options FollowSymLinks ExecCGI
> Order allow,deny
> Allow from all
>
> ##
> ## end mailman
> ##
> ######
>
> Are
Brad> Dunno. But you'd be more likely to get an answer to
> Brad> your question if you used resources appropriate to your OS.
>
> If John Dennis doesn't show up shortly with an answer, I recommend you
> write to Red Hat support and ask about "large
at is
the behavior.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
On Tue, 2005-08-09 at 16:11 -0400, John Dennis wrote:
> ouch. you're building in the install area before you've installed,
This probably was not clear because I omitted an important but somewhat
hidden fact, /usr/local/mailman is the default installation directory.
Had you typed
t is just a copy of the join script (unsubscribe is a
copy of leave). The part of install that copied the existing scripts
worked, the part that installed copies of join and leave did not. I'm
not sure why that part of the install failed but installing in
d to integrate with
existing Red Hat packages and configuration. If you do start with the
rpm it won't mean you'll be free from any configuration issues but
you'll avoid a number of headaches. If you do go this route please be
sure to follow the inst
;t perform this step.
cd to the mailman source root
./configure --with-mail-gid=mailman
make
make install
Don't forget to add any other configure options you used previously.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mai
commands under the group belonging to the alias file,
not to the mail_owner in postfix's main.cf file. I think I recall a
config variable to turn the postfix behavior off, but you should not do
that because mailman should be creating the alias file and hence it
should match the uid/gid, but if
on jobs are enabled. You can set
the time this cron job runs so you can control when they are sent out.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-
ilman using the configure option
--with-cgi-gid=apache
BTW, this is in the FAQ.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http
the service. Is there a
mailman.conf file in that directory? If not grep all the files there
looking for one that contains mailman.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/m
port 25 is being listened on the localhost (loopback) because
your loopback is 127.0.0.1 and its listening on 192.168.0.0 which is
192.168.0.0 (ficticious net addr).
If nothing is listening on the external interface, then is postfix
running? If so did you restart it after modify inet_interfac
inux, or use the vendors mailman
package (by the way this applies to everything under SELinux control
which for a mailman installation includes your MTA and web server. Your
vendor has worked hard to make sure the security policy works for all
components, if you build and install anything yourself you m
ymachine.mynetwork.com 25
Does postfix answer?
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-
help:
http://www.macosxhints.com/article.php?story=2004122809382235
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www
is
being assigned a permanent IP address via a local DHCP server you will
likely have to make that change in the DHCP configuration.
HTH,
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.
fix"
Also make sure what you used as --with-cgi-id --with-cgi-gid when you
built mailman matches the id's used by your webserver.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http:/
ailing list
has -1 request(s) waiting... ?
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.038.htp
Note: the 2.1.6 version has this fixed.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Use
is list) and
altered him to the fact there is a migration script
in /usr/share/doc/mailman-*/contrib/migrate-fhs that will tell you what
needs to be moved and move (and/or copy) it for you. Also
in /usr/share/doc/mailman-*/INSTALL.REDHAT is documentation on the
directory structure an
in an early version of
selinux-policy-targeted related to private archives which was fixed a
while ago by us.
If you do see such a message the solution is to upgrade the
selinux-policy-targeted rpm (or as a test you could put SELinux into
permissive mode
On Wed, 2005-07-13 at 14:42 -0400, Forrest Aldrich wrote:
> Right, exactly. But what' the best way to do this with Mailman.
Pick a new location of your chosing, move the cgi-bin directory to it,
then edit your httpd ScriptAlias entry for mailman.
--
John Dennis <[EMAI
e path?
Yes, I believe that would be a mistake and you may need to go back and
undo those file changes :-(
mailman_install_dir/bin/fix_perms might be helpful, the -f option will
"fix" the files.
--
John Dennis <[EMAIL PROTECTED]>
--
Mail
invoke the CGI wrapper.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives
by mailman. I don't think the problem
you're concerned about exists, unless perhaps I've misunderstood you.
You might find this FAQ helpful:
6.16. Understanding group mismatch errors - how mailman implements
security
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=
so
bounced. Once your MTA hands off a set of mail to a destination SMTP
server a whole host of things can happen to it that has nothing to do
with your server. Your best bet is to verify from the logs the mail left
your server when you expected it to.
--
John Dennis <[EMAIL PROTECTED]>
---
change its
hardcoded setting in the "driver" script, you will have to locate this
file and edit it. However, if you can, it really would be better to get
your syslog working, you do want these errors logged and it really is
better to keep sensitive information out of the publi
be able to see the stack traces). To
analyze what caused a bug you'll need the stack trace. Although the
stack trace is no longer visible it is logged on the system hosting
mailman, I believe in the mailman error.log file, its location will be
installation dependent (/var/log/mailman, /usr/local/
e that as of mailman 2.1 cron is not necessary to run
basic mailman, as of 2.1 mailman is a service (e.g. daemon). Also, the
init.d script plays an integral role in managing cron usage for the
parts of mailman that still depend on cron.
HTH, if you still have problems feel free contact me.
--
Jo
ailman is *not* setgid but postfix can pipe to that
> OK,
>
> Also, should I end up with "any" files being owned by apache2? after using
> the
> web interface to add a list I found that aliases, aliases.db and
> virtual-mailman.db were still the original ownership bu
first virtual list and getting. my data dir
> subsequently like thisneither db file were (re)generated
I suspect what is biting you is that postfix has a feature whereby
postalias runs as the user owning the alias file, this is independent of
--with-mail-gid and --with-cgi-gid.
--
J
Examine /var/log/messages and/or /var/log/audit for "avc" messages,
these log SELinux denials.
3) Try turning SELinux off (/usr/sbin/setenforce Permissive)
4) Contact me off list for a trial 2.1.6 rpm (I've created the rpm but
have not tested it yet, you could be the guinna pig :-)
B
ose permissions are granted only to a
non-root owner. Root is denied in this case. However root can su to that
owner and then perform the operation.
Also, the complete absence of execute permission is not something root
can compensate for.
--
John Dennis <[EMAIL PROTECTED]>
-
lable, free, and transparent. I
suspect your conclusions are driven by a lack of familiarity with how to
find what you are looking for rather than anything devious. To suggest
disingenuous lock in by Red Hat is utter nonsense.
--
John Dennis <[EMAIL PROTECTED]>
-
not permitted)
>
> Any comments?
I suspect /usr/local/sbin/mailman.aliases is either not executable or
not executable by the user/group the command is running under (what
user/group that is depends on how you did your installation)
What does
ls -l /usr/local/sbin/mailman.aliases
say?
--
ary to have
special Fedora instructions.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.p
idual package defaults are not a standard.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
S
rocess and every object (e.g. files, sockets, devices, etc.). It
is a Mandatory Access Control (MAC) sytem which means it cannot be
defeated and offers great granularity (and unforuntely its own set of
new headaces as the wrinkles in the security policy are ironed out ;-)
--
John Dennis &
y other things I can think of would be to strace
(assuming you're on a system with strace, e.g. Linux) the postfix
process and seeing where the failure occurs and/or to look at the
postfix code that performs the lookup and see exactly what c lib
functions it's calling and what triggers it
oked at the postfix code but I wouldn't be surprised if
postfix when it starts gets file information on all its input files
referenced in main.cf and stores that information. If that information
was altered while postfix was running it would likely get confused
because it may be using id&
Have you
tried restarting postfix? Is mailman in /etc/shadow on the machine
postfix is running on?
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-user
On Wed, 2005-05-25 at 19:39 +0200, Brad Knowles wrote:
> At 11:44 AM -0400 2005-05-25, John Dennis wrote:
>
> > I'm attaching our patch for this in case someone finds it useful.
>
> The attachment was stripped. Could you post it as a patch at the
> SourceFo
On Wed, 2005-05-25 at 10:36 -0700, Bo Gusman wrote:
> John Dennis wrote:
>
> >On Wed, 2005-05-25 at 10:13 -0700, Bo Gusman wrote:
> >>I am certain that SELinux is disabled, but how can I verify that?
> >
> >/usr/sbin/getenforce
> >
> Says "disabl
On Wed, 2005-05-25 at 10:13 -0700, Bo Gusman wrote:
> I am certain that SELinux is disabled, but how can I verify that?
/usr/sbin/getenforce
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python
ch for this in case someone finds it useful.
On Wed, 2005-05-25 at 08:13 -0700, Robert Haack wrote:
> What would happen if during the check you told mailman to stop first?
> Could this mess things up or would it be fine?
Yes you could do that, it is essent
ology. If one got left behind after the rpm install then the %post
section of the rpm is failing somehow.
--
John Dennis <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailm
1 - 100 of 197 matches
Mail list logo
