When a lotus notes user receives an email from an outlook client , the all or part of the body is missing. When the lotus notes user forwards or relys to this email , then lotus notes client can see body of email. I was told that I need to set the lotus notes client settings and change or set limit of charachters.
Hi fgrushevsky, thanks for your response. They are advising that the outlook client has an option for sending text only emails but if that is not selectted , they always send HTML format.
the option of sending HTML versus text only emails is independent from using MS RichTextFormat option.
For example: You can configure the whole Exchange system to always send mail to your notes domains as HTML and never use MS Righ Text format. Under Global Settins - Internet message format -you can add your notes internet domains there. Then, for every domain, open properties, on the second tab "Message Format" you can set Exchange to use HTML, plain text or both. Then, on the third "Advanced" tab you will specify if Exchange should use "Exchange Rich-Text format" when sending mail to this domain. You can select either "always use" (bad choice if another side is Domino), "never use" (good choice if another side is Domino) or "determined by individual user settings". If you select last option, then Outlook client will determine use of MS RTF format. In Outlook it could be set by user in the contact list (double click on email address and adjust internet format option there, or you set it for the whole Outlook (Tools-Options-Mail Format-Internet Format)
If you do not change default settings, Exchange and Outlook will use MS RTF whanever possible - which would not work well for Domino recipients
Hi fgrushevsky, thanks for your response! Can you take a look at the vendor's response. Does this make any sense to you ? Not sure how to respond to them? thanks, CJ
Here is their email response: I have read what your tech has sent and if I understood the email correctly, what they are saying is that even if we send our email communications from the system as HTML or Plain Text Only, it will not matter when it is received by the recipient on their own email client, be it Outlook or Lotus Notes. The email will be displayed to the recipient depending on what settings have been used for their email client, be it HTML, Plain Text or Rich Text format. Yes, this does makes sense to me. I am just not sure why we are concerned about the Rich Text? Does the tech think that this has anything to do with the problem?
Ok, lets take a step back and go over some basics that your vendor seems to be missing.
Although email message seems to be very simple thing, there are several ways to "write" or more accuratly prepare email message. Different email platforms (Notes/Domino, Outlook/Exchange, Eudora, The Bat! etc) have different capabilities to render and display messages received from another systems.
The variances are: - The email message can be only text. Going back to the good old days when you had only black and white alpha numerical displays and printers. It is the most common denominator. Any system can display this message, read and send it properly - The message can be in html format. This format is quite popular today. It allows you to write better looking messages as you can use variery of fonts, use bold/italic styles, colors etc. Most mail clients do a pretty decent job writing and displaing html messages, however you might see some differences in the way the message is displayed with different clients (as you might see web pages differently with different browsers). Also, as html "struggles" to be a common standard, it does not have all bells and whistles in formatting text that you can find in modern word processors such as MS Word. This bring us to the next variety in message formatting - RTF format. Rich Text Format gives your mail message pretty much all bells and whistles that your word processors allows. You really have RICH formatting capabilitis. BUT!!! MS RTF used by Outlook/Exchange is a PROPRIETARY FORMAT. IT CAN ONLY BE RENDERRED PROPERLY AND ACCURATLY by another Outlook/Exchange . Another mail systems or clients (Lotus, Eudora, The Bat! etc) will not be able to display MS RTF properly. Therefore, when Outlook/Exchange user sends mail to another internet user and another user does not have Outlook/Exchange - like in your case - then Rich Text Format will be problem. As I mentioned earlier, Exchange and Outlook will use MS RTF whanever possible which would cause problem to another mail clients So, the answer to your vendor is - "Yes, we are concern about Rich Text Format . As it not supported on our system, it prevents messages being displayed properly"
BTW, as a side note - Lotus Notes also has it's own RTF format that other clients will not handle well, but Lotus does not use it as default for all internet users.
That is an excellent explanation. The only question I have before going back to them. If they say they are sending HTML only then why would have still have a problem viewing? Just want to make sure I am clear on that. thanks, CJ
the settings on Plain Text and HTML are separate from RTF settings. They are on two different tabs. They can send mail in HTML or Text, but in the same time RTF would be still enabled and you will receive RTF emails. As I mentioned in my earlier post: Global Settins - Internet message format - this is where you vendor should can add your notes internet domains . For each of your domains, in properties,
- on the SECOND tab ("Message Format") your vendor can set Exchange to use HTML, plain text or both.
- on the THIRD ("Advanced") tab your vendor will specify if Exchange should use "Exchange Rich-Text format" when sending mail to this domain. The setting should be ""never use"
Sorry for the long delay. I just heard back and I am confused by their response below. I am not sure what question to ask next or even my next step. Any suggestions ? We do not use Microsoft exchange to send out emails, so these settings cannot be changed. We are basically using the default settings while sending emails, so this cannot be configured from our end.
