Bug 127394 - SM creates new mail after resuming a draft
Summary: SM creates new mail after resuming a draft
Alias: None
Product: Fedora
Classification: Fedora
Component: squirrelmail   
(Show other bugs)
Version: 6
Hardware: All Linux
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-07-07 17:05 UTC by Peter Robinson
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-22 17:04:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Peter Robinson 2004-07-07 17:05:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When resuming a draft email. Once the draft is sent squirrelmail 
places you into a new mail rather than returning to the current 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a mail.
2. Save it as a draft
3. Resume the draft mail
4. Send the draft mail

Actual Results:  SM Pops up a new mail message

Expected Results:  Returned to current folder list of mails

Additional info:

Comment 1 Peter Robinson 2006-02-22 17:58:09 UTC
Updating as its still relevant for FC4

Comment 2 Christian Iseli 2007-01-22 11:57:20 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?


Comment 3 Peter Robinson 2007-01-22 12:13:45 UTC
Yes this is still happening in FC6. 

Comment 4 Warren Togami 2007-01-22 17:04:55 UTC
This may still be an issue, but Fedora is unable to fix this.  Please report
this to hte upstream squirrelmail.org project and make sure it is fixed there. 
Then Fedora in the future will pull that change.

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