Showing posts with label email. Show all posts
Showing posts with label email. Show all posts

Friday, February 12, 2016

Lotus Notes / Domino Fix List



IBM Notes/Domino 9.0.1 Fix Pack 5 Release Notice
November 30, 2015

9.0.1 Fix Pack 5 is a collection of low-risk, high-impact fixes to help customers safely avoid known issues. IBM strongly recommends that customers running Notes/Domino 9.0.1x upgrade to this latest Fix Pack since it addresses a small percentage of defects that impact the broadest set of customers. Fix Packs are released periodically between Maintenance Releases to provide a greater level of stability for customer environments. They go through the same level of fix, regression and interoperability testing that occurs with Maintenance Releases. Fix Packs are always cumulative and contain all of the fixes from previous ones. All Fix Packs are language independent and may be applied on any language version of Notes/Domino 9.0.1x.

Notes/Domino 9.0.1 Fix Pack 5 addresses defects in the Client, Server, Notes Browser Plug-in and Domino OpenSocial component.

Supersedes 
9.0.1 Fix Pack 5 includes all of the content and supersedes the following deliverables:
  • Notes: 9.0.1 FP4 IF1, IF2
  • Domino: 9.0.1 FP4 IF1, IF2, IF3
  • iNotes: 9.0.1 FP4 IF1, IF2
  • JVM Patch: 1.6 SR16FP7

Important Notes
  • 9.0.1 Fix Pack 5 updates the embedded Notes/Domino JVM to 1.6 SR16 FP15 to address security vulnerabilities.
  • 9.0.1 Fix Pack 5 adds support for IE Standards Mode for iNotes. An optional Forms9s.nsf for IE 11 Standard mode has been added in 9.0.1 FP5. 9.0.1 FP5 installs a secondary iNotes client file on the Domino server named Forms9s.nsf. This file is an optional solution to "Quirks Mode". Quirks mode was a run time option first introduced in IE 6 to provide backward compatibility for programs such as iNotes but can cause some limitations running in newer versions of IE such as IE11. Forms9s.nsf removes quirks mode and runs in Standard mode. This is off by default and can be enabled via setting these in the Domino server notes.ini
iNotes_WA_DefaultFormsFile=iNotes/Forms9s.nsf
iNotes_WA_FormsFiles=iNotes/Forms9s.nsf
  • IBM Notes Mac - IBM Notes Mac 9.0.1 FP5 32-bit is superseded by Mac 9.0.1 64-bit. Customers looking for Notes Mac client 9.0.1 32-bit are encouraged instead to download and install Notes 9.0.1 Mac 64-bit. Download links can be found in this document: Supportability Q&A about IBM Notes and OS X 10.11.x
  • Windows 10 - 9.0.1 FP5 adds support for IBM Client Application Access and the Notes Browser Plug-in. Notes/iNotes added this support for 9.0.1 FP4. For more info, see this technote Supportability Q&A about Notes and Windows 10.

Known Issue
  • SPR XXLI9RNB7U - Windows Domino Server: JVM version is reverted to 9.0.1 gold's version when un-installing/downgrading from 9.0.1 Fix Pack 4 to a prior Fix Pack. This will not impact most customers, as downgrading to a prior fix pack is not a common operation. This issue also does not affect future fix pack upgrades. DETAILS: On Windows, the Domino server installer gives you an option to downgrade to either a prior Fix Pack level or to the gold release. If customers want to downgrade to an earlier Fix Pack level, it is recommended that you un-install the Fix Pack, which will leave the server at 9.0.1 Gold, then proceed with the Fix Pack install of your choice. This will ensure the correct JVM level is installed.

Download Options
For download options see technote 4037141 - "Download Options for Notes & Domino 9.0.1 Fix Packs". Note: Fix Packs will not be distributed on physical media (DVD/CD).
  • If you have Notes 9.0.1 Basic Configuration or Notes/Admin/Designer (Basic edition) 9.0.1 installed, use the Notes 9.0.1 Fix Pack 5 Basic install.
  • If you have Notes 9.0.1 Standard Configuration or Notes/Admin/Designer (Standard edition) 9.0.1 installed, use the Notes 9.0.1 Fix Pack 5 Standard install.

Decision to upgrade
Customers unable to upgrade to later Releases should install Fix Packs to benefit from later fixes made to the product. By providing a small number of fixes, customers are able to accept fewer code changes with lower risk, allowing them to "patch" an older Maintenance Release until a more extensive upgrade to the current Release is possible. 

While Fix Packs provide important fixes and IBM strongly recommends applying the latest Fix Pack available for a Maintenance Release, IBM still recommends that customers upgrade to the latest Release + Fix Pack combination to receive the broadest set of fixes available. You will receive more overall fixes with a later Release + Fix Pack than with a set of Fix Packs on top of an earlier Maintenance Release. For more information, see technote #1368141-"Differences between Notes/Domino Maintenance Releases, Fix Packs and Upgrade Packs." 

Fixes contained in this Fix Pack
A plus symbol (+) before the SPR number indicates a fix for a regression bug. A regression bug is an issue that was introduced in a Maintenance Release but did not exist in previous releases of that code stream. For example, a bug that appears in 9.0.1 but did not exist in 9.0.0 is a regression.
If an APAR exists for the corresponding SPR, the APAR number will appear in parentheses next to the SPR number. For example, SPR #nnnnnnnnnn (LO12345).


