I installed mailman on a new machine running redhat 8. That machine is also running the latest 1.X apache and sendmail packages. Everything installed fine. I copied over some other lists that were running on and older machine and they show up fine on the admin page. I can configure them and everything. All aliases are set up in /etc/aliases. However when I tried to send a test message, it seems to go through fine, I get no emails saying the the mail server rejected it or anything. What I do get is a constant and steady stream of emails from the cron daemon all saying the exact same thing:
Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 222, in ? main() File "/home/mailman/cron/gate_news", line 203, in main process_lists(lock) File "/home/mailman/cron/gate_news", line 148, in process_lists conn, first, last = open_newsgroup(mlist) File "/home/mailman/cron/gate_news", line 75, in open_newsgroup password=mm_cfg.NNTP_PASSWORD) File "/home/mailman/Mailman/pythonlib/nntplib.py", line 111, in __init__ self.sock.connect((self.host, self.port)) socket.error: (111, 'Connection refused')
I have no idea what this means. I'm pretty green when it comes to linux so keep that in mind. I do know what the cron daemon is and I did set up the mailman cron entry as instructed in there install directions.
you can also reply to me directly at aaronda@freespeech.org
Aaron,
I saw a similar "connection refused error" when I did my install on a RH 7.2 system. I added the address of the machine running Mailman to the /etc/mail/access file as in:
--- segment of access file -------------- localhost RELAY 127.0.0.1 RELAY 66.127.210.187 RELAY --------- end segment ----------------
Such that all 3 correspond to my Mailman host machine. A good sendmail installation will have RELAYing turned off by default, and so adding entries like this to the access file turns it back "on" for those hosts. Some of those addresses are probably unnecessary, and I'm not entirely sure that that was what fixed the "connection refused" problem since I did some other config things too -- but eventually things did work, so maybe it was the solution.
Note that after your changes to the /etc/mail/access file, you need to trigger the rebuild of the /etc/mail/access.db file for it to take effect. There should be a makefile in the /etc/mail directory that should do it for you.
By the your efforts will be rewarded -- once Mailman is up and running, you will be impressed with the functionality. I was. The install is the only tricky part of using Mailman.
Good luck!
-keith s.
-----Original Message----- From: Aaron M Daley [mailto:aaronda@freespeech.org] Sent: Wednesday, January 08, 2003 2:07 PM To: mailman-users@python.org Subject: [Mailman-Users] cron daemon error
I installed mailman on a new machine running redhat 8. That machine is also running the latest 1.X apache and sendmail packages. Everything installed fine. I copied over some other lists that were running on and older machine and they show up fine on the admin page. I can configure them and everything. All aliases are set up in /etc/aliases. However when I tried to send a test message, it seems to go through fine, I get no emails saying the the mail server rejected it or anything. What I do get is a constant and steady stream of emails from the cron daemon all saying the exact same thing:
Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 222, in ? main() File "/home/mailman/cron/gate_news", line 203, in main process_lists(lock) File "/home/mailman/cron/gate_news", line 148, in process_lists conn, first, last = open_newsgroup(mlist) File "/home/mailman/cron/gate_news", line 75, in open_newsgroup password=mm_cfg.NNTP_PASSWORD) File "/home/mailman/Mailman/pythonlib/nntplib.py", line 111, in __init__ self.sock.connect((self.host, self.port)) socket.error: (111, 'Connection refused')
I have no idea what this means. I'm pretty green when it comes to linux so keep that in mind. I do know what the cron daemon is and I did set up the mailman cron entry as instructed in there install directions.
you can also reply to me directly at aaronda@freespeech.org
Aaron,
I saw a similar "connection refused error" when I did my install on a RH 7.2 system. I added the address of the machine running Mailman to the /etc/mail/access file as in:
--- segment of access file -------------- localhost RELAY 127.0.0.1 RELAY 66.127.210.187 RELAY --------- end segment ----------------
Such that all 3 correspond to my Mailman host machine. A good sendmail installation will have RELAYing turned off by default, and so adding entries like this to the access file turns it back "on" for those hosts. Some of those addresses are probably unnecessary, and I'm not entirely sure that that was what fixed the "connection refused" problem since I did some other config things too -- but eventually things did work, so maybe it was the solution.
Note that after your changes to the /etc/mail/access file, you need to trigger the rebuild of the /etc/mail/access.db file for it to take effect. There should be a makefile in the /etc/mail directory that should do it for you.
By the your efforts will be rewarded -- once Mailman is up and running, you will be impressed with the functionality. I was. The install is the only tricky part of using Mailman.
Good luck!
-keith s.
-----Original Message----- From: Aaron M Daley [mailto:aaronda@freespeech.org] Sent: Wednesday, January 08, 2003 2:07 PM To: mailman-users@python.org Subject: [Mailman-Users] cron daemon error
I installed mailman on a new machine running redhat 8. That machine is also running the latest 1.X apache and sendmail packages. Everything installed fine. I copied over some other lists that were running on and older machine and they show up fine on the admin page. I can configure them and everything. All aliases are set up in /etc/aliases. However when I tried to send a test message, it seems to go through fine, I get no emails saying the the mail server rejected it or anything. What I do get is a constant and steady stream of emails from the cron daemon all saying the exact same thing:
Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 222, in ? main() File "/home/mailman/cron/gate_news", line 203, in main process_lists(lock) File "/home/mailman/cron/gate_news", line 148, in process_lists conn, first, last = open_newsgroup(mlist) File "/home/mailman/cron/gate_news", line 75, in open_newsgroup password=mm_cfg.NNTP_PASSWORD) File "/home/mailman/Mailman/pythonlib/nntplib.py", line 111, in __init__ self.sock.connect((self.host, self.port)) socket.error: (111, 'Connection refused')
I have no idea what this means. I'm pretty green when it comes to linux so keep that in mind. I do know what the cron daemon is and I did set up the mailman cron entry as instructed in there install directions.
you can also reply to me directly at aaronda@freespeech.org
participants (2)
-
Aaron M Daley -
Keith Steward