Bug 206864 - bug-buddy reports mail successfully sent even if it is not
Summary: bug-buddy reports mail successfully sent even if it is not
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bug-buddy   
(Show other bugs)
Version: 5
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-17 12:39 UTC by Vladimir Kotal
Modified: 2008-03-18 18:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-18 18:34:11 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Vladimir Kotal 2006-09-17 12:39:08 UTC
Description of problem:
After gnome-mount crash I have tried to send bug report via bug-buddy. The
report was not sent but bug-buddy happily reported that it was.

Version-Release number of selected component (if applicable):
bug-buddy-2.14.0-1

How reproducible:
disable sendmail and try to send bug report via bug-buddy

Steps to Reproduce:
1.disable sendmail
2.try to send bug report via bug-buddy
  
Actual results:
mail was not send, bug-buddy reported that it was

/var/log/maillog snippet:

Sep 17 14:28:38 erazim sendmail[1179]: k8HCSc1B001179: from=katka, size=4258,
class=0, nrcpts=1,
msgid=<200609171228.k8HCSc1B001179@erazim.local.lab.devnull.cz>,
relay=katka@localhost
Sep 17 14:28:38 erazim sendmail[1179]: k8HCSc1B001179: to=submit@bugs.gnome.org,
ctladdr=katka (501/501), delay=00:00:00, xdelay=00:00:00, mailer=relay,
pri=34258, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: Connection
refused by [127.0.0.1]


Expected results:
bug-buddy should at least report the right status

Additional info:

Comment 1 Ray Strode [halfline] 2008-03-18 18:34:11 UTC
Hi,

We no longer support Fedora Core 5 and I am currently trying to get my open bug
count down to a more manageable state.  I'm going to close this bug as WONTFIX.
 If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?

(this is a mass message)


Note You need to log in before you can comment on or make changes to this bug.