What follows is a subset of the most important issues addressed in this fix pack. For the full list of fixes, visit the fixes by release viewfor the description of each fix in this Fix Pack, including platform specific information. 

9.0.1 Fix Pack 5 Fix List descriptions:

Client
  • CSMH9QHKNF (LO83744) - Fixes issue where the incorrect font is used after installing additional True Type fonts in Notes 9. The fix requires the new notes.ini variable "UseWindowsFontSubstituteFontList" be set to the font or fonts that are to be used. This is a regression in 9.0.1.
  • HHIE9RTARJ (LO83155) - Avoids a Notes Client crash opening a document with a graphic image containing invalid dimensions. This defensive fix will avoid the crash.
  • ADEE9UCDQ2 (LO84117) - Fixes issue that could result in duplicate INI parameters for cases where the notes ini exceeds 64 bytes
  • DSAS9HBTVQ (LO79576) - Under certain conditions, the Dircat task treats a rare but routine error "Directory cataloger was unable to obtain any scheduling information" as fatal and shuts down. This fix resolves this.
  • QMGO9YXDML (LO85873) - Fixes issue where Notes fixpack ignores the custom common data setting and installs to the default common data dir causing a 1603 install error
  • SRKM9NFF7B (LO81786) - Attempts to install a Notes 9.0.1 Fix Pack fail. The install/upgrade log shows the following error: "Installation success or error status: 1603". This is a regression in 9.0.1 FP1.
  • XXZZ9JN999 (LO81356) - Fixes a cross platform crash opening emails with certain objects in them. This issue was more common on Notes Client Mac 10.9.

Server
  • RMAS9GATPK (LO81820) - The maximum NSF Pool size is hard coded by default. This fix introduces a new INI parameter to set the maximum size of the NSF Pool at runtime. Add MAX_NSFPOOL_SIZE=[new size in bytes] to set the size of the NSF Pool. Use MAX_NSFPOOL_SIZE_MB to set the size in MB instead. Note that the size cannot be set smaller than the current default maximum of 512 MB.
  • RGAU8ZRLKH (LO72483) - Fixes Domino Server crash when an xPage application with a large view is accessed and hitting last page of that largeview with the notes.ini variable Ft_max_search_results=99999999 set.
  • TMAI9YNHCD (LO85763) - Fixes issue where the return value of the len function in Lotusscript is invalid on 9.0.1 FP4. This fix was a regression caused by 9.0.1 FP4 SPR JMDK9MA6EJ. This fix reverts the fix for SPR JMDK9MA6EJ.
  • PJON9UBQMR (LO84113) - Fixes issue where Diiop connections over SSL Fail If SSLv3 is disabled. (technote 1968912)
  • SVRO9UZRQC (LO85045)- ISpy (runjava) fails to connect if SSLv3 is disabled because it was using an older SSL stack. It has been updated to a newer SSL stack that supports TLS (technote 1700925)
  • WBJT9X63VT (LO85208) - Chinese characters display incorrectly when an event is created via the Calendar service Restful API
  • YDEN9GYKRR (LO79426) - Fixes issue where user receives error: "Invalid URL exception and HTTP 500 Internal server error" when accessing a URL that contains a colon in the start and stop parameters in a URL. We now allow additional characters for 'start' and 'count' in a URL. This was a regression introduced in 9.0.
  • MKIN9BGTMX (LO77050) - Fixes a recursion crash when out of OSLocal memory. Symptoms included having http disappear without the creation of an nsd. (technote 1682289)

iNotes
  • GKLA9WVTH9 (LO85136) - Fixes issue on Mac and Linux where when using operating system timezone events viewed withcalendar views display 3 hours early in the calendar view. This is a regression in 9.0.
  • SVRO9YLM35 (LO85733) - Fixes an HTTP Crash with iNotes in MAXSPRINTF due to a null pointer caused by incorrect permissions on Dojo files (technote 1964549)
  • CKUA9HSABG (LO79874) - Notes web: Fixed an issue where email links were not resolving properly when clicked.
  • MLEY9MVG34 (LO81588) - When using iNotes with Internet Explorer, blank lines in a user's signature are deleted. This is a regression in 9.0.1.
  • RFRF9CCARU (LO77404) - Notes web: Fixed an issue where replying to all from a message in the sent view using Internet Explorer 10 would result in swapping the contents of the "To" and the "cc" fields.
  • MLEY9TMGPF (LO83786) - Notes web: Fixed an issue with slow scrolling using the navigation arrows in the One Week/One Work week calendar views


- wong chee tat :)

Saturday, July 26, 2014

“(xxxx.pst) has reached its maximum size. To reduce the amount of data in this file, select some items that you no longer need,then permanently (shift + del) delete them.”

“(xxxx.pst) has reached its maximum size. To reduce the amount of data in this file, select some items that you no longer need,then permanently (shift + del) delete them.” pops up in MS Outlook 2010.

However, deleting old mails with large file size cannot be deleted.

How to resolve that?

First, check the format of the Outlook data file (or simply email archive - pst file). Select the particular pst file,then go to Data File Properties.

In the email archive properties, select "Advanced" button.

This brings up the Outlook Data File with the follow:
You should see:
Name of the email archive,
The filename or the location,
Format.

Check the format is (97-2002). If so, this means that the particular email archive is ANSI encoded and is fast approaching 2Gb limit.

Go to the email archive location and check the file size is it around 2Gb. It should be around 1.9Gb and close to 2Gb.

