Archived:E-mail fetch limit in e-mail service settings on S60 2nd Edition (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): S60 2nd Edition FP2

---

Article

Created: User:Technical writer 1 (25 Aug 2005)

Last edited: hamishwillee (19 Jun 2012)

Overview

The SetPopulationLimitL method should be used instead of SetMaxEmailSize.

Description

When fetching new e-mail messages, the MaxEmailSize setting is not used to determine the size limit, but a value that has been set to the e-mail service settings by the SetPopulationLimitL method. This method is public but it has not been documented in the S60 2nd Edition, FP2 API reference.

How to reproduce

The problem arises only when programmatically creating a new e-mail service (and settings, e.g. by CImPop3Settings). Any e-mail maximum fetch size that has been set by the method CImPop3Settings::SetMaxEmailSize() will not be taken into account when the fetch is run.

Solution

Instead of SetMaxEmailSize use
CImPop3Settings::SetPopulationLimitL(const TInt32 aPopulationLimit).
The parameter aPopulationLimit could be defined as an enumeration as follows:
enum TEmailFetchedParts
{
EHeadersOnly = -2,
EFullBody = -1,
EUserDefinedKB = 0
};
So everything greater than (and equal to) EUserDefinedKB will set the fetch limit to a manual setting.