Your message dated Mon, 4 Jan 2010 10:18:00 +0100
with message-id <[email protected]>
and subject line Re: please check for a working smtphost before writing
.reportbugrc
has caused the Debian Bug report #468549,
regarding please check for a working smtphost before writing .reportbugrc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
468549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468549
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 3.39
Severity: normal
I'm using bugs.debian.org as SMTP-server and my .reportbugrc
is standard generated stuff without any modifications.
My firewall (firehol) permits all outgoing traffic.
I don't have problems with my network connection either.
However Sending bug report with reportbug fails with message:
Connecting to bugs.debian.org via SMTP...
SMTP send failure: (113, 'No route to host')
Wrote bug report to /tmp/reportbug-hello-20080229-20318-id8ZO6
I've tried this many times in different days and
behaviour stays, also regenerating .reportbugrc doesn't help.
za...@vesipeto:~$ ping bugs.debian.org
PING bugs.debian.org (140.211.166.43) 56(84) bytes of data.
64 bytes from rietz.debian.org (140.211.166.43): icmp_seq=1 ttl=44 time=215 ms
za...@vesipeto:~$ host bugs.debian.org
bugs.debian.org has address 140.211.166.43
bugs.debian.org mail is handled by 0 bugs.debian.org.
P.S. I'm sending this report manually via gmail. I asked about this
issue in debian-user, but
nobody had any idea, maybe you have.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/zamar/.reportbugrc:
reportbug_version "3.39"
mode standard
ui text
email "[email protected]"
no-cc
header "X-Debbugs-CC: [email protected]"
smtphost bugs.debian.org
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (700, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.11 Advanced front-end for dpkg
ii python 2.4.4-6 An interactive high-level object-o
ii python-central 0.5.15-0.1 register and build utility for Pyt
reportbug recommends no packages.
-- no debconf information
107,1 Bot
64 bytes from rietz.debian.org (140.211.166.43): icmp_seq=2 ttl=44 time=211 ms
64 bytes from rietz.debian.org (140.211.166.43): icmp_seq=3 ttl=44 time=209 ms
--- bugs.debian.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 209.469/212.255/215.776/2.679 ms
za...@vesipeto:~$ host bugs.debian.org
bugs.debian.org has address 140.211.166.43
bugs.debian.org mail is handled by 0 bugs.debian.org.
--- End Message ---
--- Begin Message ---
Hello,
- checking for a working MTA/smtphost is not the reportbug task (how
can we do it reliably? no way) but it's up to the user to configure
reportbug with a working MTA/smtphost (for sure the user sends others
mail using some other programs, so they know what's the correct
value).
- as a possible smtphost, we now provide 'reportbug.debian.org'
listening port '587' that avoids the ISP blocks on port 25.
That said, those 2 bugs can be closed.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
