Closed Bug 258454 Opened 20 years ago Closed 18 years ago

forwarded emails are "named" like the subject

Categories

(Thunderbird :: Message Compose Window, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 220646

People

(Reporter: otto, Assigned: mscott)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040617 Firefox/0.9
Build Identifier: User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)

If I forward emails they get attached and named exactely like the subject. 
I understand that filenames should not be changed but when you take the subject
of an email there is a bigger chance of mailservers bouncing mail by someone
forwarding an email with a subject ending with ".com" 
Our "solution" was to let the user use our webmail -Squirelmail, which attaches
.msg to the subject line. Other clients (mutt, outlook, outlook express) behave
"correctly" too. I understand this behaviour is not perse *wrong* but a lot of
mailservers out there bounce  -or strip parts of, mail that carries parts with
names that end with .exe, .com etc.

Reproducible: Always
Steps to Reproduce:
1. forward an email which ends with .com or any other -not that I know of any
top level domains that is a common executable extension too
2. send it to a destination that receives a lot of **** and uses body_checks
that filter out attachments that look like suspicious filenames to take the load
of the server.
3. notice that the forwarded message is removed or the message bounces.
Actual Results:  
The mail gets bounced by servers that are a little too strict.

Expected Results:  
Attach something like .msg to the name would be neater.
Fixing bug 220646 would solve this problem.
Status: UNCONFIRMED → NEW
Depends on: 220646
Ever confirmed: true
Marking as dupe of bug 220646, the fix there solves this problem too.

*** This bug has been marked as a duplicate of 220646 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
No longer depends on: 220646
You need to log in before you can comment on or make changes to this bug.