header

Type Members

1. case class Auto-Submitted(tpe: Auto-Submitted.AutoType.Value, parameters: Option[Seq[String]]) extends DefaultEmailHeaderField with Product with Serializable

   

2. case class Comments(comments: String) extends DefaultEmailHeaderField with Product with Serializable

   

   RFC 5322 3.6.5

   RFC 5322 3.6.5

   The informational fields are all optional. The "Subject:" and "Comments:" fields are unstructured fields as defined in section 2.2.1, and therefore may contain text or folding white space.

3. case class Content-Description(description: String) extends DefaultEmailHeaderField with ContentHeaderField with Product with Serializable

   

4. case class Content-Disposition(disposition: ContentDisposition) extends DefaultEmailHeaderField with ContentHeaderField with Product with Serializable

   

5. case class Content-ID(id: String) extends DefaultEmailHeaderField with ContentHeaderField with Product with Serializable

   

6. case class Content-Transfer-Encoding(value: TransferEncoding) extends ContentHeaderField with DefaultEmailHeaderField with Product with Serializable

   

7. case class Content-Type(tpe: ContentType) extends ContentHeaderField with DefaultEmailHeaderField with Product with Serializable

   

8. trait ContentHeaderDescription[H <: ContentHeaderField] extends HeaderDescription[H]

   

9. trait ContentHeaderField extends EmailHeaderField

   

   denotes header fields that may be used with MIME parts *

10. abstract class DefaultContentHeaderFieldDescription[H <: ContentHeaderField] extends DefaultHeaderDescription[H] with ContentHeaderDescription[H]

    

11. trait DefaultEmailHeaderField extends EmailHeaderField

    

12. abstract class DefaultHeaderDescription[H <: EmailHeaderField] extends HeaderDescription[H]

    

13. case class Destination(tpe: DestinationType.Value, email: EmailAddress, others: List[EmailAddress]) extends EmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.3.

    RFC 5322 3.6.3.

    The destination fields of a message consist of three possible fields, each of the same form: the field name, which is either "To", "Cc", or "Bcc", followed by a comma-separated list of one or more addresses

    tpe

    Type of the destination (To, Cc, Bcc)

    email

    Destination address

    others

    Other Email addresses

14. trait EmailHeaderField extends AnyRef

    

15. case class From(email: EmailAddress, others: List[EmailAddress]) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.2.

    RFC 5322 3.6.2.

    The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message.

    email

    Email of the person

    others

    List of other autors of this email.

16. case class GenericField(name: String, value: String) extends EmailHeaderField with ContentHeaderField with Product with Serializable

    

    Any field that is not parsed to EmailHeaderFiled types

17. trait HeaderDescription[H <: EmailHeaderField] extends AnyRef

    

    description of header, including its codec *

18. case class In-Reply-To(msgId: @@[String, Message-ID], others: List[@@[String, Message-ID]]) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.4

    RFC 5322 3.6.4

    The "In-Reply-To:" and "References:" fields are used when creating a reply to a message. They hold the message identifier of the original message and the message identifiers of other messages (for example, in the case of a reply to a message that was itself a reply). The "In-Reply-To:" field may be used to identify the message (or messages) to which the new message is a reply, while the "References:" field may be used to identify a "thread" of conversation.

    msgId

    Id of the message

    others

    Id of other messages

19. case class Keywords(keyword: String, other: List[String]) extends DefaultEmailHeaderField with Product with Serializable

    

    Created by pach on 17/10/17.

20. case class MIME-Version(version: String) extends DefaultEmailHeaderField with Product with Serializable

    

21. case class Message-ID(id: @@[String, Message-ID]) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.4

    RFC 5322 3.6.4

    The "Message-ID:" field provides a unique message identifier that refers to a particular version of a particular message. The uniqueness of the message identifier is guaranteed by the host that generates it (see below). This message identifier is intended to be machine readable and not necessarily meaningful to humans. A message identifier pertains to exactly one version of a particular message; subsequent revisions to the message each receive new message identifiers.

22. case class NonRFC(name: String, value: String) extends EmailHeaderField with ContentHeaderField with Product with Serializable

    

    Value of known header is not RFC compliant Only for decoding of incoming emails.

23. case class OriginationDate(date: ZonedDateTime) extends EmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.1

    RFC 5322 3.6.1

    The origination date specifies the date and time at which the creator of the message indicated that the message was complete and ready to enter the mail delivery system.

24. case class Received(token: String, at: ZonedDateTime) extends DefaultEmailHeaderField with Product with Serializable

    

    Created by pach on 17/10/17.

25. case class References(msgId: @@[String, Message-ID], others: List[@@[String, Message-ID]]) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.4

    RFC 5322 3.6.4

    The "In-Reply-To:" and "References:" fields are used when creating a reply to a message. They hold the message identifier of the original message and the message identifiers of other messages (for example, in the case of a reply to a message that was itself a reply). The "In-Reply-To:" field may be used to identify the message (or messages) to which the new message is a reply, while the "References:" field may be used to identify a "thread" of conversation.

    msgId

    Id of the message

    others

    Id of other messages

26. case class Resent-Date(date: ZonedDateTime) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.6:

    RFC 5322 3.6.6:

    Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.

    For instance, the "Resent-Date:" field corresponds to the "Date:" field

27. case class Resent-From(email: EmailAddress, others: List[EmailAddress]) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.6:

    RFC 5322 3.6.6:

    Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.

    For instance, the "Resent-From:" field corresponds to the "From:" field

28. case class Resent-Message-ID(id: @@[String, Message-ID]) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.6:

    RFC 5322 3.6.6:

    Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.

    For instance, the "Resent-Message-ID:" field corresponds to the "Message-ID:" field

29. case class Resent-Sender(sender: EmailAddress) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.6:

    RFC 5322 3.6.6:

    Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.

    For instance, the "Resent-Sender:" field corresponds to the "Sender:" field

30. case class ResentDestination(tpe: DestinationType.Value, email: EmailAddress, others: List[EmailAddress]) extends EmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.6:

    RFC 5322 3.6.6:

    Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system. A separate set of resent fields SHOULD be added each time this is done.

    For instance, the "Resent-To:" field corresponds to the "To:" field

    tpe

    Type of the destination (To, Cc, Bcc)

    email

    Destination address

    others

    Other Email addresses

31. case class Return-Path(path: String) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.7:

    RFC 5322 3.6.7:

    The "Return-Path:" header field contains a pair of angle brackets that enclose an optional addr-spec.

32. case class Sender(sender: EmailAddress) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.2:

    RFC 5322 3.6.2:

    if a secretary were to send a message for another person, the mailbox of the secretary would appear in the "Sender:" field and the mailbox of the actual author would appear in the "From:" field.

33. case class Subject(subject: String) extends DefaultEmailHeaderField with Product with Serializable

    

    RFC 5322 3.6.5

    RFC 5322 3.6.5

    The informational fields are all optional. The "Subject:" and "Comments:" fields are unstructured fields as defined in section 2.2.1, and therefore may contain text or folding white space.