I changed mailman to use an aliases file (/etc/mail/mailman-aliases) which is
owned by root:mailman.
I get the following, which I didn't get when the aliases where being managed by
Exim itself.
Group mismatch error. Mailman expected the mail wrapper script to be executed
as group
Hicks, Robert CTR wrote:
I changed mailman to use an aliases file (/etc/mail/mailman-aliases) which is
owned by root:mailman.
I get the following, which I didn't get when the aliases where being managed
by Exim itself.
Group mismatch error. Mailman expected the mail wrapper script to
-Original Message-
Your message did not reach some or all of the intended recipients.
Subject: Test message only
Sent:2/1/2010 9:40 AM
The following recipient(s) cannot be reached:
em...@address on 2/1/2010 9:42 AM
The e-mail account does not
Hicks, Robert CTR wrote:
Your message did not reach some or all of the intended recipients.
Subject:Test message only
Sent: 2/1/2010 9:40 AM
The following recipient(s) cannot be reached:
em...@address on 2/1/2010 9:42 AM
The e-mail account does not
On Mon, Feb 01, 2010 at 02:24:26PM -0800, Mark Sapiro wrote:
The list-name in the message you sent me ends in -admin. This is the
problem.
I came up with a work-around for this, once, but on a box I've since
decommissioned.
Your Mailman router in Exim doesn't work with list names that end
Mark Sapiro wrote:
The list-name in the message you sent me ends in -admin. This is the
problem.
Your Mailman router in Exim doesn't work with list names that end with
'-admin' or probably any of the other suffixes '-bounces', '-confirm',
'-join', '-leave', '-owner', '-request', '-subscribe' or
I've got an old install (2.10.12) where, while mail to the lists goes
thru, the daily reminders do not ie the cron
/usr/local/bin/python -S /fs/mailman/cron/checkdbs
produces
...to=|/fs/mailman/mail/wrapper mailowner mylist, ctladdr=[EMAIL PROTECTED]
(1/0), delay=00:00:01, xdelay=00:00:00,
25-Nov-03 at 12:32, Todd ([EMAIL PROTECTED]) wrote :
Yes, I saw that, and I followed those instructions, but until I
changed the ownership of /etc/aliases and /etc/postfix/aliases*
the wrapper was still being run as gid nogroup. I think the
documentation should be changed to also
The wrapper script will run as the GID that it was compiled to
run as;
this has nothing whatsoever to do with Postfix.
The postfix-users list will just tell you to come back here, I
expect.
You'll have to recompile Mailman with the correct
--with-mail-gid
option. The option to give to
26-Nov-03 at 08:57, Jeremy Gilbert ([EMAIL PROTECTED]) wrote :
The wrapper script will run as the GID that it was compiled to
run as; this has nothing whatsoever to do with Postfix.
You'll have to recompile Mailman with the correct --with-mail-gid
option. The option to give to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon White wrote:
Postfix, by default, would use postdrop as the group for most stuff;
this is described in the Postfix install instructions.
Mailman, by default, would use the group mailman.
However I really think you are going to need to
Well, README.POSTFIX does say this:
Make sure that the owner of the data/aliases and
data/aliases.db
file is `mailman' and that the group owner for those files
is
`mailman'. E.g.:
% su
% chown mailman:mailman data/aliases*
Yes, I saw that, and I followed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Gilbert wrote:
Well, README.POSTFIX does say this:
Make sure that the owner of the data/aliases and
data/aliases.db file is `mailman' and that the group owner
for those files is `mailman'. E.g.:
% su
%
I'm having a hell of a time getting this working, but I keep
coming back to this problem. I get this back whenever I send
e-mail to a list address.
[EMAIL PROTECTED]: Command died with status 2:
/usr/local/mailman/mail/mailman post test. Command output:
Group mismatch
error. Mailman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Gilbert wrote:
I'm having a hell of a time getting this working, but I keep
coming back to this problem. I get this back whenever I send
e-mail to a list address.
[EMAIL PROTECTED]: Command died with status 2:
snip
What are the perms on /usr/local/mailman/mail/mailman? Postfix
should
be executing the script as whatever group the wrapper has.
- --
ToddOpenPGP - KeyID: 0xD654075A | URL:
www.pobox.com/~tmz/pgp
/snip
-rwxr-sr-x1 mailman mailman 37699 Nov 24 10:38
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Gilbert wrote:
snip
What are the perms on /usr/local/mailman/mail/mailman? Postfix
should be executing the script as whatever group the wrapper has.
[...]
-rwxr-sr-x1 mailman mailman 37699 Nov 24 10:38
On 24 Nov 2003, at 17:25, Todd wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Gilbert wrote:
I'm having a hell of a time getting this working, but I keep
coming back to this problem. I get this back whenever I send
e-mail to a list address.
[EMAIL PROTECTED]: Command died with
Your interpretation is not quite correct.
When it is run, and as a security precaution, the mailman
wrapper
checks the group of the process which is executing it is what it
expects and then and only then runs the mail delivery script
with the
mailman gid. This expected gid is compiled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Barrett wrote:
On 24 Nov 2003, at 17:25, Todd wrote:
What are the perms on /usr/local/mailman/mail/mailman? Postfix
should be executing the script as whatever group the wrapper has.
Your interpretation is not quite correct.
When it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Gilbert wrote:
Okay, great. I'm not sure about your explanation, but when I
changed all the aliases and aliases.db files on my system to
mailman:mailman ownership, everything is finally working. By your
explanation, Postfix must be
hello,
I've one problem with the wrapper. When I use the command :
/usr/lib/mailman/mail/wrapper post list-toto
the log is :
Cannot read wrapper configuration file.
What's the solution ? I can't find it.
I use mailman 2.0.13-60 with postfix.
alex.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SoloCDM wrote:
- Transcript of session follows -
Failure to exec script. WANTED gid 65534, GOT gid 12. (Reconfigure
to take 12?)
554 5.3.0 unknown mailer error 2
[...]
Where did I go wrong?
You need to reconfigure mailman to use the
I am trying to use exim with mailman. I've followed the directions at
http://mail.python.org/pipermail/mailman-users/2002-November/
024041.html , but changing MAILMAN_WRAP=/usr/local/mailman/mail/wrapper
to MAILMAN_WRAP=/var/mailman/mail/mailman and changing the various
instances of
I've got same problem, did you found some solutions ???
-Message d'origine-
De : Joel Glickman [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 5 décembre 2002 15:43
À : [EMAIL PROTECTED]
Objet : [Mailman-Users] wrapper executing, but doing NOTHING
- Running RH7.2, sendmail, mailman 2.0.12
Greetings.
I receive an email which I pass to the mailman wrapper with the
following command:
cat reply1.txt | /var/mailman/mail/wrapper mailcmd testa
reply1.txt is a text file containing the message of a reply to a
subscribtion notice. But wrapper does not seem to do anything. The
- Running RH7.2, sendmail, mailman 2.0.12
- mailman user group exist -- /home/mailman exists with correct permissions
- ./configure --with-mail-gid=mail --with-cgi-gid=apache, (When
configuration script runs, it properly converts mail to 12 and apache to
48, which reflect what's in my
Joel Glickman wrote:
Anyone have any advice? I've RTFM'd and think I've done everything right?
You didn't RTFM the ENTIRE installation file. Nowhere do you mention anything
of the crontab that you're supposed to install for Mailman to work.
--
H | I haven't lost my mind; it's backed up
- Running RH7.2, sendmail, mailman 2.0.12
- mailman user group exist -- /home/mailman exists with correct permissions
- ./configure --with-mail-gid=mail --with-cgi-gid=apache, (When
configuration script runs, it properly converts mail to 12 and apache to
48, which reflect what's in my
Well, the problem is solved. I said that I RTFM'd and did everything
correctly. Well ... I did, in terms of configuring and installing the
mailman binaries .. my problem is that I didn't read the whole manual .. I
missed this line -- - IMPERATIVE! IMPORTANT! DO THIS! YOU'LL BE SORRY IF
Hi Guys
The wrapper is not sending mail to the users right away. I
get digested messages, even though my settings say otherwise.
There is no error in the maillog, it says message sent.
But if I look at logs from mailman its a different
story
--Post Log
Nov 11 12:28:02 2002 (30098)
Someone remind me how to fix this...
MM 2.1b3/postfix mta
getting this error after what looked like a sucessful upgrade...
-- Command died with status 1:
/var/www/mailman/mail/wrapper post camelid
Medical Fact: Realistic expectation can provide complete relief
from frequent disappointment.
- Original Message -
From: Philip White [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 16, 2002 12:48 AM
Subject: [Mailman-Users] wrapper not available for sendmail?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I created the a etc-officers mailing list, but when I
On Mon, 15 Jul 2002, Philip White wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I created the a etc-officers mailing list, but when I try to subscribe
to it from a different e-mail address, here's what I get in response to
my confirmation reply:
~ - The following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I created the a etc-officers mailing list, but when I try to subscribe
to it from a different e-mail address, here's what I get in response to
my confirmation reply:
~ - The following addresses had permanent fatal errors -
Ok, it took a good bit of tinkering, but I managed to get exim and mailman
installed and working... almost. So far, everything works up untill I try to
join a list. I get the email to verify, I reply, but then Mail Delivery
System from my server computer sends me an email saying...
This
I installed mailman on our web server ( that is configured also like
mail server).
Everything looks OK.
When i try to send a message to a mailinglist I get:
list_name... aliased to :|export/mailman/mail/wrapper post name_lis
|/export/mailman/mail/wrapper post list_name... Connecting to
On Tue, Jun 11, 2002 at 01:49:18PM -0400, Tracy Snell wrote:
Just needed to install the cron jobs. Didn't realize they were needed for
delivery. All is well now. Running virtual domains, it all is working as
advertised.
What do you mean?
I executed crontab crontab.in and when I check crons
On Tuesday 25 June 2002 04:14 pm, Gour wrote:
On Tue, Jun 11, 2002 at 01:49:18PM -0400, Tracy Snell wrote:
Just needed to install the cron jobs. Didn't realize they were needed for
delivery. All is well now. Running virtual domains, it all is working as
advertised.
What do you mean?
I
On Tue, Jun 11, 2002 at 01:49:18PM -0400, Tracy Snell wrote:
Just needed to install the cron jobs. Didn't realize they were needed for
delivery. All is well now. Running virtual domains, it all is working as
advertised.
What do you mean?
I executed: crontab crontab.in and when I check crons
Hello
My name is Camelia Botez and I'm system admin in Weizmann Institute.
I installed mailman on our web server that runs also like mail server.
Everything looks nice but when I send mail to one of the lists
,I don't get any error message , but the mail doesn't go to the users
from the list.
On 6/11/02 1:35 PM, Gour [EMAIL PROTECTED] wrote:
I can just confirm that I have the same problem, but so far didn't get
any reply hot to resolve it.
I also have Mailman 2.0.11 plus htdig patch.
Just needed to install the cron jobs. Didn't realize they were needed for
delivery. All is well
I just installed mailman. Perms check out OK. Web interface works fine. I go
to the subscribe page and sign up for my test list. I get the e-mail. When I
reply to it Postfix shows that it's delivered to wrapper with no error. From
there it disappears. No error in any logs that I can find.
On Tue, Jun 11, 2002 at 10:18:28AM -0400, Tracy Snell wrote:
I just installed mailman. Perms check out OK. Web interface works fine. I go
to the subscribe page and sign up for my test list. I get the e-mail. When I
reply to it Postfix shows that it's delivered to wrapper with no error. From
On Tuesday 11 June 2002 10:25 am, Tracy Snell wrote:
I just installed mailman. Perms check out OK. Web interface works fine. I
go to the subscribe page and sign up for my test list. I get the e-mail.
When I reply to it Postfix shows that it's delivered to wrapper with no
error. From there it
Did you setup your Aliases? :)
Jim Hale
---
http://hale.dyndns.org
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Tracy Snell
Sent: Tuesday, June 11, 2002 9:18 AM
To: [EMAIL PROTECTED]
Subject: [Mailman-Users] Wrapper problems
I just installed
Did you run newaliases after adding the wrapper aliases to
your /etc/aliases file?
-ben
On Thu, May 09, 2002 at 10:07:53PM -0700, David Burrows wrote:
Please help a new kid on the block..
I have Mailman GUI working fine, but get the following message when I try to
subscribe or send any mail
Please help a new kid on the block..
I have Mailman GUI working fine, but get the following message when I try to
subscribe or send any mail to the list..
The following addresses had permanent fatal errors -
|/var/mailman/mail/wrapper mail
(expanded from: [EMAIL PROTECTED])
tia,
David
On Thu, May 09, 2002 at 10:07:53PM -0700, David Burrows wrote:
Please help a new kid on the block..
I have Mailman GUI working fine, but get the following message when I try to
subscribe or send any mail to the list..
The following addresses had permanent fatal errors -
At 05:59 PM 4/23/02 +0200, E.J.L. Kemper wrote:
Ok, you got a point there!
So I reinstalled it again.
./configure no errors.
but make install, after a very close look gave this...
snip-
make[1]: Entering directory `/unpack/mailman-2.0.9/src'
gcc -c -I. -DPREFIX=\/home/mailman\
PROTECTED]
To: E.J.L. Kemper [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, April 22, 2002 8:10 PM
Subject: Re: [Mailman-Users] wrapper
At 11:24 AM 4/22/02 +0200, E.J.L. Kemper wrote:
Hi again,
I am using 2.09 BTW
I re-installed the whole program several times, starting with MAKE CLEAN
Hi again,
I am using 2.09 BTW
I re-installed the whole program several times, starting with MAKE CLEAN
then removing the directory.
So really from scratch?
Then
reinstall. Because the error below is very self explanatory - an
essential
piece of mailman simply isn't where you told
At 11:24 AM 4/22/02 +0200, E.J.L. Kemper wrote:
Hi again,
I am using 2.09 BTW
I re-installed the whole program several times, starting with MAKE CLEAN
then removing the directory.
So really from scratch?
Did you also delete everything under /home/mailman?
What are you feeding as
At 05:29 PM 4/20/02 +0200, E.J.L. Kemper wrote:
Hi everyone,
can anyone please tell me what I should do when I see this?
Honestly, what you need to do is delete your installed mailman config,
(save mm_cfg.py if you edited it), and go through and reverify your
settings to configure. Verify
Hi everyone,
can anyone please tell me what I should do when I see this?
snip---
Traceback (innermost last):
File bin/check_perms, line 281, in ?
checkmail()
File bin/check_perms, line 202, in checkmail
mode = statmode(wrapper)
File bin/check_perms, line 74, in statmode
Hi there!
I'm a total newbie, the newest kind... I installed Mailman under
Netmax-linux (Based on RH6) and got the follwing problem, which I even found
in the FAQ:
Problem: I send mail to the list, and get back mail saying, sh: wrapper not
available for sendmail programs
Solution: Your
Hi,
am I missing something?
in $prefix, wrapper is not made by MAKE INSTALL ??
I am trying to install Mailman 2.09.
Greetings
Erik
--
Mailman-Users mailing list
[EMAIL PROTECTED]
Title: wrapper seems to not be sgid'ing..
Am trying to run mailman v2.0.8 with postfix on SuSE v7.2. Am
getting the error at the bottom of the page. I've rebuilt, installed
and configured mailman. I built it using the correct gid values for
mail and cgi.
I ran the check_perms and when it's
On Tue, 12 Feb 2002, Mark Ash wrote:
Am trying to run mailman v2.0.8 with postfix on SuSE v7.2. Am getting
the error at the bottom of the page. I've rebuilt, installed and
configured mailman. I built it using the correct gid values for mail
and cgi.
I ran the check_perms and when it's
Title: wrapper
Hi all,
I am quite new to mailman, but an experienced mailing list admin. I have been running MJ for a couple of years and I now want to move on to MM.
[ I am not sure I am allowed to use the s u b s c r i b e or u n s u b words here, some lists have low tolerance to admin
Title: Wrapper problem (?)
(This may be a repeat, since I got a bounce notification, excuse me if this is the case)
Hi all,
I am quite new to mailman, but an experienced mailing list admin. I have
been running MJ for a couple of years and I now want to move on to MM.
[ I am not sure I
Title: Wrapper problems (I think)
(This may be a repeat of a repeat :-), since I got another bounce notification, excuse me if this is the case)
Hi all,
I am quite new to mailman, but an experienced mailing list admin. I have
been running MJ for a couple of years and I now want to move on
I have installed mailman-2.1a4 from CVS and all
appears to work ok, but now, I send a message to the
list and I get the follow error:
Hi. This is the qmail-send program at myhost.com.
I'm afraid I wasn't able to deliver your message to
the following addresses.
This is a
On Wed, 16 Jan 2002 12:51:04 -0500
Jon Parise [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:
preline: fatal: unable to
run /home/mailman/mail/wrapper: file does not exist
s/wrapper/mailman/
Jon Parise ([EMAIL PROTECTED]) . Information Technology (2001)
On Wed, Jan 16, 2002 at 03:50:35PM -0200, Ana Paula wrote:
run /home/mailman/mail/wrapper: file does not exist
s/wrapper/mailman/
Sorry, but I don't understand what you want to say with:
s/wrapper/mailman/
Replace /home/mailman/mail/wrapper with
/home/mailman/mail/mailman in your
On Wed, 16 Jan 2002 12:58:47 -0500
Jon Parise [EMAIL PROTECTED] wrote:
Sorry, but I don't understand what you want to say with:
s/wrapper/mailman/
Replace /home/mailman/mail/wrapper with
/home/mailman/mail/mailman in your aliases file.
Jon Parise ([EMAIL PROTECTED]) . Information
Hi,
Logfile :
** [EMAIL PROTECTED] D=list_request_director
T=list_request_transport: Child process of list_request_transport transport
returned 2 from command: /home/mailman/mail/wrapper
I do not know what returned 2 means... therefore no idea on how to fix...
I'm using exim +
Hi,
Logfile :
** [EMAIL PROTECTED] D=list_request_director
T=list_request_transport: Child process of list_request_transport transport
returned 2 from command: /home/mailman/mail/wrapper
There's almost certainly a corresponding error in ~mailman/logs/error
On 05 October 2001, stormlrd said:
Hi,
Logfile :
** [EMAIL PROTECTED] D=list_request_director
T=list_request_transport: Child process of list_request_transport transport
returned 2 from command: /home/mailman/mail/wrapper
I do not know what returned 2 means... therefore no idea
mailman-2.0.5.tar.gz
Python 1.5.2 (#1, Feb 1 2000, 16:32:16)
mta - right now Sendmail, will be iPlanet Messaging Server
os - Linux
I ran configure with --with-mail-gid and set correctly, after not doing
that the first time. :)
The problem I'm having is that mail addressed to [EMAIL
-Original Message-
From: Shannon Anderson [mailto:[EMAIL PROTECTED]]
OK I got the list-request wrapper to work by creating a Alias to it in
sendmail
(logical not exact wordings)
list-request = Sendtoprogram /etc/smrsh/mailman_wrapper
mailcmd listname
and now do the
Hi all,
First time caller longtime listener,
Well... Not really but ok...
I am having some wrapper problems as it seems send mail dose not like the
way I have it setup
I suspect that I have a argument missing.
Quote from email:-- The following addresses had permanent fatal
errors
OK I got the list-request wrapper to work by creating a Alias to it in
sendmail
(logical not exact wordings)
list-request = Sendtoprogram /etc/smrsh/mailman_wrapper mailcmd listname
and now do the same thing but change mailcmd to post? for the listname
wrapper.
Now is there a way built in
hello all,
i've installed mailman, it seem working fine until
i send a message to my mailing list,
then i got this error message back,
= - The following
addresses had permanent fatal errors -"|/home/mailman/mail/wrapper post
mylist2" (reason: service
unavailable) (expanded
Your sendmail is configured to use smrsh (likely via your
sendmail.mc and hence sendmail.cf), and your cgi wrapper for
mailman isn't included in the directory that holds executables allowed to
run under smrsh. There are basically 2 ways to get around thisdisable
smrsh in sendmail
I've just installed version 2.0.3 and was well impressed with just how easy
the install was: second time lucky after having to readjust the GID for my
apache web server, but that's one hell of a lot quicker than when I
attempted majordomo.
I do need some help however: I still have majordomo
I'm working on a new mailman qmail install. I've got everything pretty
much down except for this.
I did configure mailman with group 1, but its still giving this errorany
help will be greatly appreciated.
Thanks!
Chris
Mar 13 13:01:05 -hostmame qmail: 984506465.629587 starting delivery
77 matches
Mail list logo
