E-mail question
Posted: Thu Feb 17, 2011 8:30 am
I have a particular need for which I have figured a simple solution, but unfortunately it requires a minor change to a CardSchema method... I'm wondering if others have done something similar in some other way, perhaps something I am totally overlooking.
The need is to make the "destination" filename of a mail attachment different from the physical name of the file on the server. It seems that the physical filename (attachment.fileName property) is used BOTH for the File object used to process the file, and (stripped of path name of course) the mime header of the attachment.
I can easily verify that by changing a line of code in the CnSmtpStateDATA::sendFileAttachments method...
lastFilenameNode := getLastFilenameNode(attachment.fileName);
(lastFileNameNode is a few lines later used to construct the mime header) to set that variable to say some new "destFileName" property of a class derived from CnAttachment, I get the result I want.
But obviously for maintenance purposes I'd prefer not to have to fiddle with the CardSchema. I have a suspicion that this must be a requirement that others have encountered, and am wondering if I am missing a more obvious existing solution?
Cheers
David
The need is to make the "destination" filename of a mail attachment different from the physical name of the file on the server. It seems that the physical filename (attachment.fileName property) is used BOTH for the File object used to process the file, and (stripped of path name of course) the mime header of the attachment.
I can easily verify that by changing a line of code in the CnSmtpStateDATA::sendFileAttachments method...
lastFilenameNode := getLastFilenameNode(attachment.fileName);
(lastFileNameNode is a few lines later used to construct the mime header) to set that variable to say some new "destFileName" property of a class derived from CnAttachment, I get the result I want.
But obviously for maintenance purposes I'd prefer not to have to fiddle with the CardSchema. I have a suspicion that this must be a requirement that others have encountered, and am wondering if I am missing a more obvious existing solution?
Cheers
David