[Mailman-Users] Messages not being delivered

[Peter W. Caton]

I have just setup a new Mailman server on Ubuntu.

With the help of list members, I have got the web GUI working.

Now, I have discovered that when I send new messages to the one list I have, 
e-mails are not being delivered.

I did receive the initial e-mail that the list was setup.  However, none of the 
list members are receiving any new e-mails posted to the list.

I have checked the Archives, and no messages are being received (No messages 
have been posted to this list yet, so the archives are currently empty).

Here is what I see in the mail.log:

Recipient address rejected: User unknown in local recipient table

Any thoughts on how to fix this issue?

Thank you.

Peter W. Caton
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Messages not being delivered

[Mark Sapiro]

On 02/05/2016 11:02 AM, Peter W. Caton wrote:
> 
> Here is what I see in the mail.log:
> 
> Recipient address rejected: User unknown in local recipient table

You don't have aliases and/or virtual mappings set up in your MTA. See
item 3) in the FAQ at .

Note: if your MTA is Postfix, alias generation and virtual mapping
generation if required can be automated. See
.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Messages are not delivered to list members...

[Andrei]

Oh, I just noticed that owners are never notified when new list is
created. I'm confused.

Help?



On Mon, Aug 31, 2009 at 8:31 PM, Andreifunactivit...@gmail.com wrote:
 I can create a list, send emails to the list, I can even go to list
 archives to view messages, but the same messages never get sent to
 list members. List has default settings (no moderation or anything
 like that). I don't know how to troubleshoot this. Any help would be
 appreciated.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Messages are not delivered to list members...

[Andrei]

I've been at this for three hours now and still no luck.

I do have MTA = None in mm_cfg.py
bin/newlist gives me Hit enter to notify %(listname)s owner...' prompt
but the owner never gets a message.
There is nothing /var/log/mailman/error

When I try to telnet on port 25 from outside (different public
network) the connection times out.
When I try to telnet from the server on port 25 I get standard SMTP greeting.





On Mon, Aug 31, 2009 at 9:16 PM, Andreifunactivit...@gmail.com wrote:
 Oh, I just noticed that owners are never notified when new list is
 created. I'm confused.

 Help?



 On Mon, Aug 31, 2009 at 8:31 PM, Andreifunactivit...@gmail.com wrote:
 I can create a list, send emails to the list, I can even go to list
 archives to view messages, but the same messages never get sent to
 list members. List has default settings (no moderation or anything
 like that). I don't know how to troubleshoot this. Any help would be
 appreciated.


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Messages are not delivered to list members...

[Andrei]

I can send and receive emails from the command line from this server.
I assume that means exim4 is working fine. This must be a mailman
issue. I just don't know how to troubleshoot this. Arrgh...



On Mon, Aug 31, 2009 at 10:16 PM, Andreifunactivit...@gmail.com wrote:
 I've been at this for three hours now and still no luck.

 I do have MTA = None in mm_cfg.py
 bin/newlist gives me Hit enter to notify %(listname)s owner...' prompt
 but the owner never gets a message.
 There is nothing /var/log/mailman/error

 When I try to telnet on port 25 from outside (different public
 network) the connection times out.
 When I try to telnet from the server on port 25 I get standard SMTP greeting.





 On Mon, Aug 31, 2009 at 9:16 PM, Andreifunactivit...@gmail.com wrote:
 Oh, I just noticed that owners are never notified when new list is
 created. I'm confused.

 Help?



 On Mon, Aug 31, 2009 at 8:31 PM, Andreifunactivit...@gmail.com wrote:
 I can create a list, send emails to the list, I can even go to list
 archives to view messages, but the same messages never get sent to
 list members. List has default settings (no moderation or anything
 like that). I don't know how to troubleshoot this. Any help would be
 appreciated.



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Users] Messages are not delivered to list members...

[Andrei]

I can create a list, send emails to the list, I can even go to list
archives to view messages, but the same messages never get sent to
list members. List has default settings (no moderation or anything
like that). I don't know how to troubleshoot this. Any help would be
appreciated.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Messages are not delivered to list members...

[Mark Sapiro]

Andrei wrote:

I can send and receive emails from the command line from this server.
I assume that means exim4 is working fine. This must be a mailman
issue. I just don't know how to troubleshoot this. Arrgh...


Have you resolved your