A workaround would be perform a compact by clicking on Compact Now button. This would reduce the size of outlook data file.

Save and close MS Outlook and relaunch.

Try to add or delete items from the folder and it should work.



- wong chee tat :)

Tuesday, April 8, 2014

Enrol blackberry account fails!

I encountered this error on Blackberry 10 device when trying to enrol user's account to blackberry enterprise server (BES): "Your account - cannot be authenticated with your service provider.  Please make sure the account settings are correct."

How to resolve?

1) First, make sure the there is no problem accessing to internet from the blackberry 10 device. Perform a simple google / yahoo/ bing search.

2) Check if the email password is correct. To check this, ask the user to login to webmail or MS Outlook (if is password protected).

If it still fails, even if the password is entered correctly, then try this:

3a) Delete the failed account.

3b) Wipe the Blackberry 10 device to its original state. Wiping to its original state allows you to start fresh.

3c) Then, test by using your account.

If you are able to access and the enrollment process is successful, you will get a message indicationg that Blackberry is activated or similar message.

3d) If your blackberry account is activated successfully. Then it is likely that user's password is incorrect. Ask user to login to webmail or MS Outlook again.
Then, try to activate the blackberry device for user. It should be successful.


Reference: http://btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB34177&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImp


- wong chee tat :)

Monday, March 24, 2014

Lotus Notes/Domino 8.5.3 Fix Pack 6 Release Notice


Notes/Domino Fix List

Lotus Notes/Domino 8.5.3 Fix Pack 6 Release Notice
December 9, 2013

Notes/Domino 8.5.3 Fix Pack 6 is the last scheduled Fix Pack for 8.5.3. Fix Pack development will now shift to the 9.0.1 release.

8.5.3 Fix Pack 6 is a collection of low-risk, high-impact fixes to help customers safely avoid known issues. IBM strongly recommends that customers running Notes/Domino 8.5.3 upgrade to this latest Fix Pack since it addresses a small percentage of defects that impact the broadest set of customers. Fix Packs are released periodically between Maintenance Releases to provide a greater level of stability for customer environments. They go through the same level of fix, regression and interoperability testing that occurs with Maintenance Releases. Fix Packs are always cumulative and contain all of the fixes from previous ones.

Platform support added in 8.5.3 FP6:

• Windows 2012 R2
• Windows 8.1
• Mac 10.9
Known issues - see Supportability Q&A about IBM Notes and OS X 10.9.x

Note: For Windows 8.1 and Mac OS X 10.9 (Mavericks), embedded Sametime 8.5.1 is not supported. Notes 8.5.3 shipped with embedded Sametime 8.5.1, so upgrading the embedded version with a Sametime Add-on will be necessary. Testing is expected to complete late December'13/early January'14 and an IBM Sametime technote will be released. This will be Sametime add-on 8.5.2 Fix Pack 1 plus an interim fix.

As of 8.5.3 FP6, Internet Explorer 11 (IE11) is supported as the embedded browser in Notes. IE11 is not supported with iNotes and XPages. If you need IE11 support for iNotes and XPages, please look at Domino 9.0.1 which supports IE11 with iNotes as of iNotes 9.0.1 IF1 and planned support for XPages in 9.0.1 Fixpack 1 in Q1 2013.

Notes/Domino 8.5.3 Fix Pack 6 addresses defects in both the Client and Server. All Fix Packs are language independent and may be applied on any language version of Notes/Domino 8.5.3.

NOTE: The installer for Domino Interim Fixes (hotfixes) built 9 July 2012 or later requires a Perl 5.6.0 or later distribution on Unix & Linux platforms. For details, see technote 1600910.

Download Options
For download options see technote 4032242 - "Download options for Notes/Domino 8.5.3 Fix Packs". Note: Fix Packs will not be distributed on physical media (DVD/CD).
• If you have Notes 8.5.3 Basic Configuration or Notes/Admin/Designer (Basic edition) 8.5.3 installed, use the Notes 8.5.3 Fix Pack 6 Basic install.
• If you have Notes 8.5.3 Standard Configuration or Notes/Admin/Designer (Standard edition) 8.5.3 installed, use the Notes 8.5.3 Fix Pack 6 Standard install.

Decision to upgrade
Customers unable to upgrade to later Releases should install Fix Packs to benefit from later fixes made to the product. By providing a small number of fixes, customers are able to accept fewer code changes with lower risk, allowing them to "patch" an older Maintenance Release until a more extensive upgrade to the current Release is possible. We encourage customers to evaluate Notes / Domino 9.0 Social Edition and the 9.0.1 release.

While Fix Packs provide important fixes and IBM strongly recommends applying the latest Fix Pack available for a Maintenance Release, IBM still recommends that customers upgrade to the latest Release + Fix Pack combination to receive the broadest set of fixes available. You will receive more overall fixes with a later Release + Fix Pack than with a set of Fix Packs on top of an earlier Maintenance Release. For more information, see technote #1368141-"Differences between Notes/Domino Maintenance Releases, Fix Packs and Cumulative Client Hotfixes."

Fixes contained in this Fix Pack
A plus symbol (+) before the SPR number indicates a fix for a regression bug. A regression bug is an issue that was introduced in a Maintenance Release but did not exist in previous releases of that code stream. For example, a bug that appears in 8.5.3 but did not exist in 8.5.2 is a regression.
If an APAR exists for the corresponding SPR, the APAR number will appear in parentheses next to the SPR number. For example, SPR #ABCDEFGHIJ (LO12345).


