Since the 'name' parameter isn't all that vital on the receiving end 
(it's really just a handy shortcut to allow the end-user to easily 
save the part under a unique name) I've gone ahead and made this 
change.  See:

http://lists.horde.org/archives/cvs/Week-of-Mon-20070212/065396.html

You can see attached message in the attachment list, but it is without 
an extension. So Outlook Express just disables access to it (you can't 
click with a mouse on it). If I tell OE to not block those kind of 
attachments, then I can click on an attachments, but after that error 
message says that file could not be opened.



If I save this attachment to the desktop, and then add extension by 
hand, it can be opened again.



As I said this is because of the last period that goes straight before 
extension. OE RFC822 parser just strips extension in this case.

What do you mean "can't be opened"?  Can't be opened as in the RFC822 
part doesn't open as an RFC822 part in OE?  Or can't be opened as in 
the attachment does not even appear or the message doesn't open at all?



I am really hesitant to be making these kind of changes to perfectly 
fomatted e-mail messages based on the potential downstream client.

If a message has period sign as a last character in a subject, and 
then this message forwarded like attachment, it could not be opened in 
Outlook Express. I think it is because OE thinks that there is 
extension after period, but actually there isn't.



I know that this is a bug in OE most probably, but to strip last 
period sign (or replace it) from the name="rfc822 message title" part 
of the message will not cause any harm to Horde ideology or any 
standards.



Example message attached.