Error  Aug 31 16:11:17 2009 (15875) delivery to
enews-ow...@lists.myfqd.org failed with code -1: (111, 'Connection
refused')

error?

See the troubleshooting FAQ at http://wiki.list.org/x/A4E9 and also
the FAQ at http://wiki.list.org/x/-IA9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Messages are not delivered to list members...

[Adam McGreggor]

(if you expect an answer from me, please don't top-post)

On Mon, Aug 31, 2009 at 10:37:01PM -0700, Andrei wrote:
 I can send and receive emails from the command line from this server.
 I assume that means exim4 is working fine. This must be a mailman
 issue. I just don't know how to troubleshoot this. Arrgh...

From your mails, you don't mention how you've set things up.

Have a look at http://exim.org/howto/mailman21.html#lisver and
report back on the responses: *not* obscurating your domain(s) may be
useful in this case.

It may also be useful to look through Exim's logfiles.

-- 
``Eden may have invaded Egypt, but one can't be too censorious, everybody gets
  a bit silly when they're stoned.'' (Jeremy Scott, from `Fast and Louche')
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Users] Messages are not delivered?

[Mohammad Reza jamshidian]

Dear friends,
I have made a mailing list by Mailman. I tested that by subscribing 3 emails 
and sent email to the list.
All the emails delivered.
After I subscribed about 20,000 people to list, I tried again to send another 
post.
The post is not delivered to none of my colleagues emails!! and I guess it must 
not be delivered no where else.
I am in hurry to send email to the users to announce an exhibition.
Anybody can help?
Best for all,
Mohammad





 

Need Mail bonding?
Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=listsid=396546091
--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Messages are not delivered?

[Mark Sapiro]

Mohammad Reza jamshidian wrote:

I have made a mailing list by Mailman. I tested that by subscribing 3 emails 
and sent email to the list.
All the emails delivered.
After I subscribed about 20,000 people to list, I tried again to send another 
post.
The post is not delivered to none of my colleagues emails!! and I guess it 
must not be delivered no where else.


Look in Mailman's 'smtp', 'smtp-failure' and 'error' logs.

See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Messages not being delivered.

[Brad Knowles]

On 7/15/07, Brandon Slaten wrote:

  Some additional information:

  The old server:

  Using Mailman version: 2.1.6

[ ... deletia ... ]

  The new server:

  Using Mailman version: 2.1.5

With regards to software in general, moving backward in the version 
number scheme is problematic.  Can you upgrade the new machine to a 
more recent version, like 2.1.9?

-- 
Brad Knowles [EMAIL PROTECTED], Consultant  Author
LinkedIn Profile: http://tinyurl.com/y8kpxu
Slides from Invited Talks: http://tinyurl.com/tj6q4

09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Messages not being delivered.

[Mark Sapiro]

Brandon Slaten wrote:

I just moved our Mailman lists to a new server.  Accessing the listinfo
and admin pages works fine.  After creating a new list mail sent to that
list is delivered.  However mail set to the old lists, the ones that
were moved to this server, is not delivered.


What happens to mail to the old lists (after delivery to Mailman - see
below)?


See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp.


I do however get moderation and bounce notices from those lists.  I ran
check_perms to see if there were any problems with permissions and got
the following:

file permissions must be at least 660:
/var/lib/mailman/lists/ofap_mgrs/config.db (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/config.db (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/config.db.last (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/next-digest (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/next-digest-topics (fixing)


The log entry below (delivered to command:
/usr/lib/mailman/mail/mailman post listname) says you are running
Mailman 2.1.x. These residual 2.0.x files were converted to config.pck
and digest.mbox files when the installation was upgraded to 2.1. They
should now be deleted (assuming they are old and there are current
config.pck* files.


I also have this from the logs.

Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B:
from=[EMAIL PROTECTED], size=629, nrcpt=1 (queue active)
Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from
host2.atd.ucar.edu[128.117.80.16]
Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B:
to=[EMAIL PROTECTED], relay=local, delay=0, status=sent
(delivered to command: /usr/lib/mailman/mail/mailman post listname)
Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed


Assuming 'listname' above is one of the affected lists, the message is
being delivered to Mailman so the Postfix Aliases are OK. Refer to the
FAQ above (items 6-8 in particular) for other things which might be
wrong.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Messages not being delivered.

[Brandon Slaten]

Some additional information:

The old server:

Using Mailman version: 2.1.6
Compiled from src.
SunOS 5.8 Generic_117350-14 sun4u sparc SUNW,Ultra-4

The new server:

Using Mailman version: 2.1.5
Installed from mailman-2.1.5.1-34.rhel4.5
Linux 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:59:08 EDT 2007 i686 i686
i386 GNU/Linux

Since it looks like the mail server is handing off to the mailman
script, I have been looking for some sort of log or error messages in
the various system logs, with out luck so far.


Brandon Slaten wrote:
 Greetings,
 
 Thanks for any time you can give this problem.
 
 I just moved our Mailman lists to a new server.  Accessing the listinfo
 and admin pages works fine.  After creating a new list mail sent to that
 list is delivered.  However mail set to the old lists, the ones that
 were moved to this server, is not delivered.
 
 I do however get moderation and bounce notices from those lists.  I ran
 check_perms to see if there were any problems with permissions and got
 the following:
 
 file permissions must be at least 660:
 /var/lib/mailman/lists/ofap_mgrs/config.db (fixing)
 file permissions must be at least 660:
 /var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing)
 file permissions must be at least 660:
 /var/lib/mailman/lists/python/config.db (fixing)
 file permissions must be at least 660:
 /var/lib/mailman/lists/python/config.db.last (fixing)
 file permissions must be at least 660:
 /var/lib/mailman/lists/python/next-digest (fixing)
 file permissions must be at least 660:
 /var/lib/mailman/lists/python/next-digest-topics (fixing)
 
 A second run showed no errors yet still not message being delivered when
 sent to the older lists.
 
 I also have this from the logs.
 
 Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B:
 from=[EMAIL PROTECTED], size=629, nrcpt=1 (queue active)
 Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from
 host2.atd.ucar.edu[128.117.80.16]
 Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B:
 to=[EMAIL PROTECTED], relay=local, delay=0, status=sent
 (delivered to command: /usr/lib/mailman/mail/mailman post listname)
 Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed
 
 
 --
 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: http://www.mail-archive.com/mailman-users%40python.org/
 Unsubscribe: 
 http://mail.python.org/mailman/options/mailman-users/brandon%40ucar.edu
 
 Security Policy: 
 http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Messages not being delivered.

[Mark Sapiro]

Brandon Slaten wrote:

Mark Sapiro wrote:
 Brandon Slaten wrote:

~mailman - /usr/lib/mailman

There is no lock, qfiles, or log directories there to look at to assess
items 6-8 in the link above.


In redhat 2.1.5, they may be in /var/mailman

(see below)


I did find the mentioned mailman logs in /var/logs/mailman  Here is the
most recent entry in the errors log.  atd_systems_notes is one of the
lists moved over from the old server and one I have been testing with.

Jul 15 08:38:21 2007 (26407) No such list aa-optical:
Jul 15 08:40:42 2007 (26482) No such list aa-hygro-growth:
Jul 15 08:52:45 2007 (26737) No such list aa-phys-size:
Jul 15 09:02:44 2007 (27140) No such list aa-satellite:
Jul 15 09:09:19 2007 (4397) Uncaught runner exception: [Errno 13]
Permission denied:'/var/lib/mailman/lists/atd_systems_notes/digest.mbox'
Jul 15 09:09:19 2007 (4397) Traceback (most recent call last):
  File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
  File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
  File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 76, in process
mboxfp = open(mboxfile, 'a+')
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/lists/atd_systems_notes/digest.mbox'

Jul 15 09:09:19 2007 (4397) SHUNTING:
1184512159.0603149+56cd041d3f9dcb1c15807c25c069d965
53d266da
Jul 15 09:22:48 2007 (27873) No such list aa-model:
Jul 15 09:31:34 2007 (28149) No such list esigupcoming:


The permissions on the digest.mbox seems to be the issue, after changing
it to be the same as the digest.mbox for the newly created list (660)
all seems to be working.  I am surprised that the check_perms script did
not catch that.


It's a recently discovered bug in check_perms fixed for 2.1.10. See
http://mail.python.org/pipermail/mailman-users/2007-June/057487.html.

You can now run bin/unshunt to reprocess the shunted messages, but
first look at the files in qfiles/shunt to make sure there aren't
unwanted stale messages there. You can use bin/dumpdb or
bin/show_qfiles (although there is a bug in 2.1.5 show_qfiles that
affects some entries, but probably not these) to look at the
individual *.pck files in qfiles/shunt and can just remove unwanted
ones before running bin/unshunt.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

Re: [Mailman-Users] Messages not being delivered.

[Mark Sapiro]

Mark Sapiro wrote:

Brandon Slaten wrote:

Mark Sapiro wrote:
 Brandon Slaten wrote:

~mailman - /usr/lib/mailman

There is no lock, qfiles, or log directories there to look at to assess
items 6-8 in the link above.


In redhat 2.1.5, they may be in /var/mailman


But OTOH, the fact that the lists are in /var/lib/mailman/lists/* and
The python Modules are in /usr/lib/mailman/Mailman says that this is
RedHat's FHS compliant scheme.

There should be an INSTALL.REDHAT document somewhere in your
installation that tells you how to map various old RedHat locations
(mostly /var/mailman/*) into the FHS locations.

If you can't find this document, the mapping is in the online version
at
http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/mailman/F-7/mailman.INSTALL.REDHAT.in
and also in a post at
http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

[Mailman-Users] Messages not being delivered.

[Brandon Slaten]

Greetings,

Thanks for any time you can give this problem.

I just moved our Mailman lists to a new server.  Accessing the listinfo
and admin pages works fine.  After creating a new list mail sent to that
list is delivered.  However mail set to the old lists, the ones that
were moved to this server, is not delivered.

I do however get moderation and bounce notices from those lists.  I ran
check_perms to see if there were any problems with permissions and got
the following:

file permissions must be at least 660:
/var/lib/mailman/lists/ofap_mgrs/config.db (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/config.db (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/config.db.last (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/next-digest (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/next-digest-topics (fixing)

A second run showed no errors yet still not message being delivered when
sent to the older lists.

I also have this from the logs.

Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B:
from=[EMAIL PROTECTED], size=629, nrcpt=1 (queue active)
Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from
host2.atd.ucar.edu[128.117.80.16]
Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B:
to=[EMAIL PROTECTED], relay=local, delay=0, status=sent
(delivered to command: /usr/lib/mailman/mail/mailman post listname)
Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed


--
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: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp

[Mailman-Users] Messages not being delivered to lists

[Dunham, Kathy M]

  

Hello,

We recently installed mailman on HPUX 11.0. I have not had trouble
creating a list but when I attempt to post to the list the following
error message is returned:

 [EMAIL PROTECTED] on 12/3/2004 12:55 PM

The e-mail system was unable to deliver the message, but did not report
a specific reason. Check the address and try again. If it still fails,
contact your system administrator.

 ccshp.uccs.csus.edu #5.0.0

The syslog entry is as follows:

Dec 3 12:55:12 ccshp sendmail[22690]: iB3KtCj22690:
from=[EMAIL PROTECTED], size=1226, class=0, nrcpts=1,
msgid=E1EC56D4EA243D4CB4CC720B9F2A2547A763

[EMAIL PROTECTED], proto=ESMTP, daemon=MTA,
relay=sl3a.saclink.csus.edu[130.86.80.50]

Dec 3 15:55:12 ccshp Mailman mail-wrapper: Group mismatch error. Mailman
expected the mail Dec 3 12:55:12 ccshp sendmail[22691]: iB3KtCj22690:
to=|/usr/local/mailman/mail/mailman post Kdtest,
ctladdr=[EMAIL PROTECTED] (1/0), delay=00:00:

00, xdelay=00:00:00, mailer=prog, pri=30699, dsn=5.3.0, stat=unknown
mailer error 2 Dec 3 12:55:12 ccshp sendmail[22691]: iB3KtCj22690:
iB3KtCj22691: DSN: unknownmailer error 2 Dec 3 12:55:12 ccshp
sendmail[22691]: iB3KtCj22691: to=[EMAIL PROTECTED],
delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=30799,
relay=filter.csus.edu. [130.86.82.249], dsn=2.0.0, stat=Sent (Ok: queued
as 73BB3D000149)

I noticed the timestamp conflict in the log but I can't tell where the
inconsistent time is coming from. Can anyone tell me what is wrong and
what we need to do?

Thank you!

Kathy Dunham
CSU, Sacramento

--
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: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Messages not being delivered to lists

[Brad Knowles]

At 10:28 AM -0800 2005-01-05, Dunham, Kathy M wrote:
 Dec 3 15:55:12 ccshp Mailman mail-wrapper: Group mismatch error. Mailman
 expected the mail Dec 3 12:55:12 ccshp sendmail[22691]: iB3KtCj22690:
 to=|/usr/local/mailman/mail/mailman post Kdtest,
 ctladdr=[EMAIL PROTECTED] (1/0), delay=00:00:
	If you go to the Mailman FAQ Wizard at 
http://www.python.org/cgi-bin/faqw-mm.py and search for group 
mismatch, you should get your answer.

	This general solution applies for most common problems with 
Mailman -- try searching the FAQ Wizard first, then follow the 
instructions at 
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.018.htp 
to search the archives of the mailman-users mailing list.

--
Brad Knowles, [EMAIL PROTECTED]
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
  SAGE member since 1995.  See http://www.sage.org/ for more info.
--
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: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] messages aren't being delivered to users,but are in the archive

[jacob walcik]

alright, upgraded to 2.1.2 as per the recommendation in the original 
response.  same problem continues, but now i've actually got error 
messages from the logs to share.

from logs/smtp:
Jun 25 10:23:12 2003 (11504) All recipients refused: (111, 'Connection 
refused')
Jun 25 10:23:12 2003 (11504) All recipients refused: please run 
connect() first
Jun 25 10:23:12 2003 (11504) 
[EMAIL PROTECTED] smtp for 2 
recips, completed in 0.037 seconds

from Defaults.py (not overridden in mm_cfg.py):
SMTPHOST = 'localhost'
and
DELIVERY_MODULE = 'SMTPDirect'
where is the All recipients refused message coming from?  postfix's 
log shows the message going through just fine:
Jun 25 10:23:12 dastardly postfix/local[11553]: B03606000E: 
to=[EMAIL PROTECTED], relay=local, delay=1, status=sent 
(|/usr/local/mailman/mail/mailman post test)

On Tuesday, Jun 24, 2003, at 17:19 US/Central, Richard Barrett wrote:

At 22:08 24/06/2003, jacob walcik wrote:
yup, the mailman user's crontab was installed as part of the rpm
installation, and i've also tried running qrunner manually w/ the
command it's issuing, and i don't receive any errors.
assuming mailman's home is /var/mailman, where would i look for the
qfiles file.  a find ./ -name qfiles -print from /var/mailman
doesn't return anything.
Given your install in /var/mailman and a normal MM 2.0.x install there 
should be a directory called /var/mailman/qfiles. The script in 
/var/mailman/scripts takes delivery of incoming messages from the MTA 
creates a .msg and a .db file in that directory. The qrunner 
subsequently takes those files and processes them, sending mail out 
etc.

The actual qfiles directory used for enqueueing incoming messages is 
defined by the config variable QUEUE_DIR in $prefx/Mailman/Defaults.py 
or possibly (and unusually) overridden $prefix/Mailman/mm_cfg.py. If 
that directory doesn't exist then something in your install may be 
screwed.

But looking again at your original post you say the message is getting 
into the archives. That says the message is passing through qfiles, 
being picked up by the qrunner and so you would expect there to be 
some trace of its progress in one of Mailman's log files.

But you say the directory says $prefix/logs doesn't exist. The log 
file directory is defined by the config variable LOG_DIR in 
$prefix/Mailman/Defaults.py or possibly (and unusually) overridden 
$prefix/Mailman/mm_cfg.py. If that directory doesn't exist then 
something in your install may be screwed.

What value does the config variable DELIVERY_MODULE in 
$prefix/Mailman/Defaults.py or possibly overridden 
$prefix/Mailman/mm_cfg.py have and also SMTPHOST.

Are there are no logs and no sign of what is happening exists in MM's 
error, post, smtp and smtp-failure logs.
--
jacob walcik
[EMAIL PROTECTED]
--
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] messages aren't being delivered to users,but are in the archive

[Richard Barrett]

At 16:39 25/06/2003, jacob walcik wrote:
alright, upgraded to 2.1.2 as per the recommendation in the original 
response.  same problem continues, but now i've actually got error 
messages from the logs to share.

from logs/smtp:
Jun 25 10:23:12 2003 (11504) All recipients refused: (111, 'Connection 
refused')
Jun 25 10:23:12 2003 (11504) All recipients refused: please run connect() 
first
Jun 25 10:23:12 2003 (11504) 
[EMAIL PROTECTED] smtp for 2 recips, 
completed in 0.037 seconds

from Defaults.py (not overridden in mm_cfg.py):
SMTPHOST = 'localhost'
and
DELIVERY_MODULE = 'SMTPDirect'
where is the All recipients refused message coming from?  postfix's log 
shows the message going through just fine:
Jun 25 10:23:12 dastardly postfix/local[11553]: B03606000E: 
to=[EMAIL PROTECTED], relay=local, delay=1, status=sent 
(|/usr/local/mailman/mail/mailman post test)
This mail log entry apparently shows the delivery of the incoming message 
to Mailman.

The MM post log entry seems to be saying that MM could not make a 
connection in order to send _out_ a message to the list's subscribers. 
There may also be a message in the MM smtp-failure log.

You can find out what MM is trying to use for outbound message transport by 
looking in $prefix/Mailman/Defaults.py unless you have overridden these by 
assignments in $prefix/Mailman/mm_cfg.py. Usual defaults are:

DELIVERY_MODULE = 'SMTPDirect'

SMTPHOST = 'localhost'

The error reported seems to indicate that Mailman is having trouble 
connecting to whatever outgoing mail server it is trying to communicate with..


On Tuesday, Jun 24, 2003, at 17:19 US/Central, Richard Barrett wrote:

At 22:08 24/06/2003, jacob walcik wrote:
yup, the mailman user's crontab was installed as part of the rpm
installation, and i've also tried running qrunner manually w/ the
command it's issuing, and i don't receive any errors.
assuming mailman's home is /var/mailman, where would i look for the
qfiles file.  a find ./ -name qfiles -print from /var/mailman
doesn't return anything.
Given your install in /var/mailman and a normal MM 2.0.x install there 
should be a directory called /var/mailman/qfiles. The script in 
/var/mailman/scripts takes delivery of incoming messages from the MTA 
creates a .msg and a .db file in that directory. The qrunner subsequently 
takes those files and processes them, sending mail out etc.

The actual qfiles directory used for enqueueing incoming messages is 
defined by the config variable QUEUE_DIR in $prefx/Mailman/Defaults.py or 
possibly (and unusually) overridden $prefix/Mailman/mm_cfg.py. If that 
directory doesn't exist then something in your install may be screwed.

But looking again at your original post you say the message is getting 
into the archives. That says the message is passing through qfiles, being 
picked up by the qrunner and so you would expect there to be some trace 
of its progress in one of Mailman's log files.

But you say the directory says $prefix/logs doesn't exist. The log file 
directory is defined by the config variable LOG_DIR in 
$prefix/Mailman/Defaults.py or possibly (and unusually) overridden 
$prefix/Mailman/mm_cfg.py. If that directory doesn't exist then something 
in your install may be screwed.

What value does the config variable DELIVERY_MODULE in 
$prefix/Mailman/Defaults.py or possibly overridden 
$prefix/Mailman/mm_cfg.py have and also SMTPHOST.

Are there are no logs and no sign of what is happening exists in MM's 
error, post, smtp and smtp-failure logs.
--
jacob walcik
[EMAIL PROTECTED]
--
Richard Barrett  http://www.openinfo.co.uk
--
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] messages aren't being delivered to users,but are in the archive

[jacob walcik]

bizarre.  changing the SMTPHOST in mm_cfg.py from 'localhost' to the  
hostname of the server fixed it.

thanks for all the help!

On Wednesday, Jun 25, 2003, at 10:56 US/Central, Richard Barrett wrote:

At 16:39 25/06/2003, jacob walcik wrote:
alright, upgraded to 2.1.2 as per the recommendation in the original  
response.  same problem continues, but now i've actually got error  
messages from the logs to share.

from logs/smtp:
Jun 25 10:23:12 2003 (11504) All recipients refused: (111,  
'Connection refused')
Jun 25 10:23:12 2003 (11504) All recipients refused: please run  
connect() first
Jun 25 10:23:12 2003 (11504)  
[EMAIL PROTECTED] smtp for 2  
recips, completed in 0.037 seconds

from Defaults.py (not overridden in mm_cfg.py):
SMTPHOST = 'localhost'
and
DELIVERY_MODULE = 'SMTPDirect'
where is the All recipients refused message coming from?  postfix's  
log shows the message going through just fine:
Jun 25 10:23:12 dastardly postfix/local[11553]: B03606000E:  
to=[EMAIL PROTECTED], relay=local, delay=1, status=sent  
(|/usr/local/mailman/mail/mailman post test)
This mail log entry apparently shows the delivery of the incoming  
message to Mailman.

The MM post log entry seems to be saying that MM could not make a  
connection in order to send _out_ a message to the list's subscribers.  
There may also be a message in the MM smtp-failure log.

You can find out what MM is trying to use for outbound message  
transport by looking in $prefix/Mailman/Defaults.py unless you have  
overridden these by assignments in $prefix/Mailman/mm_cfg.py. Usual  
defaults are:

DELIVERY_MODULE = 'SMTPDirect'

SMTPHOST = 'localhost'

The error reported seems to indicate that Mailman is having trouble  
connecting to whatever outgoing mail server it is trying to  
communicate with..


On Tuesday, Jun 24, 2003, at 17:19 US/Central, Richard Barrett wrote:

At 22:08 24/06/2003, jacob walcik wrote:
yup, the mailman user's crontab was installed as part of the rpm
installation, and i've also tried running qrunner manually w/ the
command it's issuing, and i don't receive any errors.
assuming mailman's home is /var/mailman, where would i look for the
qfiles file.  a find ./ -name qfiles -print from /var/mailman
doesn't return anything.
Given your install in /var/mailman and a normal MM 2.0.x install  
there should be a directory called /var/mailman/qfiles. The script  
in /var/mailman/scripts takes delivery of incoming messages from the  
MTA creates a .msg and a .db file in that directory. The qrunner  
subsequently takes those files and processes them, sending mail out  
etc.

The actual qfiles directory used for enqueueing incoming messages is  
defined by the config variable QUEUE_DIR in  
$prefx/Mailman/Defaults.py or possibly (and unusually) overridden  
$prefix/Mailman/mm_cfg.py. If that directory doesn't exist then  
something in your install may be screwed.

But looking again at your original post you say the message is  
getting into the archives. That says the message is passing through  
qfiles, being picked up by the qrunner and so you would expect there  
to be some trace of its progress in one of Mailman's log files.

But you say the directory says $prefix/logs doesn't exist. The log  
file directory is defined by the config variable LOG_DIR in  
$prefix/Mailman/Defaults.py or possibly (and unusually) overridden  
$prefix/Mailman/mm_cfg.py. If that directory doesn't exist then  
something in your install may be screwed.

What value does the config variable DELIVERY_MODULE in  
$prefix/Mailman/Defaults.py or possibly overridden  
$prefix/Mailman/mm_cfg.py have and also SMTPHOST.

Are there are no logs and no sign of what is happening exists in  
MM's error, post, smtp and smtp-failure logs.
--
jacob walcik
[EMAIL PROTECTED]
--- 
---
Richard Barrett   
http://www.openinfo.co.uk


--
jacob walcik
[EMAIL PROTECTED]
--
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] messages aren't being delivered to users,but are in the archive

[jacob walcik]

hello

i just installed mailman 2.0.9 on redhat 7.3, and i've run into a snag.

i created a new list called test, added the aliases for it to 
/etc/procmail/aliases, ran postalias /etc/procmail/aliases, and then 
sent a message to my newly created list.

i can see the message in the archive, and i can see in my maillog where 
the message was piped out to the wrapper script, but i haven't received 
the message at either of the accounts that i subscribed to the list.

i don't see any errors in /var/log/messages, the check_perms script 
comes back clean, and i don't have a logs directory in /var/mailman 
as the faq states i should.  does anyone have any suggestions? (if 
someone can tell me how to enable mailman's logging, i'd appreciate 
that as well)

thanks!

--
jacob walcik
[EMAIL PROTECTED]
--
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] messages aren't being delivered to users,but are in the archive

[Richard Barrett]

At 20:59 24/06/2003, jacob walcik wrote:
hello

i just installed mailman 2.0.9 on redhat 7.3, and i've run into a snag.

i created a new list called test, added the aliases for it to 
/etc/procmail/aliases, ran postalias /etc/procmail/aliases, and then 
sent a message to my newly created list.

i can see the message in the archive, and i can see in my maillog where 
the message was piped out to the wrapper script, but i haven't received 
the message at either of the accounts that i subscribed to the list.

i don't see any errors in /var/log/messages, the check_perms script comes 
back clean, and i don't have a logs directory in /var/mailman as the faq 
states i should.  does anyone have any suggestions? (if someone can tell 
me how to enable mailman's logging, i'd appreciate that as well)

thanks!
The message is probably lodged in $prefix/qfiles.

Did you install the mailman user's crontab. Without the qrunner, which is a 
cron job, no mail will pass through Mailman. Try installing the crontab in 
$prefix/cron/crontab.in as the mailman uid's crontab

Also you are way out of date with the MM version you are running. The last 
version of was MM 2.0.x was 2.0.13 which was released nearly a year ago and 
that has superceded this year by MM 2.1.x which is up to 2.1.2. You should 
certainly consider upgrading although this is probably not the reason for 
your problem.

--
jacob walcik
[EMAIL PROTECTED]
--
Richard Barrett  http://www.openinfo.co.uk
--
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] messages aren't being delivered to users,but are in the archive

[jacob walcik]

yup, the mailman user's crontab was installed as part of the rpm  
installation, and i've also tried running qrunner manually w/ the  
command it's issuing, and i don't receive any errors.

assuming mailman's home is /var/mailman, where would i look for the  
qfiles file.  a find ./ -name qfiles -print from /var/mailman  
doesn't return anything.

this is actually the version of mailman that shipped w/ redhat 7.3.   
i've got it running on a different machine that was installed via the  
same process.  i wouldn't necessarily have any issues w/ upgrading to  
the 2.1 branch (the automatic attachment and html email filtering would  
be nice), but i'd still like to know if there's any particular reason  
why this isn't working.

On Tuesday, Jun 24, 2003, at 15:20 US/Central, Richard Barrett wrote:

At 20:59 24/06/2003, jacob walcik wrote:
hello

i just installed mailman 2.0.9 on redhat 7.3, and i've run into a  
snag.

i created a new list called test, added the aliases for it to  
/etc/procmail/aliases, ran postalias /etc/procmail/aliases, and  
then sent a message to my newly created list.

i can see the message in the archive, and i can see in my maillog  
where the message was piped out to the wrapper script, but i haven't  
received the message at either of the accounts that i subscribed to  
the list.

i don't see any errors in /var/log/messages, the check_perms script  
comes back clean, and i don't have a logs directory in /var/mailman  
as the faq states i should.  does anyone have any suggestions? (if  
someone can tell me how to enable mailman's logging, i'd appreciate  
that as well)

thanks!
The message is probably lodged in $prefix/qfiles.

Did you install the mailman user's crontab. Without the qrunner, which  
is a cron job, no mail will pass through Mailman. Try installing the  
crontab in $prefix/cron/crontab.in as the mailman uid's crontab

Also you are way out of date with the MM version you are running. The  
last version of was MM 2.0.x was 2.0.13 which was released nearly a  
year ago and that has superceded this year by MM 2.1.x which is up to  
2.1.2. You should certainly consider upgrading although this is  
probably not the reason for your problem.

--
jacob walcik
[EMAIL PROTECTED]
--- 
---
Richard Barrett   
http://www.openinfo.co.uk


--
jacob walcik
[EMAIL PROTECTED]
--
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] messages aren't being delivered to users,but are in the archive

[Richard Barrett]

At 22:08 24/06/2003, jacob walcik wrote:
yup, the mailman user's crontab was installed as part of the rpm
installation, and i've also tried running qrunner manually w/ the
command it's issuing, and i don't receive any errors.
assuming mailman's home is /var/mailman, where would i look for the
qfiles file.  a find ./ -name qfiles -print from /var/mailman
doesn't return anything.
Given your install in /var/mailman and a normal MM 2.0.x install there 
should be a directory called /var/mailman/qfiles. The script in 
/var/mailman/scripts takes delivery of incoming messages from the MTA 
creates a .msg and a .db file in that directory. The qrunner subsequently 
takes those files and processes them, sending mail out etc.

The actual qfiles directory used for enqueueing incoming messages is 
defined by the config variable QUEUE_DIR in $prefx/Mailman/Defaults.py or 
possibly (and unusually) overridden $prefix/Mailman/mm_cfg.py. If that 
directory doesn't exist then something in your install may be screwed.

But looking again at your original post you say the message is getting into 
the archives. That says the message is passing through qfiles, being picked 
up by the qrunner and so you would expect there to be some trace of its 
progress in one of Mailman's log files.

But you say the directory says $prefix/logs doesn't exist. The log file 
directory is defined by the config variable LOG_DIR in 
$prefix/Mailman/Defaults.py or possibly (and unusually) overridden 
$prefix/Mailman/mm_cfg.py. If that directory doesn't exist then something 
in your install may be screwed.

What value does the config variable DELIVERY_MODULE in 
$prefix/Mailman/Defaults.py or possibly overridden 
$prefix/Mailman/mm_cfg.py have and also SMTPHOST.

Are there are no logs and no sign of what is happening exists in MM's 
error, post, smtp and smtp-failure logs.

this is actually the version of mailman that shipped w/ redhat 7.3.
i've got it running on a different machine that was installed via the
same process.  i wouldn't necessarily have any issues w/ upgrading to
the 2.1 branch (the automatic attachment and html email filtering would
be nice), but i'd still like to know if there's any particular reason
why this isn't working.
On Tuesday, Jun 24, 2003, at 15:20 US/Central, Richard Barrett wrote:

At 20:59 24/06/2003, jacob walcik wrote:
hello

i just installed mailman 2.0.9 on redhat 7.3, and i've run into a
snag.
i created a new list called test, added the aliases for it to
/etc/procmail/aliases, ran postalias /etc/procmail/aliases, and
then sent a message to my newly created list.
i can see the message in the archive, and i can see in my maillog
where the message was piped out to the wrapper script, but i haven't
received the message at either of the accounts that i subscribed to
the list.
i don't see any errors in /var/log/messages, the check_perms script
comes back clean, and i don't have a logs directory in /var/mailman
as the faq states i should.  does anyone have any suggestions? (if
someone can tell me how to enable mailman's logging, i'd appreciate
that as well)
thanks!
The message is probably lodged in $prefix/qfiles.

Did you install the mailman user's crontab. Without the qrunner, which
is a cron job, no mail will pass through Mailman. Try installing the
crontab in $prefix/cron/crontab.in as the mailman uid's crontab
Also you are way out of date with the MM version you are running. The
last version of was MM 2.0.x was 2.0.13 which was released nearly a
year ago and that has superceded this year by MM 2.1.x which is up to
2.1.2. You should certainly consider upgrading although this is
probably not the reason for your problem.
--
jacob walcik
[EMAIL PROTECTED]
--- 
---
Richard Barrett
http://www.openinfo.co.uk

--
jacob walcik
[EMAIL PROTECTED]
--
Richard Barrett  http://www.openinfo.co.uk
--
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