What follows is a subset of the most important issues addressed in this fix pack. For the full list of fixes, please visit the fixes by release view for the description of each fix in this Fix Pack, including platform specific information.

8.5.3 Fix Pack 6 Preliminary Fix List descriptions:

Client
SPR# TSHI8SD538(LO68047) - Fixed an intermittent Notes client crash when opening a corrupted Notes document.
+SPR# MLAT99RKAG(LO76668) - Improved javascript disablement and disabled for HTML Email messages (body field and memo form) only. This regression was introduced in 8.5.3 FP5.
SPR# ACHG8STC6T(LO68380) - Fixes intermittent Notes Client crash when the user hits "send" on a large email (also the email is lost).
SPR# MCHZ8R4HPK(LO67040) - "Search Directory For" results in Typeahead are displayed in Alphabetical Order. (technote 1580001)

Server
SPR# KBRN8Q6JXC(LO71360) - Performance and reliability fix to network session code. Prior to this fix, many users accessing a Domino server simultaneously could cause a performance bottleneck resulting in slow server response or timeouts attempting to connect to the server. The error 'Unable to redirect failover from ' could also appear where SERVERNAME is the same name of the server encountering the issue.
SPR# JPAI94HR3N(LO75003) - Fixes potential deadlock on process startup between LkMgr locker and semaphore locker(Directory manager queue semaphore). (technote 1644240)
SPR# MYAA8LV385(LO64012) - Fixes an issue where an incorrect warning for a database over quota threshold could be generated.
+SPR# RMAA94WKMG(LO73956) - Fixes intermittent Domino Server crash when closing a database. This regression was introduced in 8.5.2. (technote 1644232)
SPR# VPRS8YBRZ6(LO71728) - Fixes Domino Server mail relay host crash on router on Jonah::asn_sorted::encode_value
+SPR# AJMO8NVM8F(LO66491) - Prevent Directory Assistance on Domino 64-bit servers from doing unnecessary search references and referrals which were leading to "81" LDAP timeout errors. This regression was introduced in 8.5.
SPR# JPMS8KZLLC(LO63217) - Fixes Domino Server crash during database cache maintenance with PANIC: ERROR - LockMemHandle() Handle 0xF0259F47 is not allocated
SPR# PPET98CPBN(LO7562) - Security enhancement to scrub query strings causing search to fail; work around is to add the following notes.ini: HTTP_QUERY_STRING_SCRUB=0. This fix changes the default to be off instead of being on and adds new code to prevent security X-Site script attacks against search urls.
SPR# AJAS8WSB9B(LO70861) - Prior to this fix multiple "Received" headers could be overwritten by one when retrieving e-Mails with IMAP client.
SPR# KHAN87ZUTS(LO55991) - Prevents excessive InsertPermutations recursion that can lead to a Domino Server crash. The new notes.ini variable MAX_PERMUTE_RECURSE=, where limits the number of hierarchical responses that can be added to a given collection, is recommended to be set to 200. (technote 1600317)
+SPR# PHEY8UDJYW(LO65911) - Fixes ACL corruption with: "ACL Corrupt in database creating new ACL with default set to no access". Now we block unintended deletion of ACL Note that would leave to a DB set to no access. This was a regression introduced in 8.5.3.

iNotes
SPR# WRAY8QKLTQ(LO66604) - Fixed issue where when opening messages in iNotes Ultra Light Mode, that have mixed case mail file names specified in the URL, the mail message fails to open.
SPR# KRAU8Y2MX6(LO71593) - Fixes issue where the iNotes UI window shrinks to a small size when the iNotes UI is resized several times.
SPR# HKOA7T4DN5(LO49113) - Notes web: Fixed an issue where the web browser could hang if a window is resized to or from a very small size.
SPR# PTHN96NRTP(LO45468) - Notes web: Fixed an issue where the unread count on a folder is not updated automatically when new messages were transferred into it via a mail rule. Clicking on the folder or using F5 to refresh would update the count.
+SPR# HSKM8TN39T(LO68949) - Fixed problem which caused a custom sized table to be inserted in the wrong place in the Rich Text Editor. This is a regression in 8.5.3.

- wong chee tat :)



























Tuesday, August 20, 2013

IRAS warns of scam email

IRAS warns of scam email

    POSTED: 20 Aug 2013 5:41 PM
 
The IRAS has warned of a scam email with the subject title "IRAS Reward".

SINGAPORE: The IRAS has warned of a scam email with the subject title "IRAS Reward".

The scam email asks recipients to click on an attached link to fill in a form on a website to claim cash rewards, says the Inland Revenue Authority of Singapore (IRAS).

Members of the public should not respond to the email, click on its hyperlink or provide their particulars. The email and the website are scams, says IRAS.

The IRAS has made a police report and is investigating the matter.

Anyone who has received a suspicious email, letter, SMS or phone call purportedly from IRAS should immediately contact IRAS at iras@iras.gov.sg or call 1800 356 8225 to verify the authenticity of such a request. 

- CNA/ir

- wong chee tat :)

Monday, June 24, 2013

Server settings for email for android phones

Server settings for email for android phones

1) Enter domain\username
2) Enter password. This could be the same as your windows login password
3) Enter mail server (mail.something.com or similar)
4) Check Use secure connection (SSL)
5) Accept all SSL certificates

