Okay...we've had some thinking here and here's what we have learnt.
Example 1:An email is sent in with an attachment from a webmail account.
In the MIME settings of that message coming in, via the log, the following is visable:
Code: Select all
--B_3331801349_858650
Content-type: video/x-flv; name="sxbackup.pdf"
Content-disposition: attachment;
filename="sxbackup.pdf"
Content-transfer-encoding: base64
The attachment will arrive at the destination with the correct name.
Example 2:In the MIME settings of a message sent in via the automated app Logicity the following is visable:
Code: Select all
----boundary_0_e31aeac6-1096-4be6-8dbc-bec22c887b32
Content-Type: application/octet-stream; name=vod_consumption.pdf
Content-Transfer-Encoding: base64
The attachment will arrive with the email but without name. Instead it has attachment.pdf or 1.2.pdf or attachment1234.pdf.
The obvious thing which stands out is the absence of a MIME command which states FILENAME= and it may be easy to point the finger at this lack of MIME and say there's the problem, it's with that app, were it not for some other facts. a) the old mail system based on POSTFIX and IMAP worked. b) the customers receiving this message from the external servers receive the attachment correctly through their mail servers.
The problem only occurs when the message reaches Scalix. At this point, the system looses the ability to apply NAME= to the attachment, which the other mail systems can.
Assuming this is the case then I am hopeful a config file exists someplace to allow this function.
All help appreciated.