Closed Bug 288935 Opened 20 years ago Closed 19 years ago

Attach different attachment with same name again retrieves old one from cache

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: rigasp, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; el-GR; rv:1.7.6) Gecko/20050321 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; el-GR; rv:1.7.6) Gecko/20050321 Firefox/1.0.2

Mozilla composer seems to have a cache for attachments that does not update.
When I keep sending a mail with an attachment with the same name, but I change
the file, it keeps getting the old file


Reproducible: Always

Steps to Reproduce:
1. Send a mail with a zip file hello.zip
2. Change the file hello.zip
3. Send another mail and attach the same file hello.zip -> Old file is sent

Also:
1. Send a picture hello.gif
2. Senders sends you the modified picture but with same name
3. In the preview you get the old picture



Expected Results:  
Show and send the actual file and not the one from cache(?)
Changing component to MailNews: Main Mail Window.

Reporter, what version of the Mozilla Suite are you getting this problem with?
Please post the build string from Help, About.
Component: Composer → MailNews: Main Mail Window
Assignee: composer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.