MailBee.NET Objects 7.2

SendMailJobCollection Class

Represents a collection of assigned tasks of sending e-mails.

For a list of all members of this type, see SendMailJobCollection Members.

System.Object
   MailBee.SmtpMail.SendMailJobCollection

[DefaultMember(MemberName="Item")]
public class SendMailJobCollection : ICollection, IEnumerable

Thread Safety

Public static (Shared in Visual Basic) members of this type are safe for multithreaded operations. Instance members are not guaranteed to be thread-safe.

Remarks

In MailBee, instances of this class contain lists of mail messages or mail merge tasks which will be (or already have been) processed.

JobsPending, JobsRunning, JobsSuccessful, and JobsFailed properties of Smtp class have SendMailJobCollection type.

JobsPending contains jobs to be processed, JobsRunning - currently being processed, JobsSuccessful and JobsFailed - finished jobs.

During processing, jobs migrate between the collections (i.e. the job which had originally been placed into JobsPending moves into JobsRunning when processing starts, and ends up in JobsSuccessful or JobsFailed).

However, mail merge jobs may spawn additional jobs. I.e. if a mail merge job of processing 10 data table rows goes into processing, it resides in JobsPending for a while (and the number of rows yet to be processed sequentially decrements to 9, 8, etc). At the same time, rows which are being processed are converted into SendMailJob objects representing tasks to process a single data row as mail merge. Thus, usually mail merge of 10 data rows (a single job) finally ends up in 10 SendMailJob objects in JobsSuccessful or JobsFailed collections. To change this behavior, create mail merge jobs using AddJob overload.

Requirements

Namespace: MailBee.SmtpMail

Assembly: MailBee.NET (in MailBee.NET.dll)

See Also

SendMailJobCollection Members | MailBee.SmtpMail Namespace | SendMailJob