Select Done

It will take some time to verify with the mail server and you will see emails downloading to your phone.


- wong chee tat :)

Saturday, April 20, 2013

Yahoo China to end email service: media

Yahoo China to end email service: media

    POSTED: 19 Apr 2013 7:48 PM
    UPDATED: 19 Apr 2013 10:45 PM
 
Yahoo's China arm will shut down its email service later this year, state media reported on Friday, in a move illustrating the brand's diminishing profile in the country.

BEIJING: Yahoo's China arm will shut down its email service later this year, state media reported Friday, illustrating the brand's diminishing profile in the country.

China Yahoo! announced it will close its email service by August 19, a move the China Daily said will leave it with just its web portal business.

Users of the service were informed that they must register with AliCloud, a unit of Chinese e-commerce giant Alibaba, to prevent emails and other information from being deleted when Yahoo's mail service stops.

China Yahoo! has been operated by Alibaba since 2005, the paper said.

The US Internet giant Yahoo! has come under criticism in the past over its business in China, with executives apologising in 2007 for providing evidence that Chinese authorities used to convict government critics.

The company said it was legally obliged to divulge information about its users to the Chinese government but that it was unaware it would be used to convict dissidents.

The end of the service will affect millions of users, the paper quoted Alibaba public relations official Zhang Jianhua as saying, though he did not have a total figure.

The China Daily quoted Zhang as saying the move was because "we are not sure how long we can provide the email service under Yahoo's current technological structure".

In September, Alibaba Group Holding Limited announced that it has bought back billions of dollars worth of stock from Yahoo!, by completing an initial repurchase of shares from the US company and other transactions valued at approximately US$7.6 billion.

The move partly fulfilled a previous deal that Yahoo! would sell back its 40 percent stake in Alibaba.

In a statement to AFP, a spokesperson for China Yahoo! confirmed that the email service would be suspended and said: "We will offer several options to our users to make this transition as smooth as possible, and China Yahoo! users will have four months time to migrate their accounts."

The statement said that the migration process had started on Thursday.

Users of China's Twitter-like microblogs expressed anger at the news.

A post under the name "Lisa's paw" said: "How can they do this? All of sudden Yahoo mail can't be logged onto and everything was moved to AliCloud. Did you ask for users' opinions?"

- AFP/fl

- wong chee tat :)

Thursday, February 28, 2013

Recall or replace an email message that you sent

The recall feature in Microsoft Outlook tries to stop delivery and, optionally, replace an email message that you have already sent to another Microsoft Exchange Server user within your organization. Message recall is available after you click Send and then realize that you forgot to attach a file, include information in the message, or want to revise what was originally sent. You can’t recall messages sent to email addresses outside your organization.
 Note    A Microsoft Exchange Server account is required.
In this article

Recall a message

To recall a message without sending a revised message, do the following:
  1. In Mail, in the Navigation Pane, click Sent Items.
  2. Open the message that you want to recall.
  3. On the Message tab, in the Move group, click Actions, and then click Recall This Message.
  4. Click Delete unread copies of this message.
 Note    If you don’t see the Message tab, make sure that you have opened a sent message as described in steps 1 and 2.
Recall This Message command on the ribbon
 Note    If you are sending the message to many people, you may want to clear the Tell me if recall succeeds or fails for each recipient check box.
Top of Page Top of Page

Recall and replace a message

In addition to trying to recall a message, you can send a replacement message. For example, if you forgot to include an attachment, you can try to recall the message, and then send a replacement message that has the attachment. The original message is removed from the mailboxes of the recipients who have not yet opened it, and then is replaced with the updated message.
To recall a message and then send a revised message, do the following:
  1. In Mail, in the Navigation Pane, click Sent Items.
  2. Open the message that you want to recall and replace.
  3. On the Message tab, in the Move group, click Actions, and then click Recall This Message.
Recall This Message command on the ribbon
  1. Click Delete unread copies and replace with a new message.
 Note    If you are sending the message to many people, you may want to clear the Tell me if recall succeeds or fails for each recipient check box.
  1. Click OK, and then update the new message. You can also remove or add file attachments.
  2. Click Send.
Top of Page Top of Page

Scenarios that affect recall success

The success or failure of a message recall depends on the recipients' settings in Outlook. In the following table, five scenarios are presented:
  • Four scenarios that explain what happens when message recall is tried in various situations
  • One scenario that describes what happens when the recall of a message that was sent to a Microsoft Exchange public folder is tried
Action Result
You send a message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, under Tracking, the Automatically process requests and responses to meeting requests and polls check box is selected.
 Note   To view this setting, click the File tab. Under Outlook, click Options, click Mail, and then scroll to the Tracking section.
Both the original message and the recall message are received in the recipient's Inbox.
Assuming the original message has not been read, the original message is deleted and the recipient is informed that you, the sender, deleted the message from his or her mailbox.
 Note    If the original message is marked as read (viewing in the Reading Pane is not reading in this scenario) when the recall message is processed, the recipient is informed that you, the sender, want to delete the message. However, the message remains in the recipient's Outlook folder.
You send a message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, under Tracking, the Automatically process requests and responses to meeting requests and polls check box is not selected.
 Note   To view this setting, click the File tab. Under Outlook, click Options, click Mail, and then scroll to the Tracking section.
