I would like to allow variant end users to download a message file from my system "As Is" so they will be able to open in easily.
i don't want to use the Outlook .msg format because not all of the users have Microsoft Outlook. HTML is not good because i can not convert emails with attachments to HTML.
I investigated and found 2 common formats. EML and MAI.
Can you explain about each of them so i will be able to decide on the right format?
while testing, i took MAI file, renamed it to EML and i could successfully open if with programs supports EML files like Outlook so i am wondering, is it the same format but with different extension only?
I added the MailEnable tag because i understood that if i am taking EML file and rename it to MAI it should work. and i am wondering if its correct without no exceptions. Because as per my understanding, EML if more common so i may choose that format but i still want to be able to load the EML files to MailEnable inbox for searching and manage using the Web interface.
EML isn't a format, it's just a file extension that is typically used for email messages in the MIME format.
I have no idea what MAI is, I've never heard of it and Google isn't turning anything up.
Since MIME is the only standard email format in existence, use that.
Related
i am writing a web application with React, where users can write protocolls for their appointments. The current system is: the web application saves the word file in the local file system, the user edits it and uploads it via a macro in word.
That seems a bit clunky to me and i am not so sure about the security issues of letting the browser directly access the local file system.
So i wanted to let the users edit the files directly via the browser, with an editor similar to GoogleDocs.
Problem is:
Documents have to remain on premis
Converting doc files to a format that can be displayed in a browser and back seems to have some formating issues.
The user must be able to download the file and edit it, in case they have an appointment without internet access and upload it later. So it has to be at least convertable to a document that can be easily edited in Word.
There are so many richtext editor, but from what ive seen none is designed for that use-case. So my question is: Is what i want to do even possible, and if so does anyone know a good editor or library for doing so?
I am not a programmer. I am a software solution designer. For compliance reasons I have to recover the messages received in our MS Exchange mailboxes and save them in their original form as an EML file, before I can save them to our CRM database for treatment by backoffice personnel.
My question is : Can I read the message and write the inputstream directly to the EML file without parsing it?
Our Sofware Architect and Judicial teams want to be sure that the contents are exactly equal to the original received e-mails in case of regulatory audit/investigation.
Also, can I save it to a blob-type database field and create a link that can be used to download the file?
Sorry for my lack of knowledge, but I am original a COBOL analyst.
Thanks!
Our CRM software package uses JavaMail to send and receive e-mail messages from our MS Exchange Server, and stores them in the package database (Oracle Exadata) for issue/ticket management.
EML files are MIME format. You can use JavaMail to read the MIME content of a message and write it to an EML file without parsing it first.
However, note that Exchange does not store the message in MIME format. So, even though the message may be received in MIME format, Exchange may transform it into its own internal format, and then transform it back to MIME when the message is read. Depending on your Exchange configuration, this transformation may or may not preserve the original MIME content exactly. In some case Exchange will transform the message into a different MIME format that it thinks will be easier for the client to process. I'm not an Exchange expert so if this concerns you you'll need to look into the Exchange documentation in more detail.
The short: I inherited a website I didn't make. The previous site (which I have been redesigning) had a file upload feature which converted .docx, .xlsx, .pdf, etc. into .fil and stored them in an uploads folder.
The previous developer is no longer available and I'm looking for a reliable way to convert the files back into their original types/extensions. Any ideas on a reliable conversion application? Or just a simple way to go about this?
I'd try to just change the file extension to .pdf or .doc and try to open the file with Microsoft Word or Adobe Reader. If that fails, give opening straight into Word a shot. I don't think that Word handles that file extension natively, but it may be able to interpret it. Good luck.
I am going to ask very basic question of difference between EML and MSG file stack. But I am not expecting "MSG is outlook-understandable format" as an answer. I need to know, if I am using EML what properties, I won't be able to extract. I am fairly familiar with OLE and MIME
I am writing a metadata extractor that will get integrated with SOLR. I am using EWS(Exchange Web Services) which is quite easy to use with many advantages and disadvantages.
This question is to summon all Exchange Experts to shed some light on EML or MSG. I have tried endless blogs but none is explaining why to choose what for now.
Reference: Difference between a .msg file and a .eml file
Note: I don't want to convert EML to MSG or vice versa. I will be happy to use any of the component.
Okay so given your last comment your actual question is about the Message Body so you don't need to worry about MSG vs EML. Exchange stores bodies in one of three formats either Text, HTML or RTF (or a combination of these) and it will perform an on the fly conversion if a client asks for a specific format and that is not available. I would say for what you doing just use HTML (which is the default format EWS will return) and you won't have problem. Its pretty rare for people these days to use RTF (HTML has been the default format in Outlook since 2000).I would suggest reading https://msdn.microsoft.com/en-us/library/cc463905(v=exchg.80).aspx . The only time I could see you losing format in the body if you go with HTML is if you have RTF messages with embedded Ole objects but this is pretty rare for people to use these days.
Cheers
Glen
Is there a way to send a mail with different PDF file to different contacts using file maker?
I am aware of sending batch emails with one attachment but I would like to send a personalize PDF for each contact which seems not so simple.
Also
Can I add PDF files to the table itself or would I have to use the path to the file?
Example:
Table 1
**Name** [James Brown] [James Blue]
**Email** [brown.j#gmail.com] [blue.j#gmail.com]
**PDFfileAttchamnet** [folder/PDF/JamesBrown.pdf] [folder/PDF/JamesBlue.pdf]
So an Email for James Brown would look like:
Dear James Brown, please see the attached file.
Attachment [JamesBrown.pdf] {actual file}
and
Dear James Blue, please see the attached file.
Attachment [JamesBlue.pdf] {actual file}
I think you can solve it by creating container field in you database and import the pdfs in it.
then you can use export Field Contents[] to export it and send it by email
Hope it useful
I would like to send a personalize PDF for each contact which seems
not so simple.
Find the records of contacts you want to include and loop among them, sending mail to each one individually (i.e. without selecting the 'Collect addresses across found set' option).
Can I add PDF files to the table itself or would I have to use the
path to the file?
You can do either, it's up to you. If the path to the file can be calculated (as in your example), you can calculate it right there in the Send Mail script step.
Note that you can also generate the PDF files during the process itself.
Do I understand correctly that you would actually like to personalize the PDF document(s)?
This is possible, maybe not very simple, but quite simple. The trick is to prepare the PDF as a form, and then fill the form fields to personalize.
PDF has a native forms data format (called FDF), which is described in ISO 32000 (as well as the older PDF specification documents provided by Adobe, as you can find in the Acrobat SDK, downloadable from the Adobe website).
FDF is a simple structured text file, which can easily be assembled using FileMaker (I have done that routinely for several catalog projects). The easiest way to get going is to open the form in Acrobat, fill in the fields, and then export the data as FDF. This gives you the pattern to "fill in the blanks".
So, you create the FDF files using Filemaker. With them you can fill the blank form and feed the saved document to the eMail system.
Which tool to use to fill the blank form depends on the volume you have to process. Acrobat is not very powerful (and you may end up in a bit of a legal gray zone, because Acrobat is not set up for being used as a service). There are applications which are made specifically for filling out forms on a server (such as FDFMerge by Appligent), or there are also several libraries which have the tools to fill out forms (iText or pdflib come to my mind). These applications also allow you to flatten the PDF, which means that there are no longer form fields, but their contents becomes part of the base.
The resulting file can now be either made to an eMail attachment, or you make it available on a server and send an eMail with the link to the file (which method you will use may depend on security and privacy regulations).