1
Mail as an attachement
Question asked by Riddheh Bhandari - 12/1/2014 at 1:53 AM
Unanswered
Many times I receive a mail which has attachment as a "mail" having .eml or .msg extensions but there is no extension with it while they are fetched in system's older version but after upgrade to version 10.1 I am not able to receive this attachment and got one error message something like "Sender tries to send attachment but it is not allowed and got failed" on top of the ticket. Can please let me know how can i resolve this issue ?
 
Waiting for your update.
 
Thanks in Advance  

4 Replies

Reply to Thread
0
Employee Replied
Employee Post
Good day Riddheh,
 
Thanks for the inquiry. Are you trying to allow certain file extensions on attachments in SmarterTrack ? You may need to review the current configurations in the General Settings | Files section.
 
 
Please let us know if this helps or if you need assistance with the configurations.
 
Thanks.
 
0
H Gregory Silber Replied
Did anyone find a resolution to this.  I am having the same issue with attached messages .msg extensions not being accepted via email even though I have .* added to both settings boxes.
 
Thanks
0
Steve Reid Replied
Try adding the extension specifically without using a wildcard
0
Serge Baranovsky Replied
Posting as a reply to hopefully preserve formatting:
 
Steve,
 
Adding .eml and .msg is not solving the issue when email has another email copy-pasted into it - the issue described by the original poster above.  ST blocks those with a "The user attempted to send a file through email with an extension that is not allowed: Attachment 1" note even when we have .eml and .msg extensions enabled. 
 
Gmail shows those as noname.eml but in fact there is no file name for the email message embedded into the email message:
 
=================
--_000_CY1PR0401MB1308717F31E54A2204430B7ABF490CY1PR0401MB1308_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
 
PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
=================

Reply to Thread