Both the original message and the recall message are received in the recipient's Inbox.
On the recipient's computer, one of the following results occurs:
  • If the recipient opens the recall message first, the original message is deleted, and the recipient is informed that you, the sender, have deleted the message from their mailbox.
  • If the recipient opens the original message first, the recall fails, and both the original and recall messages are available.
 Note    If the original message is marked as read (viewing in the Reading Pane is not reading in this scenario) when the recall message is processed, the recipient is informed that you, the sender, want to delete the message. However, the message remains in the recipient's Outlook folder.
You send a message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, either by rule or by action of the recipient, the original message is moved out of the Inbox to another folder and the recall message remains in the Inbox (or it is moved to another folder also).
If the recall message and the original message exist in separate folders, the recipient receives a message that indicates a recall attempt failed. This occurs regardless of the Outlook configurations and the read status of the message.
The original message and the new message are both available to the recipient.
You send a message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, either by rule or by action of the recipient, both messages are moved to the same folder. This results in behavior similar to what occurs when Outlook is not configured to automatically process messages.
On the recipient's computer, one of the following results occurs:
  • If the recipient opens the recall message first, the original message is deleted, and the recipient is informed that you, the sender, deleted the message from his or her mailbox.
  • If the recipient opens the original message first, the recall fails, and both the old and new messages are available.
You send a message to a public folder. You recall the original message and replace it with a new one. One of the following results occurs:
  • If the recipient who reads the recall message has read access to all the items in the public folder but did not read the original message, the recall succeeds, and only the new message remains. You, the sender, receive a message that indicates the recall succeeded.
  • If the recipient has already marked the original message as read, he or she is informed that the recall failed, and only the recall message is deleted.
If a user who has any other public folder rights opens the recall message, the recall fails, and the user receives a message that states the recall failed. Both the old and new messages remain in the public folder.
 Notes 
  • If the recipient reads the original message and then marks it as unread, it is considered never read and recall is successful.
  • In the public folder, it is the reader's rights, not the sender's, that determine the success or failure of the recall.
- wong chee tat :)

Saturday, November 10, 2012

Tuesday, November 6, 2012

Microsoft Exchange Server 2013 is Now Available

Microsoft Exchange Server 2013 is Now Available
ServerAndToolsBlogsTeam
2 Nov 2012 2:38 PM

Three weeks ago the Exchange Server team announced the RTM of Exchange Server 2013 on their team blog.  Since that time the team has been working diligently to get the product ready for general availability via the various channels.  We’re happy to say Exchange Server 2013 is now generally available.

Microsoft Exchange Server 2013 enables you to maintain control, increase user productivity, and keep your organization safe:

    Remain in control, online and on-premises - Exchange Server 2013 enables you to tailor your solution based on your unique needs and ensures your communications are always available while you remain in control, on your own terms - online, on-premises, or a hybrid of the two.

    Do more, on any device - Exchange Server 2013 helps your users be more productive by helping them manage increasing volumes of communications across multiple devices and work together more effectively as teams.
    Keep your organization safe - Exchange Server 2013 keeps your organization safe by enabling you to protect business communications and sensitive information to meet internal and regulatory compliance requirements.

You can go get the download off the evaluation center at http://technet.microsoft.com/hh973395.  See the product information at http://microsoft.com/exchange.

Technical information for all of the Exchange Server products can be found at http://technet.microsoft.com/exchange.  For those of you with TechNet or MSDN subscriptions, head on over to the subscriber download center and grab the DVD .ISO file.



- wong chee tat :)

Friday, October 12, 2012

Saturday, February 4, 2012

Color-coding mail to help identify senders

- wong chee tat :)

Tuesday, May 10, 2011

Error 'Insufficient frame/frameset handles' when working in mail file

Error 'Insufficient frame/frameset handles' when working in mail file

On the Lotus Notes® client, you receive the following error message "Insufficient frame/frameset handles" when creating or opening a memo, reply or calendar entry. Why does this occur?

The common cause for this error is having too many windows open. Typically this issue is not observed unless there are more than 30 to 40 windows open.

If this error occurs and 20 or more windows are open, then try closing between 5 to 10 of the windows and see if the issue is resolved. If so, Notes is working as designed.

If the issue occurs when there is not more than 20 to 30 windows open, then this is not the expected behavior. First try exiting Notes and restarting Windows, and then see if the issue is resolved.

If the issue continues then you may want to try renaming the Notes data files: cache.ndk, bookmark.nsf, and desktop6.ndk. You could try this by individual file at first (using the order given) to see whether any of these files was having an affect on the issue.


- wong chee tat :)

Tuesday, April 12, 2011

Lotus Notes 8.5: Links & Hotspots

In Lotus Notes 8.5 client, we can create a link to point to another location.

It is simple but it took me some time to figure it out. A quick search bring us to the following:

Here are the steps to create the same.

1) Enter the text you want to appear as the hyperlink in the mail message (eg: Google)

2) Select the text and click on Create –>; Hotspot ->; Link hotspot

3) Enter the desired URL in the Value text box. (eg: www.google.com) and close it

4) It will add the hotspot and select ‘Show border around hotspot’ to display a background highlighting around the link. Otherwise apply underline (press Ctl + U)

5) Send the mail to the recipients

Note: The link will not be active until you send the mail. If you click on the hotspot before sending it, it may not work.

And another link:


One of the new user-friendly features of the IBM Lotus Notes 8.5.1 client is the new menu command of "Create >> Hyperlink"

New create hyperlink menu option in Lotus Notes 8.5.1


