Last modified by Thomas Mortagne on 2020/01/28

<
From version < 17.2 >
edited by Vincent Massol
on 2015/09/24
To version < 17.3 >
edited by Vincent Massol
on 2015/09/24
>
Change comment: typo

Summary

Details

Page properties
Content
... ... @@ -288,7 +288,7 @@
288 288  
289 289  There is now more than one message state representing an error, therefore, the MailStatusResult interface has been extended with a ###getAllError()## method to retrieve all message status in error. Moreover, the ###getTotalMailCount()# may represent a partial total in case of failure of the prepare phase. In that case, it represents the number of mails sent to the send phase. As a consequence, ###isProcessed()# and ###waitTillProcess()# now considerer the batch to be processed when all successfully prepared mail has been sent, or failed to be prepared or sent.##
290 290  
291 -Please review the [[new way to check for errors>>extensions:Extension.Mail Sender API||anchor="HCheckforErrors"]]].
291 +Please review the [[new way to check for errors>>extensions:Extension.Mail Sender API||anchor="HCheckforErrors"]].
292 292  
293 293  The mail API is now tracking individual message based on the standard Message-ID headers, which made it fully compliant with RFC-822 WRT the mail identification. Caller that want to specify custom Message-ID may do so by extending MimeMessage to preserve the Message-ID of the message. Caller is also responsible to ensure that different messages are identified by unique message identifier.
294 294  

Get Connected