Class AppendedMailCopy

Namespace

MailFathom.Domain.Delivery.Filing

Assembly

MailFathom.Domain.dll

What a mail server said about the copy it accepted into a folder.

public sealed record AppendedMailCopy : IEquatable<AppendedMailCopy>

Inheritance

object

AppendedMailCopy

Implements

IEquatable<AppendedMailCopy>

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Remarks

The two answers are both here because the join uses whichever it can get. RFC 4315's APPENDUID names the new occurrence exactly and is what a server advertising UIDPLUS returns; a server that advertises none accepts the same message and says nothing about where it went, and the identity in the message's own headers is then all there is to recognize it by later.

The identity is read off the bytes that were appended rather than assumed from what was composed, so what is recorded is what a mail server will report back. Nothing else about the message crosses this boundary.

Constructors

AppendedMailCopy(RemoteEmailPlacement, string?)

What a mail server said about the copy it accepted into a folder.

Properties

InternetMessageId

The Message-ID the appended bytes carry, or null when they carry none.

Placement

Where the folder put the copy, when the server named it.