This should make things much easier for end users who want to create hyperlinks in a Notes mail message or in vanilla, frameless Notes client based applications.

But for users and developers who create web-based applications there is an important feature missing if you use this menu option.
What is missing? The ability to set a target frame like you can using "Create >> Hotspot >> Link Hotspot":

Create hotspot link menu


This is not to say the end user cannot fix this problem. They can just right click on the linked text and select "Hotspot Properties":

This does not bring them back to the dialog box that displayed when they created the hyperlink, but to the hotspot properties dialog box, where they can enter the target window ("_blank" for a new browser window):

hotspot link dialog box


The downside to this is that users may get confused by the different dialog boxes, and most probably do not know the syntax to set a target window. And it is not just the Notes client where you will see this. There are many instances of Web 2.0 editors where you cannot set the target when you create the hyperlink, including Google Blogger:

Google blogger link interface


In an ideal world, what should happen with this new "Create Hyperlink" dialog box? There should be a single checkbox with a label of "Open link in new browser window", along with an action pop-up message:

Google blogger link interface


There is something else to point out as well, something that will require additional user education. If you click on some text that has a hotspot created, the menu system ads a "Hotspot" entry, and the option to remove the hotspot:

hotspot link menu


But if you created the link using the "Create Hyperlink" menu, you do not get a "Hyperlink" menu item. You get the same "Hotspot" menu item:

hotspot link menu


So as you work with your users in setting up Lotus Notes 8.5.1, be sure to keep these differences in mind.




By the way, it worked in Lotus Notes 8.5.2 too.




 - wong chee tat :)













Sunday, February 6, 2011

(Feb 2011) Potential security vulnerabilities in Lotus Notes & Domino

(Feb 2011) Potential security vulnerabilities in Lotus Notes & Domino
 Flash (Alert)
Abstract
TippingPoint's Zero Day Initiative (ZDI) contacted IBM Lotus to report nine potential buffer overflow vulnerabilities in Lotus Notes and Domino; for four of which IBM Lotus has fixes, two of which IBM Lotus continues to investigate a fix, and three of which IBM Lotus cannot reproduce and is pursuing additional information.

Content

