[Mailman-Developers] bug report : nntp connect failure does not specify host nameZ

[dhesi at rahul.net]

Hi, I'm sorry, I tried to submit a bug report via the SourceForge
project page, but could not find any buttons or links on the 'bugs' and
'tracker' pages that would let me submit a new bug report.

I am using Mailman 2.0.13 as included RedHat Linux 7.2.

When mailman is unable to make an nntp connection to a News host, it
returns an error of the form shown below.  In this error message it does
not specify to which host it was trying to connect.  This seems like a
minor thing.  But in fact, due to this omission, I spent a lot of time
debugging a connection failure problem.  I did not realize that due to a
DNS and /etc/hosts inconsistency, mailman was trying to connect to the
wrong host.

Rahul


---------- Forwarded message ----------
Date: Wed, 15 Jan 2003 20:05:36 -0800 (PST)
From: Cron Daemon <root at pink.rahul.net>
To: mailman at rahul.net
Subject: Cron <mailman at pink> /usr/bin/python -S /var/mailman/cron/gate_news

Traceback (innermost last):
  File "/var/mailman/cron/gate_news", line 222, in ?
    main()
  File "/var/mailman/cron/gate_news", line 203, in main
    process_lists(lock)
  File "/var/mailman/cron/gate_news", line 148, in process_lists
    conn, first, last = open_newsgroup(mlist)
  File "/var/mailman/cron/gate_news", line 75, in open_newsgroup
    password=mm_cfg.NNTP_PASSWORD)
  File "/var/mailman/Mailman/pythonlib/nntplib.py", line 111, in __init__
    self.sock.connect((self.host, self.port))
socket.error: (113, 'No route to host')

== END ==