Most of these attacks represent denial of service attacks by buffer overflow. To exploit these vulnerabilities, an attacker would need to send maliciously malformed messages to the Lotus Domino server over a variety of protocols as indicated below. However, in specific situations, there exists the possibility to execute arbitrary code. In the case of ZDI-CAN-647 (SPR# PRAD82YJW2), malicious users could supply damaged cai::URIs to facilitate execution of arbitrary code in Notes. Refer to the table for more information on each, including the SPR number for tracking purposes and, where applicable, fix availability.

For four of these nine, namely ZDI-CAN-373, ZDI-CAN-647, ZDI-CAN-758, ZDI-CAN-759, IBM Lotus has fixes. For two of these, ZDI-CAN-375 and ZDI-CAN-927, IBM has confirmed the issue and continues to pursue appropriate fixes. IBM Lotus is currently unable to reproduce the remaining three exploits based on the information provided by TippingPoint's ZDI.


TippingPoint Reference #
Description
IBM Lotus SPR #
Status
ZDI-CAN-375Domino MIME stack overflowKLYH889M8HConfirmed. Investigating fix.
ZDI-CAN-647Notes cai URI Handler remote code execution vulnerabilityPRAD82YJW2Confirmed. Fixed in 8.0.2 FP6, 8.5.1 FP5, 8.5.2 and later releases
ZDI-CAN-373Notes iCal stack overflowKLYH87LL23Confirmed. Fixed in 8.5.3
ZDI-CAN-758Domino DIIOP remote code execution vulnerabilityKLYH87LML7Confirmed. Fixed in 8.5.3
ZDI-CAN-759Domino DIIOP remote code execution vulnerabilityKLYH87LM4SConfirmed. Fixed in 8.5.3
ZDI-CAN-927Domino Remote Console authentication bypass remote code execution vulnerabilityPRAD89WGRSConfirmed. Unsuppported configuration with workaround available.
ZDI-CAN-372Domino Router stack overflowKLYH87LKREUnconfirmed. Unable to reproduce. Need more information.
ZDI-CAN-374Domino IMAP and POP3 stack overflowKLYH87LLVJUnconfirmed. Unable to reproduce. Need more information.
ZDI-CAN-779Domino LDAP bind request remote code execution vulnerabilityKLYH87LMVXUnconfirmed. Unable to reproduce. Need more information.


IBM targets 2Q2011 for release of Lotus Notes and Domino 8.5.3. You can track progress at the Notes/Domino Update Status page.

At time of publication, there currently are no known active exploits of these issues. However, if you encounter any of the unconfirmed issues, contact IBM Support with reproducible steps, referencing the related SPR number.

For additional information on these issues, you can access the TippingPoint's ZDI advisories at the following link: http://www.zerodayinitiative.com/advisories


Workarounds:

For ZDI-CAN-927 (SPR# PRAD89WGRS), Domino does not support use of UNC paths for usage with Remote Console. As a workaround, you should specify absolute paths.

For all others, there are currently no known workarounds to avoid these issues.


CVSS scoring for fixed & confirmed issues

The following CVSS scores are based on testing results observed by IBM*.

SPR KLYH87LL23 - Lotus Notes ICAL Stack Overflow

Security Rating using Common Vulnerability Scoring System (CVSS) v2
CVSS Base Score: < 7.1>
---- Impact Subscore: < 6.9>
---- Exploitability Subscore: < 8.6>
CVSS Temporal Score: < 5.6 >
CVSS Environmental Score: < Undefined* >
Overall CVSS Score: < 5.6>
Base Score Metrics:
  • Related exploit range/Attack Vector: < Network >
  • Access Complexity: < Medium >
  • Authentication < None >
  • Confidentiality Impact: < None >
  • Integrity Impact: < None >
  • Availability Impact: < Complete >
Temporal Score Metrics:
  • Exploitability: < Proof of Concept Code >
  • Remediation Level: < Official Fix >
  • Report Confidence: < Confirmed >
References:



SPR PRAD82YJW2 - Lotus Notes cai URI Handler Remote Code Execution

Security Rating using Common Vulnerability Scoring System (CVSS) v2
CVSS Base Score: < 7.1>
---- Impact Subscore: < 6.9>
---- Exploitability Subscore: < 8.6>
CVSS Temporal Score: < 5.6 >
CVSS Environmental Score: < Undefined* >
Overall CVSS Score: < 5.6>
Base Score Metrics:
  • Related exploit range/Attack Vector: < Network >
  • Access Complexity: < Medium >
  • Authentication < None >
  • Confidentiality Impact: < None >
  • Integrity Impact: < None >
  • Availability Impact: < Complete >
Temporal Score Metrics:
  • Exploitability: < Proof of Concept Code >
  • Remediation Level: < Official Fix >
  • Report Confidence: < Confirmed >
References:



SPR KLYH87LML7 - Lotus Domino DIIOP Remote Code Execution

Security Rating using Common Vulnerability Scoring System (CVSS) v2
CVSS Base Score: < 6.9>
---- Impact Subscore: < 10>
CVSS Temporal Score: < 3.4 >
CVSS Environmental Score: < Undefined* >
Overall CVSS Score: < 5.4>
Base Score Metrics:
  • Related exploit range/Attack Vector: < Local >
  • Access Complexity: < Medium >
  • Authentication < None >
  • Confidentiality Impact: < Complete>
  • Integrity Impact: < Complete >
  • Availability Impact: < Complete >
Temporal Score Metrics:
  • Exploitability: < Proof of Concept Code >
  • Remediation Level: < Official Fix >
  • Report Confidence: < Confirmed >
References:



SPR KLYH889MH8 - Lotus Domino MIME Stack Overflow

Security Rating using Common Vulnerability Scoring System (CVSS) v2
CVSS Base Score: < 7.1>
---- Impact Subscore: < 6.9>
CVSS Temporal Score: < 6.1>
CVSS Environmental Score: < Undefined* >
Overall CVSS Score: < 6.1>
Base Score Metrics:
  • Related exploit range/Attack Vector: < Network >
  • Access Complexity: < Medium >
  • Authentication < None >
  • Confidentiality Impact: < None>
  • Integrity Impact: < None >
  • Availability Impact: < Complete >
Temporal Score Metrics:
  • Exploitability: < Proof of Concept Code >
  • Remediation Level: < Unavailable>
  • Report Confidence: < Confirmed >
References:

*The CVSS Environment Score is customer environment-specific and will ultimately impact the Overall CVSS score. Customers can evaluate the impact of this vulnerability in their environments by accessing the referenced links.



- wong chee tat :)

Sunday, January 30, 2011

Sunday, January 2, 2011

Hotmail Users Report Blank Inboxes

Hotmail Users Report Blank Inboxes

By: David Murphy
  • 01.01.2011
The ring of the new year has come with an unpleasant surprise for some users of Microsoft's Hotmail service. According to multiple postings on Microsoft's official support forum for Windows Live, a number of users are reporting that their entire Hotmail accounts have been completely deleted without warning.

However, it's not as if Microsoft has—for whatever reason—pulled the plug on the accounts themselves. Users can still log in sans issue. However, they arrive at empty inboxes: No custom folders, no messages in "Sent" or "Deleted," nothing. As one might expect, the abruptness (and unexpectedness) of the purge has left some of Hotmail's long-time users a bit in the dark.

"I have a Hotmail account since I remember myself on the web (1990's)," writes user Yair Gil. "I logged into it on 31th December 2010 at around 06:30hrs. Got an error message and a 'new' hotmail account with a first system welcome message. All previous mails in the inbox are gone and all the folders created are also not there."

There's been no indication as to how many Hotmail users are affected by whatever it is that's going on over on Microsoft's end. Reports of the email outage, for lack of a better term, have been surfacing on Microsoft's help boards since early this past week. According to moderators' responses, Microsoft's product team is allegedly aware of the issue and is actively looking into whatever it might be.

But that's about as specific as Microsoft has been with its explanation as to why inboxes—in their entirety—are being wiped out. As well, there's been no indication as to what—if anything—Microsoft will be able to recover. As many of those on Microsoft's Solution Center team are quick to point out, message recovery on Microsoft's end, post-deletion, doesn't always work as expected. A special exception might be made for widespread issues but, again, that's mere speculation at this point.

Normally, a user's Hotmail account goes up for automatic deletion if it isn't touched for a period of 120 days or within the first 10 days of the account's activation. At that point, all messages, contacts, and folders get tossed, but the email account itself remains eligible for reactivation for a period of 90 extra days—or 210 days in total.

We'll keep tabs on this story and update with any information from Microsoft's end as soon as its available.



- wong chee tat :)